NICE IBT4 (gate controller) errors

[devachnid]

I have the NICE IBT4ZWAVE BUS-T4 controller, and have successfully included the device (S2 authenticated), and it is visible and alive in Home Assistant.

The issue I have is when I active it (to open the gate), the motor is not activated. In the logs I can see "failed":

2022-06-22T12:58:33.423Z DRIVER » [Node 055] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      54
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 6
                                    └─[SupervisionCCGet]
                                      │ session id:      11
                                      │ request updates: true
                                      └─[MultilevelSwitchCCSet]
                                          target value: 98
                                          duration:     default
2022-06-22T12:58:33.431Z SERIAL « [ACK]                                                                   (0x06)
2022-06-22T12:58:33.436Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-06-22T12:58:33.437Z SERIAL » [ACK]                                                                   (0x06)
2022-06-22T12:58:33.438Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-06-22T12:58:33.468Z SERIAL « 0x011d00a93600000301a87f7f7f7f00000307000000030100007f7f7f7f7fae    (31 bytes)
2022-06-22T12:58:33.470Z SERIAL » [ACK]                                                                   (0x06)
2022-06-22T12:58:33.471Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            54
                                    transmit status:        OK, took 30 ms
                                    repeater node IDs:      7
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    ACK RSSI:               -88 dBm
                                    ACK RSSI on repeaters:  N/A
                                    ACK channel no.:        0
                                    TX channel no.:         0
2022-06-22T12:58:33.549Z SERIAL « 0x011d00a8000137149f0200010e59f86c0d57a33b4c91be28d7b661f600a8e0    (31 bytes)
2022-06-22T12:58:33.550Z SERIAL » [ACK]                                                                   (0x06)
2022-06-22T12:58:33.551Z DRIVER « [Node 055] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -88 dBm
                                  └─[Security2CCNonceReport]
                                      sequence number:  0
                                      SOS:              true
                                      MOS:              false
                                      receiver entropy: 0x0e59f86c0d57a33b4c91be28d7b661f6
**2022-06-22T12:58:33.553Z CNTRLR   [Node 055] failed to decode the message, retrying with SPAN extension...**
2022-06-22T12:58:33.557Z SERIAL » 0x013200a90137269f030701124194567f59a4613932b48f6c5b96a1cdf9b4fc70b (52 bytes)
                                  e9d6de4312f2fb76ef265fb8825000000003714
2022-06-22T12:58:33.558Z DRIVER » [Node 055] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      55
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 7
                                    │ extensions:
                                    │ · type: SPAN
                                    │   sender EI: 0x94567f59a4613932b48f6c5b96a1cdf9
                                    └─[SupervisionCCGet]
                                      │ session id:      11
                                      │ request updates: true
                                      └─[MultilevelSwitchCCSet]
                                          target value: 98
                                          duration:     default
2022-06-22T12:58:33.567Z SERIAL « [ACK]                                                                   (0x06)
2022-06-22T12:58:33.569Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-06-22T12:58:33.570Z SERIAL » [ACK]                                                                   (0x06)
2022-06-22T12:58:33.573Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-06-22T12:58:33.670Z SERIAL « 0x011d00a93700000901a87f7f7f7f00000307000000030100007f7f7f7f7fa5    (31 bytes)
2022-06-22T12:58:33.671Z SERIAL » [ACK]                                                                   (0x06)
2022-06-22T12:58:33.674Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            55
                                    transmit status:        OK, took 90 ms
                                    repeater node IDs:      7
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    ACK RSSI:               -88 dBm
                                    ACK RSSI on repeaters:  N/A
                                    ACK channel no.:        0
                                    TX channel no.:         0
2022-06-22T12:58:33.751Z SERIAL « 0x011a00a8000137119f0301005f98b4c87c19c5cac03dc8eb1500a845          (28 bytes)
2022-06-22T12:58:33.752Z SERIAL » [ACK]                                                                   (0x06)
2022-06-22T12:58:33.753Z DRIVER « [Node 055] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -88 dBm
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 1
                                    └─[SupervisionCCReport]
                                        session id:          11
                                        more updates follow: false
                                        **status:              Fail**
                                        duration:            0s

Diagnostic log: zwave_js-dd1cda8da4696afeceb45843baadb85a-BusT4-Z-Wave interface-b916d98329dbaeb0f381a7f3136dc419.json.txt

[AlCalzone]

The first thing you highlighted is (assuming there was not more context before this log snippet that you cut off) is the node telling zwave-js "I cannot decode your last message". Z-Wave JS then re-transmits it, with additional info to re-sync the encryption state. This can happen, nothing to worry about usually.

The second thing you highlighted is the node telling zwave-js "I could not execute your last command", in this case opening the gate. Unfortunately that doesn't tell us why, but the issue definitely seem to be on the device side. Z-Wave communication seems to be working as intended.