[Bug]: all devices goes unavailable when high load

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Zwavejs2Mqtt version
6.9.0
ZwaveJS version
9.2.1
Describe the bug
When there is heavy load, multiple activities like all light off, lock all doors etc zwave is making all my devices unavailable, after some time or if i ping them they are coming back online.
It might be node 25 that is a ID-Lock that has issues,
i am using zstick gen 7 with latest firmware
To Reproduce
fire multiple events
Expected behavior
consisten network behaviour
Additional context
2022-05-07T12:59:14.874Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:15.187Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:27.077Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:28.451Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:29.934Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:30.225Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:30.359Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:30.571Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:30.603Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:30.668Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:30.754Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:31.040Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:31.090Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:31.122Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:31.297Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:31.783Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:32.014Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:32.214Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:32.422Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:32.889Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:33.028Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:33.233Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:34.154Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:34.420Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:34.754Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:35.267Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:35.639Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.010Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.107Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.172Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:36.218Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.321Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.432Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.492Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:36.510Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.530Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.592Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.636Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.651Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.667Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:36.752Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:36.943Z DRIVER   Dropping message with invalid payload
2022-05-07T12:59:37.487Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:43.620Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:43.646Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:43.691Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:43.844Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:44.116Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:44.389Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:48.160Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:48.240Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:48.319Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:48.473Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:48.624Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:48.775Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:48.903Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:49.216Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:49.530Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:49.866Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:50.038Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:50.351Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:50.723Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:50.831Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:51.071Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:51.774Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:51.984Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.056Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.200Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.237Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.250Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.293Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.307Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.340Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.400Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.410Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.527Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.550Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.579Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.606Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:52.617Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:57.989Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:58.052Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:58.077Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:58.230Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:58.502Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:58.712Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:58.840Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:58.944Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:59.257Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T12:59:59.865Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:00:00.108Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:00:00.212Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:00:00.584Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:00:00.827Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:00:01.002Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:00:01.494Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:00:01.764Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:00:01.854Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:00:01.926Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:00:30.518Z CNTRLR   [Node 012] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:31.035Z CNTRLR   [Node 012] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:31.553Z CNTRLR   [Node 012] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:31.580Z CNTRLR   [Node 025] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:31.599Z CNTRLR   [Node 026] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:32.115Z CNTRLR   [Node 026] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:32.632Z CNTRLR   [Node 026] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:32.649Z CNTRLR   [Node 014] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:33.165Z CNTRLR   [Node 014] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:33.681Z CNTRLR   [Node 014] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:33.710Z CNTRLR   [Node 015] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:34.226Z CNTRLR   [Node 015] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:34.753Z CNTRLR   [Node 015] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:34.780Z CNTRLR   [Node 004] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:35.296Z CNTRLR   [Node 004] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:35.814Z CNTRLR   [Node 004] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:35.844Z CNTRLR   [Node 007] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:36.359Z CNTRLR   [Node 007] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:36.875Z CNTRLR   [Node 007] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:36.900Z CNTRLR   [Node 002] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:37.415Z CNTRLR   [Node 002] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:37.931Z CNTRLR   [Node 002] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:37.955Z CNTRLR   [Node 002] The node did not respond after 1 attempts, it is presumed dead
2022-05-07T13:00:37.975Z CNTRLR   [Node 005] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:38.490Z CNTRLR   [Node 005] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:39.006Z CNTRLR   [Node 005] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:39.032Z CNTRLR   [Node 005] The node did not respond after 1 attempts, it is presumed dead
2022-05-07T13:00:39.053Z CNTRLR   [Node 009] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:39.568Z CNTRLR   [Node 009] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:40.084Z CNTRLR   [Node 009] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:40.109Z CNTRLR   [Node 008] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:40.625Z CNTRLR   [Node 008] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-05-07T13:00:41.145Z CNTRLR   [Node 008] The node did not respond after 3 attempts, it is presumed dead
2022-05-07T13:00:41.170Z CNTRLR   [Node 005] The node did not respond after 1 attempts, it is presumed dead
2022-05-07T13:00:54.161Z DRIVER     no handlers registered!
2022-05-07T13:23:17.677Z DRIVER   Dropping message with invalid payload
2022-05-07T13:23:17.709Z DRIVER   Dropping message with invalid payload
2022-05-07T13:23:47.340Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport
2022-05-07T13:23:47.385Z CNTRLR   [Node 025] in the process of replying to a NonceGet, won't send another NonceR
eport

