Nothing is configured in those files in regards to this. I made a guide on getting Inovelli devices in HA for Zwave 1.4 here. OpenZwave (Beta) and Zwave JS don’t have this issue because the config files are included in those integrations.
Followed your guide to a T (which included editing the configuration.yaml file) and it continues to pair the same way (Inovelli Unknown) and no configuration parameters available. If I delete the Zwave integration it will not load Zwave at all even though my configuration.yaml is configured (running HA .105.5.) This leads me to believe that at some point they gave all the power of zwave config to the integrations section of the HA GUI…
See the quote from this thread below. I’ve asked him directly what he modified but have yet to hear back. I tried adding the path to the same file but it must be getting put in the wrong spot because it makes no difference.
No… I’m running 105.5 and everything is working A-OK for me but I configure through configuration.yaml. The integrations page simply overrides whats in the configuration.yaml. It has no bearing on product names that appear in home assistant. If you are using the UI to configure, you have to move it to your configuration.yaml because I don’t believe the UI gives the ability to override the ozwave config directory.
You are missing a step in the guide or the guide is incomplete. I’m pretty sure the guide is complete, because I wrote it as I was building it… All in 105.5 btw.
Also, I only moved over the devices I own from ozw 1.6 to 1.4. What’s the model number of your dimmer?
@samduster Are you shutting down the network when editing the files (maybe even home assistant itself)? I don’t know the technical reason why, but the files will over-write themselves periodically so you can end up in a position where the edits are never actually saved.
@petro don’t think I saw a step included to shut down your instance before trying to edit the files.
1 Like
Good point. I definitely assumed people would know to do that. I’ll add it in. Thank you!
Hey all – going through the forum and cleaning it up a bit. Looks like multiple people solved this in various ways. I’m not that familiar with HA, but what’s the general consensus here? Did we get everything working?
Thanks again for everyone’s help and hopefully we can mark this one as officially solved and closed!
Yes, Eric. The issues were due to older Zwave implementation in Home Assistant. We’ve now got newer, more up-to-date Z-wave support in HA.
I marked the proper solution and edited the title to reflect the version of Zwave in home assistant. That probably should be enough to solve and close the thread.
OpenZwave (Beta) and Zwave JS don’t have this issue because the config files are included.
1 Like