You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally, something like this will happen to one of my nodes:
2022-10-02T16:50:44.318Z SERIAL « 0x010b00040044056c0228ff0008 (13 bytes)
2022-10-02T16:50:44.319Z SERIAL » [ACK] (0x06)
2022-10-02T16:50:44.320Z DRIVER « [Node 068] [REQ] [ApplicationCommand]
└─[SupervisionCCReport]
session id: 40
more updates follow: false
status: Success
duration: 0s
2022-10-02T16:50:44.321Z CNTRLR « [Node 068] Received update for a Supervision session
2022-10-02T16:50:44.322Z CNTRLR [Node 068] [~] [Multilevel Switch] currentValue: 99 => 0 [Endpoint 0]
2022-10-02T16:50:44.349Z SERIAL » 0x010e001344076c01ad03260104251773 (16 bytes)
2022-10-02T16:50:44.350Z DRIVER » [Node 068] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 23
└─[SupervisionCCGet]
│ session id: 45
│ request updates: true
└─[MultilevelSwitchCCSet]
target value: 4
2022-10-02T16:50:44.351Z SERIAL « [ACK] (0x06)
2022-10-02T16:50:44.357Z SERIAL « 0x0104011301e8 (6 bytes)
2022-10-02T16:50:44.358Z SERIAL » [ACK] (0x06)
2022-10-02T16:50:44.358Z DRIVER « [RES] [SendData]
was sent: true
2022-10-02T16:50:44.431Z SERIAL « 0x010b0004004405260300000094 (13 bytes)
2022-10-02T16:50:44.432Z SERIAL » [ACK] (0x06)
2022-10-02T16:50:44.432Z CNTRLR [Node 068] [~] [Multilevel Switch] targetValue: 0 => 0 [Endpoint 0]
2022-10-02T16:50:44.436Z CNTRLR [Node 068] [~] [Multilevel Switch] duration: {"value":0,"unit":"s [Endpoint 0]
econds"} => {"value":0,"unit":"seconds"}
2022-10-02T16:50:44.438Z CNTRLR [Node 068] [~] [Multilevel Switch] currentValue: 0 => 0 [Endpoint 0]
2022-10-02T16:50:44.439Z DRIVER « [Node 068] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0
target value: 0
duration: 0s
2022-10-02T16:50:44.502Z SERIAL « 0x010700131700000ff3 (9 bytes)
2022-10-02T16:50:44.502Z SERIAL » [ACK] (0x06)
2022-10-02T16:50:44.503Z DRIVER « [REQ] [SendData]
callback id: 23
transmit status: OK
2022-10-02T16:50:45.663Z CNTRLR [Node 068] Timed out while waiting for a response from the node (ZW0201)
2022-10-02T16:50:45.663Z CNTRLR [Node 068] [~] [Multilevel Switch] currentValue: 0 => 4 [Endpoint 0]
Is there a way to get Zwave JS to retry this failed command instead of just giving up after timeout?
The issue seems to happen mostly when I trigger multiple requests in a short time (such as lowering all of my blinds simultaneously), which implies that network is sometimes too chatty to get all commands through. But if the last command was repeated after the chatter has subsided, it should have gone through.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Occasionally, something like this will happen to one of my nodes:
Is there a way to get Zwave JS to retry this failed command instead of just giving up after timeout?
The issue seems to happen mostly when I trigger multiple requests in a short time (such as lowering all of my blinds simultaneously), which implies that network is sometimes too chatty to get all commands through. But if the last command was repeated after the chatter has subsided, it should have gone through.
Beta Was this translation helpful? Give feedback.
All reactions