Domoticz

Open source Home Automation System
https://forum.domoticz.com/

zwave-js-ui container keeps restarting (loops)

https://forum.domoticz.com/viewtopic.php?t=42062

Page 1 of 2

zwave-js-ui container keeps restarting (loops)

Posted: Sunday 25 February 2024 17:02
by hvoorend
Hi all, I'm in the process of migrating to MQTT-zwavejs-ui. MQTT (Mosquitto) container installed and gateway definitions in Domoticz created for "MQTT Client Gateway" and "MQTT Auto Discover Client Gateway". After spinning up the zwave-js-ui container, I'm able to access it via my browser. After zwavejs-ui configuration (according to the instructions here (https://www.domoticz.com/wiki/Zwave-JS-UI)), I do see devices coming into the zwavejs-ui but after about 50 seconds they disappear and I can see from "docker ps" that my container restarted. Then it starts all over again. Any idea what could be wrong or help on how to investigate ?

Re: zwave-js-ui container keeps restarting (loops)

Posted: Sunday 25 February 2024 18:11
by mgugu
Check logs. Use docker-compose up without daemon, In a terminal, write:

Code: Select all

cd <yml directory>
docker-compose down
docker-compose up
Logs should appear in the terminal

Re: zwave-js-ui container keeps restarting (loops)

Posted: Sunday 25 February 2024 20:21
by akamming
Or just docker compose logs -f

Re: zwave-js-ui container keeps restarting (loops)

Posted: Sunday 25 February 2024 21:27
by hvoorend
Thanks. Got this:

Code: Select all

zwave-js-ui  | #
zwave-js-ui  | # Fatal error in , line 0
zwave-js-ui  | # unreachable code
zwave-js-ui  | #
zwave-js-ui  | #
zwave-js-ui  | #
zwave-js-ui  | #FailureMessage Object: 0x74007764
zwave-js-ui exited with code 0
Running Buster currently. Do you think I need to upgrade to Bookworm and retry ?

Re: zwave-js-ui container keeps restarting (loops)

Posted: Sunday 25 February 2024 22:34
by Varazir
I hade issue with looping as well. Both times was that it couldn't access the device.
Could you share your compose conf file ?
What type of Zwave HW do you use ?

Re: zwave-js-ui container keeps restarting (loops)

Posted: Monday 26 February 2024 18:39
by hvoorend
Thanks Varazir and others. Am not able to answer the questions yet as I decided to upgrade to Bookworm in the meantime, but the upgrade ran into an error (libc6) and wacked my full raspbian (seems to be a known error. At least not to me. So I had to recover from an SD-card image. Luckily only one week old but I had to rebuild my MQTT/ZWaveJS-UI efforts from Docker Engine up. Almost there again and will retest then. Maybe with better results. Who knows. Will keep yo posted.

Re: zwave-js-ui container keeps restarting (loops)

Posted: Tuesday 27 February 2024 21:01
by hvoorend
Unfortunately still a looping container. Here a list of my Pi USB devices:

Code: Select all

pi@raspberrypi:~ $ ls /dev/serial/by-id -l
total 0
lrwxrwxrwx 1 root root 13 Feb 23 22:36 usb-0658_0200-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Feb 23 22:36 usb-RFXCOM_RFXtrx433_A12WY8N-if00-port0 -> ../../ttyUSB0
So usb-0658_0200-if00 is my Aeon zStick 5 (as you can see I also have a RFXCOM dongle installed: usb-RFXCOM_RFXtrx433_A12WY8N-if00-port0).
Here the contents of /opt/zwavejs-ui/docker-compose.yml:

Code: Select all

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

Does anyone have any suggestions ?

Re: zwave-js-ui container keeps restarting (loops)

Posted: Tuesday 27 February 2024 21:07
by hvoorend
By the way: a "docker compose up" shows:

Code: Select all

root@raspberrypi:/opt/zwavejs-ui# docker compose up
[+] Running 1/1
 ✔ Container zwave-js-ui  Recreated                                                                                                                                       0.4s
Attaching to zwave-js-ui
zwave-js-ui  | 2024-02-27 21:04:24.357 INFO APP: Version: 9.9.0.09b107a
zwave-js-ui  | 2024-02-27 21:04:24.390 INFO APP: Application path:/usr/src/app
zwave-js-ui  |   ______  __          __                      _  _____     _    _ _____
zwave-js-ui  |  |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
zwave-js-ui  |     / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
zwave-js-ui  |    / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
zwave-js-ui  |   / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
zwave-js-ui  |  /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
zwave-js-ui  |
zwave-js-ui  | 2024-02-27 21:04:24.542 WARN STORE: scenes.json not found
zwave-js-ui  |
zwave-js-ui  | /usr/src/app/server/app.js:597
zwave-js-ui  |             gw.zwave?.setUserCallbacks();
zwave-js-ui  |                ^
zwave-js-ui  | TypeError: Cannot read properties of undefined (reading 'zwave')
zwave-js-ui  |     at SocketManager.<anonymous> (/usr/src/app/server/app.js:597:16)
zwave-js-ui  |     at SocketManager.emit (node:events:517:28)
zwave-js-ui  |     at SocketManager._onConnection (/usr/src/app/server/lib/SocketManager.js:48:14)
zwave-js-ui  |     at Namespace.emit (node:events:529:35)
zwave-js-ui  |     at Namespace.emitReserved (/usr/src/app/node_modules/socket.io/dist/typed-events.js:56:22)
zwave-js-ui  |     at Namespace._doConnect (/usr/src/app/node_modules/socket.io/dist/namespace.js:269:14)
zwave-js-ui  |     at /usr/src/app/node_modules/socket.io/dist/namespace.js:231:22
zwave-js-ui  |     at processTicksAndRejections (node:internal/process/task_queues:77:11)
zwave-js-ui exited with code 0
root@raspberrypi:/opt/zwavejs-ui#

Re: zwave-js-ui container keeps restarting (loops)

Posted: Wednesday 28 February 2024 23:32
by hvoorend
I’m pretty much stuck. Anyone any suggestions for a direction to look into? Hope someone can help me out. Otherwise I need to revert back to OZW… :roll: . Thanks in advance for your thoughts.

Re: zwave-js-ui container keeps restarting (loops)

Posted: Thursday 29 February 2024 0:05
by waltervl
Perhaps better to ask this to the specialists of Zwave-JS-UI on their GitHub repository
https://github.com/zwave-js/zwave-js-ui/issues

Re: zwave-js-ui container keeps restarting (loops)

Posted: Thursday 29 February 2024 9:21
by mgugu
hvoorend wrote: ↑Tuesday 27 February 2024 21:01 Here the contents of /opt/zwavejs-ui/docker-compose.yml:

Code: Select all

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

Does anyone have any suggestions ?
You set an internal zwave device as /dev/zwave but it should be /dev/ttyACM0. This is probably the source of error shown in the logs

Re: zwave-js-ui container keeps restarting (loops)

Posted: Thursday 29 February 2024 17:15
by waltervl
/dev/serial/by-id/usb-0658_0200-if00 is a proper device and should be used in favorite of eg /dev/ttyACM0 as those can change when having multiple USB devices in use.....
So the docker-compose.yml seems OK. Something else is wrong here....

Re: zwave-js-ui container keeps restarting (loops)

Posted: Thursday 29 February 2024 17:27
by hvoorend
Might my zStick Gen5 running firmware 1.0 need a firmware update ? (think 1.2 is the latest if I’m correct). Thanks for your responses sofar. Will consult the GitHub guys as well in the meantime.

Re: zwave-js-ui container keeps restarting (loops)

Posted: Thursday 29 February 2024 17:37
by mgugu
waltervl wrote: ↑Thursday 29 February 2024 17:15 /dev/serial/by-id/usb-0658_0200-if00 is a proper device and should be used in favorite of eg /dev/ttyACM0 as those can change when having multiple USB devices in use.....
So the docker-compose.yml seems OK. Something else is wrong here....
I do not speak about the docker external device but the internal on whick AFAIK has to be /dev/ttyACM0 and not /dev/zwave.
So the complete devices option should be:

Code: Select all

devices:
      - '/dev/serial/by-id/usb-0658_0200-if00:/dev/ttyACM0'

Re: zwave-js-ui container keeps restarting (loops)

Posted: Thursday 29 February 2024 18:48
by waltervl
It is the default setup of the Zwave-JS-UI docker container to use /dev/zwave so it should have no impact.
BUT in Zwave-JS-UI user interface (port 8091) settings check that the correct device is used: the second part of the docker device configuration /dev/zwave or /dev/ttyACM0 and press on SAVE (important action!!)

Re: zwave-js-ui container keeps restarting (loops)

Posted: Thursday 29 February 2024 19:37
by mgugu
At this step of installation he has no access to the UI so no possibility to change something.
My interpretation of the log

Code: Select all

zwave-js-ui  | /usr/src/app/server/app.js:597
zwave-js-ui  |             gw.zwave?.setUserCallbacks();
zwave-js-ui  |                ^
zwave-js-ui  | TypeError: Cannot read properties of undefined (reading 'zwave')
is that the gateway 'zwave' cannot be accessed, so an exception is raised.
It is worth to try to change the device name, at least for a test.

Re: zwave-js-ui container keeps restarting (loops)

Posted: Thursday 29 February 2024 21:10
by hvoorend
I ran some test with your suggestions: first I changed to '/dev/serial/by-id/usb-0658_0200-if00:/dev/ttyACM0' in docker-compose.yaml and restarted the zwavejs-ui container. Connected to the UI and changed Zwave Serial port settings to
zwave serial port.png
zwave serial port.png (30.98 KiB) Viewed 2127 times
and SAVED :D . This resulted in
Driver failed to open.png
Driver failed to open.png (19.37 KiB) Viewed 2127 times
Restart of the container -> same result.
Reverted back to '/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave' in docker-compose.yml and started the container without -d flag (so: docker compose up). Changed to /dev/zwave in UI settings and the driver was opened all right:
zwave serial port2.png
zwave serial port2.png (32.81 KiB) Viewed 2127 times
but the container crashed with:

Code: Select all

pi@raspberrypi:/opt/zwavejs-ui $ sudo docker compose up
[+] Running 2/2
 ✔ Network zwavejs-ui_default  Created                                                                                                                                                                                                  0.5s
 ✔ Container zwave-js-ui       Created                                                                                                                                                                                                  0.3s
Attaching to zwave-js-ui
zwave-js-ui  | 2024-02-29 19:58:25.938 INFO APP: Version: 9.9.0.09b107a
zwave-js-ui  | 2024-02-29 19:58:25.968 INFO APP: Application path:/usr/src/app
zwave-js-ui  |   ______  __          __                      _  _____     _    _ _____
zwave-js-ui  |  |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
zwave-js-ui  |     / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
zwave-js-ui  |    / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
zwave-js-ui  |   / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
zwave-js-ui  |  /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
zwave-js-ui  |
zwave-js-ui  | 2024-02-29 19:58:26.116 WARN STORE: scenes.json not found
zwave-js-ui  | Logging to file:
zwave-js-ui  |  /usr/src/app/store/logs/zwavejs_2024-02-29.log
zwave-js-ui  |
zwave-js-ui  |
zwave-js-ui  | #
zwave-js-ui  | # Fatal error in , line 0
zwave-js-ui  | # unreachable code
zwave-js-ui  | #
zwave-js-ui  | #
zwave-js-ui  | #
zwave-js-ui  | #FailureMessage Object: 0x75821764
zwave-js-ui exited with code 0
pi@raspberrypi:/opt/zwavejs-ui $
I have attached a piece of /usr/src/app/store/logs/zwavejs_2024-02-29.log . I actually do not see any signs that there is something wrong, but I'm not into the internals of zwavejs-ui. I did notice that the log times from the docker are 1 hour behind on my RPI (local) time (?).

Code: Select all

docker exec -it zwave-js-ui sh
/usr/src/app/
cat store/logs/zwavejs_2024-02-29.log

2024-02-29T19:18:32.796Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2024-02-29T19:18:32.805Z DRIVER   version 12.4.4
2024-02-29T19:18:32.810Z DRIVER
2024-02-29T19:18:32.814Z DRIVER   starting driver...
2024-02-29T19:18:32.816Z DRIVER   opening serial port /dev/zwave
2024-02-29T19:18:33.052Z DRIVER   serial port opened
2024-02-29T19:18:33.064Z SERIAL » 0x15                                                                 (1 bytes)
2024-02-29T19:18:33.138Z SERIAL « 0x0110000400290a7105000000ff070001084d                              (18 bytes)
2024-02-29T19:18:33.178Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2024-02-29T19:18:33.185Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:33.198Z SERIAL « 0x0110000400260a32022134000000310000d3                              (18 bytes)
2024-02-29T19:18:33.211Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2024-02-29T19:18:33.214Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:34.120Z DRIVER   loading configuration...
2024-02-29T19:18:34.176Z CONFIG   Using external configuration dir /usr/src/app/store/.config-db
2024-02-29T19:18:34.180Z CONFIG   version 12.4.4
2024-02-29T19:18:41.678Z DRIVER   beginning interview...
2024-02-29T19:18:41.689Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
                                  1 registered
2024-02-29T19:18:41.691Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
                                  1 registered
2024-02-29T19:18:41.692Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
                                  1 registered
2024-02-29T19:18:41.696Z DRIVER   added request handler for SerialAPIStarted (0x0a)...
                                  1 registered
2024-02-29T19:18:41.703Z CNTRLR   querying Serial API capabilities...
2024-02-29T19:18:43.599Z SERIAL » 0x01030007fb                                                         (5 bytes)
2024-02-29T19:18:43.612Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-02-29T19:18:43.696Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:43.718Z SERIAL « 0x012b0107010000860001005afe81ff884f1f0000fb9f7da067000080008086000 (45 bytes)
                                  000e87300000e0000600000fb
2024-02-29T19:18:43.734Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:43.748Z DRIVER « [RES] [GetSerialApiCapabilities]
                                    payload: 0x010000860001005afe81ff884f1f0000fb9f7da067000080008086000000e8730
                                  0000e0000600000
2024-02-29T19:18:43.881Z CNTRLR   received API capabilities:
                                    firmware version:    1.0
                                    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)
2024-02-29T19:18:43.887Z CNTRLR   querying version info...
2024-02-29T19:18:43.982Z SERIAL » 0x01030015e9                                                         (5 bytes)
2024-02-29T19:18:43.986Z DRIVER » [REQ] [GetControllerVersion]
2024-02-29T19:18:44.050Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:44.067Z SERIAL « 0x011001155a2d5761766520332e3935000199                              (18 bytes)
2024-02-29T19:18:44.074Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:44.081Z DRIVER « [RES] [GetControllerVersion]
                                    payload: 0x5a2d5761766520332e39350001
2024-02-29T19:18:44.105Z CNTRLR   received version info:
                                    controller type: Static Controller
                                    library version: Z-Wave 3.95
2024-02-29T19:18:44.107Z CNTRLR   querying protocol version info...
2024-02-29T19:18:44.149Z SERIAL » 0x01030009f5                                                         (5 bytes)
2024-02-29T19:18:44.155Z DRIVER » [REQ] [GetProtocolVersion]
2024-02-29T19:18:44.167Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:44.176Z SERIAL « 0x0107010900035f00ac                                                 (9 bytes)
2024-02-29T19:18:44.181Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:44.189Z DRIVER « [RES] [GetProtocolVersion]
                                    payload: 0x00035f00
2024-02-29T19:18:44.207Z CNTRLR   received protocol version info:
                                    protocol type:             Z-Wave
                                    protocol version:          3.95.0
2024-02-29T19:18:44.214Z CNTRLR   querying controller IDs...
2024-02-29T19:18:44.251Z SERIAL » 0x01030020dc                                                         (5 bytes)
2024-02-29T19:18:44.257Z DRIVER » [REQ] [GetControllerId]
2024-02-29T19:18:44.274Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:44.285Z SERIAL « 0x01080120fdd0547b01d5                                              (10 bytes)
2024-02-29T19:18:44.293Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:44.301Z DRIVER « [RES] [GetControllerId]
                                    home ID:     0xfdd0547b
                                    own node ID: 1
2024-02-29T19:18:44.321Z CNTRLR   received controller IDs:
                                    home ID:     0xfdd0547b
                                    own node ID: 1
2024-02-29T19:18:44.340Z DRIVER   all queues idle
2024-02-29T19:18:44.489Z CNTRLR   Performing soft reset...
2024-02-29T19:18:44.503Z DRIVER   all queues busy
2024-02-29T19:18:44.521Z SERIAL » 0x01030008f4                                                         (5 bytes)
2024-02-29T19:18:44.525Z DRIVER » [REQ] [SoftReset]
2024-02-29T19:18:44.544Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:44.562Z CNTRLR   Waiting for the controller to reconnect...
2024-02-29T19:18:44.569Z DRIVER   all queues idle
2024-02-29T19:18:46.070Z CNTRLR   Re-opening serial port...
2024-02-29T19:18:47.098Z CNTRLR   Waiting for the Serial API to start...
2024-02-29T19:18:47.851Z SERIAL « 0x010f00040029097105000000ff07080050                                (17 bytes)
2024-02-29T19:18:47.862Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:47.878Z CNTRLR   [Node 041] is unknown - discarding received command...
2024-02-29T19:18:47.892Z DRIVER « [Node 041] [REQ] [ApplicationCommand]                              [discarded]
                                  └─[NotificationCCReport]
                                      notification type:   Home Security
                                      notification status: 255
                                      notification state:  Motion detection
2024-02-29T19:18:47.899Z SERIAL « 0x01090004000903300300cb                                            (11 bytes)
2024-02-29T19:18:47.910Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:47.915Z CNTRLR   [Node 009] is unknown - discarding received command...
2024-02-29T19:18:47.921Z DRIVER « [Node 009] [REQ] [ApplicationCommand]                              [discarded]
                                  └─[BinarySensorCCReport]
                                      type:  Any
                                      value: false
2024-02-29T19:18:47.926Z SERIAL « 0x01090004000903200100d9                                            (11 bytes)
2024-02-29T19:18:47.933Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:47.940Z CNTRLR   [Node 009] is unknown - discarding received command...
2024-02-29T19:18:47.944Z DRIVER « [Node 009] [REQ] [ApplicationCommand]                              [discarded]
                                  └─[BasicCCSet]
                                      target value: 0
2024-02-29T19:18:52.102Z CNTRLR   Did not receive notification that Serial API has started, checking if it respo
                                  nds...
2024-02-29T19:18:52.116Z DRIVER   all queues busy
2024-02-29T19:18:52.136Z SERIAL » 0x01030015e9                                                         (5 bytes)
2024-02-29T19:18:52.144Z DRIVER » [REQ] [GetControllerVersion]
2024-02-29T19:18:52.154Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:52.162Z SERIAL « 0x011001155a2d5761766520332e3935000199                              (18 bytes)
2024-02-29T19:18:52.166Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:52.172Z DRIVER « [RES] [GetControllerVersion]
                                    payload: 0x5a2d5761766520332e39350001
2024-02-29T19:18:52.191Z CNTRLR   Serial API responded
2024-02-29T19:18:52.197Z DRIVER   all queues idle
2024-02-29T19:18:52.289Z CNTRLR   supported Z-Wave features:
2024-02-29T19:18:52.291Z CNTRLR   querying controller capabilities...
2024-02-29T19:18:52.299Z DRIVER   all queues busy
2024-02-29T19:18:52.314Z SERIAL » 0x01030005f9                                                         (5 bytes)
2024-02-29T19:18:52.319Z DRIVER » [REQ] [GetControllerCapabilities]
2024-02-29T19:18:52.327Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:52.333Z SERIAL « 0x010401051ce3                                                       (6 bytes)
2024-02-29T19:18:52.339Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:52.344Z DRIVER « [RES] [GetControllerCapabilities]
                                    payload: 0x1c
2024-02-29T19:18:52.358Z CNTRLR   received controller capabilities:
                                    controller role:      primary
                                    is the SUC:           true
                                    started this network: true
                                    SIS is present:       true
                                    was real primary:     true
2024-02-29T19:18:52.359Z CNTRLR   finding SUC...
2024-02-29T19:18:52.381Z SERIAL » 0x01030056aa                                                         (5 bytes)
2024-02-29T19:18:52.383Z DRIVER » [REQ] [GetSUCNodeId]
2024-02-29T19:18:52.402Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:52.408Z SERIAL « 0x0104015601ad                                                       (6 bytes)
2024-02-29T19:18:52.412Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:52.416Z DRIVER « [RES] [GetSUCNodeId]
                                    payload: 0x01
2024-02-29T19:18:52.431Z CNTRLR   This is the SUC
2024-02-29T19:18:52.434Z CNTRLR   querying additional controller information...
2024-02-29T19:18:52.460Z SERIAL » 0x01030002fe                                                         (5 bytes)
2024-02-29T19:18:52.465Z DRIVER » [REQ] [GetSerialApiInitData]
2024-02-29T19:18:52.477Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:52.562Z SERIAL « 0x0125010205081d01dd66daa201000000000000000000000000000000000000000 (39 bytes)
                                  000000005000f
2024-02-29T19:18:52.569Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:52.573Z DRIVER « [RES] [GetSerialApiInitData]
                                    payload: 0x05081d01dd66daa20100000000000000000000000000000000000000000000000
                                  500
2024-02-29T19:18:52.588Z CNTRLR   received additional controller information:
                                    Z-Wave API version:         5 (legacy)
                                    Z-Wave chip type:           ZW050x
                                    node type                   Controller
                                    controller role:            primary
                                    controller is the SIS:      true
                                    controller supports timers: false
                                    nodes in the network:       1, 9, 11, 12, 13, 15, 16, 18, 19, 22, 23, 26, 28
                                  , 29, 31, 32, 34, 38, 40, 41
2024-02-29T19:18:52.952Z DRIVER   Cache file for homeId 0xfdd0547b found, attempting to restore the network from
                                   cache...
2024-02-29T19:18:53.021Z DRIVER   all queues idle
2024-02-29T19:18:53.834Z CNTRLR   [Node 001] Embedded device config loaded
2024-02-29T19:18:53.865Z DRIVER   Restoring the network from cache was successful!
2024-02-29T19:18:53.890Z CNTRLR   [Node 001] [Manufacturer Specific] manufacturerId: metadata updated
2024-02-29T19:18:53.896Z CNTRLR   [Node 001] [Manufacturer Specific] productType: metadata updated
2024-02-29T19:18:53.901Z CNTRLR   [Node 001] [Manufacturer Specific] productId: metadata updated
2024-02-29T19:18:53.910Z CNTRLR   [Node 001] [~] [Manufacturer Specific] manufacturerId: 134 => 134
2024-02-29T19:18:53.916Z CNTRLR   [Node 001] [~] [Manufacturer Specific] productType: 1 => 1
2024-02-29T19:18:53.919Z CNTRLR   [Node 001] [~] [Manufacturer Specific] productId: 90 => 90
2024-02-29T19:18:53.929Z CNTRLR   [Node 001] [Version] firmwareVersions: metadata updated
2024-02-29T19:18:53.933Z CNTRLR   [Node 001] [~] [Version] firmwareVersions: 1.0 => 1.0
2024-02-29T19:18:53.937Z CNTRLR   [Node 001] [Version] zWaveProtocolVersion: metadata updated
2024-02-29T19:18:53.940Z CNTRLR   [Node 001] [~] [Version] zWaveProtocolVersion: "3.95.0" => "3.95.0"
2024-02-29T19:18:53.945Z CNTRLR   [Node 001] [Version] sdkVersion: metadata updated
2024-02-29T19:18:53.948Z CNTRLR   [Node 001] [~] [Version] sdkVersion: "6.51.2" => "6.51.2"
2024-02-29T19:18:53.950Z CNTRLR   setting serial API timeouts: ack = 1000 ms, byte = 150 ms
2024-02-29T19:18:53.960Z DRIVER   all queues busy
2024-02-29T19:18:53.976Z SERIAL » 0x01050006640f97                                                     (7 bytes)
2024-02-29T19:18:53.981Z DRIVER » [REQ] [SetSerialApiTimeouts]
                                    payload: 0x640f
2024-02-29T19:18:54.000Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:54.005Z SERIAL « 0x01050106960f64                                                     (7 bytes)
2024-02-29T19:18:54.011Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:54.017Z DRIVER « [RES] [SetSerialApiTimeouts]
                                    payload: 0x960f
2024-02-29T19:18:54.031Z CNTRLR   serial API timeouts overwritten. The old values were: ack = 1500 ms, byte = 15
                                  0 ms
2024-02-29T19:18:54.032Z CNTRLR   Interview completed
2024-02-29T19:18:54.034Z DRIVER   No network key for S0 configured, communication with secure (S0) devices won't
                                   work!
2024-02-29T19:18:54.036Z DRIVER   No network key for S2 configured, communication with secure (S2) devices won't
                                   work!
2024-02-29T19:18:54.037Z DRIVER   driver ready
2024-02-29T19:18:54.051Z DRIVER   Checking for configuration updates...
2024-02-29T19:18:54.317Z CNTRLR   [Node 001] The node is alive.
2024-02-29T19:18:54.421Z CNTRLR   [Node 001] The node is ready to be used
2024-02-29T19:18:54.448Z CNTRLR   Interviewing nodes and/or determining their status: 19, 9, 11, 12, 13, 15, 16,
                                   18, 22, 23, 26, 28, 29, 31, 32, 34, 38, 40, 41
2024-02-29T19:18:54.459Z CNTRLR   [Node 019] Beginning interview - last completed stage: ProtocolInfo
2024-02-29T19:18:54.462Z CNTRLR » [Node 019] pinging the node...
2024-02-29T19:18:55.154Z CNTRLR   [Node 009] The node is asleep.
2024-02-29T19:18:55.163Z CNTRLR   [Node 009] Beginning interview - last completed stage: ProtocolInfo
2024-02-29T19:18:55.168Z CNTRLR » [Node 009] querying node info...
2024-02-29T19:18:55.183Z CNTRLR   [Node 011] Beginning interview - last completed stage: None
2024-02-29T19:18:55.184Z CNTRLR   [Node 011] new node, doing a full interview...
2024-02-29T19:18:55.192Z CNTRLR » [Node 011] querying protocol info...
2024-02-29T19:18:55.210Z CNTRLR   [Node 012] Beginning interview - last completed stage: None
2024-02-29T19:18:55.212Z CNTRLR   [Node 012] new node, doing a full interview...
2024-02-29T19:18:55.220Z CNTRLR » [Node 012] querying protocol info...
2024-02-29T19:18:55.266Z CNTRLR   [Node 013] Beginning interview - last completed stage: None
2024-02-29T19:18:55.268Z CNTRLR   [Node 013] new node, doing a full interview...
2024-02-29T19:18:55.271Z CNTRLR » [Node 013] querying protocol info...
2024-02-29T19:18:55.282Z CNTRLR   [Node 015] Beginning interview - last completed stage: None
2024-02-29T19:18:55.284Z CNTRLR   [Node 015] new node, doing a full interview...
2024-02-29T19:18:55.287Z CNTRLR » [Node 015] querying protocol info...
2024-02-29T19:18:55.298Z CNTRLR   [Node 016] Beginning interview - last completed stage: None
2024-02-29T19:18:55.300Z CNTRLR   [Node 016] new node, doing a full interview...
2024-02-29T19:18:55.303Z CNTRLR » [Node 016] querying protocol info...
2024-02-29T19:18:55.316Z CNTRLR   [Node 018] Beginning interview - last completed stage: None
2024-02-29T19:18:55.317Z CNTRLR   [Node 018] new node, doing a full interview...
2024-02-29T19:18:55.322Z CNTRLR » [Node 018] querying protocol info...
2024-02-29T19:18:55.332Z CNTRLR   [Node 022] Beginning interview - last completed stage: None
2024-02-29T19:18:55.333Z CNTRLR   [Node 022] new node, doing a full interview...
2024-02-29T19:18:55.338Z CNTRLR » [Node 022] querying protocol info...
2024-02-29T19:18:55.348Z CNTRLR   [Node 023] Beginning interview - last completed stage: None
2024-02-29T19:18:55.350Z CNTRLR   [Node 023] new node, doing a full interview...
2024-02-29T19:18:55.353Z CNTRLR » [Node 023] querying protocol info...
2024-02-29T19:18:55.364Z CNTRLR   [Node 026] Beginning interview - last completed stage: None
2024-02-29T19:18:55.365Z CNTRLR   [Node 026] new node, doing a full interview...
2024-02-29T19:18:55.368Z CNTRLR » [Node 026] querying protocol info...
2024-02-29T19:18:55.377Z CNTRLR   [Node 028] Beginning interview - last completed stage: None
2024-02-29T19:18:55.378Z CNTRLR   [Node 028] new node, doing a full interview...
2024-02-29T19:18:55.381Z CNTRLR » [Node 028] querying protocol info...
2024-02-29T19:18:55.391Z CNTRLR   [Node 029] Beginning interview - last completed stage: None
2024-02-29T19:18:55.393Z CNTRLR   [Node 029] new node, doing a full interview...
2024-02-29T19:18:55.395Z CNTRLR » [Node 029] querying protocol info...
2024-02-29T19:18:55.404Z CNTRLR   [Node 031] Beginning interview - last completed stage: None
2024-02-29T19:18:55.406Z CNTRLR   [Node 031] new node, doing a full interview...
2024-02-29T19:18:55.408Z CNTRLR » [Node 031] querying protocol info...
2024-02-29T19:18:55.418Z CNTRLR   [Node 032] Beginning interview - last completed stage: None
2024-02-29T19:18:55.420Z CNTRLR   [Node 032] new node, doing a full interview...
2024-02-29T19:18:55.423Z CNTRLR » [Node 032] querying protocol info...
2024-02-29T19:18:55.431Z CNTRLR   [Node 034] Beginning interview - last completed stage: None
2024-02-29T19:18:55.433Z CNTRLR   [Node 034] new node, doing a full interview...
2024-02-29T19:18:55.435Z CNTRLR » [Node 034] querying protocol info...
2024-02-29T19:18:55.443Z CNTRLR   [Node 038] Beginning interview - last completed stage: None
2024-02-29T19:18:55.445Z CNTRLR   [Node 038] new node, doing a full interview...
2024-02-29T19:18:55.447Z CNTRLR » [Node 038] querying protocol info...
2024-02-29T19:18:55.456Z CNTRLR   [Node 040] Beginning interview - last completed stage: None
2024-02-29T19:18:55.457Z CNTRLR   [Node 040] new node, doing a full interview...
2024-02-29T19:18:55.460Z CNTRLR » [Node 040] querying protocol info...
2024-02-29T19:18:55.468Z CNTRLR   [Node 041] Beginning interview - last completed stage: None
2024-02-29T19:18:55.470Z CNTRLR   [Node 041] new node, doing a full interview...
2024-02-29T19:18:55.473Z CNTRLR » [Node 041] querying protocol info...
2024-02-29T19:18:55.580Z SERIAL » 0x010800131301002501d2                                              (10 bytes)
2024-02-29T19:18:55.586Z DRIVER » [Node 019] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      1
                                  └─[NoOperationCC]
2024-02-29T19:18:55.740Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:18:55.746Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2024-02-29T19:18:55.750Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:55.818Z DRIVER « [RES] [SendData]
                                    was sent: true
2024-02-29T19:18:55.858Z SERIAL « 0x0107001301000005ef                                                 (9 bytes)
2024-02-29T19:18:55.866Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:18:55.876Z DRIVER « [REQ] [SendData]
                                    callback id:     1
                                    transmit status: OK
2024-02-29T19:18:55.904Z CNTRLR   [Node 019] The node is alive.
2024-02-29T19:18:55.914Z CNTRLR « [Node 019] ping successful
2024-02-29T19:18:55.915Z CNTRLR » [Node 019] querying node info...
2024-02-29T19:18:55.947Z SERIAL » 0x010400410bb1                                                       (6 bytes)
2024-02-29T19:18:55.950Z DRIVER » [REQ] [GetNodeProtocolInfo]
                                    payload: 0x0b
2024-02-29T19:19:40.607Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2024-02-29T19:19:40.618Z DRIVER   version 12.4.4
2024-02-29T19:19:40.624Z DRIVER
2024-02-29T19:19:40.628Z DRIVER   starting driver...
2024-02-29T19:19:40.630Z DRIVER   opening serial port /dev/zwave
2024-02-29T19:19:40.909Z DRIVER   serial port opened
2024-02-29T19:19:40.922Z SERIAL » 0x15                                                                 (1 bytes)
2024-02-29T19:19:41.006Z SERIAL « 0x010900040009033003ff34                                            (11 bytes)
2024-02-29T19:19:41.051Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2024-02-29T19:19:41.058Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:19:41.071Z SERIAL « 0x010900040009032001ff26                                            (11 bytes)
2024-02-29T19:19:41.084Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2024-02-29T19:19:41.087Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:19:41.987Z DRIVER   loading configuration...
2024-02-29T19:19:42.035Z CONFIG   Using external configuration dir /usr/src/app/store/.config-db
2024-02-29T19:19:42.038Z CONFIG   version 12.4.4
2024-02-29T19:19:49.089Z DRIVER   beginning interview...
2024-02-29T19:19:49.100Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
                                  1 registered
2024-02-29T19:19:49.102Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
                                  1 registered
2024-02-29T19:19:49.103Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
                                  1 registered
2024-02-29T19:19:49.107Z DRIVER   added request handler for SerialAPIStarted (0x0a)...
                                  1 registered
2024-02-29T19:19:49.115Z CNTRLR   querying Serial API capabilities...
2024-02-29T19:19:51.158Z SERIAL » 0x01030007fb                                                         (5 bytes)
2024-02-29T19:19:51.169Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-02-29T19:19:51.208Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:19:51.223Z SERIAL « 0x012b0107010000860001005afe81ff884f1f0000fb9f7da067000080008086000 (45 bytes)
                                  000e87300000e0000600000fb
2024-02-29T19:19:51.233Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:19:51.243Z DRIVER « [RES] [GetSerialApiCapabilities]
                                    payload: 0x010000860001005afe81ff884f1f0000fb9f7da067000080008086000000e8730
                                  0000e0000600000
2024-02-29T19:19:51.291Z CNTRLR   received API capabilities:
                                    firmware version:    1.0
                                    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)
2024-02-29T19:19:51.294Z CNTRLR   querying version info...
2024-02-29T19:19:51.339Z SERIAL » 0x01030015e9                                                         (5 bytes)
2024-02-29T19:19:51.342Z DRIVER » [REQ] [GetControllerVersion]
2024-02-29T19:19:51.407Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:19:51.444Z SERIAL « 0x011001155a2d5761766520332e3935000199                              (18 bytes)
2024-02-29T19:19:51.451Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:19:51.471Z DRIVER « [RES] [GetControllerVersion]
                                    payload: 0x5a2d5761766520332e39350001
2024-02-29T19:19:51.506Z CNTRLR   received version info:
                                    controller type: Static Controller
                                    library version: Z-Wave 3.95
2024-02-29T19:19:51.519Z CNTRLR   querying protocol version info...
2024-02-29T19:19:51.610Z SERIAL » 0x01030009f5                                                         (5 bytes)
2024-02-29T19:19:51.616Z DRIVER » [REQ] [GetProtocolVersion]
2024-02-29T19:19:51.636Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:19:51.648Z SERIAL « 0x0107010900035f00ac                                                 (9 bytes)
2024-02-29T19:19:51.654Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:19:51.662Z DRIVER « [RES] [GetProtocolVersion]
                                    payload: 0x00035f00
2024-02-29T19:19:51.681Z CNTRLR   received protocol version info:
                                    protocol type:             Z-Wave
                                    protocol version:          3.95.0
2024-02-29T19:19:51.685Z CNTRLR   querying controller IDs...
2024-02-29T19:19:51.772Z SERIAL » 0x01030020dc                                                         (5 bytes)
2024-02-29T19:19:51.778Z DRIVER » [REQ] [GetControllerId]
2024-02-29T19:19:51.795Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:19:51.806Z SERIAL « 0x01080120fdd0547b01d5                                              (10 bytes)
2024-02-29T19:19:51.813Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:19:51.821Z DRIVER « [RES] [GetControllerId]
                                    home ID:     0xfdd0547b
                                    own node ID: 1
2024-02-29T19:19:51.841Z CNTRLR   received controller IDs:
                                    home ID:     0xfdd0547b
                                    own node ID: 1
2024-02-29T19:19:51.856Z DRIVER   all queues idle
2024-02-29T19:19:51.960Z CNTRLR   Performing soft reset...
2024-02-29T19:19:51.970Z DRIVER   all queues busy
2024-02-29T19:19:51.986Z SERIAL » 0x01030008f4                                                         (5 bytes)
2024-02-29T19:19:51.989Z DRIVER » [REQ] [SoftReset]
2024-02-29T19:19:52.004Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:19:52.021Z CNTRLR   Waiting for the controller to reconnect...
2024-02-29T19:19:52.027Z DRIVER   all queues idle
2024-02-29T19:19:53.527Z CNTRLR   Re-opening serial port...
2024-02-29T19:19:54.554Z CNTRLR   Waiting for the Serial API to start...
2024-02-29T19:19:59.558Z CNTRLR   Did not receive notification that Serial API has started, checking if it respo
                                  nds...
2024-02-29T19:19:59.571Z DRIVER   all queues busy
2024-02-29T19:19:59.585Z SERIAL » 0x01030015e9                                                         (5 bytes)
2024-02-29T19:19:59.592Z DRIVER » [REQ] [GetControllerVersion]
2024-02-29T19:19:59.604Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:19:59.610Z SERIAL « 0x011001155a2d5761766520332e3935000199                              (18 bytes)
2024-02-29T19:19:59.613Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:19:59.620Z DRIVER « [RES] [GetControllerVersion]
                                    payload: 0x5a2d5761766520332e39350001
2024-02-29T19:19:59.632Z CNTRLR   Serial API responded
2024-02-29T19:19:59.638Z DRIVER   all queues idle
2024-02-29T19:19:59.709Z CNTRLR   supported Z-Wave features:
2024-02-29T19:19:59.710Z CNTRLR   querying controller capabilities...
2024-02-29T19:19:59.721Z DRIVER   all queues busy
2024-02-29T19:19:59.740Z SERIAL » 0x01030005f9                                                         (5 bytes)
2024-02-29T19:19:59.744Z DRIVER » [REQ] [GetControllerCapabilities]
2024-02-29T19:19:59.757Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:19:59.763Z SERIAL « 0x010401051ce3                                                       (6 bytes)
2024-02-29T19:19:59.768Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:19:59.774Z DRIVER « [RES] [GetControllerCapabilities]
                                    payload: 0x1c
2024-02-29T19:19:59.791Z CNTRLR   received controller capabilities:
                                    controller role:      primary
                                    is the SUC:           true
                                    started this network: true
                                    SIS is present:       true
                                    was real primary:     true
2024-02-29T19:19:59.793Z CNTRLR   finding SUC...
2024-02-29T19:19:59.815Z SERIAL » 0x01030056aa                                                         (5 bytes)
2024-02-29T19:19:59.819Z DRIVER » [REQ] [GetSUCNodeId]
2024-02-29T19:19:59.830Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:19:59.836Z SERIAL « 0x0104015601ad                                                       (6 bytes)
2024-02-29T19:19:59.840Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:19:59.845Z DRIVER « [RES] [GetSUCNodeId]
                                    payload: 0x01
2024-02-29T19:19:59.860Z CNTRLR   This is the SUC
2024-02-29T19:19:59.862Z CNTRLR   querying additional controller information...
2024-02-29T19:19:59.893Z SERIAL » 0x01030002fe                                                         (5 bytes)
2024-02-29T19:19:59.898Z DRIVER » [REQ] [GetSerialApiInitData]
2024-02-29T19:19:59.909Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:19:59.994Z SERIAL « 0x0125010205081d01dd66daa201000000000000000000000000000000000000000 (39 bytes)
                                  000000005000f
2024-02-29T19:20:00.001Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:20:00.006Z DRIVER « [RES] [GetSerialApiInitData]
                                    payload: 0x05081d01dd66daa20100000000000000000000000000000000000000000000000
                                  500
2024-02-29T19:20:00.021Z CNTRLR   received additional controller information:
                                    Z-Wave API version:         5 (legacy)
                                    Z-Wave chip type:           ZW050x
                                    node type                   Controller
                                    controller role:            primary
                                    controller is the SIS:      true
                                    controller supports timers: false
                                    nodes in the network:       1, 9, 11, 12, 13, 15, 16, 18, 19, 22, 23, 26, 28
                                  , 29, 31, 32, 34, 38, 40, 41
2024-02-29T19:20:00.378Z DRIVER   Cache file for homeId 0xfdd0547b found, attempting to restore the network from
                                   cache...
2024-02-29T19:20:00.440Z DRIVER   all queues idle
2024-02-29T19:20:01.359Z CNTRLR   [Node 001] Embedded device config loaded
2024-02-29T19:20:01.387Z DRIVER   Restoring the network from cache was successful!
2024-02-29T19:20:01.417Z CNTRLR   [Node 001] [Manufacturer Specific] manufacturerId: metadata updated
2024-02-29T19:20:01.424Z CNTRLR   [Node 001] [Manufacturer Specific] productType: metadata updated
2024-02-29T19:20:01.428Z CNTRLR   [Node 001] [Manufacturer Specific] productId: metadata updated
2024-02-29T19:20:01.436Z CNTRLR   [Node 001] [~] [Manufacturer Specific] manufacturerId: 134 => 134
2024-02-29T19:20:01.445Z CNTRLR   [Node 001] [~] [Manufacturer Specific] productType: 1 => 1
2024-02-29T19:20:01.450Z CNTRLR   [Node 001] [~] [Manufacturer Specific] productId: 90 => 90
2024-02-29T19:20:01.455Z CNTRLR   [Node 001] [Version] firmwareVersions: metadata updated
2024-02-29T19:20:01.459Z CNTRLR   [Node 001] [~] [Version] firmwareVersions: 1.0 => 1.0
2024-02-29T19:20:01.467Z CNTRLR   [Node 001] [Version] zWaveProtocolVersion: metadata updated
2024-02-29T19:20:01.471Z CNTRLR   [Node 001] [~] [Version] zWaveProtocolVersion: "3.95.0" => "3.95.0"
2024-02-29T19:20:01.474Z CNTRLR   [Node 001] [Version] sdkVersion: metadata updated
2024-02-29T19:20:01.477Z CNTRLR   [Node 001] [~] [Version] sdkVersion: "6.51.2" => "6.51.2"
2024-02-29T19:20:01.479Z CNTRLR   setting serial API timeouts: ack = 1000 ms, byte = 150 ms
2024-02-29T19:20:01.489Z DRIVER   all queues busy
2024-02-29T19:20:01.505Z SERIAL » 0x01050006640f97                                                     (7 bytes)
2024-02-29T19:20:01.511Z DRIVER » [REQ] [SetSerialApiTimeouts]
                                    payload: 0x640f
2024-02-29T19:20:01.544Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:20:01.550Z SERIAL « 0x01050106960f64                                                     (7 bytes)
2024-02-29T19:20:01.554Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:20:01.560Z DRIVER « [RES] [SetSerialApiTimeouts]
                                    payload: 0x960f
2024-02-29T19:20:01.575Z CNTRLR   serial API timeouts overwritten. The old values were: ack = 1500 ms, byte = 15
                                  0 ms
2024-02-29T19:20:01.576Z CNTRLR   Interview completed
2024-02-29T19:20:01.578Z DRIVER   No network key for S0 configured, communication with secure (S0) devices won't
                                   work!
2024-02-29T19:20:01.580Z DRIVER   No network key for S2 configured, communication with secure (S2) devices won't
                                   work!
2024-02-29T19:20:01.581Z DRIVER   driver ready
2024-02-29T19:20:01.595Z DRIVER   Checking for configuration updates...
2024-02-29T19:20:01.828Z CNTRLR   [Node 001] The node is alive.
2024-02-29T19:20:01.906Z CNTRLR   [Node 001] The node is ready to be used
2024-02-29T19:20:01.919Z CNTRLR   Interviewing nodes and/or determining their status: 19, 9, 11, 12, 13, 15, 16,
                                   18, 22, 23, 26, 28, 29, 31, 32, 34, 38, 40, 41
2024-02-29T19:20:01.931Z CNTRLR   [Node 019] Beginning interview - last completed stage: ProtocolInfo
2024-02-29T19:20:01.934Z CNTRLR » [Node 019] pinging the node...
2024-02-29T19:20:02.585Z CNTRLR   [Node 009] The node is asleep.
2024-02-29T19:20:02.594Z CNTRLR   [Node 009] Beginning interview - last completed stage: ProtocolInfo
2024-02-29T19:20:02.599Z CNTRLR » [Node 009] querying node info...
2024-02-29T19:20:02.612Z CNTRLR   [Node 011] Beginning interview - last completed stage: None
2024-02-29T19:20:02.614Z CNTRLR   [Node 011] new node, doing a full interview...
2024-02-29T19:20:02.620Z CNTRLR » [Node 011] querying protocol info...
2024-02-29T19:20:02.634Z CNTRLR   [Node 012] Beginning interview - last completed stage: None
2024-02-29T19:20:02.636Z CNTRLR   [Node 012] new node, doing a full interview...
2024-02-29T19:20:02.640Z CNTRLR » [Node 012] querying protocol info...
2024-02-29T19:20:02.654Z CNTRLR   [Node 013] Beginning interview - last completed stage: None
2024-02-29T19:20:02.655Z CNTRLR   [Node 013] new node, doing a full interview...
2024-02-29T19:20:02.659Z CNTRLR » [Node 013] querying protocol info...
2024-02-29T19:20:02.696Z CNTRLR   [Node 015] Beginning interview - last completed stage: None
2024-02-29T19:20:02.697Z CNTRLR   [Node 015] new node, doing a full interview...
2024-02-29T19:20:02.701Z CNTRLR » [Node 015] querying protocol info...
2024-02-29T19:20:02.711Z CNTRLR   [Node 016] Beginning interview - last completed stage: None
2024-02-29T19:20:02.713Z CNTRLR   [Node 016] new node, doing a full interview...
2024-02-29T19:20:02.716Z CNTRLR » [Node 016] querying protocol info...
2024-02-29T19:20:02.727Z CNTRLR   [Node 018] Beginning interview - last completed stage: None
2024-02-29T19:20:02.728Z CNTRLR   [Node 018] new node, doing a full interview...
2024-02-29T19:20:02.734Z CNTRLR » [Node 018] querying protocol info...
2024-02-29T19:20:02.746Z CNTRLR   [Node 022] Beginning interview - last completed stage: None
2024-02-29T19:20:02.748Z CNTRLR   [Node 022] new node, doing a full interview...
2024-02-29T19:20:02.754Z CNTRLR » [Node 022] querying protocol info...
2024-02-29T19:20:02.767Z CNTRLR   [Node 023] Beginning interview - last completed stage: None
2024-02-29T19:20:02.769Z CNTRLR   [Node 023] new node, doing a full interview...
2024-02-29T19:20:02.773Z CNTRLR » [Node 023] querying protocol info...
2024-02-29T19:20:02.783Z CNTRLR   [Node 026] Beginning interview - last completed stage: None
2024-02-29T19:20:02.784Z CNTRLR   [Node 026] new node, doing a full interview...
2024-02-29T19:20:02.787Z CNTRLR » [Node 026] querying protocol info...
2024-02-29T19:20:02.797Z CNTRLR   [Node 028] Beginning interview - last completed stage: None
2024-02-29T19:20:02.798Z CNTRLR   [Node 028] new node, doing a full interview...
2024-02-29T19:20:02.801Z CNTRLR » [Node 028] querying protocol info...
2024-02-29T19:20:02.813Z CNTRLR   [Node 029] Beginning interview - last completed stage: None
2024-02-29T19:20:02.814Z CNTRLR   [Node 029] new node, doing a full interview...
2024-02-29T19:20:02.817Z CNTRLR » [Node 029] querying protocol info...
2024-02-29T19:20:02.828Z CNTRLR   [Node 031] Beginning interview - last completed stage: None
2024-02-29T19:20:02.830Z CNTRLR   [Node 031] new node, doing a full interview...
2024-02-29T19:20:02.833Z CNTRLR » [Node 031] querying protocol info...
2024-02-29T19:20:02.843Z CNTRLR   [Node 032] Beginning interview - last completed stage: None
2024-02-29T19:20:02.844Z CNTRLR   [Node 032] new node, doing a full interview...
2024-02-29T19:20:02.847Z CNTRLR » [Node 032] querying protocol info...
2024-02-29T19:20:02.857Z CNTRLR   [Node 034] Beginning interview - last completed stage: None
2024-02-29T19:20:02.858Z CNTRLR   [Node 034] new node, doing a full interview...
2024-02-29T19:20:02.861Z CNTRLR » [Node 034] querying protocol info...
2024-02-29T19:20:02.872Z CNTRLR   [Node 038] Beginning interview - last completed stage: None
2024-02-29T19:20:02.874Z CNTRLR   [Node 038] new node, doing a full interview...
2024-02-29T19:20:02.877Z CNTRLR » [Node 038] querying protocol info...
2024-02-29T19:20:02.889Z CNTRLR   [Node 040] Beginning interview - last completed stage: None
2024-02-29T19:20:02.891Z CNTRLR   [Node 040] new node, doing a full interview...
2024-02-29T19:20:02.895Z CNTRLR » [Node 040] querying protocol info...
2024-02-29T19:20:02.907Z CNTRLR   [Node 041] Beginning interview - last completed stage: None
2024-02-29T19:20:02.909Z CNTRLR   [Node 041] new node, doing a full interview...
2024-02-29T19:20:02.912Z CNTRLR » [Node 041] querying protocol info...
2024-02-29T19:20:03.006Z SERIAL » 0x010800131301002501d2                                              (10 bytes)
2024-02-29T19:20:03.020Z DRIVER » [Node 019] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      1
                                  └─[NoOperationCC]
2024-02-29T19:20:03.189Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:20:03.195Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2024-02-29T19:20:03.199Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:20:03.263Z DRIVER « [RES] [SendData]
                                    was sent: true
2024-02-29T19:20:03.309Z SERIAL « 0x0107001301000005ef                                                 (9 bytes)
2024-02-29T19:20:03.315Z SERIAL » [ACK]                                                                   (0x06)
2024-02-29T19:20:03.326Z DRIVER « [REQ] [SendData]
                                    callback id:     1
                                    transmit status: OK
2024-02-29T19:20:03.353Z CNTRLR   [Node 019] The node is alive.
2024-02-29T19:20:03.362Z CNTRLR « [Node 019] ping successful
2024-02-29T19:20:03.363Z CNTRLR » [Node 019] querying node info...
2024-02-29T19:20:03.393Z SERIAL » 0x010400410bb1                                                       (6 bytes)
2024-02-29T19:20:03.396Z DRIVER » [REQ] [GetNodeProtocolInfo]
                                    payload: 0x0b
2024-02-29T19:20:04.233Z SERIAL « [ACK]                                                                   (0x06)
2024-02-29T19:20:04.280Z SERIAL « 0x01090141529c000420015d                                            (11 bytes)
2024-02-29T19:20:04.330Z SERIAL » [ACK]

Re: zwave-js-ui container keeps restarting (loops)

Posted: Thursday 29 February 2024 21:49
by waltervl
Again, please discuss this issue with the Zwave-JS-UI specialists in their GitHub repository.

Re: zwave-js-ui container keeps restarting (loops)

Posted: Thursday 29 February 2024 23:13
by mgugu
I would try a clean install, either in a new folder (only yml file in it) or by deleting the 'store' folder. Here is my working yml:

Code: Select all

version: '3.7'
services:
  zwave-js-ui:
    container_name: zwave-js-ui
    image: zwavejs/zwave-js-ui:latest
    restart: always
    tty: true
    stop_signal: SIGINT
    environment:
      - SESSION_SECRET=mysupersecretkey
      - TZ=<zone>
    networks:
      - zwave
    devices:
      - /dev/serial/by-id/usb-0658_0200-if00:/dev/ttyACM0
    volumes:
      - ./store:/usr/src/app/store
    ports:
      - '8091:8091' # port for web interface
      - '3100:3000' # port for zwave-js websocket server
networks:
  zwave:
    name: zwavejs2mqtt
    external: true

Re: zwave-js-ui container keeps restarting (loops)

Posted: Saturday 02 March 2024 22:24
by hvoorend
Thanks waltervl and mgugu. Already did a clean install as my attempt upgrade Raspbian to Bookworm ruined my Pi-OS. Results after clean install
Were exactly alike. Will aks the Zwave-JS-UI specialists in their GitHub repository.
All times are UTC+02:00
Page 1 of 2

Powered by phpBB® Forum Software © phpBB Limited