@bcopeland - getting Z-Wave lighting delays since I switched to Z-WaveJS a couple days ago. Delays are on automations that ran w/out issue on ZipGateway. C8-Pro, 2.4.3.137.
Happened three times in last two days that I've noticed. Two different locations, twice on one room and once on another. Delays were 1m, 30s for the first two, and unfortunately wasn't able to time the third this AM, but well over 30s delay.
I did have Z-Wave logs on for the one that happened this AM. Two lights in the room, one is dumb light on a plug (Zigbee) and that worked normally/quickly. Other is Utility Room Light (GE Z-Wave switch) and that's the one that was delayed. Didn't get delays on ZipGateway.
Entered utility room at 8:26:04, motion activation started, logs said the Utility Room light turned on but it didn't. Couldn't time delay in light actually turning on, unfortunately, but it was significant (well over 30s).
Regular and Z-Wave logs below...see anything interesting? Anything additional you'd like to know?
Z-Wave logs:
2025-10-17 08:26:53.796 AMSERIAL « [ACK] (0x06)
2025-10-17 08:26:53.793 AMDRIVER » [REQ] [SendDataAbort]
2025-10-17 08:26:53.791 AMSERIAL » 0x01030016ea (5 bytes)
2025-10-17 08:26:33.788 AMDRIVER « [RES] [SendDataBridge] - was sent: true
2025-10-17 08:26:33.786 AMSERIAL » [ACK] (0x06)
2025-10-17 08:26:33.783 AMSERIAL « 0x010401a90152 (6 bytes)
2025-10-17 08:26:33.780 AMSERIAL « [ACK] (0x06)
2025-10-17 08:26:33.776 AMDRIVER » [Node 045] [REQ] [SendDataBridge] - │ source node id: 1 - │ transmit options: 0x25 - │ callback id: 87 - └─[Security2CCMessageEncapsulation] - │ sequence number: 170 - │ security class: S2_Authenticated - └─[SupervisionCCGet] - │ session id: 45 - │ request updates: true - └─[MultilevelSwitchCCSet] - target value: 50
2025-10-17 08:26:33.771 AMSERIAL » 0x012200a90001002d149f03aa00cdf7099cb551a927f1d0ce0ccd4ed7fa2500000 (36 bytes) - 0005780
2025-10-17 08:26:33.764 AMDRIVER « [REQ] [SendDataBridge] - callback id: 87 - transmit status: NoAck, took 28120 ms - repeater node IDs: 155, 35 - routing attempts: 1 - protocol & route speed: Z-Wave, 9.6 kbit/s - routing scheme: LWR - TX channel no.: 1
2025-10-17 08:26:33.760 AMSERIAL » [ACK] (0x06)
2025-10-17 08:26:33.758 AMSERIAL « 0x011d00a957010afc027f7f7f7f7f0001039b230000010100007f7f7f7f7f53 (31 bytes)
2025-10-17 08:26:25.450 AMSERIAL « [ACK] (0x06)
2025-10-17 08:26:25.448 AMDRIVER » [REQ] [SendDataAbort]
2025-10-17 08:26:25.446 AMSERIAL » 0x01030016ea (5 bytes)
2025-10-17 08:26:05.442 AMDRIVER « [RES] [SendDataBridge] - was sent: true
2025-10-17 08:26:05.439 AMSERIAL » [ACK] (0x06)
2025-10-17 08:26:05.437 AMSERIAL « 0x010401a90152 (6 bytes)
2025-10-17 08:26:05.432 AMSERIAL « [ACK] (0x06)
2025-10-17 08:26:05.431 AMDRIVER » [Node 045] [REQ] [SendDataBridge] - │ source node id: 1 - │ transmit options: 0x25 - │ callback id: 87 - └─[Security2CCMessageEncapsulation] - │ sequence number: 170 - │ security class: S2_Authenticated - └─[SupervisionCCGet] - │ session id: 45 - │ request updates: true - └─[MultilevelSwitchCCSet] - target value: 50
2025-10-17 08:26:05.417 AMCNTRLR Switching to 16-bit node IDs successful
2025-10-17 08:26:05.414 AMDRIVER « [RES] [SerialAPISetup] - command: SetNodeIDType - success: true
2025-10-17 08:26:05.410 AMSERIAL « 0x0105010b800171 (7 bytes)
2025-10-17 08:26:05.407 AMSERIAL « [ACK] (0x06)
2025-10-17 08:26:05.402 AMDRIVER » [REQ] [SerialAPISetup] - command: SetNodeIDType - node ID type: 16 bit
2025-10-17 08:26:05.398 AMSERIAL » 0x0105000b800273 (7 bytes)
2025-10-17 08:26:05.396 AMDRIVER one or more queues busy
2025-10-17 08:26:05.392 AMCNTRLR The controller is no longer unresponsive
2025-10-17 08:26:05.348 AMCNTRLR reconnected and restarted
2025-10-17 08:26:05.344 AMDRIVER « [REQ] [SerialAPIStarted] - wake up reason: SoftwareReset - watchdog enabled: false - generic device class: 0x02 - specific device class: 0x07 - always listening: false - supports Long Range: true
2025-10-17 08:26:05.341 AMSERIAL » [ACK] (0x06)
2025-10-17 08:26:05.339 AMSERIAL « 0x0118000a07000302070a5e5556226c748a8f989f01031d00009c (26 bytes)
2025-10-17 08:26:05.207 AMDRIVER all queues idle
2025-10-17 08:26:05.206 AMCNTRLR Waiting for the controller to reconnect...
2025-10-17 08:26:05.199 AMSERIAL « [ACK] (0x06)
2025-10-17 08:26:05.196 AMDRIVER » [REQ] [SoftReset]
2025-10-17 08:26:05.193 AMSERIAL » 0x01030008f4 (5 bytes)
2025-10-17 08:26:05.187 AMCNTRLR Performing soft reset...
2025-10-17 08:26:05.183 AMCNTRLR The controller is unresponsive
2025-10-17 08:25:55.188 AMDRIVER » [REQ] [SendDataAbort]
Z-Wave Details is clear of ghosts, I do have one Aeotec Minimote that is paired but not connected, has been that way for ages on ZipGateway w/out issues. Battery operated so not an issue AFAIK.
