It does appear that the new 1.6 OZW Daemon does check in with the device database on start up and will pull missing configuration files. If you check the logs of the integration you will see it attempting to pull missing records from http://download.db.openzwave.com/. So theoretically once it shows up in the device database on openzwave.com, it should be pulled into your config directory after a restart. If you don’t want to wait, you can locate your core_zwave data directory on the host machine and pull it manually as the Inovelli Support page (listed above) describes. The location of the core_zwave data will depend on your installation method (This can’t be done through either SSH addon, and isn’t support by Home Assistant so use caution.).
I think you need to unpair and repair your device for it to pull the correct information. I don’t think it updates otherwise. I got mine set up but I followed the work around instructions before the device was added.
This worked for me, thanks! For others on 1.4, if it wasn’t clear find the proper <Node> block in your zwcfg_****.xml file to make the suggested edits. I searched my file for “LZW45” to find that block easily.
Result is an adjustable color and brightness light entity along with the other sensor and zwave entities I had prior.
@nathanfiscus so I plugged keyboard into my HA blue device. I was able to CD to the inovelli config folder. When I tried your sudo curl command from the other thread, I’m getting a /bin/ash: sudo : not found. Or trying the command with sudo, i get curl not found
The Blue device runs HA OS, which is a minimal OS that only has what it needs to run HA and doesn’t include the ability to run to sudo or curl.
One way may work for you is to install the SSH add-on in the HA store, and use something like WinSCP to edit the files via SSH.
So im in a catch 22 here, i cant get access to root system in SSH and I cant do the commands I need in root. I dont get why the openzwave database takes so long to update?!?!?
You can use the SSH addon to download the file and then use the host system to move the file to the correct location. Then modify the manufacturer_specific.xml in the host system.
This is for just one item, you technically could clone the entire openzwave config xml and just move and overwrite the current config. Then you wouldn’t have to modify the manufacturer_specific.xml file. You can also use vi to edit the manufacturer file, but you would probably need to read up on the keyboard shortcuts in order to update without the sed command.
Another option would be to setup SSH with the host system and then use scp to copy the file from another machine.
That sed command took me forever to type out and it had some error in it. I just ended up copying the manufactuer_specific.xml from the git and moving it on the host system.
Restarting Z wave now and will try to refresh the node…
@nathanfiscus for future reference, could you tell me what I would type in the curl command to pull the entire OZW config folder into my home assistant config folder? Would it be the following?
It would be better to just use git to clone the repo like in the support article supplied by Inovelli and then mv to move the entire config folder over the ozw config.