2022-05-07T20:02:49.601Z SERIAL « 0x010b00a800011202840700b27c                                        (13 bytes) 2022-05-07T20:02:49.601Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:02:49.602Z DRIVER « [Node 018] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -78 dBm                                   └─[WakeUpCCWakeUpNotification] 2022-05-07T20:02:49.602Z CNTRLR « [Node 018] received wakeup notification 2022-05-07T20:02:49.603Z CNTRLR   [Node 018] The node is now awake. 2022-05-07T20:02:50.604Z CNTRLR » [Node 018] Sending node back to sleep... 2022-05-07T20:02:50.610Z SERIAL » 0x010e00a90112028408250000000026c6                                  (16 bytes) 2022-05-07T20:02:50.611Z DRIVER » [Node 018] [REQ] [SendDataBridge]                                   │ source node id:   1                                   │ transmit options: 0x25                                   │ callback id:      38                                   └─[WakeUpCCNoMoreInformation] 2022-05-07T20:02:50.616Z SERIAL « [ACK]                                                                   (0x06) 2022-05-07T20:02:50.617Z SERIAL « 0x010401a90152                                                       (6 bytes) 2022-05-07T20:02:50.618Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:02:50.618Z DRIVER « [RES] [SendDataBridge]                                     was sent: true 2022-05-07T20:02:50.744Z SERIAL « 0x011d00a92600000c01b37f7f7f7f02010302000000010100007f7f7f7f7fae    (31 bytes) 2022-05-07T20:02:50.744Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:02:50.745Z DRIVER « [REQ] [SendDataBridge]                                     callback id:            38                                     transmit status:        OK, took 120 ms                                     repeater node IDs:      2                                     routing attempts:       1                                     protocol & route speed: Z-Wave, 9.6 kbit/s                                     ACK RSSI:               -77 dBm                                     ACK RSSI on repeaters:  N/A                                     ACK channel no.:        2                                     TX channel no.:         1 2022-05-07T20:02:50.750Z CNTRLR   [Node 018] The node is now asleep. 2022-05-07T20:03:11.582Z SERIAL « 0x011300a80001060a600d010131050422000000b187                        (21 bytes) 2022-05-07T20:03:11.583Z CNTRLR   [Node 006] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:03:11.584Z CNTRLR   [Node 006] [~] [Multilevel Sensor] Power: 0 => 0                  [Endpoint 1] 2022-05-07T20:03:11.585Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:03:11.586Z DRIVER « [Node 006] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -79 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 0 2022-05-07T20:05:27.759Z SERIAL « 0x011700a80001140e600d0101320221440000062f000000b3f9                (25 bytes) 2022-05-07T20:05:27.761Z CNTRLR   [Node 020] [~] [Meter] value[65537]: 15.83 => 15.83               [Endpoint 1] 2022-05-07T20:05:27.762Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:05:27.762Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -77 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MeterCCReport]                                         type:       Electric                                         scale:      kWh                                         rate type:  Consumed                                         value:      15.83                                         time delta: 0 seconds 2022-05-07T20:07:18.423Z SERIAL « 0x011300a80001130a600d010131050422000000bd9e                        (21 bytes) 2022-05-07T20:07:18.424Z CNTRLR   [Node 019] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:07:18.425Z CNTRLR   [Node 019] [~] [Multilevel Sensor] Power: 0 => 0                  [Endpoint 1] 2022-05-07T20:07:18.426Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:07:18.426Z DRIVER « [Node 019] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -67 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 0 2022-05-07T20:09:35.298Z SERIAL « 0x011700a800010b0e600d01013202214400000f0e000000a9d4                (25 bytes) 2022-05-07T20:09:35.299Z CNTRLR   [Node 011] [~] [Meter] value[65537]: 38.54 => 38.54               [Endpoint 1] 2022-05-07T20:09:35.300Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:09:35.301Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MeterCCReport]                                         type:       Electric                                         scale:      kWh                                         rate type:  Consumed                                         value:      38.54                                         time delta: 0 seconds 2022-05-07T20:09:35.481Z SERIAL « 0x011700a800010b0e600d01013202214400000f0e000000a9d4                (25 bytes) 2022-05-07T20:09:35.482Z CNTRLR   [Node 011] [~] [Meter] value[65537]: 38.54 => 38.54               [Endpoint 1] 2022-05-07T20:09:35.482Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:09:35.482Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MeterCCReport]                                         type:       Electric                                         scale:      kWh                                         rate type:  Consumed                                         value:      38.54                                         time delta: 0 seconds 2022-05-07T20:09:35.945Z SERIAL « 0x011700a800010b0e600d01013202214400000f0e000000aad7                (25 bytes) 2022-05-07T20:09:35.945Z CNTRLR   [Node 011] [~] [Meter] value[65537]: 38.54 => 38.54               [Endpoint 1] 2022-05-07T20:09:35.946Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:09:35.946Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -86 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MeterCCReport]                                         type:       Electric                                         scale:      kWh                                         rate type:  Consumed                                         value:      38.54                                         time delta: 0 seconds 2022-05-07T20:09:36.198Z SERIAL « 0x011700a800010b0e600d01013202214400000f0e000000a9d4                (25 bytes) 2022-05-07T20:09:36.199Z CNTRLR   [Node 011] [~] [Meter] value[65537]: 38.54 => 38.54               [Endpoint 1] 2022-05-07T20:09:36.200Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:09:36.201Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MeterCCReport]                                         type:       Electric                                         scale:      kWh                                         rate type:  Consumed                                         value:      38.54                                         time delta: 0 seconds 2022-05-07T20:10:21.970Z SERIAL « 0x011700a80001060e600d0101320221440000060f000000b0c8                (25 bytes) 2022-05-07T20:10:21.971Z CNTRLR   [Node 006] [~] [Meter] value[65537]: 15.51 => 15.51               [Endpoint 1] 2022-05-07T20:10:21.972Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:10:21.972Z DRIVER « [Node 006] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -80 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MeterCCReport]                                         type:       Electric                                         scale:      kWh                                         rate type:  Consumed                                         value:      15.51                                         time delta: 0 seconds 2022-05-07T20:15:59.120Z SERIAL « 0x011700a80001070e600d01013202214400002157000000b3b5                (25 bytes) 2022-05-07T20:15:59.121Z CNTRLR   [Node 007] [~] [Meter] value[65537]: 85.35 => 85.35               [Endpoint 1] 2022-05-07T20:15:59.122Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:15:59.123Z DRIVER « [Node 007] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -77 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MeterCCReport]                                         type:       Electric                                         scale:      kWh                                         rate type:  Consumed                                         value:      85.35                                         time delta: 0 seconds 2022-05-07T20:16:53.949Z SERIAL » 0x011400a9010e08600d0001260100ff250000000027f3                      (22 bytes) 2022-05-07T20:16:53.950Z DRIVER » [Node 014] [REQ] [SendDataBridge]                                   │ source node id:   1                                   │ transmit options: 0x25                                   │ callback id:      39                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      0                                     │ destination: 1                                     └─[MultilevelSwitchCCSet]                                         target value: 0                                         duration:     default 2022-05-07T20:16:53.956Z SERIAL « [ACK]                                                                   (0x06) 2022-05-07T20:16:53.957Z SERIAL « 0x010401a90152                                                       (6 bytes) 2022-05-07T20:16:53.957Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:16:53.958Z DRIVER « [RES] [SendDataBridge]                                     was sent: true 2022-05-07T20:16:53.973Z SERIAL « 0x011d00a92700000100ad7f7f7f7f00000300000000030100007f7f7f7f7fbe    (31 bytes) 2022-05-07T20:16:53.973Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:16:53.974Z DRIVER « [REQ] [SendDataBridge]                                     callback id:            39                                     transmit status:        OK, took 10 ms                                     routing attempts:       1                                     protocol & route speed: Z-Wave, 100 kbit/s                                     ACK RSSI:               -83 dBm                                     ACK channel no.:        0                                     TX channel no.:         0 2022-05-07T20:16:53.977Z CNTRLR   [Node 014] [~] [Multilevel Switch] currentValue: 32 => 0          [Endpoint 1] 2022-05-07T20:16:54.312Z SERIAL « 0x011000a800010e07600d010126030000acab                              (18 bytes) 2022-05-07T20:16:54.313Z CNTRLR   [Node 014] [~] [Multilevel Switch] currentValue: 0 => 0           [Endpoint 1] 2022-05-07T20:16:54.313Z CNTRLR   [Node 014] Scheduled poll canceled because expected value was received 2022-05-07T20:16:54.314Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:16:54.316Z DRIVER « [Node 014] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -84 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSwitchCCReport]                                         current value: 0 2022-05-07T20:16:55.202Z SERIAL « 0x011300a800010e0a600d010131050422001a00ad89                        (21 bytes) 2022-05-07T20:16:55.203Z CNTRLR   [Node 014] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:16:55.203Z CNTRLR   [Node 014] [~] [Multilevel Sensor] Power: 11.4 => 2.6             [Endpoint 1] 2022-05-07T20:16:55.204Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:16:55.205Z DRIVER « [Node 014] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -83 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.6 2022-05-07T20:16:59.450Z SERIAL » 0x011400a9010c08600d0001260101ff250000000028ff                      (22 bytes) 2022-05-07T20:16:59.451Z DRIVER » [Node 012] [REQ] [SendDataBridge]                                   │ source node id:   1                                   │ transmit options: 0x25                                   │ callback id:      40                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      0                                     │ destination: 1                                     └─[MultilevelSwitchCCSet]                                         target value: 1                                         duration:     default 2022-05-07T20:16:59.457Z SERIAL « [ACK]                                                                   (0x06) 2022-05-07T20:16:59.457Z SERIAL « 0x010401a90152                                                       (6 bytes) 2022-05-07T20:16:59.458Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:16:59.458Z DRIVER « [RES] [SendDataBridge]                                     was sent: true 2022-05-07T20:16:59.495Z SERIAL « 0x011d00a92800000301a57f7f7f7f00000304000000030100007f7f7f7f7fbe    (31 bytes) 2022-05-07T20:16:59.495Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:16:59.496Z DRIVER « [REQ] [SendDataBridge]                                     callback id:            40                                     transmit status:        OK, took 30 ms                                     repeater node IDs:      4                                     routing attempts:       1                                     protocol & route speed: Z-Wave, 100 kbit/s                                     ACK RSSI:               -91 dBm                                     ACK RSSI on repeaters:  N/A                                     ACK channel no.:        0                                     TX channel no.:         0 2022-05-07T20:16:59.498Z CNTRLR   [Node 012] [~] [Multilevel Switch] currentValue: 5 => 1           [Endpoint 1] 2022-05-07T20:16:59.569Z SERIAL « 0x011000a800010c07600d010126030100a6a2                              (18 bytes) 2022-05-07T20:16:59.570Z CNTRLR   [Node 012] [~] [Multilevel Switch] currentValue: 1 => 1           [Endpoint 1] 2022-05-07T20:16:59.570Z CNTRLR   [Node 012] Scheduled poll canceled because expected value was received 2022-05-07T20:16:59.570Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:16:59.572Z DRIVER « [Node 012] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -90 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSwitchCCReport]                                         current value: 1 2022-05-07T20:17:00.734Z SERIAL « 0x011300a800010c0a600d010131050422000e00a694                        (21 bytes) 2022-05-07T20:17:00.735Z CNTRLR   [Node 012] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:00.735Z CNTRLR   [Node 012] [~] [Multilevel Sensor] Power: 1.8 => 1.4              [Endpoint 1] 2022-05-07T20:17:00.736Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:00.736Z DRIVER « [Node 012] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -90 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 1.4 2022-05-07T20:17:01.571Z SERIAL » 0x011400a9010b08600d0001260101ff250000000029f9                      (22 bytes) 2022-05-07T20:17:01.571Z DRIVER » [Node 011] [REQ] [SendDataBridge]                                   │ source node id:   1                                   │ transmit options: 0x25                                   │ callback id:      41                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      0                                     │ destination: 1                                     └─[MultilevelSwitchCCSet]                                         target value: 1                                         duration:     default 2022-05-07T20:17:01.577Z SERIAL « [ACK]                                                                   (0x06) 2022-05-07T20:17:01.578Z SERIAL « 0x010401a90152                                                       (6 bytes) 2022-05-07T20:17:01.578Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:01.581Z DRIVER « [RES] [SendDataBridge]                                     was sent: true 2022-05-07T20:17:01.722Z SERIAL « 0x011d00a92900000e01a97f7f7f7f02010303000000010100007f7f7f7f7fb8    (31 bytes) 2022-05-07T20:17:01.723Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:01.723Z DRIVER « [REQ] [SendDataBridge]                                     callback id:            41                                     transmit status:        OK, took 140 ms                                     repeater node IDs:      3                                     routing attempts:       1                                     protocol & route speed: Z-Wave, 9.6 kbit/s                                     ACK RSSI:               -87 dBm                                     ACK RSSI on repeaters:  N/A                                     ACK channel no.:        2                                     TX channel no.:         1 2022-05-07T20:17:01.725Z CNTRLR   [Node 011] [~] [Multilevel Switch] currentValue: 5 => 1           [Endpoint 1] 2022-05-07T20:17:02.117Z SERIAL « 0x011000a800010b07600d010126030100aaa9                              (18 bytes) 2022-05-07T20:17:02.118Z CNTRLR   [Node 011] [~] [Multilevel Switch] currentValue: 1 => 1           [Endpoint 1] 2022-05-07T20:17:02.118Z CNTRLR   [Node 011] Scheduled poll canceled because expected value was received 2022-05-07T20:17:02.119Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:02.119Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -86 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSwitchCCReport]                                         current value: 1 2022-05-07T20:17:02.668Z SERIAL « 0x011300a800010b0a600d010131050422001a00a988                        (21 bytes) 2022-05-07T20:17:02.669Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:02.669Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 3.4 => 2.6              [Endpoint 1] 2022-05-07T20:17:02.670Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:02.671Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.6 2022-05-07T20:17:02.849Z SERIAL « 0x011300a800010b0a600d010131050422001a00a988                        (21 bytes) 2022-05-07T20:17:02.849Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:02.850Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.6 => 2.6              [Endpoint 1] 2022-05-07T20:17:02.850Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:02.851Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.6 2022-05-07T20:17:03.028Z SERIAL « 0x011300a800010b0a600d010131050422001a00a988                        (21 bytes) 2022-05-07T20:17:03.029Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:03.029Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.6 => 2.6              [Endpoint 1] 2022-05-07T20:17:03.030Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:03.030Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.6 2022-05-07T20:17:04.731Z SERIAL « 0x011300a800010c0a600d010131050422000d00a697                        (21 bytes) 2022-05-07T20:17:04.733Z CNTRLR   [Node 012] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:04.733Z CNTRLR   [Node 012] [~] [Multilevel Sensor] Power: 1.4 => 1.3              [Endpoint 1] 2022-05-07T20:17:04.734Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:04.734Z DRIVER « [Node 012] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -90 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 1.3 2022-05-07T20:17:05.185Z SERIAL « 0x011300a800010e0a600d010131050422000000ad93                        (21 bytes) 2022-05-07T20:17:05.185Z CNTRLR   [Node 014] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:05.186Z CNTRLR   [Node 014] [~] [Multilevel Sensor] Power: 2.6 => 0                [Endpoint 1] 2022-05-07T20:17:05.186Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:05.187Z DRIVER « [Node 014] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -83 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 0 2022-05-07T20:17:07.672Z SERIAL « 0x011300a800010b0a600d010131050422001600a984                        (21 bytes) 2022-05-07T20:17:07.674Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:07.674Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.6 => 2.2              [Endpoint 1] 2022-05-07T20:17:07.675Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:07.676Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:07.922Z SERIAL « 0x011300a800010b0a600d010131050422001600a984                        (21 bytes) 2022-05-07T20:17:07.923Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:07.923Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:07.924Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:07.924Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:08.032Z SERIAL « 0x011300a800010b0a600d010131050422001600aa87                        (21 bytes) 2022-05-07T20:17:08.033Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:08.033Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:08.034Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:08.034Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -86 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:08.380Z SERIAL « 0x011300a800010b0a600d010131050422001600a984                        (21 bytes) 2022-05-07T20:17:08.381Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:08.381Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:08.382Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:08.382Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:08.561Z SERIAL « 0x011300a800010b0a600d010131050422001600a984                        (21 bytes) 2022-05-07T20:17:08.561Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:08.562Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:08.562Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:08.563Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:08.671Z SERIAL « 0x011300a800010b0a600d010131050422001600a984                        (21 bytes) 2022-05-07T20:17:08.672Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:08.672Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:08.672Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:08.673Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -87 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:09.470Z SERIAL « 0x011300a800010b0a600d01013105042200160098b5                        (21 bytes) 2022-05-07T20:17:09.471Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:09.472Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:09.472Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:09.473Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -104 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:09.559Z SERIAL « 0x011300a800010b0a600d010131050422001600a588                        (21 bytes) 2022-05-07T20:17:09.560Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:09.560Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:09.560Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:09.562Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -91 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:09.637Z SERIAL « 0x011300a800010b0a600d010131050422001600a68b                        (21 bytes) 2022-05-07T20:17:09.637Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:09.640Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:09.640Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:09.641Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -90 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:09.662Z SERIAL « 0x011300a800010b0a600d010131050422001600a68b                        (21 bytes) 2022-05-07T20:17:09.662Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:09.663Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:09.663Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:09.663Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -90 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:09.754Z SERIAL « 0x011300a800010b0a600d010131050422001600a588                        (21 bytes) 2022-05-07T20:17:09.755Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:09.755Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:09.756Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:09.756Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -91 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:09.836Z SERIAL « 0x011300a800010b0a600d010131050422001600a588                        (21 bytes) 2022-05-07T20:17:09.836Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:09.836Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:09.837Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:09.837Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -91 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:09.864Z SERIAL « 0x011300a800010b0a600d010131050422001600a588                        (21 bytes) 2022-05-07T20:17:09.865Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:09.865Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:09.866Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:09.866Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -91 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:09.975Z SERIAL « 0x011300a800010b0a600d010131050422001600b19c                        (21 bytes) 2022-05-07T20:17:09.975Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:09.975Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:09.976Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:09.976Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -79 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.035Z SERIAL « 0x011300a800010b0a600d010131050422001600b19c                        (21 bytes) 2022-05-07T20:17:10.035Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.036Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.036Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.036Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -79 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.060Z SERIAL « 0x011300a800010b0a600d010131050422001600b29f                        (21 bytes) 2022-05-07T20:17:10.060Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.061Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.061Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.061Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -78 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.280Z SERIAL « 0x011300a800010b0a600d010131050422001600b69b                        (21 bytes) 2022-05-07T20:17:10.281Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.281Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.281Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.282Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -74 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.362Z SERIAL « 0x011300a800010b0a600d010131050422001600b598                        (21 bytes) 2022-05-07T20:17:10.362Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.363Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.363Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.364Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -75 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.391Z SERIAL « 0x011300a800010b0a600d010131050422001600b598                        (21 bytes) 2022-05-07T20:17:10.391Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.391Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.392Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.392Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -75 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.627Z SERIAL « 0x011300a800010b0a600d0101310504220016009bb6                        (21 bytes) 2022-05-07T20:17:10.627Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.628Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.628Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.629Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ RSSI: -101 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.753Z SERIAL « 0x011300a814010b0a600d010131050422001600d4ed                        (21 bytes) 2022-05-07T20:17:10.753Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.754Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.754Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.755Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -44 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.787Z SERIAL « 0x011300a814010b0a600d010131050422001600d3ea                        (21 bytes) 2022-05-07T20:17:10.787Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.787Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.788Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.788Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -45 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.803Z SERIAL « 0x011300a814010b0a600d010131050422001600d2eb                        (21 bytes) 2022-05-07T20:17:10.804Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.804Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.805Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.806Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -46 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.821Z SERIAL « 0x011300a814010b0a600d010131050422001600d9e0                        (21 bytes) 2022-05-07T20:17:10.821Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.822Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.822Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.822Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -39 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:10.833Z SERIAL « 0x011300a814010b0a600d010131050422001600cef7                        (21 bytes) 2022-05-07T20:17:10.833Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:10.834Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:10.835Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:10.835Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -50 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:11.006Z SERIAL « 0x011300a814010b0a600d010131050422001600d2eb                        (21 bytes) 2022-05-07T20:17:11.007Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:11.007Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:11.008Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.008Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -46 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:11.123Z SERIAL « 0x011300a814010b0a600d010131050422001600dde4                        (21 bytes) 2022-05-07T20:17:11.124Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:11.125Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:11.125Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.126Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -35 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:11.171Z SERIAL « 0x011300a814010b0a600d010131050422001600d5ec                        (21 bytes) 2022-05-07T20:17:11.172Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:11.172Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:11.173Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.173Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -43 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:11.251Z SERIAL » 0x010f00a9011a039f015325000000002a83                                (17 bytes) 2022-05-07T20:17:11.251Z DRIVER » [Node 026] [REQ] [SendDataBridge]                                   │ source node id:   1                                   │ transmit options: 0x25                                   │ callback id:      42                                   └─[Security2CCNonceGet]                                       sequence number: 83 2022-05-07T20:17:11.252Z SERIAL « 0x011300a814010b0a600d010131050422001600d1e8                        (21 bytes) 2022-05-07T20:17:11.252Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:11.253Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:11.253Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.253Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -47 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:11.255Z SERIAL « [CAN]                                                                   (0x18) 2022-05-07T20:17:11.256Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i                                   n 100 ms. 2022-05-07T20:17:11.286Z SERIAL « 0x011300a814010b0a600d010131050422001600d5ec                        (21 bytes) 2022-05-07T20:17:11.286Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:11.287Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:11.287Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.288Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -43 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:11.357Z SERIAL » 0x010f00a9011a039f015325000000002a83                                (17 bytes) 2022-05-07T20:17:11.358Z DRIVER » [Node 026] [REQ] [SendDataBridge]                                   │ source node id:   1                                   │ transmit options: 0x25                                   │ callback id:      42                                   └─[Security2CCNonceGet]                                       sequence number: 83 2022-05-07T20:17:11.363Z SERIAL « [ACK]                                                                   (0x06) 2022-05-07T20:17:11.363Z SERIAL « 0x010401a90152                                                       (6 bytes) 2022-05-07T20:17:11.364Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.364Z DRIVER « [RES] [SendDataBridge]                                     was sent: true 2022-05-07T20:17:11.370Z SERIAL « 0x011d00a92a0200000000000000000000000000000000000000000000000063    (31 bytes) 2022-05-07T20:17:11.370Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.370Z DRIVER « [REQ] [SendDataBridge]                                     callback id:                           42                                     transmit status:                       Fail, took 0 ms                                     routing attempts:                      0                                     protocol & route speed:                Unknown (0x00)                                     ACK RSSI:                              0 dBm                                     ACK channel no.:                       0                                     TX channel no.:                        0                                     TX power:                              0 dBm                                     measured noise floor:                  0 dBm                                     ACK TX power by destination:           0 dBm                                     measured RSSI of ACK from destination: 0 dBm                                     measured noise floor by destination:   0 dBm 2022-05-07T20:17:11.373Z CNTRLR   [Node 026] The node did not respond after 3 attempts, it is presumed dead 2022-05-07T20:17:11.373Z CNTRLR   [Node 026] The node is now dead. 2022-05-07T20:17:11.380Z SERIAL « 0x011300a814010b0a600d010131050422001600d3ea                        (21 bytes) 2022-05-07T20:17:11.380Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:11.381Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:11.381Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.383Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -45 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:11.456Z SERIAL « 0x011300a814010b0a600d010131050422001600dde4                        (21 bytes) 2022-05-07T20:17:11.457Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:11.457Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:11.458Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.458Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -35 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:11.524Z SERIAL « 0x011300a814010b0a600d010131050422001600d1e8                        (21 bytes) 2022-05-07T20:17:11.524Z CNTRLR   [Node 011] [Multilevel Sensor] Power: metadata updated            [Endpoint 1] 2022-05-07T20:17:11.525Z CNTRLR   [Node 011] [~] [Multilevel Sensor] Power: 2.2 => 2.2              [Endpoint 1] 2022-05-07T20:17:11.525Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.526Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]                                   │ type:        broadcast                                   │ target node: 255                                   │ RSSI:        -47 dBm                                   └─[MultiChannelCCCommandEncapsulation]                                     │ source:      1                                     │ destination: 1                                     └─[MultilevelSensorCCReport]                                         type:  Power                                         scale: Watt                                         value: 2.2 2022-05-07T20:17:11.720Z SERIAL » 0x010e00a9011902984025000000002b94                                  (16 bytes) 2022-05-07T20:17:11.720Z DRIVER » [Node 025] [REQ] [SendDataBridge]                                   │ source node id:   1                                   │ transmit options: 0x25                                   │ callback id:      43                                   └─[SecurityCCNonceGet] 2022-05-07T20:17:11.725Z SERIAL « [ACK]                                                                   (0x06) 2022-05-07T20:17:11.726Z SERIAL « 0x010401a90152                                                       (6 bytes) 2022-05-07T20:17:11.726Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.727Z DRIVER « [RES] [SendDataBridge]                                     was sent: true 2022-05-07T20:17:11.732Z SERIAL « 0x011d00a92b0200000000000000000000000000000000000000000000000062    (31 bytes) 2022-05-07T20:17:11.732Z SERIAL » [ACK]                                                                   (0x06) 2022-05-07T20:17:11.733Z DRIVER « [REQ] [SendDataBridge]                                     callback id:                           43                                     transmit status:                       Fail, took 0 ms                                     routing attempts:                      0                                     protocol & route speed:                Unknown (0x00)                                     ACK RSSI:                              0 dBm                                     ACK channel no.:                       0                                     TX channel no.:                        0                                     TX power:                              0 dBm                                     measured noise floor:                  0 dBm                                     ACK TX power by destination:           0 dBm                                     measured RSSI of ACK from destination: 0 dBm                                     measured noise floor by destination:   0 dBm 2022-05-07T20:17:11.735Z CNTRLR   [Node 025] The node did not respond after 3 attempts, it is presumed dead 2022-05-07T20:17:11.735Z CNTRLR   [Node 025] The node is now dead.


