ZwaveJs2Mqtt broken down

Configuration Z-Wave
1

I run two nodes with Zwqavejs2MQTT , two identical raspberry pi 3 with AEOTEC Gen5 stick running zwavejs2mqtt in docker mode with MQTT turned off. I have about 35 devices on each node. Yesterday I saw that I lost connection with one of them from Homeassistant (separate Intel Nuc device). I turned on debug on the node and I can see that the Zwavejs “component” is just looping. It comes to node 021 and the it states:
2021-09-30T07:11:34.104Z DRIVER Failed to initialize the driver: Octal literals are not allowed in strict mode.
After that it shuts down the driver and tries again…

I tried updating the docker container but with the same exact result. I changed to a raspberry pi 4 and copied the config from one Aeotec Gen5 stick (yeah turns out you can do that…) to another but I got the EXACT same issue…

I reealy don’t want to scrap the whole config and start over . Has anyone seen this issue before ?
Longer log:

2021-09-30T07:11:31.001Z CNTRLR   Interview completed
2021-09-30T07:11:31.001Z DRIVER   Network key for S0 configured, enabling S0 security manager...
2021-09-30T07:11:31.007Z DRIVER   At least one network key for S2 configured, enabling S2 security manager...
2021-09-30T07:11:31.025Z DRIVER   driver ready
2021-09-30T07:11:31.038Z DRIVER   Checking for configuration updates...
2021-09-30T07:11:31.231Z CNTRLR   [Node 001] The node is alive.
2021-09-30T07:11:31.244Z CNTRLR   [Node 001] The node is ready to be used
2021-09-30T07:11:31.246Z CNTRLR » [Node 005] pinging the node...
2021-09-30T07:11:31.770Z DRIVER » [Node 005] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      1
                                  └─[NoOperationCC]
2021-09-30T07:11:31.776Z CNTRLR   [Node 006] The node is asleep.
2021-09-30T07:11:32.110Z CNTRLR   [Node 006] The node is ready to be used
2021-09-30T07:11:32.112Z CNTRLR » [Node 007] pinging the node...
2021-09-30T07:11:32.118Z CNTRLR » [Node 008] pinging the node...
2021-09-30T07:11:32.124Z CNTRLR » [Node 009] pinging the node...
2021-09-30T07:11:32.133Z CNTRLR   [Node 012] The node is asleep.
2021-09-30T07:11:32.472Z CNTRLR   [Node 012] The node is ready to be used
2021-09-30T07:11:32.473Z CNTRLR » [Node 013] pinging the node...
2021-09-30T07:11:32.483Z CNTRLR   [Node 014] The node is asleep.
2021-09-30T07:11:32.858Z CNTRLR   [Node 014] The node is ready to be used
2021-09-30T07:11:32.859Z CNTRLR » [Node 015] pinging the node...
2021-09-30T07:11:32.873Z CNTRLR » [Node 016] pinging the node...
2021-09-30T07:11:32.898Z CNTRLR   [Node 017] The node is asleep.
2021-09-30T07:11:33.207Z CNTRLR   [Node 017] The node is ready to be used
2021-09-30T07:11:33.208Z CNTRLR » [Node 018] pinging the node...
2021-09-30T07:11:33.219Z CNTRLR   [Node 019] The node is asleep.
2021-09-30T07:11:33.477Z CNTRLR   [Node 019] The node is ready to be used
2021-09-30T07:11:33.483Z CNTRLR   [Node 020] The node is asleep.
2021-09-30T07:11:33.710Z CNTRLR   [Node 020] The node is ready to be used
2021-09-30T07:11:33.714Z CNTRLR   [Node 021] The node is asleep.
2021-09-30T07:11:33.956Z CNTRLR   [Node 021] The node is ready to be used
2021-09-30T07:11:33.961Z CNTRLR   [Node 022] The node is asleep.
2021-09-30T07:11:34.104Z DRIVER   Failed to initialize the driver: Octal literals are not allowed in strict mode
                                  .
2021-09-30T07:11:34.110Z DRIVER   destroying driver instance...
2021-09-30T07:11:34.714Z DRIVER   ███████╗ ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗             ██╗ ███████╗
                                  ╚══███╔╝ ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝             ██║ ██╔════╝
                                    ███╔╝  ██║ █╗ ██║ ███████║ ██║   ██║ █████╗   █████╗      ██║ ███████╗
                                   ███╔╝   ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝   ╚════╝ ██   ██║ ╚════██║
                                  ███████╗ ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗        ╚█████╔╝ ███████║
                                  ╚══════╝  ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝         ╚════╝  ╚══════╝
2021-09-30T07:11:34.715Z DRIVER   version 8.3.1
2021-09-30T07:11:34.715Z DRIVER
2021-09-30T07:11:34.716Z DRIVER   starting driver...
2021-09-30T07:11:34.726Z DRIVER   opening serial port /dev/ttyACM0
2021-09-30T07:11:34.735Z DRIVER   serial port opened
2021-09-30T07:11:34.741Z DRIVER « [RES] [SendData]
                                    was sent: true
2021-09-30T07:11:34.748Z DRIVER « [RES] [SendData]                                                  [unexpected]
                                    was sent: true
2021-09-30T07:11:34.749Z DRIVER   unexpected response, discarding...
2021-09-30T07:11:34.754Z DRIVER « [REQ] [SendData]
                                    callback id:     1
                                    transmit status: OK
2021-09-30T07:11:34.760Z DRIVER   handling request SendData (19)
2021-09-30T07:11:34.761Z DRIVER     no handlers registered!
2

This may be your issue too, i guess?

3

I saw that post ( should have mentioned that maybe… ) but the thing is I did not update the Zwavejs. And I am running the same version (8.3.1) on my other node without issues.
I am also a bit confused about the version numbers. If I look here:

I can’t really find 0.1.4.x so I don’t know which product is in what “project”…

4

Ok I might have fixed it actually. I tried removing node 022 but I coudl not do it from the gui since it was constantly looping so I manually edited the .json file ( /var/log/zwavejs/dc93f59a.json in my case) that has all the node info and removed the node 022 from the file. After I started the container again the and no more error message. I just have that one node that probably needs a reinterview. Weird stuff…