Aeontec z-wave gen5 / Synology zwave-js-ui docker installation

[mareda]

Dear all

I am running Domoticz in Docker on my DS716+II and DSM6,2. I have installed zwave-js-ui according to the instructions on
https://www.domoticz.com/wiki/Zwave-JS- ... %3A8091%20)

Besides I have running eclipse-mosquitto as well.

However I have not got it to work now. Maybe someone could give me a hand to find the problem?

My settings in the Synology DS of the container are as following:

General Settings:
Container Name: zwavejs-zwave-js-ui1
Running at high priority: checked
Automatic restart: checked

Volume: (Folder in File Station created under docker with the name zwavejs2mqtt)
data/folder: docker/zwavejs2mqtt
mount tree: /usr/src/app/store

Port settings:
Local: 3000 Container: 3000 TCP
Local: 8091 Container: 8091 TCP

-> I can access the user interface via web browser.... under IP of NAS and Port 8091

Question1:
Is there a configuarion file required (in folder docker\zwavejs2mqtt\data)?
If yes what should be the content?

Question2:
I am not sure whether the stick is operating properly. It is plugged in on the front USB port of the NAS and it is listed in the Info center of the NAS.
How can I check the right port? (I have done ssh but and I think it is on ttyAC0)

Question3:
Is there maybe a step by stap guide to setup it on Synology?

Thanks in advance for your help...

[waltervl]

Did you configure your USB stick port in the Zwave-JS web page?
Did you stop your old Domoticz OpenZwave network as the USB stick can only look at 1 environment (Zwave-JS-UI or Domoticz OZW)
Did you check the log file of Zwave-JS-UI?
Did you check the forum of Zwave-JS-UI for Synology instructions?

[mareda]

Dear waltervl

First of all thank you very much for your help!!!

Please find my answers to your questions below:

Did you configure your USB stick port in the Zwave-JS web page?
- I have found the stick on ttyAC0 via SSH command and configured it in the Zwave-JS web page (Snology IP:8091).
Did you stop your old Domoticz OpenZwave network as the USB stick can only look at 1 environment (Zwave-JS-UI or Domoticz OZW)
-I have updated the Docker container with Domoticz version 2023,2 build 15621. So the OpenZwave is not there anymore...(?)
Did you check the log file of Zwave-JS-UI?
- Sure, kindly find attached the information in the file:
2023-11-16T00:05: 813Z DRIVER version 12,3,0
2023-11-16T00:05: 813Z DRIVER
2023-11-16T00:05: 813Z DRIVER starting driver...
2023-11-16T00:05: "8,813Z DRIVER opening serial port /dev/ttyACM1
2023-11-16T00:05:17,827Z DRIVER Failed to open the serial port: Error: No such file or directory, cannot open
/dev/ttyACM1
2023-11-16T00:05:17,828Z DRIVER destroying driver instance...
2023-11-16T00:05:17,828Z DRIVER driver instance destroyed
2023-11-16T00:05:32,833Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚═
Did you check the forum of Zwave-JS-UI for Synology instructions?
- I have read a lot during the last weeks. Could you please send me the link to your suggested information source?

Thanks!

[waltervl]

You say you think USB stick is on /dev/ttyACM0 but Zwave-JS-UI is looking at /dev/ttyACM1 and not finding it.

[mareda]

Thanks, I will check this evening... and post the result

[waltervl]

Also in docker you have to map your USB to an internal device

Code: Select all

docker run --rm -it -p 8091:8091 -p 3000:3000 --device=/dev/serial/by-id/insert_stick_reference_here:/dev/zwave

I don't know what the equivalent is in Synology docker

[mareda]

Thanks waltervl