Errors in the build process

When running the BuildProcess.exe it looks like Unit tests are failing,
although they run successfully in VS.

The error we see is the following:
....
'Google.Apis.Tests.Apis.Http.ConfigurableMessageHandlerTest.SendAsync_BackOffExc
eptionHandler_DontThrow'
   Google.Build.Tester:   Testing 'Google.Apis.Tests.Apis.Http.ConfigurableMessageHandlerTest.SendAsync_BackOffExceptionHandler_Throw_Max1Hour'
   Google.Build.Tester:     [CreateRequest_DeveloperKey]: FAILED!
   Google.Build.Tester:       System.IO.FileLoadException : Could not load file or assembly 'System.Net.Http.Primitives, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependenc
s. The located assembly's manifest definition does not match the assembly
reference. (Exception from HRESULT: 0x80131040)
   Google.Build.Tester:     [CreateRequest_DeveloperKey_RequiresEscape]: FAILED!
   Google.Build.Tester:       System.IO.FileLoadException : Could not load file or assembly 'System.Net.Http.Primitives, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependenc
s. The located assembly's manifest definition does not match the assembly
reference. (Exception from HRESULT: 0x80131040)
....

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 24 Jun 2013 at 8:35

buildprocess.exe is no longer required to build.


Revert "Noissue remove redundant depth param"

