If zigbee2mqtt can do it for Zigbee and HomeSeer can do it for Z-Wave, zwave2mqtt/OpenZWave will be able to also. At least you gave me another option to try: ttynvt…
I just got everything installed and set up. had a few strange issues that I thought I worked around, but I can’t seem to get ozw working.
I created a docker container with docker-compose. My docker-compose file was v 2.1 so i made some changes only realy issue I ran into was it didnt like the volume “- ozwd:/opt/ozw/config” you can see the changes I made below. I ran docker-compose up -d ozwd and looking at the logs it appears that everything is working.
## qt-openzwave (ozwdaemon)
ozwd:
container_name: "ozwdaemon"
image: openzwave/ozwdaemon:latest
ports:
- 1983:1983
restart: unless-stopped
security_opt:
- seccomp:unconfined
volumes:
- /opt/ozw/config:/opt/ozw/config
devices:
- /dev/ttyACM0:/dev/ttyACM0:rwm
environment:
- MQTT_SERVER=192.168.1.67
- MQTT_USERNAME=****
- MQTT_PASSWORD=****
- USB_PATH=/dev/ttyACM0
- OZW_NETWORK_KEY=****
next i updated hacs because I couldn’t install the “z-Wave over mqtt” integration because of an issue my version of hacs so I manually updated that. Got that integration installed. Restarted HA then went to Configuration -> Integrations, removed my old zwave integration. added a new “OpenZWave” integration. Saw a modal dialog that said “Confirm set up” so i clicked submit, it then said “Success! created configuration for openzwave”.
This is where I am stuck. none of my devices come through and i cant call the ozw service all of the methods return with a popup error that says
'NoneType' object has no attribute 'add_node'
UPDATE: just needed to restart the server that my docker containers were running on. Not the best solution and not entirely clear as to why this was necessary, but it worked!
Haven’t used my z-wave stuff (Aeotec stick and multisensor 6) in a few months after moving from Hass.io on RPI3b+ to Core on my Mac mini running Ubuntu and docker. I decided it was time to include and expand my z-wave network again. Followed the documentation and eventually now have my RPI running docker container for OZWdaemon (allinone), my Linux server (Mac mini) running docker containers for Mosquitto and Home Assistant core.
It all seems to work quite good and I’m not that experienced with docker or not at all with z-wave. The z wave network was up running quite fast after the containers were spun up, the multi sensor reporting in home assistant without any configuration.
Looking forward to some more control from the integration GUI, but for now it works. Will try to include a Aeotec Siren and a HeatIt Z-Water device as well and see if it’s still good.
Follow-up: ttynvt was a no-go also. However, I finally did get ozwdaemon to talk to the RaZberry. I used Z-Way server to turn off SUC/SIS management on the RaZberry (something I think HomeSeer had set) and now it’s up and running.
Hello all,
I’m trying to setup OZWDaemon on my server, to use the OpenZWave Beta on HomeAssistant.
When I run my docker, the logs only show this:
[ozwdaemon]: ========================================================================
[ozwdaemon]: Detailed Logging is available in the logs directory of the mapped volume
[ozwdaemon]: ========================================================================
[ozwdaemon]:
[ozwdaemon]: Waiting until the MQTT broker at 192.168.1.110:1883 is available...
[ozwdaemon]: Starting...
[ozwdaemon]: Executing: /usr/local/bin/ozwdaemon
That’s it…
I am able to see the Aeotek USB when I connect via VNC, but I cannot add new nodes.
Any suggestions? This is WAY over my head unfortunately, but I have a fibaro walli that does not work with the old zwave integration.
Do you have an MQTT server running? If running supervised, you can just add it via the store. OpenZwave does the rest.
1 Like
How did you setup double tap with the new open zwave integration? I had it on the old one and I’m not sure how it works in the new open zwave. The old zwave integration used zwave.node_event, and I think it is different now.
The new event is ozw.scene_activated.
1 Like
I have been testing OpenZwave and came across a problem: the Nortek USB controller (HUSBZB-1) that I have been using with my main HA set up doesn’t seem to be recognized.
I also tested with an AeoTec Z-Stick Gen5 which is recognized but I am confused that the ZWave Plus option is not checked.
Is the OpenZWave add-on going to support the same controllers currently supported by the ZWave version built into HA to ensure a smooth transition or will I have to switch to a different ZWave controller?
Why is ZWave Plus not enabled?
Make sure you have the path correct for the stick.
They support the same controllers.
That’s just a display error, all the sticks regardless of ZW+ or not show as not having ZW+.
I am not sure why I am not using ozw.scene_activated. I am using a sensor to catch the MQTT topic
- platform: mqtt
name: 'name_of_the_button'
state_topic: 'OpenZWave/1/node/9/instance/1/commandclass/43/value/<id>/'
value_template: "{{ value_json.Value }}"
This sensor can be 0 (idle), 26 (single) and 24 (double), or the triple/secondary button values. This can trigger an automation:
id: toggle_bankje
alias: 'WK muur: Toggle aan/uit'
trigger:
- entity_id: sensor.name_of_the_button
platform: state
to: '26'
action:
- data:
brightness: 125
entity_id: light.wk_muur_level
transition: 3
service: light.toggle
mode: single
Can someone point me to instructions on how to move back to the old zwave integration? This new one is giving me tons of issues with no clear advantages.