I added a new Z-Wave plug-in module, and it’s oddly reporting as “GE Unknown: type=5052, id=3038”.
I searched the OpenZwave GitHub project, and i found an XML file for it (Link), but it was only committed 18 days ago. Is there a way to manually add that file to my build? Or is there anyway to tell if that config file was included in build 0.83?
One thing to be aware of is that Home Assistant uses a forked version of Open Zwave. I don’t know how often that is refreshed, but that could be the reason. You could check with Discord chat.
It’s possible you will have to hand-edit the zwcfg*.xml file and remove the existing entry for the node. If it’s already there, OZW usually will not refresh it with the new config values unless it has to. If you remove it, OZW will see it’s missing and query the device and read in the data from the new config file. In that case you would 1) stop HA, 2) edit zwcfg*.xml and remove the node entry, 3) start HA. I don’t know if there’s a way to force it to update the xml file otherwise.
The other way would be to remove (exclude) the node and add it again. Adding a node causes it go through a discovery process where OZW will check the XML files.
Or is there anyway to tell if that config file was included in build 0.83?
You can check if the files exist in the released version of HA by looking at the OZW config files included in the python_openzwave module for your python installation. For my virtualenv, the config files are located in /home/homeassistant/.pyenv/versions/3.6.3/envs/homeassistant-3.6.3/lib/python3.6/site-packages/python_openzwave/ozw_config. Hass.io will probably be somewhere else with a similar path.
Actually, after updating the config files and restarting HA, using the “Refresh Node” button in the z-wave control panel should trigger a refresh of the zwcfg*.xml file. The question is if HA will update its information.
I located the HASS.IO OZW config files, they are located at the following path when you run /bin/bash within the docker image “/usr/local/lib/python3.6/site-packages/python_openzwave/ozw_config/”.
I did not see the " 28169-plugin-switch.xml" file, so I copied it from the OpenZWave GitHub, and added the necessary entry to the “manufacturer_specific.xml” file.
I just checked again. It looks like my OZW conf changes weren’t persistent, and have been reverted after restarting the container. Now I need to look into making the changes persistent.
I recently had the same thing happen with my new Zooz switches, although I was still able to configure and use the switches in my Hassio installation. Aside from aesthetics, is there any need to worry about the “unknown” state if the switch still works?