Hardware watchdog restarts serial API repeatedly

[bill-long]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?

After the addon auto-updated from 0.6.2 to 0.7.1, it was no longer possible to control any ZWave devices from my Home Assistant. This addon update bumped the zwave-js version from 12.11.2 to 13.3.0, which includes the new hardware monitor. The log shows:

2024-09-14T10:47:00.806Z DRIVER « [REQ] [SerialAPIStarted]
                                    wake up reason:        WatchdogReset
                                    watchdog enabled:      false
                                    generic device class:  0x02
                                    specific device class: 0x01
                                    always listening:      false
                                    supports Long Range:   true
2024-09-14T10:47:00.806Z CNTRLR   Serial API restarted unexpectedly.
2024-09-14T10:47:00.807Z CNTRLR   Currently active command will be retried...
2024-09-14T10:47:00.807Z CNTRLR   Starting hardware watchdog...
2024-09-14T10:47:00.813Z SERIAL » 0x010300d22e                                                         (5 bytes)
2024-09-14T10:47:00.813Z DRIVER » [REQ] [StartWatchdog]
2024-09-14T10:47:00.815Z CNTRLR   Switching serial API to 16-bit node IDs...
2024-09-14T10:47:00.818Z SERIAL » 0x0105000b800273                                                     (7 bytes)
2024-09-14T10:47:00.819Z DRIVER » [REQ] [SerialAPISetup]
                                    command:      SetNodeIDType
                                    node ID type: 16 bit
2024-09-14T10:47:00.820Z SERIAL « [ACK]                                                                   (0x06)
2024-09-14T10:47:00.828Z SERIAL « [ACK]                                                                   (0x06)
2024-09-14T10:47:00.828Z SERIAL « 0x0105010b800171                                                     (7 bytes)
2024-09-14T10:47:00.829Z SERIAL » [ACK]                                                                   (0x06)
2024-09-14T10:47:00.830Z DRIVER « [RES] [SerialAPISetup]
                                    command: SetNodeIDType
                                    success: true
2024-09-14T10:47:00.831Z CNTRLR   Switching to 16-bit node IDs successful
2024-09-14T10:47:00.833Z SERIAL » 0x010f00a900010030010025000000002a66                                (17 bytes)
2024-09-14T10:47:00.834Z DRIVER » [Node 048] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      42
                                  └─[NoOperationCC]
2024-09-14T10:47:00.840Z SERIAL « [ACK]                                                                   (0x06)
2024-09-14T10:47:00.841Z SERIAL « 0x010401a90152                                                       (6 bytes)
2024-09-14T10:47:00.841Z SERIAL » [ACK]                                                                   (0x06)
2024-09-14T10:47:00.842Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2024-09-14T10:47:03.141Z SERIAL « 0x010a000a03000102010001ff                                          (12 bytes)
2024-09-14T10:47:03.141Z SERIAL » [ACK]                                                                   (0x06)
2024-09-14T10:47:03.142Z DRIVER « [REQ] [SerialAPIStarted]
                                    wake up reason:        WatchdogReset
                                    watchdog enabled:      false
                                    generic device class:  0x02
                                    specific device class: 0x01
                                    always listening:      false
                                    supports Long Range:   true
2024-09-14T10:47:03.143Z CNTRLR   Serial API restarted unexpectedly.

This repeats infinitely, with the serial API restarting every couple of seconds.

Restarting ZWaveJS, restarting Home Assistant, completely powering it down and then booting again, nothing fixes it. As soon as it loads it goes into this loop and it never comes out.

What did you expect to happen instead?

To work as usual.

Steps to reproduce the behavior:

N/A

Anything else we should know?

Similar behavior was reported a few months ago in the Discord here: https://discord.com/channels/330944238910963714/332357267364249621/1259591191419293797

In that instance, the user set ZWAVEJS_DISABLE_WATCHDOG, which fixed it.

I tried to figure out how to get into my Home Assistant OS to set the environment variable mentioned there, but I couldn't seem to get an SSH session that wasn't inside a docker container. I gave up on that approach and instead restored the backup of 0.6.2. That fixed it.

Software versions

Home Assistant Z-Wave JS Addon: 0.7.1

Device information

Manufacturer: ...
Model name: ...
Node ID: ...

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

core_zwave_js_2024-09-14T10-46-34.011Z.log

[AlCalzone]

Which stick is that?

[bill-long]

How can I tell? It's whatever came with the ODROID N2+ Home Assistant Bundle from AmeriDroid in June of 2021.

[AlCalzone]

I should probably say on the stick

[bill-long]

It says:

Zooz
S2 Stick 700
ZST10 700