Driver problem with Zwavejs Topic is solved

[Bospieper]

Hi,
I'am also migrated from OZW to Zwavejs-ui. Almost everything is working except there is a problem with the driver.
This is the log from de ZUI:
<2024-01-03 19:07:47.222 INFO MQTT: Client closed
2024-01-03 19:08:44.706 DEBUG SOCKET: New connection RyYSo1w7IyrmIPuqAAAB
2024-01-03 19:08:44.740 DEBUG SOCKET: Event INITED emitted to RyYSo1w7IyrmIPuqAAAB
2024-01-03 19:08:47.915 INFO Z-WAVE: Controller status: Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:5256:23)
at ZWaveController.identify (/usr/src/app/node_modules/zwave-js/src/lib/controller/Controller.ts:897:37)
at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts26)
at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts16) (ZW0100)
2024-01-03 19:08:47.918 INFO Z-WAVE: Restarting client in 1 seconds, retry 1
2024-01-03 19:08:48.832 INFO MQTT: Message received on homeassistant/status: 'online'
2024-01-03 19:08:48.833 INFO GATEWAY: Home Assistant is ONLINE
2024-01-03 19:08:48.922 INFO GATEWAY: Driver is CLOSED
2024-01-03 19:08:48.924 DEBUG MQTT: Publishing to zwavejs/driver/status: false with options { qos: 1, retain: true }
2024-01-03 19:08:48.927 INFO Z-WAVE: Client closed
2024-01-03 19:08:48.928 INFO GATEWAY: Driver is CLOSED
2024-01-03 19:08:48.930 DEBUG MQTT: Publishing to zwavejs/driver/status: false with options { qos: 1, retain: true }
2024-01-03 19:08:48.940 INFO Z-WAVE: Connecting to /dev/zwave
Logging to file:
/usr/src/app/store/logs/zwavejs_2024-01-03.log>

This is my dockercompose.yml:
<version: "3.7"
services:
zwave-js-ui:
container_name: zwave-js-ui
image: zwavejs/zwave-js-ui:latest
restart: unless-stopped
tty: true
stop_signal: SIGINT
environment:
- SESSION_SECRET=mySecretSession
- TZ=Europe/Amsterdam
devices:
- '/dev/serial/by-id/usb-0658_0200_if00:/dev/zwave'
volumes:
- ./store:/usr/src/app/store
ports:
- "8091:8091" # port for web interface
- "3000:3000" # port for Z-Wave JS websocket server>

Any advice how to solve this would be appreciated
Grz. Piet

[roblom]

Maybe try

Code: Select all

- "/dev/serial/by-id/usb-0658_0200_if00:/dev/zwave"

Instead of the

Code: Select all

- '/dev/serial/by-id/usb-0658_0200_if00:/dev/zwave'

[Bospieper]

Hello roblom,
Replacing ' ' with " " did not solve the problem. As you can see in my MQTT Explorer is everything on-line except the driver.

[Kochmeister]

Same issue here, running from a proxmox LXC Ubuntu.

Any update, Did you get this working @Bospieper?

[waltervl]

This was the solution (type the /dev/serial/by-id/ name correctly, last underscore was a dash)
https://www.domoticz.com/forum/viewtopi ... 21#p311021

[Kochmeister]

Ah on that bicycle, thanks for the reply, but this is not the problem/solution in my case unfortuanately.
The search continues....
Thanks for responding anyway

[waltervl]

Did your zwave usb device work previously on the same hardware with OpenZwave? Or is it a new implementation?

[Kochmeister]

Here some background:
For years had domoticz running on a RPI with the AEON Z stick gen-5.
I kept domoticz up to date and at some point open-zwave was gone.
As the new way of working was too much challenge, so I set a backup of my RPI back and did not update domoticz for ~1year.
Frustrated with the backups on the RPI and some other reasons (Plex & minimserver & for fun & just because I can) I bought miniPC and isntalled Proxmox. From there I wanted to make a Domoticz container (ubuntu). (proxmox alows snapshots and automated backups to my NAS!)
After some more extensive reasearch and a lot of try&error I figured out that I needed to setup the proxmox LXC container in a different way to alow communication with the Z-stick.
The clou in this story is --> when using proxmox LXC; UNCHECK the previliged container checkbox upon creation

This is the long story to say:
Yes - same hardware (stick)
No - different "computer" RPI to MiniPC
implementation: from RPI to UBUNTU LCX container