GetSensorUnit - Unknown SensorType 1 about addon-zwave2mqtt

[Munsio]

I had something similar and solved it by using the following path as "Path to database" in the config /usr/etc/openzwave

I think the problem occures cause zwave2Mqtt expects the openzwave device db under /etc/openzwave but in the docker container it gets moved to another path.

[cd334]

I tried out. A little bit better I see the unit of the value, but the name still unknown.

I think tis log entrys related to this:
2020-03-06 14:08:44.937 Warning, Localization::ReadXMLVIDHelp: Error in /opt/store/ozwcache_0xfb630523.xml at line 74 - No Help Entry for CommandClass 114, ValueID: 1 (-1): (null) (Lang: )
2020-03-06 14:08:44.938 Warning, Localization::ReadXMLVIDHelp: Error in /opt/store/ozwcache_0xfb630523.xml at line 77 - No Help Entry for CommandClass 114, ValueID: 2 (-1): (null) (Lang: )
2020-03-06 14:08:44.940 Warning, Localization::ReadXMLVIDHelp: Error in /opt/store/ozwcache_0xfb630523.xml at line 80 - No Help Entry for CommandClass 114, ValueID: 3 (-1): (null) (Lang: )
2020-03-06 14:08:44.941 Warning, Localization::ReadXMLVIDHelp: Error in /opt/store/ozwcache_0xfb630523.xml at line 83 - No Help Entry for CommandClass 114, ValueID: 4 (-1): (null) (Lang: )

[Munsio]

Did you try to run "refresh node" on one of them?

[cd334]

Did you try to run "refresh node" on one of them?

I tried out, and it worked. After the "refresh node"my battery devices were marked as "dead" but after "send NIF" they are back to normal state.

[addons-assistant]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[addons-assistant]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.