Reverts BIBSYSDEV/nva-cristin-service#412

Removed a query parameter which should not be removed as it actually was in use. Reverting the change


Horovod & py3.8

What does this PR do?
resolving Horovod as discussed in #2745
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

LGTM!  Thanks @Borda!

Surprisingly simple. LGTM 😄

yeah, we shall keep PR as simple as possible to the review is quick...


How do we want to give instructions for inputdata?

How should we properly instruct our team to reference the input-data folders in the run documentation?
Current instructions:
The first time, or whenever your $WORKDIR is cleaned, you need to link your working directory with your input data
[~/CTSM_ROOT]$ cd cime/scripts
[~/CTSM_ROOT/cime/scripts]$ ./link_dirtree $CESM_DATA /work/users/$USER/inputdata

I feel this is not following our recommended practices. Where do we distribute the link_dirtree-script?

Another argument for not keeping the link_dirtree in our document is that it is not supported anymore, as pointed out by @devarajun in #14.

The other way to instruct pointing out the input data in user_nl_clm. Maybe we need to come up with a better way instead of manually adding in user_nl_clm. How is it done for site simulations @huitang-earth?

@sunnivin, This is definitely a question for further discussion. Since link_tree is not supported anymore, I don't think we should use it. Instead, we should guide people to use the inputdata folders properly. Here are my suggestions:
(1) Global clm simulations: the inputdata will be "/cluster/shared/noresm/inputdata/". If there are some missing input, please contact someone (e.g., Kjetil or Sunniva or others) to put the data in place.
(2) Regional and single cell clm simulations: usually people have to generate the inputdata by themselves. So, we could suggest that they put all the inputdata in "/work/users/$USER/inputdata" for running the model, but for long-term storage, please copy the folder to either /cluster/projects/$project-number/ or NIRD.
Key thing here is that all the inputdata should have a backup after the simulation is done to make sure that the simulations are reproducible.