It looks now quite differently:
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2023-11-16T18:41:25.903Z DRIVER version 12.3.0
2023-11-16T18:41:25.903Z DRIVER
2023-11-16T18:41:25.903Z DRIVER starting driver...
2023-11-16T18:41:25.903Z DRIVER opening serial port /dev/ttyACM0
2023-11-16T18:41:25.948Z DRIVER serial port opened
2023-11-16T18:41:25.950Z SERIAL » 0x15 (1 bytes)
2023-11-16T18:41:26.960Z DRIVER loading configuration...
2023-11-16T18:41:26.999Z CONFIG Using external configuration dir /usr/src/app/store/.config-db
2023-11-16T18:41:26.999Z CONFIG version 12.3.0
2023-11-16T18:41:28.909Z DRIVER beginning interview...
2023-11-16T18:41:28.912Z DRIVER added request handler for AddNodeToNetwork (0x4a)...
1 registered
2023-11-16T18:41:28.912Z DRIVER added request handler for RemoveNodeFromNetwork (0x4b)...
1 registered
2023-11-16T18:41:28.912Z DRIVER added request handler for ReplaceFailedNode (0x63)...
1 registered
2023-11-16T18:41:28.912Z DRIVER added request handler for SerialAPIStarted (0x0a)...
1 registered
2023-11-16T18:41:28.914Z CNTRLR querying Serial API capabilities...
2023-11-16T18:41:29.328Z SERIAL » 0x01030007fb (5 bytes)
2023-11-16T18:41:29.331Z DRIVER » [REQ] [GetSerialApiCapabilities]
2023-11-16T18:41:29.355Z SERIAL « [ACK] (0x06)
2023-11-16T18:41:29.360Z SERIAL « 0x012b0107010100860001005afe81ff884f1f0000fb9f7da067000080008086000 (45 bytes)
000e87300000e0000600000fa
2023-11-16T18:41:29.363Z SERIAL » [ACK] (0x06)
2023-11-16T18:41:29.365Z DRIVER « [RES] [GetSerialApiCapabilities]
payload: 0x010100860001005afe81ff884f1f0000fb9f7da067000080008086000000e8730
0000e0000600000
2023-11-16T18:41:29.375Z CNTRLR received API capabilities:
firmware version: 1.1
manufacturer ID: 0x86
product type: 0x01
product ID: 0x5a
supported functions:
· GetSerialApiInitData (0x02)
· SetApplicationNodeInformation (0x03)
· ApplicationCommand (0x04)
· GetControllerCapabilities (0x05)
· SetSerialApiTimeouts (0x06)
· GetSerialApiCapabilities (0x07)
· SoftReset (0x08)
· GetProtocolVersion (0x09)
· SetRFReceiveMode (0x10)
· UNKNOWN_FUNC_SET_SLEEP_MODE (0x11)
· FUNC_ID_ZW_SEND_NODE_INFORMATION (0x12)
· SendData (0x13)
· SendDataMulticast (0x14)
· GetControllerVersion (0x15)
· SendDataAbort (0x16)
· FUNC_ID_ZW_R_F_POWER_LEVEL_SET (0x17)
· UNKNOWN_FUNC_SEND_DATA_META (0x18)
· FUNC_ID_ZW_GET_RANDOM (0x1c)
· GetControllerId (0x20)
· UNKNOWN_FUNC_MEMORY_GET_BYTE (0x21)
· UNKNOWN_FUNC_MEMORY_PUT_BYTE (0x22)
· UNKNOWN_FUNC_MEMORY_GET_BUFFER (0x23)
· UNKNOWN_FUNC_MEMORY_PUT_BUFFER (0x24)
· EnterBootloader (0x27)
· GetNVMId (0x29)
· ExtNVMReadLongBuffer (0x2a)
· ExtNVMWriteLongBuffer (0x2b)
· ExtNVMReadLongByte (0x2c)
· ExtExtWriteLongByte (0x2d)
· GetNodeProtocolInfo (0x41)
· HardReset (0x42)
· FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
· FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
· AssignReturnRoute (0x46)
· DeleteReturnRoute (0x47)
· RequestNodeNeighborUpdate (0x48)
· ApplicationUpdateRequest (0x49)
· AddNodeToNetwork (0x4a)
· RemoveNodeFromNetwork (0x4b)
· FUNC_ID_ZW_CREATE_NEW_PRIMARY (0x4c)
· FUNC_ID_ZW_CONTROLLER_CHANGE (0x4d)
· FUNC_ID_ZW_SET_LEARN_MODE (0x50)
· AssignSUCReturnRoute (0x51)
· FUNC_ID_ZW_REQUEST_NETWORK_UPDATE (0x53)
· SetSUCNodeId (0x54)
· DeleteSUCReturnRoute (0x55)
· GetSUCNodeId (0x56)
· UNKNOWN_FUNC_SEND_SUC_ID (0x57)
· FUNC_ID_ZW_EXPLORE_REQUEST_INCLUSION (0x5e)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
· UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
· GetRoutingInfo (0x80)
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· GetPriorityRoute (0x92)
· SetPriorityRoute (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· UNKNOWN_FUNC_UNKNOWN_0xB4 (0xb4)
· UNKNOWN_FUNC_WATCH_DOG_ENABLE (0xb6)
· UNKNOWN_FUNC_WATCH_DOG_DISABLE (0xb7)
· UNKNOWN_FUNC_WATCH_DOG_KICK (0xb8)
· UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
· UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
· UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
· UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
· UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· undefined (0xee)
· UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)

