Thanks for replying @cgarwood and @Fishwaldo. It’s great to see Z-Wave getting some love in Home Assistant.
I think that if you need any beta testers you have the right audience in this thread 
2 Likes
I’d be willing to test the migration if needed.
Thanks for words from the horses mouth. It brings us better clarity.
You mention that there’s likely to be advantages / disadvantages to both implementations.
Where can we bone up on this to help us decide ?
Given what you said about feature implementation, do you think that they will proceed somewhat evenly or will one be in advance of the other (from what you said I infer that mqtt ‘might’ be (initially at least) better supported) ?
My bias would be qt-openzwave, I think, but will hear arguments 
2 Likes
Hi Fishwaldo. Great initiative for supporting the HA community. This will be a win win for both open zwave and HA. Any idea on the timeline for this to happen.
1 Like
Really excited for this! Will this improve the UI responsiveness for dimmers? Right now, Lovelace doesn’t show the correct state when you turn on/off a dimmer. I haven’t found a reliable workaround yet.
Yes it all depends on how it’s implemented. The devs can do it in a way where it requires zero changes for users or in a way which requires a ton of changes for users… We will see which one they choose.
The goal is to implement the new z-wave component in a way that requires relatively few modifications for users of the stock zwave component, but there’s no plans to add a migration path for those using zwave2mqtt.
2 Likes
The challenge is up until recently the zwave specifications were not clear in how to report the “value” of a dimmer when its transitioning. Some vendors would send the “final” value (and GUI’s would “work”) while others send the “instant” value. (Which could be some value between the start value and end value). It’s these second group that cause this issue.
I’ve posted some guidelines for how this should be handled on the HA side here: https://github.com/cgarwood/python-openzwave-mqtt/issues/8#issuecomment-563307603
2 Likes
What month are we striving for with these changes? Will there be a ‘beta’ for us to test?
No clue on timing, but yes I’m planning to have beta pre-releases available as a custom component through HACS. Standard “may break everything” disclaimer will apply 
7 Likes
@cgarwood - I have the Docker container running and added your early code to my environment; but i am failing to activate the component, can you share some basic configuration steps?
Thanks
Damian
MQTT will need set up in Home Assistant & then add the zwave mqtt component from the Integrations page. Should just work after that (or spit some errors out into the logs)
Sorry - I should have updated this thread - i figure out my silliness a week back. I have the container and integrations running SOLID for a week, updated to the newest integration during the week, and i can turn on and off power sockets, and get some climate related data in.
this is already more stable than the alternatives! - I am looking forward to the climate platform support
1 Like
In the migration, would the entity_ids from the old zwave integration be able to transfer to the new one? I have around 40 zwave devices and having to manually delete the entity_ids from the entity registry from the old integration and then rename the new ones to match the old would be a very painstaking process.
Just watching this as I also want to know if we will need to reset and repair all Z-Wave devices to use the new integration.
Also, how does the new integration handle security enabled devices?
I understand it is currently in a testing state and not complete.
Thanks
The devices are linked to Z-Wave stick. So if you keep the security key the same, it should work out of the box - without repairing.
1 Like
The security key is specified by config in OpenZWave or random generated by HA. Are you sure the security key is on the stick /zwave controller?
I know paired devices are on the stick, but I thought OZW stored the security key elsewhere.
It is not, it’s in your configuration. In Home Assistant, that’ll be in configuration.yaml or in the config files in .storage.
1 Like
In OpenZWave it is configuration (one of the XML files), so not on the stick.
1 Like