@sunnivin, This is definitely a question for further discussion. Since link_tree is not supported anymore, I don't think we should use it. Instead, we should guide people to use the inputdata folders properly. Here are my suggestions:
(1) Global clm simulations: the inputdata will be "/cluster/shared/noresm/inputdata/". If there are some missing input, please contact someone (e.g., Kjetil or Sunniva or others) to put the data in place.
(2) Regional and single cell clm simulations: usually people have to generate the inputdata by themselves. So, we could suggest that they put all the inputdata in "/work/users/$USER/inputdata" for running the model, but for long-term storage, please copy the folder to either /cluster/projects/$project-number/ or NIRD.
Key thing here is that all the inputdata should have a backup after the simulation is done to make sure that the simulations are reproducible.

I totally agree. I'm thinking that this is a good topic for our team-meeting tomorrow?

After discussing this topic at our weekly CTSM-Norway meeting we agreed that we will include the comments here made by @huitang-earth, and wait with finishing this feature until the NorESM-group has clarified how they would like to organize their group ownerships.


Support Time Index to support seeking based on time in reader interface.

Is your feature request related to a problem? Please describe.
Right now we can seek to earliest or latest. But we are not able seek based on time in the reader interface.
Describe the solution you'd like
In the reader interface, we can support time-based seek along with earliest and latest?
Describe alternatives you've considered
We are thinking of randomly picking a message id and trying to go to the nearest specified time by incrementing the ID.

