The regular “Z-Wave” integration is the current integration. All it requires is a Z-Wave usb stick connected to your HA system, but it uses an older version of OpenZWave, so some device support is lacking.
The new integration is “OpenZWave (beta)” in the integrations list, and requires ozwdaemon (OpenZWave in the supervisor addon store) and MQTT to be running. The new component currently has limited platform support. Currently limited to binary_sensor, sensor, switch, and basic dimming lights. Climate just got merged in and should be available in .111. Cover, RGB light, lock, and fan support is still in progress as well.
Thanks for the explanation! Actually I have an AEON Stick Gen5, two Range exender 6, and a pile of Sensative Strips Comfort for lux measurement. I had it working with a Vera controller, I built some automations around it to control KNX-based rollershutters. It worked fine, but some time ago the Vera controller started acting very strange, at the and now it looks it’s brick. Now I want to move to the AEON USB stick. The regular zwave integration recognised my AEON Stick and also the range extenders, but I have difficulties adding the sensative strips. I’m just wondering if I should do it with the regular setup or move to the new beta? Please advise!
Yes it will require MQTT. The whole thing is built around MQTT to decouple OpenZwave from HASS. Has two main benefits: 1) Zwave network stays up when HASS reboots and 2) faster/easier updates to OpenZwave (straight from developer).
When we fully transition to the new platform, will mqtt allow for light transitions? There appears to be some conflicting statements in the documentation. The below chart says it does not, by default, and the written text says it does.
Good to know. I’ve read a few comments which stated that light_transition isn’t available over MQTT. Looks like they were wrong or, more likely, I misread the details.
put my device (Leviton DZPD3 dimmer) in pairing mode (when light is green, hold down 15sec to factory reset; when green again hold for 7sec until flashing amber for pairing)
call: ozw.add_node
device stops flashing
Configuration -> Devices
DZPD3-1LW Plug-In Dimming Lamp Module appears
All done!
A couple of questions:
I seem to have double-added my dimmer before I figured out how this worked. Is a way I can delete the nonfunctioning duplicate (“Delete” button from entity is disabled)?
@cgarwood is your add-on a more advanced fork of Marcel’s, trying to understand how it fits together?
There is an official OpenZwave add-on in the Add-ons store with recent commits as well, was that for the old 1.4 implementation?
The big picture is not yet super clear for noobs like me approaching this.
EDIT: I just spent a couple of hours trying to get my WD500Z-1 Linear Zwave switch to pair with the OpenZwave beta, I wasn’t successful. I added the older Zwave integration and was able to find it and add it in the older UI in 30 seconds.
Based on the lack of UI with the beta, my advice is for new users to stay clear of this… It’s a bit closer to Alpha atm.
Hi,
I have spent some nights trying to figure this out.
I want to run Mosquitto on a different server, not within HA addon.
I am unable to get Open Z-wave Deamon to start. Mosquitto is running (checked) MQTT integration is pointing to that IP.
When I start OZW deamon addon. I see: [ERROR] No Hass.io mqtt service found!
I tested with mosquitto addon, it starts fine then.
Is the Mosquitto addon obliged instead of selfhosted server? or is this a bug / still being worked on?
@nickrout
If the question is directed at me. Answer: Yes I think so, if that means:
add integration: MQTT > enter IP, User/Login, discovery Yes
Restart, go to development > MQTT > Add # to listen to, and then I see mqtt messages.
Go to integration, install OZW deamon, press start. >> I see this message. “[ERROR] No Hass.io mqtt service found!”. The icon color chages from green to grey again, indicating it has stopped. I can press start again.
I also tried deleting the mqtt integration again, adding mqtt: to the config.
mqtt:
broker: 192.168.4.13
port: 1883
username: user
password: login
discovery: true <tried adding this one as a third attempt.
all with the same result. OZW daemon does not start with the error message mentioned.
I am wondering if this is intended behaviour.
If it is not, I am happy to create an issue in github, help with logs, test etc.
Just to add info. If I install mosquitto add-on, install mqtt integration, install ozw-daemon and start it, there is no error message. I starts, and I see node information comming through in mqtt as expected.
If I install Zwave2mqtt, the external mosquitto server is seen as expected.
To make sure I am not the issue here with leftover bitsnbobs, I created a second fresh VM of homeassistant and did the above steps.
It feels to me that something is preventing ozw-daemon to see the external mqtt server.
Has anybody tried adding a ZWave controller using its “By-ID” descriptor?
I played with this new approach yesterday, but I couldn’t get the daemon to accept the string for the controller if I included a ‘By-ID’ type descriptor.
If I were to install Mosquitto add-on, instead of self hosted mosquitto. Would that in anyway result in mqtt topic to change when I am switching over from one broker to the other?
I suspect switching broker doesnt change it, but I would like to have it confirmed.
Again, thanks to all the devs and the work on zwave integration. A lot of hard work and dedication. You guys are awesome.
Regards
OK, I have the daemon installed and running, and the integration.
HA recognised my TKB switches OK, but only partially recognised the Danfoss radiator valves. It recognised the device and the battery state entity, but not the set points and other entities. Looking at log.json, there’s plenty of traffic about full discovery of the rads, so I’m guessing that there’s something missing in the addon.
Luckily, I don’t need the rads right now - I hope - so I’ll stick with it.
I’ll dig deeper and raise an issue where appropriate.
EDIT: I see from github that the climate elements were only added to the codebase a couple of days ago. I’ll leave well alone for now as I’m running 110 rather than dev code.
Hi, there seem to be 2 repos for this integration:
The custom component:
and the official version:
Can anyone explain the difference? I would like to use a cover node but that is not included in the “core” version but it seems to be included in the custom component. Does it make sense to start an issue for the core version or will it be included in a next Home Assistant Core version?