What should I do next?

[waltervl]

I don't know. Perhaps check the error in the Zwave-JS-UI project https://github.com/zwave-js/zwave-js-ui

[mareda]

Dear waltervl

I have re-installed and tested mosquitto according to the following tutorial:

https://www.youtube.com/watch?v=kQ159NLCJts&t=0s

and re-installded zwavejs2mqtt similar to the follwing tutorial:

https://www.youtube.com/watch?v=-GW_9K_Gd6k

It seems that ther is no communicaton between zwavesjs2mqtt and mosquitto.

[waltervl]

Then you know where to search: in the Zwave-JS-UI MQTT configuration. For example do not use localhost as server name as from a docker perspective the localhost does not run MQTT broker. It is in another container. Use the IP address of your Synology.

As the instruction you followed is 2 years old MQTT is already on a new version (2.x). For newer MQTT versions you need extra configuration: https://www.domoticz.com/wiki/MQTT#Gene ... 2.0_and_up
Be aware the instruction is for a non Docker environment so your mosquitto.conf is in another location!

[mareda]

Dear waltervl

Thanks you very much for your support. I will check and post the result!

BR

[mareda]

Dear waltervl

I have the following log entries from the mosquitto log files:

1700550130: New client connected from 192.... as Domoticz-MQTT-AutoDiscoverec0ffb20-623f-49f2-b454-ea48e5a72a9217 (c1, k120).
1700551505: mosquitto version 1.4.15 terminating
1700551509: mosquitto version 1.4.15 (build date Sat, 07 Apr 2018 11:13:41 +0100) starting
1700551509: Config loaded from /mqtt/config/mosquitto.conf.
1700551509: Opening ipv4 listen socket on port 1883.
1700551509: Opening ipv6 listen socket on port 1883.
1700551511: New connection from 192.... on port 1883.
1700551511: New client connected from 192.... as 34ddxjdC9rHb2WdjbSvhnM (c1, k60, u'username').
1700551524: New connection from 192....on port 1883.
1700551524: New client connected from 192....as Domoticz-MQTT-AutoDiscoverfe15cb3f-9dba-4af1-b02f-c8fa144405a518 (c1, k120).
1700551526: New connection from 192.....on port 1883.

Do you see something suspicous?

[waltervl]

No, seems OK for me but I am not using MQTT..... You are using an old 1.4 mosquitto version from 2018 it seems. But is should work.
Also check your Zwave-JS-UI log and your Domoticz Log for errors.

[mareda]

Hi waltervl

I am a step further now. The problem was the host setting in the zwave-JS User Interface. (I put mqtt:// before the IP...)
The devices are now listed in the device list of Domoticz.
I still have some doubts.. Shouldn't the stick also be visible under the setup menu of MQTT Auto Discovery Client Gateway with LAN interface?

[waltervl]

No, Zwave-JS-UI talks with the stick and with MQTT broker. Domoticz only talks with MQTT broker and knows nothing about Zwave-JS-UI and the zwave stick.