One problem here would be that timestamps on messages aren't necessarily monotonically increasing, but there is a plan to fix that.


fish auto-completion

I'm trying to configure autocompletion but it seems not supported.
I'm not sure if it was removed, but here is the message:
> ~ kubectl completion fish
error: Unsupported shell type "fish".

If I try to update the kubectl as I thought it was my case:
⋊> ~ brew upgrade kubectl
Warning: kubectl 1.23.4 already installed

Indeed the completion help mention no support for fish:

kubectl completion -h                                                                    16:57:41
Output shell completion code for the specified shell (bash or zsh). The shell code must be evaluated
to provide interactive completion of kubectl commands.  This can be done by sourcing it from the
.bash_profile.

Was it removed? anything I missed?

/kind support

Hi @jonatas
Have you added kubectl completion fish to Fish's config i.e ~/.config/fish/config.fish (see here) and reloaded the shell.

Hello @anubha-v-ardhan, my problem is that it seems the completion for fish is not available. I tried and when I create a new tab in my terminal I see the same error in the output message.
 kubectl completion fish
 error: Unsupported shell type "fish".
See 'kubectl completion -h' for help and examples

@jonatas kubectl completion is supported for fish in v1.23.

kubectl completion -h 16:57:41
Output shell completion code for the specified shell (bash or zsh). The shell code must be evaluated
to provide interactive completion of kubectl commands. This can be done by sourcing it from the
.bash_profile.

