Do not use that one, use the Remote OZWDaemon start button. 
Your log looks fine, everything is good.
Re-reviewing your log, this might be a problem. Maybe @Fishwaldo or @freshcoast could give insight on that error.
Ok, thanks.
With the HUSBZB-1. I was able to get further. I successfully paired an unused inovelli wall switch but nothing was appearing in HASS. I needed to add
-e MQTT_USERNAME="homeassistant" \
-e MQTT_PASSWORD=" <redacted> " \
to my docker startup and then it was able to connect to MQTT server.
I discovered this via MQTT Explorer not showing anything via anonymous login to 192.168.1.104. I went to HASS MQTT Mosquitto Broker integration and via reconfigure, retrieved username and password. Once adding those credentials to MQTT Explorer, it was able to connect and display “stuff”. So I then added to docker container startup configuration. Eventually, the USB adapter appeared in HASS followed shortly thereafter by the inovelli switch, which is controllable!
Now, if I can get the RaZberry card working, I’d be happy!
BTW, it is running the latest firmware which if memory serves me correctly is 5.37???
Just to clarity, I was using two different “instances”, so to speak but only one at a time. I was actually doing docker stop, docker rm, and then docker run -d the other one as there were usually changes in my docker run commands. Now that I have the run syntax sorted out so they both work, I could instantiate both containers and then just docker stop/docker start to flip them.
docker run -d \
--name ozw_ama \
--restart=unless-stopped \
--security-opt seccomp=unconfined \
--device=/dev/ttyAMA0 \
-v $PWD/ozw:/opt/ozw/config \
-e MQTT_SERVER="192.168.1.104" \
-e MQTT_USERNAME="homeassistant" \
-e MQTT_PASSWORD="she3ieroquoow1ko2cu7iesa0bohVoo4AiQuakothahliphoghohphaephohKo1r" \
-e USB_PATH=/dev/ttyAMA0 \
-e OZW_NETWORK_KEY=0xBC,0x87,0xD5,0xE2,0x51,0xB3,0xA7,0x44,0x05,0x20,0xEA,0x0E,0xBC,0xF9,0xD6,0x17 \
-p 1983:1983 \
-p 5901:5901 \
-p 7800:7800 \
openzwave/ozwdaemon:allinone-latest
docker run -d \
--name ozw_usb \
--restart=unless-stopped \
--security-opt seccomp=unconfined \
--device=/dev/ttyUSB0 \
-v $PWD/ozw:/opt/ozw/config \
-e MQTT_SERVER="192.168.1.104" \
-e MQTT_USERNAME="homeassistant" \
-e MQTT_PASSWORD="she3ieroquoow1ko2cu7iesa0bohVoo4AiQuakothahliphoghohphaephohKo1r" \
-e USB_PATH=/dev/ttyUSB0 \
-e OZW_NETWORK_KEY=0xBC,0x87,0xD5,0xE2,0x51,0xB3,0xA7,0x44,0x05,0x20,0xEA,0x0E,0xBC,0xF9,0xD6,0x17 \
-p 1983:1983 \
-p 5901:5901 \
-p 7800:7800 \
openzwave/ozwdaemon:allinone-latest
I am using the Razberry fine on a Pi 4 (PI Os 64 bit; not using all-in-one). The main trick I needed was to ensure that there was no “serial port” contention. Here are the notes I made when I was setting it up:
Disable bluetooth so Razberry has exclusive use of the UART at ttyAMA0
by adding the follow line to /boot/firmware/usrcfg.txt:
dtoverlay=disable-bt
Ensure that getty console doesn't also start running on ttyAMA0!
- need to disable getty on serial ttyAMA0
- systemctl stop serial-getty@ttyAMA0
- systemctl disable serial-getty@ttyAMA0
- systemctl mask serial-getty@ttyAMA0
- remove console=serial0,115200 from /boot/firmware/cmdline.txt
Check ‘lsof /dev/ttyAMA0’ to ensure that getty or any other programs
are not using this interface.
My docker-compose.yml is based on the example from: https://github.com/tprelog/iocage-homeassistant/wiki/Using-a-RPI-for-Z-Wave .
1 Like
Thanks but that’s not my issue. I set up the Pi over 2 years year ago with HomeSeer (Pi Version) on it. Then upgraded/moved HS to Linux version on a new box and I’ve been using ttyAMA0 on my Pi (192.168.1.101) via ser2net with HomeSeer at 192.168.1.103 for more than a year. Before starting ozwdaemon I do stop ser2net and lsof /dev/ttyAMA0 shows nothing has it open.
OK. You can run both at the same time if you set OZW_INSTANCE to something besides 1 for one of the containers.
This doesn’t seem to be anything. I always see it.
Seems like something is going on with your serial port. Here’s what a “normal” start looks like.
[20200715 8:30:35.113 PDT] [ozw.library] [info]: Info - Node: 0 mgr, Added driver for controller /dev/ttyUSB0
[20200715 8:30:35.113 PDT] [ozw.manager] [debug]: AddDriver Completed
[20200715 8:30:35.114 PDT] [ozw.library] [info]: Info - Node: 0 Timer: thread starting
[20200715 8:30:35.114 PDT] [ozw.library] [debug]: Detail - Node: 0 Timer: waiting with timeout -1 ms
[20200715 8:30:35.114 PDT] [ozw.library] [info]: Info - Node: 0 Opening controller /dev/ttyUSB0
[20200715 8:30:35.114 PDT] [ozw.library] [info]: Info - Node: 0 Trying to open serial port /dev/ttyUSB0 (attempt 1)
[20200715 8:30:35.147 PDT] [ozw.library] [info]: Info - Node: 0 Serial port /dev/ttyUSB0 opened (attempt 1)
[20200715 8:30:35.147 PDT] [ozw.library] [debug]: Detail - Node: 255 Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
The messages Trying to open serial port /dev/ttyUSB0 (attempt 1) and Serial port /dev/ttyUSB0 opened (attempt 1) are from the same function call. Since your last message is basically Trying to open serial port /dev/ttyAMA0 (attempt 1), and there are no error messages, it’s as if that function is hung trying to open the serial port or do something with it. I haven’t seen this before so I don’t have much more to add.
Thanks for the analysis. OZW says they support the RaZberry card in addition to the RaZberry USB stick. I will try some things like disabling ser2net from starting and rebooting the Pi even though lsof says its clear. I also have a Pi 1B with a fresh new Raspberry OS on it. I will transfer the RaZberry to it, install docker, etc. and try it there.
It would be really nice if ozwdaemon supported IP:Port connections. How would one go about requesting that new feature?
Sorry, that’s probably not gonna happen. FR: Add Support for network attached USB stick · Issue #79 · OpenZWave/qt-openzwave · GitHub
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