Zooz ZEN72 interview fails repeatedly

Added a new Zooz ZEN72 to the network. Device is recognized, but fails during the interview. I’ve retried multiple times, each with the same failure on parameter #9. Log output below. FWIW, I have 2 other ZEN72 devices I added a few weeks ago that are working fine. Wonder if a recent change might have broken something.

2022-05-26T03:31:54.113Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T03:31:54.114Z DRIVER « [Node 053] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -81 dBm
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_NoSPAN
2022-05-26T03:31:54.114Z CNTRLR   [Node 053] No SPAN is established yet, cannot decode command.
2022-05-26T03:31:54.129Z SERIAL « 0x011e00a8000135159f03a800b10d66d903c477c54d385372dfe2fdc17500afa5  (32 bytes)
2022-05-26T03:31:54.130Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T03:31:54.131Z DRIVER « [Node 053] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -81 dBm
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_NoSPAN
2022-05-26T03:31:54.131Z CNTRLR   [Node 053] No SPAN is established yet, cannot decode command.
2022-05-26T03:31:54.144Z SERIAL « 0x011d00a8000135149f03a90081967995bd653abff07189f82156f39c00b0a1    (31 bytes)
2022-05-26T03:31:54.144Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T03:31:54.145Z DRIVER « [Node 053] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -80 dBm
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_NoSPAN
2022-05-26T03:31:54.145Z CNTRLR   [Node 053] No SPAN is established yet, cannot decode command.
2022-05-26T03:31:54.204Z SERIAL » 0x012e00a90135229f03a20112412e66e5ad49bd4210dac80fbe9a468730d2d5088 (48 bytes)
                                  5ec904c025eaf62f42500000000b422
2022-05-26T03:31:54.205Z DRIVER » [Node 053] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      180
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 162
                                    │ extensions:
                                    │ · type: SPAN
                                    │   sender EI: 0x2e66e5ad49bd4210dac80fbe9a468730
                                    └─[ConfigurationCCPropertiesGet]
                                        parameter #: 9
2022-05-26T03:31:54.220Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T03:31:54.221Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-05-26T03:31:54.221Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T03:31:54.222Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-05-26T03:31:54.236Z SERIAL « 0x011d00a9b400000100af7f7f7f7f00000300000000030100007f7f7f7f7f2f    (31 bytes)
2022-05-26T03:31:54.237Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T03:31:54.237Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            180
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    ACK RSSI:               -81 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0
2022-05-26T03:31:54.239Z SERIAL » 0x012000a90135149f02a3016df473b52fce86c31e8100405083c3be0500000000b (34 bytes)
                                  553
2022-05-26T03:31:54.240Z DRIVER » [Node 053] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x05
                                  │ callback id:      181
                                  └─[Security2CCNonceReport]
                                      sequence number:  163
                                      SOS:              true
                                      MOS:              false
                                      receiver entropy: 0x6df473b52fce86c31e8100405083c3be
2022-05-26T03:31:54.247Z SERIAL « 0x011d00a8000135149f02aa01b9a431a8c8ff3977ad5f4893f462373d00aeba    (31 bytes)
2022-05-26T03:31:54.248Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T03:31:54.248Z DRIVER « [Node 053] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -82 dBm
                                  └─[Security2CCNonceReport]
                                      sequence number:  170
                                      SOS:              true
                                      MOS:              false
                                      receiver entropy: 0xb9a431a8c8ff3977ad5f4893f462373d
2022-05-26T03:31:54.249Z CNTRLR   [Node 053] failed to decode the message after re-transmission with SPAN extens
                                  ion, dropping the message.
2022-05-26T03:31:54.250Z CNTRLR   [Node 053] Failed all interview attempts, giving up.
2022-05-26T03:31:54.251Z SERIAL « [CAN]                                                                   (0x18)
2022-05-26T03:31:54.252Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-05-26T03:31:54.353Z SERIAL » 0x012000a90135149f02a3016df473b52fce86c31e8100405083c3be0500000000b (34 bytes)
                                  553
2022-05-26T03:31:54.353Z DRIVER » [Node 053] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x05
                                  │ callback id:      181
                                  └─[Security2CCNonceReport]
                                      sequence number:  163
                                      SOS:              true
                                      MOS:              false
                                      receiver entropy: 0x6df473b52fce86c31e8100405083c3be
2022-05-26T03:31:54.376Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T03:31:54.377Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-05-26T03:31:54.378Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T03:31:54.378Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-05-26T03:31:54.392Z SERIAL « 0x011d00a9b500000100af7f7f7f7f00000300000000030100007f7f7f7f7f2e    (31 bytes)
2022-05-26T03:31:54.393Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T03:31:54.393Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            181
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    ACK RSSI:               -81 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0

I am far, far from an expert, but I recently had exactly the same thing happen here. I manually turned the switch on and off and many minutes later it finally showed up on the UI.

It’s been hours and no change so far.

Another day, still seeing the same failure. I have been exchanging emails with Zooz support. There were no immediate “AHA!” moments, still in dialog with them.

I successfully paired a motion sensor today, and everything else on the network is working fine. Seems unlikely that it’s a systemic problem.

I tried healing the node and it was successful in a few seconds. Re-interview after that failed in exactly the same way.

After 4 days, the problem cured itself overnight. I assume the interview process was continuing in the background and succeeded at some point. I’m concerned that there’s still an underlying problem, but have no clue how to diagnose it.