Since kubectl completion -h is only showing us support for bash and zsh, my guess is the version in use is 1.22 or older. Can you please show output of
kubectl version

Thanks for the info @anubha-v-ardhan! Looks like I'm on .22 and the .23 is not available via brew install yet.
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"darwin/arm64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.9", GitCommit:"9dd794e454ac32d97cde41ae10be801ae98f75df", GitTreeState:"clean", BuildDate:"2021-03-18T01:00:06Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.22) and server (1.19) exceeds the supported minor version skew of +/-1

Is there any process to release the .23 on via homebrew? Maybe I can also provide the PR if necessary.

@jonatas 1.23 is available via homebrew (see https://formulae.brew.sh/formula/kubernetes-cli)
I'm not a mac or brew user so, I can't test the issue myself but I found related issue on stackoverflow which may help

⋊> ~ brew upgrade kubectl
Warning: kubectl 1.23.4 already installed

Looks like 1.23 is already installed, it's just not linked. Can you try running
brew link --overwrite kubernetes-cli

and see if it helps

/transfer kubectl

SIG CLI folks, I'm minded to treat this as a support request and close it (GitHub is not the right place to ask for support).


revert(client): add react suspense and lazy loading

Because https://github.com/freeCodeCamp/freeCodeCamp/pull/50528 revert the breaking change, we can revert the suspense PR which shows the 404 page, while the page is loading.
We can comeback to adding suspense later, when we have another way to access the profile page.

Because https://github.com/freeCodeCamp/freeCodeCamp/pull/50528 revert the breaking change, we can revert the suspense PR

Could you provide more detailed information on why this rollback is necessary? Was is rushed or something else.

Never mind, I did a more comprehensive analysis of the original implementation. And the suspense stuff has to go.
It's pretty late here; I will land this later in the afternoon when I am up or Monday.
I left some notes in the team chat, but the main thing is that #49151 is a bad idea with the current Gatsby-based setup. It's a legacy architecture that needs changing if you want to use those cool new features.
IMHO, I advise checking with other folks on the dev team (like double-checking over chats and call, not just asking for a PR review) when you are modifying legacy code. But again you can't see everything coming, so no harm done!
Cheers.

Sorry for not answering quickly, I went to sleep after opening the PR.


Set fragment tag

How to set fragment tag to the fragment?

See my pull request: https://github.com/DesarrolloAntonio/FragmentTransactionExtended/pull/9

Thank you!


[Feature] Explain Required Permissions

Feature description
A simple page describing what the required browser permissions are needed for would be helpful for users to understand what they are being asked to permit.
Stretch goal - another simple page explaining the benefits and risks associated with linking a Lightning Node to your web browser.
Describe the solution
uBlock Origin have a great example of this
Describe alternatives
No response
Additional context
No response
Are you working on this?
No

Excellent!  Glad to hear it, and thanks for the documentation!


[Security] Workflow release.yml is using vulnerable action actions/checkout

The workflow release.yml is referencing action actions/checkout using references v1. However this reference is missing the commit a6747255bd19d7a757dbdda8c654a9f84db19839 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

Thanks for heads-up, we use v2


Cookie parsing exceptions

While parsing set-cookie-string, var res = COOKIE_PAIR.exec(str); can return an array or null.
In case it returns null, an exception is thrown by res[KEY_INDEX].
Also, decodeURIComponent used to decode res[KEY_INDEX] can throw an exception as well.
Maybe these exceptions could be caught and either trigger an error on the request or just discard the invalid cookie.
If they are not caught, may an option to disable cookie parsing altogether be useful?

Good point. Can you share an example that provokes this exception?
I do think it's a good idea to allow disabling cookie parsing (being false the default option). It might be a performance win on some situations.

Yes, here are a few examples I ran into (inputs to parseSetCookieString function):

empty string
HttpOnly;Secure
language_Ryan USA=1; path=/

Hey @pierreliefauche -- sorry for the delay.

This still ongoing? I have the problem too..
(empty string)

Ok, just fixed this error and pushed a new version to npm. Can you try it and see if it works?


Depth map crashing some time after pressing generate

After some time after pressing Generate button I have error:
Saving faces: 100%|███████████████| 5232425/5232425 [00:17<00:00, 307174.04it/s]
0%|                                                     | 0/1 [10:34<?, ?it/s]
All done.
Error completing request
Arguments: (0, <PIL.Image.Image image mode=RGB size=512x768 at 0x7F9B024AD5A0>, None, '', '', 0, 2, 512, 512, False, True, False, False, 0, 1, True, 1, True, True, False, False, ['left-right', 'red-cyan-anaglyph'], 2.5, 'polylines_sharp', 0, True, True, False, False, False, 'u2net', False, 0, 2, False, None, True, False, True, False) {}
Traceback (most recent call last):
File "/workspace/sd/stable-diffusion-webui/modules/call_queue.py", line 57, in f
res = list(func(*args, **kwargs))
File "/workspace/sd/stable-diffusion-webui/modules/call_queue.py", line 37, in f
res = func(*args, **kwargs)
File "/workspace/sd/stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/depthmap.py", line 1184, in run_generate
outputs, mesh_fi, meshsimple_fi = run_depthmap(
File "/workspace/sd/stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/depthmap.py", line 779, in run_depthmap
mesh_fi = run_3dphoto(device, inpaint_imgs, inpaint_depths, inputnames, outpath, fnExt, vid_ssaa, inpaint_vids)
File "/workspace/sd/stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/depthmap.py", line 944, in run_3dphoto
run_3dphoto_videos(mesh_fi, basename, outpath, 300, 40,
File "/workspace/sd/stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/depthmap.py", line 972, in run_3dphoto_videos
vispy.use(app='egl')
File "/usr/local/lib/python3.10/dist-packages/vispy/util/wrappers.py", line 93, in use
use_app(app)
File "/usr/local/lib/python3.10/dist-packages/vispy/app/_default_app.py", line 47, in use_app
default_app = Application(backend_name)
File "/usr/local/lib/python3.10/dist-packages/vispy/app/application.py", line 47, in init
self._use(backend_name)
File "/usr/local/lib/python3.10/dist-packages/vispy/app/application.py", line 240, in _use
raise RuntimeError(msg)
RuntimeError: Could not import backend "EGL":
Could not initialize
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/gradio/routes.py", line 408, in run_predict
output = await app.get_blocks().process_api(
File "/usr/local/lib/python3.10/dist-packages/gradio/blocks.py", line 1318, in process_api
data = self.postprocess_data(fn_index, result["prediction"], state)
File "/usr/local/lib/python3.10/dist-packages/gradio/blocks.py", line 1221, in postprocess_data
self.validate_outputs(fn_index, predictions)  # type: ignore
File "/usr/local/lib/python3.10/dist-packages/gradio/blocks.py", line 1196, in validate_outputs
raise ValueError(
ValueError: An event handler (f) didn't receive enough output values (needed: 5, received: 3).
Wanted outputs:
[gallery, textbox, model3d, html, html]
Received outputs:
[None, "", "RuntimeError: Could not import backend "EGL":
Could not initializeTime taken: 11m 59.28sTorch active/reserved: 12381/12588 MiB, Sys VRAM: 13749/16118 MiB (85.3%)"]
Generate 3D inpainted mesh. (Sloooow, required for generating videos) is on
dpt_beit_large_384 (midas 3.1)
GPU
on 1 x RTX A4000
8 vCPU 31 GB RAM

i have exactly save error with this one, how to fix?

Please run pip list in the venv and post the result here.


PROD SUPPORT: ROLE MAPPING ISSUE: NOT ABLE TO EVEN START HEARINGS BY MAGISTRATE

Describe the bug
"Judge is not able to start hearings. There are user role mapping issue. Every employees roles have to be updated as some of the things are not working correctly.Magistrate is also not able to go to Filings_Tab
Today's cases are not rescheduled because of this issue"
Screenshots

Start hearing and filings_tab issues are solved
screenshots fr ref:


Shiro native support #1844

Issue: https://github.com/apache/camel-quarkus/issues/1844
[ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #.
[ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough.
[ ] Phrases like Fix # or Fixes # will auto-close the named issue upon merging the pull request. Using them is typically a good idea.
[ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request.
[ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html

I've added change in bom, which is not necessary and is the reason of the build failure. I'll fix it.

I'll rebase it and at least move changes for bindy component  (caused by change of  doc) into separate commit (in case rebasing won't remove it)

Current build problems seems to be caused by changes in camel-google-pubsub (e.g. https://github.com/apache/camel/commit/320dd0df9dd362523c0ee8769f87eebf8100b465#diff-6632f36f07e08f4a58c2460394178025L234)

@aldettinger thanks for all the suggestions, I've implemented all of them. PR is ready to merge.

Ok, I see the build issue is coming from another component. Merged.