Closed DerEmder closed 1 year ago
Bitte Z-Wave log aktivieren und ein paar Minuten nach dem Start hier die Datei hochladen.
Habe ich gemacht - wo finde ich die Logdatei?
In /opt/iobroker/node_modules/iobroker.zwave2/build/
- nimm die mit dem Datum von heute im Namen.
Da hätte ich lange suchen können .... ;)
2022-08-27T15:44:06.919Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2022-08-27T15:44:06.921Z DRIVER version 10.0.1
2022-08-27T15:44:06.922Z DRIVER
2022-08-27T15:44:06.922Z DRIVER starting driver...
2022-08-27T15:44:06.958Z DRIVER opening serial port /dev/serial/by-id/usb-0658_0200-if00
2022-08-27T15:44:06.983Z DRIVER serial port opened
2022-08-27T15:44:06.985Z SERIAL » [NAK] (0x15)
2022-08-27T15:44:07.002Z DRIVER loading configuration...
2022-08-27T15:44:07.005Z SERIAL « 0x0110000400260a600d0100310504220000b9 (18 bytes)
2022-08-27T15:44:07.014Z DRIVER Dropping message because the driver is not ready to handle it yet.
2022-08-27T15:44:07.015Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:07.062Z SERIAL « 0x01080004000e0284077c (10 bytes)
2022-08-27T15:44:07.073Z DRIVER Dropping message because the driver is not ready to handle it yet.
2022-08-27T15:44:07.073Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:07.083Z CONFIG version 10.0.0
2022-08-27T15:44:08.186Z DRIVER beginning interview...
2022-08-27T15:44:08.188Z DRIVER added request handler for AddNodeToNetwork (0x4a)...
1 registered
2022-08-27T15:44:08.188Z DRIVER added request handler for RemoveNodeFromNetwork (0x4b)...
1 registered
2022-08-27T15:44:08.189Z DRIVER added request handler for ReplaceFailedNode (0x63)...
1 registered
2022-08-27T15:44:08.190Z CNTRLR querying controller IDs...
2022-08-27T15:44:08.464Z SERIAL » 0x01030020dc (5 bytes)
2022-08-27T15:44:08.466Z DRIVER » [REQ] [GetControllerId]
2022-08-27T15:44:08.470Z SERIAL « [ACK] (0x06)
2022-08-27T15:44:08.473Z SERIAL « 0x01080120e919d96e0190 (10 bytes)
2022-08-27T15:44:08.475Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:08.478Z DRIVER « [RES] [GetControllerId]
home ID: 0xe919d96e
own node ID: 1
2022-08-27T15:44:08.493Z CNTRLR received controller IDs:
home ID: 0xe919d96e
own node ID: 1
2022-08-27T15:44:08.494Z CNTRLR querying API capabilities...
2022-08-27T15:44:08.518Z SERIAL » 0x01030007fb (5 bytes)
2022-08-27T15:44:08.520Z DRIVER » [REQ] [GetSerialApiCapabilities]
2022-08-27T15:44:08.525Z SERIAL « [ACK] (0x06)
2022-08-27T15:44:08.528Z SERIAL « 0x012b01070506011504000001fe83ff88cf1f0000fb9f7da067008080008086000 (45 bytes)
000e87300000e0000401a000d
2022-08-27T15:44:08.530Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:08.533Z DRIVER « [RES] [GetSerialApiCapabilities]
payload: 0x0506011504000001fe83ff88cf1f0000fb9f7da067008080008086000000e8730
0000e0000401a00
2022-08-27T15:44:08.543Z CNTRLR received API capabilities:
firmware version: 5.6
manufacturer ID: 0x0115
product type: 0x0400
product ID: 0x01
supported functions:
· GetSerialApiInitData (0x02)
· SetApplicationNodeInformation (0x03)
· ApplicationCommand (0x04)
· GetControllerCapabilities (0x05)
· SetSerialApiTimeouts (0x06)
· GetSerialApiCapabilities (0x07)
· SoftReset (0x08)
· GetProtocolVersion (0x09)
· SerialAPIStarted (0x0a)
· SetRFReceiveMode (0x10)
· UNKNOWN_FUNC_SET_SLEEP_MODE (0x11)
· FUNC_ID_ZW_SEND_NODE_INFORMATION (0x12)
· SendData (0x13)
· SendDataMulticast (0x14)
· GetControllerVersion (0x15)
· SendDataAbort (0x16)
· FUNC_ID_ZW_R_F_POWER_LEVEL_SET (0x17)
· UNKNOWN_FUNC_SEND_DATA_META (0x18)
· FUNC_ID_ZW_GET_RANDOM (0x1c)
· GetControllerId (0x20)
· UNKNOWN_FUNC_MEMORY_GET_BYTE (0x21)
· UNKNOWN_FUNC_MEMORY_PUT_BYTE (0x22)
· UNKNOWN_FUNC_MEMORY_GET_BUFFER (0x23)
· UNKNOWN_FUNC_MEMORY_PUT_BUFFER (0x24)
· UNKNOWN_FUNC_FlashAutoProgSet (0x27)
· UNKNOWN_FUNC_UNKNOWN_0x28 (0x28)
· GetNVMId (0x29)
· ExtNVMReadLongBuffer (0x2a)
· ExtNVMWriteLongBuffer (0x2b)
· ExtNVMReadLongByte (0x2c)
· ExtExtWriteLongByte (0x2d)
· GetNodeProtocolInfo (0x41)
· HardReset (0x42)
· FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
· FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
· AssignReturnRoute (0x46)
· DeleteReturnRoute (0x47)
· RequestNodeNeighborUpdate (0x48)
· ApplicationUpdateRequest (0x49)
· AddNodeToNetwork (0x4a)
· RemoveNodeFromNetwork (0x4b)
· FUNC_ID_ZW_CREATE_NEW_PRIMARY (0x4c)
· FUNC_ID_ZW_CONTROLLER_CHANGE (0x4d)
· FUNC_ID_ZW_SET_LEARN_MODE (0x50)
· AssignSUCReturnRoute (0x51)
· FUNC_ID_ZW_REQUEST_NETWORK_UPDATE (0x53)
· SetSUCNodeId (0x54)
· DeleteSUCReturnRoute (0x55)
· GetSUCNodeId (0x56)
· UNKNOWN_FUNC_SEND_SUC_ID (0x57)
· FUNC_ID_ZW_EXPLORE_REQUEST_INCLUSION (0x5e)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
· UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
· UNKNOWN_FUNC_UNKNOWN_0x78 (0x78)
· GetRoutingInfo (0x80)
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· UNKNOWN_FUNC_GET_PRIORITY_ROUTE (0x92)
· UNKNOWN_FUNC_SET_PRIORITY_ROUTE (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· UNKNOWN_FUNC_UNKNOWN_0xB4 (0xb4)
· UNKNOWN_FUNC_WATCH_DOG_ENABLE (0xb6)
· UNKNOWN_FUNC_WATCH_DOG_DISABLE (0xb7)
· UNKNOWN_FUNC_WATCH_DOG_KICK (0xb8)
· UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
· UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
· UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
· UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
· UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)
· UNKNOWN_FUNC_ZMEFreqChange (0xf2)
· UNKNOWN_FUNC_ZMEBootloaderFlash (0xf4)
· UNKNOWN_FUNC_ZMECapabilities (0xf5)
2022-08-27T15:44:08.578Z DRIVER Soft reset is enabled through config, but this stick does not support it.
2022-08-27T15:44:08.664Z CNTRLR querying version info...
2022-08-27T15:44:08.675Z SERIAL » 0x01030015e9 (5 bytes)
2022-08-27T15:44:08.676Z DRIVER » [REQ] [GetControllerVersion]
2022-08-27T15:44:08.679Z SERIAL « [ACK] (0x06)
2022-08-27T15:44:08.682Z SERIAL « 0x011001155a2d5761766520342e3035000197 (18 bytes)
2022-08-27T15:44:08.683Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:08.684Z DRIVER « [RES] [GetControllerVersion]
payload: 0x5a2d5761766520342e30350001
2022-08-27T15:44:08.692Z CNTRLR received version info:
controller type: Static Controller
library version: Z-Wave 4.05
2022-08-27T15:44:08.692Z CNTRLR querying protocol version info...
2022-08-27T15:44:08.704Z SERIAL » 0x01030009f5 (5 bytes)
2022-08-27T15:44:08.705Z DRIVER » [REQ] [GetProtocolVersion]
2022-08-27T15:44:08.707Z SERIAL « [ACK] (0x06)
2022-08-27T15:44:08.709Z SERIAL « 0x0107010900040500f1 (9 bytes)
2022-08-27T15:44:08.711Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:08.712Z DRIVER « [RES] [GetProtocolVersion]
payload: 0x00040500
2022-08-27T15:44:08.721Z CNTRLR received protocol version info:
protocol type: Z-Wave
protocol version: 4.5.0
2022-08-27T15:44:08.725Z CNTRLR supported Z-Wave features:
2022-08-27T15:44:08.725Z CNTRLR querying controller capabilities...
2022-08-27T15:44:08.735Z SERIAL » 0x01030005f9 (5 bytes)
2022-08-27T15:44:08.736Z DRIVER » [REQ] [GetControllerCapabilities]
2022-08-27T15:44:08.739Z SERIAL « [ACK] (0x06)
2022-08-27T15:44:08.741Z SERIAL « 0x010401051ce3 (6 bytes)
2022-08-27T15:44:08.742Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:08.743Z DRIVER « [RES] [GetControllerCapabilities]
payload: 0x1c
2022-08-27T15:44:08.750Z CNTRLR received controller capabilities:
controller role: primary
is the SUC: true
started this network: true
SIS is present: true
was real primary: true
2022-08-27T15:44:08.751Z CNTRLR finding SUC...
2022-08-27T15:44:08.762Z SERIAL » 0x01030056aa (5 bytes)
2022-08-27T15:44:08.762Z DRIVER » [REQ] [GetSUCNodeId]
2022-08-27T15:44:08.765Z SERIAL « [ACK] (0x06)
2022-08-27T15:44:08.767Z SERIAL « 0x0104015601ad (6 bytes)
2022-08-27T15:44:08.768Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:08.769Z DRIVER « [RES] [GetSUCNodeId]
payload: 0x01
2022-08-27T15:44:08.776Z CNTRLR This is the SUC
2022-08-27T15:44:08.776Z CNTRLR querying additional controller information...
2022-08-27T15:44:08.793Z SERIAL » 0x01030002fe (5 bytes)
2022-08-27T15:44:08.794Z DRIVER » [REQ] [GetSerialApiInitData]
2022-08-27T15:44:08.797Z SERIAL « [ACK] (0x06)
2022-08-27T15:44:08.889Z SERIAL « 0x0125010205081d0d2dc97f3e07000000000000000000000000000000000000000 (39 bytes)
0000000050063
2022-08-27T15:44:08.891Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:08.892Z DRIVER « [RES] [GetSerialApiInitData]
payload: 0x05081d0d2dc97f3e0700000000000000000000000000000000000000000000000
500
2022-08-27T15:44:08.902Z CNTRLR received additional controller information:
Z-Wave API version: 5 (legacy)
Z-Wave chip type: ZW050x
node type Controller
controller role: primary
controller is the SIS: true
controller supports timers: false
nodes in the network: 1, 3, 4, 9, 11, 12, 14, 17, 20, 23, 24, 25, 26,
27, 28, 29, 30, 31, 34, 35, 36, 37, 38, 41, 42, 43
2022-08-27T15:44:09.010Z DRIVER Cache file for homeId 0xe919d96e found, attempting to restore the network from
cache...
2022-08-27T15:44:09.027Z CNTRLR [Node 001] Embedded device config loaded
2022-08-27T15:44:09.116Z CNTRLR [Node 003] Embedded device config loaded
2022-08-27T15:44:09.122Z CNTRLR [Node 009] Embedded device config loaded
2022-08-27T15:44:09.128Z CNTRLR [Node 011] Embedded device config loaded
2022-08-27T15:44:09.186Z CNTRLR [Node 012] Embedded device config loaded
2022-08-27T15:44:09.195Z CNTRLR [Node 014] Embedded device config loaded
2022-08-27T15:44:09.235Z CNTRLR [Node 017] Embedded device config loaded
2022-08-27T15:44:09.267Z CNTRLR [Node 020] Embedded device config loaded
2022-08-27T15:44:09.316Z CNTRLR [Node 023] Embedded device config loaded
2022-08-27T15:44:09.327Z CNTRLR [Node 024] Embedded device config loaded
2022-08-27T15:44:09.340Z CNTRLR [Node 026] Embedded device config loaded
2022-08-27T15:44:09.360Z CNTRLR [Node 027] Embedded device config loaded
2022-08-27T15:44:09.380Z CNTRLR [Node 028] Embedded device config loaded
2022-08-27T15:44:09.392Z CNTRLR [Node 029] Embedded device config loaded
2022-08-27T15:44:09.404Z CNTRLR [Node 030] Embedded device config loaded
2022-08-27T15:44:09.521Z CNTRLR [Node 034] Embedded device config loaded
2022-08-27T15:44:09.558Z CNTRLR [Node 035] Embedded device config loaded
2022-08-27T15:44:09.581Z CNTRLR [Node 036] Embedded device config loaded
2022-08-27T15:44:09.605Z CNTRLR [Node 037] Embedded device config loaded
2022-08-27T15:44:09.645Z CNTRLR [Node 038] Embedded device config loaded
2022-08-27T15:44:09.653Z CNTRLR [Node 041] Embedded device config loaded
2022-08-27T15:44:09.663Z CNTRLR [Node 042] Embedded device config loaded
2022-08-27T15:44:09.680Z CNTRLR [Node 043] Embedded device config loaded
2022-08-27T15:44:09.683Z DRIVER Restoring the network from cache was successful!
2022-08-27T15:44:09.688Z CNTRLR [Node 001] [Manufacturer Specific] manufacturerId: metadata updated
2022-08-27T15:44:09.689Z CNTRLR [Node 001] [Manufacturer Specific] productType: metadata updated
2022-08-27T15:44:09.690Z CNTRLR [Node 001] [Manufacturer Specific] productId: metadata updated
2022-08-27T15:44:09.692Z CNTRLR [Node 001] [~] [Manufacturer Specific] manufacturerId: 277 => 277
2022-08-27T15:44:09.693Z CNTRLR [Node 001] [~] [Manufacturer Specific] productType: 1024 => 1024
2022-08-27T15:44:09.694Z CNTRLR [Node 001] [~] [Manufacturer Specific] productId: 1 => 1
2022-08-27T15:44:09.696Z CNTRLR [Node 001] [Version] firmwareVersions: metadata updated
2022-08-27T15:44:09.696Z CNTRLR [Node 001] [~] [Version] firmwareVersions: 5.6 => 5.6
2022-08-27T15:44:09.697Z CNTRLR [Node 001] [Version] sdkVersion: metadata updated
2022-08-27T15:44:09.698Z CNTRLR [Node 001] [~] [Version] sdkVersion: "4.5.0" => "4.5.0"
2022-08-27T15:44:09.699Z CNTRLR setting serial API timeouts: ack = 2000 ms, byte = 150 ms
2022-08-27T15:44:09.710Z SERIAL » 0x01050006c80f3b (7 bytes)
2022-08-27T15:44:09.712Z DRIVER » [REQ] [SetSerialApiTimeouts]
payload: 0xc80f
2022-08-27T15:44:09.716Z SERIAL « [ACK] (0x06)
2022-08-27T15:44:09.720Z SERIAL « 0x01050106c80f3a (7 bytes)
2022-08-27T15:44:09.721Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:09.722Z DRIVER « [RES] [SetSerialApiTimeouts]
payload: 0xc80f
2022-08-27T15:44:09.730Z CNTRLR serial API timeouts overwritten. The old values were: ack = 2000 ms, byte = 15
0 ms
2022-08-27T15:44:09.730Z CNTRLR Interview completed
2022-08-27T15:44:09.731Z DRIVER Network key for S0 configured, enabling S0 security manager...
2022-08-27T15:44:09.734Z DRIVER No network key for S2 configured, communication with secure (S2) devices won't
work!
2022-08-27T15:44:09.734Z DRIVER driver ready
2022-08-27T15:44:09.740Z CNTRLR [Node 001] The node is alive.
2022-08-27T15:44:09.741Z CNTRLR [Node 001] The node is ready to be used
2022-08-27T15:44:09.743Z CNTRLR [Node 003] The node is asleep.
2022-08-27T15:44:09.746Z CNTRLR [Node 003] The node is ready to be used
2022-08-27T15:44:09.748Z CNTRLR [Node 004] Beginning interview - last completed stage: ProtocolInfo
2022-08-27T15:44:09.749Z CNTRLR » [Node 004] pinging the node...
2022-08-27T15:44:09.939Z CNTRLR » [Node 009] pinging the node...
2022-08-27T15:44:09.943Z CNTRLR [Node 011] The node is asleep.
2022-08-27T15:44:09.945Z CNTRLR [Node 011] The node is ready to be used
2022-08-27T15:44:09.946Z CNTRLR [Node 012] The node is asleep.
2022-08-27T15:44:09.956Z CNTRLR [Node 012] The node is ready to be used
2022-08-27T15:44:09.957Z CNTRLR [Node 014] The node is asleep.
2022-08-27T15:44:09.959Z CNTRLR [Node 014] The node is ready to be used
2022-08-27T15:44:09.960Z CNTRLR [Node 017] The node is asleep.
2022-08-27T15:44:09.962Z CNTRLR [Node 017] The node is ready to be used
2022-08-27T15:44:09.963Z CNTRLR [Node 020] The node is asleep.
2022-08-27T15:44:09.981Z CNTRLR [Node 020] The node is ready to be used
2022-08-27T15:44:09.982Z CNTRLR » [Node 023] pinging the node...
2022-08-27T15:44:09.986Z CNTRLR » [Node 024] pinging the node...
2022-08-27T15:44:09.991Z CNTRLR [Node 025] Beginning interview - last completed stage: ProtocolInfo
2022-08-27T15:44:09.992Z CNTRLR » [Node 025] pinging the node...
2022-08-27T15:44:09.995Z CNTRLR » [Node 026] pinging the node...
2022-08-27T15:44:09.998Z CNTRLR » [Node 027] pinging the node...
2022-08-27T15:44:10.002Z CNTRLR » [Node 028] pinging the node...
2022-08-27T15:44:10.006Z CNTRLR » [Node 029] pinging the node...
2022-08-27T15:44:10.009Z CNTRLR » [Node 030] pinging the node...
2022-08-27T15:44:10.014Z CNTRLR [Node 031] The node is asleep.
2022-08-27T15:44:10.017Z CNTRLR [Node 031] Beginning interview - last completed stage: NodeInfo
2022-08-27T15:44:10.024Z CNTRLR [Node 031] Interviewing Wake Up...
2022-08-27T15:44:10.024Z CNTRLR » [Node 031] retrieving wakeup interval from the device...
2022-08-27T15:44:10.037Z CNTRLR » [Node 034] pinging the node...
2022-08-27T15:44:10.045Z CNTRLR [Node 035] The node is asleep.
2022-08-27T15:44:10.047Z CNTRLR [Node 035] The node is ready to be used
2022-08-27T15:44:10.048Z CNTRLR » [Node 036] pinging the node...
2022-08-27T15:44:10.054Z CNTRLR » [Node 037] pinging the node...
2022-08-27T15:44:10.058Z CNTRLR » [Node 038] pinging the node...
2022-08-27T15:44:10.062Z CNTRLR [Node 041] The node is asleep.
2022-08-27T15:44:10.064Z CNTRLR [Node 041] The node is ready to be used
2022-08-27T15:44:10.065Z CNTRLR » [Node 042] pinging the node...
2022-08-27T15:44:10.069Z CNTRLR » [Node 043] pinging the node...
2022-08-27T15:44:10.078Z SERIAL » 0x010800130401002501c5 (10 bytes)
2022-08-27T15:44:10.080Z DRIVER » [Node 004] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 1
└─[NoOperationCC]
2022-08-27T15:44:10.089Z SERIAL « [ACK] (0x06)
2022-08-27T15:44:10.094Z SERIAL « 0x0104011301e8 (6 bytes)
2022-08-27T15:44:10.095Z SERIAL » [ACK] (0x06)
2022-08-27T15:44:10.098Z DRIVER « [RES] [SendData]
was sent: true
2022-08-27T15:44:10.150Z DRIVER Checking for configuration updates...
2022-08-27T15:44:11.077Z DRIVER No configuration update available...
2022-08-27T15:45:08.655Z DRIVER destroying driver instance...
2022-08-27T15:45:08.849Z DRIVER driver instance destroyed
Ha, "Good News" würde ich sagen, vor wenigen Sekunden hat sich das Licht über einen meiner Bewegungsmelder eingeschaltet, als ich vorbei ging. Ich muss mal im Gebäude testen, ob es plötzlich geht. Vor dem Debug-Log ging es nicht - jetzt scheint der Adapter "aufzuwachen", sehr merkwürdig.
ich melde mich, wenn sich hier etwas tut.
So, alle Bewegungsmelder sind wieder online und funktionieren wie vor dem Update. Allerdings funktioniert, mit einer Ausnahme, keiner meiner Fibaro Shutter Controller. Schreiben in die Datenpunkte (numerisch oder Close/Open) haben keinen Effekt. Da tut sich nichts. Lediglich der Controller für ein Dachfenster-Rolladen funktioniert wieder wie vor dem Update. Alles sehr unbefriedigend. Wenn ich noch Infos beisteuern kann - nur raus damit.
Die Controller zu exkludieren und neu einzubinden ist nicht - die sind in allen Räumen in der Wand. Leider hat der Adapter auch keine Funktion mehr um dies zu tun.
Noch eine Info:
bei allen Roller Shuttern steht in Multilevel_Switch.close der Wert (null) drin. Wenn ich diesen manuell auf true setze, dann wird als Wert false übernommen. Danach kann ich einen Wert in Multilevel_Switch.targetValue schreiben - z.B. 0 und schwupps fährt der Rolladen zu (dann wechselt auch currentValue auf den richtigen Wert). Ohne Änderung von Multilevel_Switch.close kann ich beliebige Werte schreiben - es tut sich nichts. Irgend etwas ist dort falsch oder gar nicht initialisiert worden - ich bin kein Programmierer, kann also nur mutmaßen.
Bitte die problematischen Geräte mal neu interviewen.
Die Funktion ist seit Version 2.0.0 im Z-Wave Tab und nicht in den Adaptereinstellungen. Falls das Tab fehlt, muss es möglicherweise eingeblendet werden, links oben in der Seitenleiste im Admin.
Neu interviewen geht nicht. Punkt. Jedenfalls nicht diese Woche. Ich habe den Z-Wave Tab tatsächlich versehentlich ausgeblendet. Habe es jetzt wieder. Sorry.
Ich habe jetzt von Hand alle Controller im Datenpunkt Close, Open, Down, Up usw. mit true beschrieben. Jetzt funktioniert alles wie vorher.
Wie auch immer - es kann nicht sein, das ich nach jedem größeren Update die Geräte neu interviewen muss. Dass ist bei größeren Haus-Installationen so gut wie unmöglich, zumal es hier ja wie mit "Kanonen auf Spatzen schießen" wirkt. Augenscheinlich wurden nur ein paar Datenpunkte nicht korrekt initialisiert. Sollte nicht passieren, ist es aber. Kein großes Ding - für das nächste Update bin ich dann vorbereitet, wenn es wieder Probleme gibt. So lerne auch ich dazu.
🤷🏻♂️ ich verstehe nicht was bei dir schiefgelaufen ist. In den 2-3 Monaten die ich an der neuen Version gearbeitet hab, ist mir das nicht 1x passiert. Die Daten sollten schon von vorher im Cache sein.
Und neu interviewen bei nem Roller Shutter sollte max. 30 Sekunden dauern. Um sicher zu gehen, ich rede nicht von neu einbinden.
Ah, ok - du meinst nicht bei jedem Gerät 3x die Taste drücken. Denn dann wäre ich den halben Tag mit Werkzeug unterwegs. Das kann ich natürlich machen - und habe es auch gerade. Alles soweit in Ordnung. Ich hoffe das morgen früh die Rollläden am ganzen Haus entsprechend fahren und keine weiteren Probleme auftauchen.
Aber trotzdem - irgend etwas ist da schief gelaufen. Reproduzierbar ist es leider nicht, da ja jetzt alles wieder läuft. Ich kann es nur im Auge behalten und bei Bedarf wieder melden.
Ich habe fast die Vermutung dass deine Cache-Dateien kaputt gegangen sind. Warum auch immer - die sind eigentlich append-only.
Bzgl. Neu interviewen: Batteriebetriebene Geräte werden erst neu interviewt wenn sie auch aufwachen. Das kann ein paar Stunden dauern.
Das ist schon klar - aber alle Roller Shutter Controller sind natürlich netzbetrieben und immer online. Die Bewegungsmelder sind aber, mit Ausnahme der Radar-BMs, alle batteriebetrieben - das würde aber nicht erklären, warum sie ca. 4-5 Stunden nach dem Update plötzlich alle(!) zum gleichen Zeitpunkt wieder funktionieren.
Wie können Cache-Dateien durch ein Update kaputt gehen? Und falls - wäre ein Löschen und neu anlegen sinnvoll und möglich? Ich frage nur, bevor ich irgendwelchen Blödsinn anstelle.
Nach dem Update von 3.0.0 auf 3.0.1 das gleiche Problem - alles tot, nichts geht mehr. Ich habe jetzt in den Logs mehrfach die Fehlermeldung "Node xy does not support the Command Class Binary Switch! (ZW0302)"
Bewegungsmelder alle stumm, Rolladen Controller fahren mit mehr-minütiger Verzögerung - wenn überhaupt. Ich hab die Dinger schon neu interviewed - keine Änderung.
Ich lasse gerade das detaillierte Log mitlaufen, ich lade es dann später hoch.
Schick mir dann bitte auch die Dateien aus /opt/iobroker/iobroker-data/zwave.0/cache.
Mache ich.
Habe gerade Log ausgeschaltet - Adapter startet neu und bleibt rot. Hab schon neugestartet - keine Änderung. Der Adapter startet nicht mehr. Irgendeine Idee wie ich das Ding wieder aktivieren kann?
PS:
Jetzt habe ich es geschafft - von Hand deaktivert, dann eine Minute warten und dann startet er wieder. Alles sehr seltsam.
Wie gestern auch - nach etwa zweieinhalb Stunden erwachen alle Bewegungsmelder zum Leben. Nur die Rolläden laufen nicht - selbst mit Tricks geht es nicht. Als der Adapter nicht wollte hatte ich folgendes im Log:
zwave2.0 2022-08-29 19:28:48.669 error adapter disabled
zwave2.0 2022-08-29 19:28:41.771 error Restarting the adapter in a second...
zwave2.0 2022-08-29 19:28:41.766 error Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:3834:23) at ZWaveController.identify (/opt/iobroker/node_modules/zwave-js/src/lib/controller/Controller.ts:713:33) at Driver.initializeControllerAndNodes (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:1185:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:992:16) (ZW0100)
zwave2.0 2022-08-29 19:28:23.901 error Restarting the adapter in a second...
zwave2.0 2022-08-29 19:28:23.899 error Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:3834:23) at ZWaveController.identify (/opt/iobroker/node_modules/zwave-js/src/lib/controller/Controller.ts:713:33) at Driver.initializeControllerAndNodes (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:1185:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:992:16) (ZW0100)
zwave2.0 2022-08-29 19:28:00.525 error Exception-Code: 103: The controller is not yet ready! (ZW0103)
zwave2.0 2022-08-29 19:28:00.525 error ZWaveError: The controller is not yet ready! (ZW0103) at Driver.get controller [as controller] (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:674:10) at /opt/iobroker/node_modules/iobroker.zwave2/src/main.ts:309:26 at Array.filter (<anonymous>) at Driver.<anonymous> (/opt/iobroker/node_modules/iobroker.zwave2/src/main.ts:308:42) at runNextTicks (internal/process/task_queues.js:60:5) at processImmediate (internal/timers.js:437:9)
zwave2.0 2022-08-29 19:28:00.524 error uncaught exception: The controller is not yet ready! (ZW0103)
zwave2.0 2022-08-29 19:28:00.523 error Exception-Code: 103: The controller is not yet ready! (ZW0103)
zwave2.0 2022-08-29 19:28:00.523 error ZWaveError: The controller is not yet ready! (ZW0103) at Driver.get controller [as controller] (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:674:10) at /opt/iobroker/node_modules/iobroker.zwave2/src/main.ts:309:26 at Array.filter (<anonymous>) at Driver.<anonymous> (/opt/iobroker/node_modules/iobroker.zwave2/src/main.ts:308:42) at runNextTicks (internal/process/task_queues.js:60:5) at processImmediate (internal/timers.js:437:9)
zwave2.0 2022-08-29 19:28:00.522 error unhandled promise rejection: The controller is not yet ready! (ZW0103)
zwave2.0 2022-08-29 19:28:00.521 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
zwave2.0 2022-08-29 19:28:00.400 error Exception-Code: 103: The controller is not yet ready! (ZW0103)
zwave2.0 2022-08-29 19:28:00.399 error ZWaveError: The controller is not yet ready! (ZW0103) at Driver.get controller [as controller] (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:674:10) at ZWave2.onNodeReady (/opt/iobroker/node_modules/iobroker.zwave2/src/main.ts:501:28) at Driver.<anonymous> (/opt/iobroker/node_modules/iobroker.zwave2/src/main.ts:287:16) at processTicksAndRejections (internal/process/task_queues.js:95:5) at runNextTicks (internal/process/task_queues.js:64:3) at processImmediate (internal/timers.js:437:9)
zwave2.0 2022-08-29 19:28:00.399 error uncaught exception: The controller is not yet ready! (ZW0103)
zwave2.0 2022-08-29 19:28:00.398 error Exception-Code: 103: The controller is not yet ready! (ZW0103)
Hier das Log (mit Neustart) - als ZIP wegen der Größe
Hier das Cache Verzeichnis als ZIP
Ich muss jetzt irgendwie die Rollläden runter fahren - aber selbst manuell in die Datenpunkte schreiben geht nicht.
Zieh mal den Stick raus und stecke ihn neu ein. Sieht aus als hängt der.
Hier hilft nichts. Ich kann schreiben was ich will. In den Logs tauchen immer mehr "errors" auf:
zwave2.0 | 2022-08-29 21:02:36.319 | info | Node 35 is now awake
-- | -- | -- | --
zwave2.0 | 2022-08-29 21:01:55.666 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 21:01:48.893 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 21:01:23.681 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 21:01:23.162 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 21:01:23.079 | warn | State value to set for "zwave2.0.Node_041.Basic.currentValue" has value "255" greater than max "99"
zwave2.0 | 2022-08-29 21:01:20.593 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 21:01:16.323 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 21:01:16.255 | warn | State value to set for "zwave2.0.Node_041.Basic.currentValue" has value "255" greater than max "99"
zwave2.0 | 2022-08-29 21:00:39.103 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 21:00:30.336 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 20:59:54.684 | error | Node 29 does not support the Command Class Scene Activation! (ZW0302)
zwave2.0 | 2022-08-29 20:59:48.645 | error | Node 29 does not support the Command Class Scene Activation! (ZW0302)
zwave2.0 | 2022-08-29 20:59:34.588 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 20:59:29.756 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 20:59:20.364 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 20:59:15.859 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 20:59:07.332 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 20:59:02.015 | error | Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
zwave2.0 | 2022-08-29 20:58:47.668 | error | Node 29 does not support the Command Class Binary Switch! (ZW0302)
zwave2.0 | 2022-08-29 20:58:42.397 | error | Node 29 does not support the Command Class Binary Switch! (ZW0302)
zwave2.0 | 2022-08-29 20:56:53.027 | info | Node 41: interview restarted
zwave2.0 | 2022-08-29 20:56:43.049 | info | Node 37: interview restarted
zwave2.0 | 2022-08-29 20:56:38.923 | info | Node 36: interview restarted
zwave2.0 | 2022-08-29 20:52:33.967 | info | Node 30: interview restarted
zwave2.0 | 2022-08-29 20:52:25.739 | info | Node 29: interview restarted
zwave2.0 | 2022-08-29 20:52:22.044 | info | Node 28: interview restarted
zwave2.0 | 2022-08-29 20:52:18.023 | info | Node 27: interview restarted
zwave2.0 | 2022-08-29 20:52:11.906 | info | Node 26: interview restarted
zwave2.0 | 2022-08-29 20:50:33.984 | error | Multilevel Switch: "duration" is not a supported property (ZW0322)
Mach ich mal. Obwohl ja die Bewegungsmelder funktionieren - nur die Roller Shutter nicht.
Und dann geh am besten zurück auf Version 2.6.0, damit zumindest wieder alles läuft.
Bei Node 29 und 30 scheint das Abfragen der unterstützen Kommandos während des Interviews nicht geklappt zu haben. Leider ist das nicht im Log. Falls du noch auf 3.0.1 bist, kannst du die grade noch neu interviewen und das Log davon posten?
Downgrade funktioniert nicht, wie oben bereits erwähnt. Dann passiert genau das gleiche. Ich werde mal die 3.0.0 wieder versuchen.
Seltsam, ich habe das Log eigentlich laufen lassen und dann auf "Interview" geklickt.
Zwischendurch steigt dein Stick aus und reagiert einfach nicht mehr. Nicht dass das die ganzen Probleme verursacht 🤔
Ich mach den mal raus und starte neu (mit 3.0.1)
Runtergefahren - stromlos gemacht - hochgefahren. Wieder alles tot. Weder BM noch Roller Shutter funktionieren.
Das "Node 29 does not support the Command Class Multilevel Switch! (ZW0302)" kommt immer noch.
Bei fast allen Nodes kommt "Node xy interview failed: Attempt 1/5 failed".
Ich gehe jetzt erstmal auf 3.0.0 zurück - das war die letzte funktionierende Version.
Bei fast allen Nodes kommt "Node xy interview failed: Attempt 1/5 failed".
Und davon würde ich das Log gerne mal sehen. (Logdatei, nicht aus dem ioBroker-Protokoll)
Argh, wenige Sekunden zu spät - bin gerade auf 3.0.0 zurück. ...
da kommt direkt
Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:3834:23) at ZWaveController.identify (/opt/iobroker/node_modules/zwave-js/src/lib/controller/Controller.ts:713:33) at Driver.initializeControllerAndNodes (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:1185:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:992:16) (ZW0100)
Ich werde morgen nochmal rumprobieren und ein Log machen. Jetzt habe ich erstmal die Faxen dicke, lasse die Rolläden oben und schalte Licht manuell.
Timeout while waiting for an ACK from the controller
Das ist der Stick, der nicht reagiert. Schau mal in die Einstellungen, und stelle sicher dass der Haken "Controller nicht neustarten" gesetzt ist.
v3.0.2 ist in Kürze verfügbar. Gerne mal ausprobieren ob das deine Probleme behebt. Also zumindest das was nicht damit zu tun hat, dass der Stick sich komplett verabschiedet.
Hallo,
ich habe jetzt einen Restore des Systems gemacht - ich belasse es für die nächsten Tage bei der 3.0.0, nach etwa 3-4 Stunden funktionierte wieder (fast) alles, sonst dreht mir meine Frau den Hals um. Mal sehen, ob ich nächste Woche Zeit finde, mich darum zu kümmern, ich bin derzeit arbeitsmäßig etwas ausgelastet und habe die nächsten Tage wenig Zeit.
3.0.0 ist aber mit ziemlicher Sicherheit instabiler als 2.6 und 3.0.2 🤷♂️
Das mag sein - die läuft jetzt aber - alles funktioniert jetzt. Ich lass die laufen und mache das Update dann am Wochenende - dann habe ich auch bessere Nerven wenn wieder etwas schief geht. Mein Frauchen hat mir aufgetragen "Spielereien" an Licht und Sonnenschutz bzw. Verdunklung am Tage zu machen. Kann man nichts machen - die 3.0.2 kommt also am WE dran.
Mein Frauchen hat mir aufgetragen [...]. Kann man nichts machen
touche
Danke :)
Du kannst dir also vorstellen, wie mein gestriger Abend abgelaufen ist ....
So, das Update von 3.0.0 auf 3.0.2 durchgeführt : gleiches Verhalten wie oben beschrieben - nichts geht mehr bzw. nur mit minutenlanger Verzögerung. Ich habe dir das Log mal unten angehängt.
Als Beispiel nehme ich immer Node29 - das ist der Rolladen am Dachfenster. Die States sehen nach dem Update so aus:
Die States sind so sicher nicht korrekt (open = true?) Schreibe ich, wie zu sehen, einen Wert in target dann dauert es Minuten bis der Rolladen fährt und dann als current auftaucht. Ich denke ich werde jetzt wieder zwei bis drei Stunden warten dürfen, bis das meiste wieder funktioniert.
Log:
2022-09-04T09:43:11.409Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2022-09-04T09:43:11.411Z DRIVER version 10.0.3
2022-09-04T09:43:11.411Z DRIVER
2022-09-04T09:43:11.412Z DRIVER starting driver...
2022-09-04T09:43:11.438Z DRIVER opening serial port /dev/serial/by-id/usb-0658_0200-if00
2022-09-04T09:43:11.465Z DRIVER serial port opened
2022-09-04T09:43:11.467Z SERIAL » [NAK] (0x15)
2022-09-04T09:43:11.481Z DRIVER loading configuration...
2022-09-04T09:43:11.513Z CONFIG version 10.0.3
2022-09-04T09:43:12.506Z SERIAL « 0x010f00040003097105000000ff0708007a (17 bytes)
2022-09-04T09:43:12.515Z DRIVER Dropping message because the driver is not ready to handle it yet.
2022-09-04T09:43:12.516Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:12.708Z SERIAL « 0x0107001301011c56a1 (9 bytes)
2022-09-04T09:43:12.710Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:12.718Z DRIVER « [REQ] [SendData]
callback id: 1
transmit status: NoAck
2022-09-04T09:43:12.728Z DRIVER handling request SendData (19)
2022-09-04T09:43:12.728Z DRIVER no handlers registered!
2022-09-04T09:43:19.593Z CONFIG Device index regenerated
2022-09-04T09:43:19.644Z DRIVER beginning interview...
2022-09-04T09:43:19.646Z DRIVER added request handler for AddNodeToNetwork (0x4a)...
1 registered
2022-09-04T09:43:19.647Z DRIVER added request handler for RemoveNodeFromNetwork (0x4b)...
1 registered
2022-09-04T09:43:19.647Z DRIVER added request handler for ReplaceFailedNode (0x63)...
1 registered
2022-09-04T09:43:19.648Z CNTRLR querying controller IDs...
2022-09-04T09:43:19.938Z SERIAL » 0x01030020dc (5 bytes)
2022-09-04T09:43:19.939Z DRIVER » [REQ] [GetControllerId]
2022-09-04T09:43:19.943Z SERIAL « [ACK] (0x06)
2022-09-04T09:43:19.947Z SERIAL « 0x01080120e919d96e0190 (10 bytes)
2022-09-04T09:43:19.949Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:19.950Z DRIVER « [RES] [GetControllerId]
home ID: 0xe919d96e
own node ID: 1
2022-09-04T09:43:19.964Z CNTRLR received controller IDs:
home ID: 0xe919d96e
own node ID: 1
2022-09-04T09:43:19.964Z CNTRLR querying API capabilities...
2022-09-04T09:43:19.976Z SERIAL » 0x01030007fb (5 bytes)
2022-09-04T09:43:19.977Z DRIVER » [REQ] [GetSerialApiCapabilities]
2022-09-04T09:43:19.981Z SERIAL « [ACK] (0x06)
2022-09-04T09:43:19.983Z SERIAL « 0x012b01070506011504000001fe83ff88cf1f0000fb9f7da067008080008086000 (45 bytes)
000e87300000e0000401a000d
2022-09-04T09:43:19.985Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:19.987Z DRIVER « [RES] [GetSerialApiCapabilities]
payload: 0x0506011504000001fe83ff88cf1f0000fb9f7da067008080008086000000e8730
0000e0000401a00
2022-09-04T09:43:19.995Z CNTRLR received API capabilities:
firmware version: 5.6
manufacturer ID: 0x0115
product type: 0x0400
product ID: 0x01
supported functions:
· GetSerialApiInitData (0x02)
· SetApplicationNodeInformation (0x03)
· ApplicationCommand (0x04)
· GetControllerCapabilities (0x05)
· SetSerialApiTimeouts (0x06)
· GetSerialApiCapabilities (0x07)
· SoftReset (0x08)
· GetProtocolVersion (0x09)
· SerialAPIStarted (0x0a)
· SetRFReceiveMode (0x10)
· UNKNOWN_FUNC_SET_SLEEP_MODE (0x11)
· FUNC_ID_ZW_SEND_NODE_INFORMATION (0x12)
· SendData (0x13)
· SendDataMulticast (0x14)
· GetControllerVersion (0x15)
· SendDataAbort (0x16)
· FUNC_ID_ZW_R_F_POWER_LEVEL_SET (0x17)
· UNKNOWN_FUNC_SEND_DATA_META (0x18)
· FUNC_ID_ZW_GET_RANDOM (0x1c)
· GetControllerId (0x20)
· UNKNOWN_FUNC_MEMORY_GET_BYTE (0x21)
· UNKNOWN_FUNC_MEMORY_PUT_BYTE (0x22)
· UNKNOWN_FUNC_MEMORY_GET_BUFFER (0x23)
· UNKNOWN_FUNC_MEMORY_PUT_BUFFER (0x24)
· UNKNOWN_FUNC_FlashAutoProgSet (0x27)
· UNKNOWN_FUNC_UNKNOWN_0x28 (0x28)
· GetNVMId (0x29)
· ExtNVMReadLongBuffer (0x2a)
· ExtNVMWriteLongBuffer (0x2b)
· ExtNVMReadLongByte (0x2c)
· ExtExtWriteLongByte (0x2d)
· GetNodeProtocolInfo (0x41)
· HardReset (0x42)
· FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
· FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
· AssignReturnRoute (0x46)
· DeleteReturnRoute (0x47)
· RequestNodeNeighborUpdate (0x48)
· ApplicationUpdateRequest (0x49)
· AddNodeToNetwork (0x4a)
· RemoveNodeFromNetwork (0x4b)
· FUNC_ID_ZW_CREATE_NEW_PRIMARY (0x4c)
· FUNC_ID_ZW_CONTROLLER_CHANGE (0x4d)
· FUNC_ID_ZW_SET_LEARN_MODE (0x50)
· AssignSUCReturnRoute (0x51)
· FUNC_ID_ZW_REQUEST_NETWORK_UPDATE (0x53)
· SetSUCNodeId (0x54)
· DeleteSUCReturnRoute (0x55)
· GetSUCNodeId (0x56)
· UNKNOWN_FUNC_SEND_SUC_ID (0x57)
· FUNC_ID_ZW_EXPLORE_REQUEST_INCLUSION (0x5e)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
· UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
· UNKNOWN_FUNC_UNKNOWN_0x78 (0x78)
· GetRoutingInfo (0x80)
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· UNKNOWN_FUNC_GET_PRIORITY_ROUTE (0x92)
· UNKNOWN_FUNC_SET_PRIORITY_ROUTE (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· UNKNOWN_FUNC_UNKNOWN_0xB4 (0xb4)
· UNKNOWN_FUNC_WATCH_DOG_ENABLE (0xb6)
· UNKNOWN_FUNC_WATCH_DOG_DISABLE (0xb7)
· UNKNOWN_FUNC_WATCH_DOG_KICK (0xb8)
· UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
· UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
· UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
· UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
· UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)
· UNKNOWN_FUNC_ZMEFreqChange (0xf2)
· UNKNOWN_FUNC_ZMEBootloaderFlash (0xf4)
· UNKNOWN_FUNC_ZMECapabilities (0xf5)
2022-09-04T09:43:20.107Z CNTRLR querying version info...
2022-09-04T09:43:20.121Z SERIAL » 0x01030015e9 (5 bytes)
2022-09-04T09:43:20.122Z DRIVER » [REQ] [GetControllerVersion]
2022-09-04T09:43:20.124Z SERIAL « [ACK] (0x06)
2022-09-04T09:43:20.127Z SERIAL « 0x011001155a2d5761766520342e3035000197 (18 bytes)
2022-09-04T09:43:20.128Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:20.129Z DRIVER « [RES] [GetControllerVersion]
payload: 0x5a2d5761766520342e30350001
2022-09-04T09:43:20.137Z CNTRLR received version info:
controller type: Static Controller
library version: Z-Wave 4.05
2022-09-04T09:43:20.138Z CNTRLR querying protocol version info...
2022-09-04T09:43:20.149Z SERIAL » 0x01030009f5 (5 bytes)
2022-09-04T09:43:20.150Z DRIVER » [REQ] [GetProtocolVersion]
2022-09-04T09:43:20.153Z SERIAL « [ACK] (0x06)
2022-09-04T09:43:20.157Z SERIAL « 0x0107010900040500f1 (9 bytes)
2022-09-04T09:43:20.158Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:20.160Z DRIVER « [RES] [GetProtocolVersion]
payload: 0x00040500
2022-09-04T09:43:20.168Z CNTRLR received protocol version info:
protocol type: Z-Wave
protocol version: 4.5.0
2022-09-04T09:43:20.171Z CNTRLR supported Z-Wave features:
2022-09-04T09:43:20.172Z CNTRLR querying controller capabilities...
2022-09-04T09:43:20.183Z SERIAL » 0x01030005f9 (5 bytes)
2022-09-04T09:43:20.184Z DRIVER » [REQ] [GetControllerCapabilities]
2022-09-04T09:43:20.186Z SERIAL « [ACK] (0x06)
2022-09-04T09:43:20.189Z SERIAL « 0x010401051ce3 (6 bytes)
2022-09-04T09:43:20.190Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:20.191Z DRIVER « [RES] [GetControllerCapabilities]
payload: 0x1c
2022-09-04T09:43:20.198Z CNTRLR received controller capabilities:
controller role: primary
is the SUC: true
started this network: true
SIS is present: true
was real primary: true
2022-09-04T09:43:20.199Z CNTRLR finding SUC...
2022-09-04T09:43:20.210Z SERIAL » 0x01030056aa (5 bytes)
2022-09-04T09:43:20.211Z DRIVER » [REQ] [GetSUCNodeId]
2022-09-04T09:43:20.214Z SERIAL « [ACK] (0x06)
2022-09-04T09:43:20.216Z SERIAL « 0x0104015601ad (6 bytes)
2022-09-04T09:43:20.217Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:20.218Z DRIVER « [RES] [GetSUCNodeId]
payload: 0x01
2022-09-04T09:43:20.224Z CNTRLR This is the SUC
2022-09-04T09:43:20.225Z CNTRLR querying additional controller information...
2022-09-04T09:43:20.241Z SERIAL » 0x01030002fe (5 bytes)
2022-09-04T09:43:20.242Z DRIVER » [REQ] [GetSerialApiInitData]
2022-09-04T09:43:20.245Z SERIAL « [ACK] (0x06)
2022-09-04T09:43:20.337Z SERIAL « 0x0125010205081d0d2dc97f3e07000000000000000000000000000000000000000 (39 bytes)
0000000050063
2022-09-04T09:43:20.339Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:20.340Z DRIVER « [RES] [GetSerialApiInitData]
payload: 0x05081d0d2dc97f3e0700000000000000000000000000000000000000000000000
500
2022-09-04T09:43:20.346Z CNTRLR received additional controller information:
Z-Wave API version: 5 (legacy)
Z-Wave chip type: ZW050x
node type Controller
controller role: primary
controller is the SIS: true
controller supports timers: false
nodes in the network: 1, 3, 4, 9, 11, 12, 14, 17, 20, 23, 24, 25, 26,
27, 28, 29, 30, 31, 34, 35, 36, 37, 38, 41, 42, 43
2022-09-04T09:43:20.451Z DRIVER Cache file for homeId 0xe919d96e found, attempting to restore the network from
cache...
2022-09-04T09:43:20.462Z CNTRLR [Node 001] Embedded device config loaded
2022-09-04T09:43:20.506Z CNTRLR [Node 003] Embedded device config loaded
2022-09-04T09:43:20.510Z CNTRLR [Node 009] Embedded device config loaded
2022-09-04T09:43:20.515Z CNTRLR [Node 011] Embedded device config loaded
2022-09-04T09:43:20.548Z CNTRLR [Node 012] Embedded device config loaded
2022-09-04T09:43:20.555Z CNTRLR [Node 014] Embedded device config loaded
2022-09-04T09:43:20.594Z CNTRLR [Node 017] Embedded device config loaded
2022-09-04T09:43:20.626Z CNTRLR [Node 020] Embedded device config loaded
2022-09-04T09:43:20.656Z CNTRLR [Node 023] Embedded device config loaded
2022-09-04T09:43:20.666Z CNTRLR [Node 024] Embedded device config loaded
2022-09-04T09:43:20.678Z CNTRLR [Node 026] Embedded device config loaded
2022-09-04T09:43:20.689Z CNTRLR [Node 027] Embedded device config loaded
2022-09-04T09:43:20.701Z CNTRLR [Node 028] Embedded device config loaded
2022-09-04T09:43:20.712Z CNTRLR [Node 029] Embedded device config loaded
2022-09-04T09:43:20.725Z CNTRLR [Node 030] Embedded device config loaded
2022-09-04T09:43:20.757Z CNTRLR [Node 034] Embedded device config loaded
2022-09-04T09:43:20.791Z CNTRLR [Node 035] Embedded device config loaded
2022-09-04T09:43:20.816Z CNTRLR [Node 036] Embedded device config loaded
2022-09-04T09:43:20.834Z CNTRLR [Node 037] Embedded device config loaded
2022-09-04T09:43:20.860Z CNTRLR [Node 038] Embedded device config loaded
2022-09-04T09:43:20.867Z CNTRLR [Node 041] Embedded device config loaded
2022-09-04T09:43:20.876Z CNTRLR [Node 042] Embedded device config loaded
2022-09-04T09:43:20.884Z CNTRLR [Node 043] Embedded device config loaded
2022-09-04T09:43:20.887Z DRIVER Restoring the network from cache was successful!
2022-09-04T09:43:20.891Z CNTRLR [Node 001] [Manufacturer Specific] manufacturerId: metadata updated
2022-09-04T09:43:20.892Z CNTRLR [Node 001] [Manufacturer Specific] productType: metadata updated
2022-09-04T09:43:20.893Z CNTRLR [Node 001] [Manufacturer Specific] productId: metadata updated
2022-09-04T09:43:20.895Z CNTRLR [Node 001] [~] [Manufacturer Specific] manufacturerId: 277 => 277
2022-09-04T09:43:20.896Z CNTRLR [Node 001] [~] [Manufacturer Specific] productType: 1024 => 1024
2022-09-04T09:43:20.897Z CNTRLR [Node 001] [~] [Manufacturer Specific] productId: 1 => 1
2022-09-04T09:43:20.899Z CNTRLR [Node 001] [Version] firmwareVersions: metadata updated
2022-09-04T09:43:20.899Z CNTRLR [Node 001] [~] [Version] firmwareVersions: 5.6 => 5.6
2022-09-04T09:43:20.900Z CNTRLR [Node 001] [Version] sdkVersion: metadata updated
2022-09-04T09:43:20.901Z CNTRLR [Node 001] [~] [Version] sdkVersion: "4.5.0" => "4.5.0"
2022-09-04T09:43:20.901Z CNTRLR setting serial API timeouts: ack = 2000 ms, byte = 150 ms
2022-09-04T09:43:20.911Z SERIAL » 0x01050006c80f3b (7 bytes)
2022-09-04T09:43:20.912Z DRIVER » [REQ] [SetSerialApiTimeouts]
payload: 0xc80f
2022-09-04T09:43:20.916Z SERIAL « [ACK] (0x06)
2022-09-04T09:43:20.918Z SERIAL « 0x01050106c80f3a (7 bytes)
2022-09-04T09:43:20.919Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:20.920Z DRIVER « [RES] [SetSerialApiTimeouts]
payload: 0xc80f
2022-09-04T09:43:20.926Z CNTRLR serial API timeouts overwritten. The old values were: ack = 2000 ms, byte = 15
0 ms
2022-09-04T09:43:20.926Z CNTRLR Interview completed
2022-09-04T09:43:20.927Z DRIVER Network key for S0 configured, enabling S0 security manager...
2022-09-04T09:43:20.930Z DRIVER No network key for S2 configured, communication with secure (S2) devices won't
work!
2022-09-04T09:43:20.930Z DRIVER driver ready
2022-09-04T09:43:20.935Z CNTRLR [Node 001] The node is alive.
2022-09-04T09:43:20.936Z CNTRLR [Node 001] The node is ready to be used
2022-09-04T09:43:20.938Z CNTRLR [Node 003] The node is asleep.
2022-09-04T09:43:20.940Z CNTRLR [Node 003] The node is ready to be used
2022-09-04T09:43:20.943Z CNTRLR [Node 004] Beginning interview - last completed stage: ProtocolInfo
2022-09-04T09:43:20.944Z CNTRLR » [Node 004] pinging the node...
2022-09-04T09:43:21.008Z CNTRLR » [Node 009] pinging the node...
2022-09-04T09:43:21.012Z CNTRLR [Node 011] The node is asleep.
2022-09-04T09:43:21.022Z CNTRLR [Node 011] The node is ready to be used
2022-09-04T09:43:21.024Z CNTRLR [Node 012] The node is asleep.
2022-09-04T09:43:21.026Z CNTRLR [Node 012] The node is ready to be used
2022-09-04T09:43:21.027Z CNTRLR [Node 014] The node is asleep.
2022-09-04T09:43:21.029Z CNTRLR [Node 014] The node is ready to be used
2022-09-04T09:43:21.030Z CNTRLR [Node 017] The node is asleep.
2022-09-04T09:43:21.042Z CNTRLR [Node 017] The node is ready to be used
2022-09-04T09:43:21.043Z CNTRLR [Node 020] The node is asleep.
2022-09-04T09:43:21.045Z CNTRLR [Node 020] The node is ready to be used
2022-09-04T09:43:21.046Z CNTRLR » [Node 023] pinging the node...
2022-09-04T09:43:21.050Z CNTRLR » [Node 024] pinging the node...
2022-09-04T09:43:21.055Z CNTRLR [Node 025] Beginning interview - last completed stage: ProtocolInfo
2022-09-04T09:43:21.055Z CNTRLR » [Node 025] pinging the node...
2022-09-04T09:43:21.059Z CNTRLR » [Node 026] pinging the node...
2022-09-04T09:43:21.062Z CNTRLR » [Node 027] pinging the node...
2022-09-04T09:43:21.066Z CNTRLR » [Node 028] pinging the node...
2022-09-04T09:43:21.069Z CNTRLR » [Node 029] pinging the node...
2022-09-04T09:43:21.073Z CNTRLR » [Node 030] pinging the node...
2022-09-04T09:43:21.078Z CNTRLR [Node 031] The node is asleep.
2022-09-04T09:43:21.082Z CNTRLR [Node 031] Beginning interview - last completed stage: NodeInfo
2022-09-04T09:43:21.089Z CNTRLR [Node 031] Interviewing Wake Up...
2022-09-04T09:43:21.089Z CNTRLR » [Node 031] retrieving wakeup capabilities from the device...
2022-09-04T09:43:21.091Z CNTRLR » [Node 034] pinging the node...
2022-09-04T09:43:21.095Z CNTRLR [Node 035] The node is asleep.
2022-09-04T09:43:21.097Z CNTRLR [Node 035] The node is ready to be used
2022-09-04T09:43:21.098Z CNTRLR » [Node 036] pinging the node...
2022-09-04T09:43:21.102Z CNTRLR » [Node 037] pinging the node...
2022-09-04T09:43:21.106Z CNTRLR » [Node 038] pinging the node...
2022-09-04T09:43:21.110Z CNTRLR [Node 041] The node is asleep.
2022-09-04T09:43:21.112Z CNTRLR [Node 041] The node is ready to be used
2022-09-04T09:43:21.113Z CNTRLR » [Node 042] pinging the node...
2022-09-04T09:43:21.117Z CNTRLR » [Node 043] pinging the node...
2022-09-04T09:43:21.126Z SERIAL » 0x010800130401002501c5 (10 bytes)
2022-09-04T09:43:21.128Z DRIVER » [Node 004] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 1
└─[NoOperationCC]
2022-09-04T09:43:21.129Z CNTRLR [Node 031] Error during node interview: Node #31 does not support the command
IntervalCapabilitiesGet! (ZW0302)
2022-09-04T09:43:21.130Z CNTRLR » [Node 031] Assigning SUC return route...
2022-09-04T09:43:21.147Z SERIAL « [ACK] (0x06)
2022-09-04T09:43:21.150Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:43:21.151Z SERIAL » [ACK] (0x06)
2022-09-04T09:43:21.154Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:43:21.180Z DRIVER Checking for configuration updates...
2022-09-04T09:43:21.983Z DRIVER No configuration update available...
2022-09-04T09:44:26.169Z SERIAL » 0x01030016ea (5 bytes)
2022-09-04T09:44:26.170Z DRIVER » [REQ] [SendDataAbort]
2022-09-04T09:44:26.177Z CNTRLR [Node 004] ping failed: Timeout while waiting for a callback from the controll
er (ZW0200)
2022-09-04T09:44:26.180Z CNTRLR » [Node 004] querying node info...
2022-09-04T09:44:28.193Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-09-04T09:44:28.296Z SERIAL » 0x01030016ea (5 bytes)
2022-09-04T09:44:28.297Z DRIVER » [REQ] [SendDataAbort]
2022-09-04T09:44:30.301Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-09-04T09:44:31.414Z SERIAL » 0x01030016ea (5 bytes)
2022-09-04T09:44:31.415Z DRIVER » [REQ] [SendDataAbort]
2022-09-04T09:44:33.423Z SERIAL » 0x010800130901002502cb (10 bytes)
2022-09-04T09:44:33.424Z DRIVER » [Node 009] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 2
└─[NoOperationCC]
2022-09-04T09:44:33.479Z SERIAL « [ACK] (0x06)
2022-09-04T09:44:33.482Z SERIAL « 0x01090004082b0380036435 (11 bytes)
2022-09-04T09:44:33.486Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:33.491Z CNTRLR [Node 043] [~] [Battery] level: 100 => 100 [Endpoint 0]
2022-09-04T09:44:33.493Z CNTRLR [Node 043] [~] [Battery] isLow: false => false [Endpoint 0]
2022-09-04T09:44:33.495Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[BatteryCCReport]
level: 100
is low: false
2022-09-04T09:44:33.501Z SERIAL « [CAN] (0x18)
2022-09-04T09:44:33.503Z SERIAL « [CAN] (0x18)
2022-09-04T09:44:33.505Z SERIAL « [CAN] (0x18)
2022-09-04T09:44:33.541Z SERIAL « 0x010c0004002b063105012200d914 (14 bytes)
2022-09-04T09:44:33.543Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:33.546Z CNTRLR [Node 043] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-09-04T09:44:33.548Z CNTRLR [Node 043] [~] [Multilevel Sensor] Air temperature: 21.8 => 21.7 [Endpoint 0]
2022-09-04T09:44:33.550Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 21.7
2022-09-04T09:44:33.603Z SERIAL « 0x010c0004002b063105012200d914 (14 bytes)
2022-09-04T09:44:33.607Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:33.609Z CNTRLR [Node 043] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-09-04T09:44:33.611Z CNTRLR [Node 043] [~] [Multilevel Sensor] Air temperature: 21.7 => 21.7 [Endpoint 0]
2022-09-04T09:44:33.613Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 21.7
2022-09-04T09:44:33.643Z SERIAL « 0x0107001301011c54a3 (9 bytes)
2022-09-04T09:44:33.645Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:33.648Z DRIVER « [REQ] [SendData]
callback id: 1
transmit status: NoAck
2022-09-04T09:44:33.652Z DRIVER handling request SendData (19)
2022-09-04T09:44:33.653Z DRIVER no handlers registered!
2022-09-04T09:44:36.952Z SERIAL « 0x01090004080303300300c9 (11 bytes)
2022-09-04T09:44:36.954Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:36.958Z CNTRLR [Node 003] [Binary Sensor] Any: metadata updated [Endpoint 0]
2022-09-04T09:44:36.960Z CNTRLR [Node 003] [~] [Binary Sensor] Any: false => false [Endpoint 0]
2022-09-04T09:44:36.962Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
│ type: multicast
└─[BinarySensorCCReport]
type: Any
value: false
2022-09-04T09:44:36.971Z SERIAL « 0x01090004000303300300c1 (11 bytes)
2022-09-04T09:44:36.972Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:36.979Z CNTRLR [Node 003] [Binary Sensor] Any: metadata updated [Endpoint 0]
2022-09-04T09:44:36.982Z CNTRLR [Node 003] [~] [Binary Sensor] Any: false => false [Endpoint 0]
2022-09-04T09:44:36.984Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
└─[BinarySensorCCReport]
type: Any
value: false
2022-09-04T09:44:37.074Z SERIAL « 0x01090004080303200100db (11 bytes)
2022-09-04T09:44:37.075Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:37.076Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
│ type: multicast
└─[BasicCCSet]
target value: 0
2022-09-04T09:44:37.080Z CNTRLR [Node 003] treating BasicCC::Set as a report
2022-09-04T09:44:37.081Z CNTRLR [Node 003] [~] [Basic] currentValue: 0 => 0 [Endpoint 0]
2022-09-04T09:44:37.091Z SERIAL « 0x01090004000303200100d3 (11 bytes)
2022-09-04T09:44:37.092Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:37.093Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
└─[BasicCCSet]
target value: 0
2022-09-04T09:44:37.096Z CNTRLR [Node 003] treating BasicCC::Set as a report
2022-09-04T09:44:37.096Z CNTRLR [Node 003] [~] [Basic] currentValue: 0 => 0 [Endpoint 0]
2022-09-04T09:44:43.484Z CNTRLR No response from controller after 1/3 attempts. Scheduling next try in 100 ms.
2022-09-04T09:44:43.587Z SERIAL » 0x010800130901002502cb (10 bytes)
2022-09-04T09:44:43.589Z DRIVER » [Node 009] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 2
└─[NoOperationCC]
2022-09-04T09:44:43.594Z SERIAL « [ACK] (0x06)
2022-09-04T09:44:43.599Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:44:43.600Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:43.601Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:44:44.844Z SERIAL « 0x010700130200007d94 (9 bytes)
2022-09-04T09:44:44.845Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:44.847Z DRIVER « [REQ] [SendData]
callback id: 2
transmit status: OK
2022-09-04T09:44:44.860Z CNTRLR [Node 009] The node is alive.
2022-09-04T09:44:44.862Z CNTRLR [Node 009] The node is ready to be used
2022-09-04T09:44:44.873Z CNTRLR « [Node 009] ping successful
2022-09-04T09:44:44.887Z SERIAL » 0x010800131701002503d4 (10 bytes)
2022-09-04T09:44:44.890Z DRIVER » [Node 023] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 3
└─[NoOperationCC]
2022-09-04T09:44:44.897Z SERIAL « [ACK] (0x06)
2022-09-04T09:44:44.903Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:44:44.905Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:44.909Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:44:44.916Z SERIAL « 0x0107001303000003eb (9 bytes)
2022-09-04T09:44:44.918Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:44.920Z DRIVER « [REQ] [SendData]
callback id: 3
transmit status: OK
2022-09-04T09:44:44.930Z CNTRLR [Node 023] The node is alive.
2022-09-04T09:44:44.931Z CNTRLR [Node 023] The node is ready to be used
2022-09-04T09:44:44.936Z CNTRLR « [Node 023] ping successful
2022-09-04T09:44:44.941Z SERIAL » 0x010800131801002504dc (10 bytes)
2022-09-04T09:44:44.942Z DRIVER » [Node 024] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 4
└─[NoOperationCC]
2022-09-04T09:44:44.949Z SERIAL « [ACK] (0x06)
2022-09-04T09:44:44.952Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:44:44.952Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:44.955Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:44:45.086Z SERIAL « 0x010700130400000ee1 (9 bytes)
2022-09-04T09:44:45.087Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:45.089Z DRIVER « [REQ] [SendData]
callback id: 4
transmit status: OK
2022-09-04T09:44:45.095Z CNTRLR [Node 024] The node is alive.
2022-09-04T09:44:45.096Z CNTRLR [Node 024] The node is ready to be used
2022-09-04T09:44:45.102Z CNTRLR « [Node 024] ping successful
2022-09-04T09:44:45.107Z SERIAL » 0x010800131901002505dc (10 bytes)
2022-09-04T09:44:45.108Z DRIVER » [Node 025] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 5
└─[NoOperationCC]
2022-09-04T09:44:45.113Z SERIAL « [ACK] (0x06)
2022-09-04T09:44:50.301Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:44:50.302Z SERIAL » [ACK] (0x06)
2022-09-04T09:44:50.305Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:55.314Z SERIAL » 0x01030016ea (5 bytes)
2022-09-04T09:45:55.315Z DRIVER » [REQ] [SendDataAbort]
2022-09-04T09:45:55.320Z CNTRLR [Node 025] ping failed: Timeout while waiting for a callback from the controll
er (ZW0200)
2022-09-04T09:45:55.323Z CNTRLR » [Node 025] querying node info...
2022-09-04T09:45:57.330Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-09-04T09:45:57.438Z SERIAL » 0x01030016ea (5 bytes)
2022-09-04T09:45:57.439Z DRIVER » [REQ] [SendDataAbort]
2022-09-04T09:45:57.960Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:57.970Z SERIAL » 0x010800131a01002506dc (10 bytes)
2022-09-04T09:45:57.971Z DRIVER » [Node 026] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 6
└─[NoOperationCC]
2022-09-04T09:45:57.974Z SERIAL « 0x01090004082b0380036435 (11 bytes)
2022-09-04T09:45:57.975Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:57.976Z SERIAL « [CAN] (0x18)
2022-09-04T09:45:57.979Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-09-04T09:45:57.980Z SERIAL « [CAN] (0x18)
2022-09-04T09:45:58.009Z CNTRLR [Node 043] [~] [Battery] level: 100 => 100 [Endpoint 0]
2022-09-04T09:45:58.011Z CNTRLR [Node 043] [~] [Battery] isLow: false => false [Endpoint 0]
2022-09-04T09:45:58.013Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[BatteryCCReport]
level: 100
is low: false
2022-09-04T09:45:58.080Z SERIAL » 0x010800131a01002506dc (10 bytes)
2022-09-04T09:45:58.082Z DRIVER » [Node 026] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 6
└─[NoOperationCC]
2022-09-04T09:45:58.084Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:58.089Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:45:58.090Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.091Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:58.148Z SERIAL « 0x0107001306000006eb (9 bytes)
2022-09-04T09:45:58.148Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.150Z DRIVER « [REQ] [SendData]
callback id: 6
transmit status: OK
2022-09-04T09:45:58.155Z CNTRLR [Node 026] The node is alive.
2022-09-04T09:45:58.156Z CNTRLR [Node 026] The node is ready to be used
2022-09-04T09:45:58.161Z CNTRLR « [Node 026] ping successful
2022-09-04T09:45:58.166Z SERIAL » 0x010800131b01002507dc (10 bytes)
2022-09-04T09:45:58.167Z DRIVER » [Node 027] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 7
└─[NoOperationCC]
2022-09-04T09:45:58.172Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:58.183Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:45:58.184Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.186Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:58.222Z SERIAL « 0x0107001307000005e9 (9 bytes)
2022-09-04T09:45:58.223Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.225Z DRIVER « [REQ] [SendData]
callback id: 7
transmit status: OK
2022-09-04T09:45:58.244Z CNTRLR [Node 027] The node is alive.
2022-09-04T09:45:58.245Z CNTRLR [Node 027] The node is ready to be used
2022-09-04T09:45:58.266Z CNTRLR « [Node 027] ping successful
2022-09-04T09:45:58.272Z SERIAL » 0x010800131c01002508d4 (10 bytes)
2022-09-04T09:45:58.273Z DRIVER » [Node 028] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 8
└─[NoOperationCC]
2022-09-04T09:45:58.278Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:58.283Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:45:58.285Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.287Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:58.320Z SERIAL « 0x0107001308000004e7 (9 bytes)
2022-09-04T09:45:58.321Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.324Z DRIVER « [REQ] [SendData]
callback id: 8
transmit status: OK
2022-09-04T09:45:58.331Z CNTRLR [Node 028] The node is alive.
2022-09-04T09:45:58.333Z CNTRLR [Node 028] The node is ready to be used
2022-09-04T09:45:58.345Z CNTRLR « [Node 028] ping successful
2022-09-04T09:45:58.352Z SERIAL » 0x010800131d01002509d4 (10 bytes)
2022-09-04T09:45:58.353Z DRIVER » [Node 029] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 9
└─[NoOperationCC]
2022-09-04T09:45:58.359Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:58.364Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:45:58.365Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.369Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:58.427Z SERIAL « 0x0107001309000006e4 (9 bytes)
2022-09-04T09:45:58.429Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.444Z DRIVER « [REQ] [SendData]
callback id: 9
transmit status: OK
2022-09-04T09:45:58.449Z CNTRLR [Node 029] The node is alive.
2022-09-04T09:45:58.450Z CNTRLR [Node 029] The node is ready to be used
2022-09-04T09:45:58.458Z CNTRLR « [Node 029] ping successful
2022-09-04T09:45:58.462Z SERIAL » 0x010800131e0100250ad4 (10 bytes)
2022-09-04T09:45:58.463Z DRIVER » [Node 030] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 10
└─[NoOperationCC]
2022-09-04T09:45:58.470Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:58.474Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:45:58.475Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.482Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:58.489Z SERIAL « 0x010700130a000002e3 (9 bytes)
2022-09-04T09:45:58.490Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.500Z DRIVER « [REQ] [SendData]
callback id: 10
transmit status: OK
2022-09-04T09:45:58.505Z CNTRLR [Node 030] The node is alive.
2022-09-04T09:45:58.506Z CNTRLR [Node 030] The node is ready to be used
2022-09-04T09:45:58.512Z CNTRLR « [Node 030] ping successful
2022-09-04T09:45:58.519Z SERIAL » 0x01080013220100250be9 (10 bytes)
2022-09-04T09:45:58.520Z DRIVER » [Node 034] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 11
└─[NoOperationCC]
2022-09-04T09:45:58.530Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:58.532Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:45:58.537Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.542Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:58.550Z SERIAL « 0x010700130b000002e2 (9 bytes)
2022-09-04T09:45:58.551Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.553Z DRIVER « [REQ] [SendData]
callback id: 11
transmit status: OK
2022-09-04T09:45:58.560Z CNTRLR [Node 034] The node is alive.
2022-09-04T09:45:58.562Z CNTRLR [Node 034] The node is ready to be used
2022-09-04T09:45:58.571Z CNTRLR « [Node 034] ping successful
2022-09-04T09:45:58.592Z SERIAL » 0x01080013240100250ce8 (10 bytes)
2022-09-04T09:45:58.593Z DRIVER » [Node 036] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 12
└─[NoOperationCC]
2022-09-04T09:45:58.602Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:58.607Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:45:58.608Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.611Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:58.712Z SERIAL « 0x010700130c00000aed (9 bytes)
2022-09-04T09:45:58.713Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.717Z DRIVER « [REQ] [SendData]
callback id: 12
transmit status: OK
2022-09-04T09:45:58.724Z CNTRLR [Node 036] The node is alive.
2022-09-04T09:45:58.725Z CNTRLR [Node 036] The node is ready to be used
2022-09-04T09:45:58.730Z CNTRLR « [Node 036] ping successful
2022-09-04T09:45:58.737Z SERIAL » 0x01080013250100250de8 (10 bytes)
2022-09-04T09:45:58.738Z DRIVER » [Node 037] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 13
└─[NoOperationCC]
2022-09-04T09:45:58.747Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:58.753Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:45:58.754Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.758Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:58.862Z SERIAL « 0x010700130d00000bed (9 bytes)
2022-09-04T09:45:58.863Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.866Z DRIVER « [REQ] [SendData]
callback id: 13
transmit status: OK
2022-09-04T09:45:58.870Z CNTRLR [Node 037] The node is alive.
2022-09-04T09:45:58.871Z CNTRLR [Node 037] The node is ready to be used
2022-09-04T09:45:58.877Z CNTRLR « [Node 037] ping successful
2022-09-04T09:45:58.881Z SERIAL » 0x01080013260100250ee8 (10 bytes)
2022-09-04T09:45:58.882Z DRIVER » [Node 038] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 14
└─[NoOperationCC]
2022-09-04T09:45:58.891Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:58.898Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:45:58.899Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.905Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:58.935Z SERIAL « 0x01090004082b0380036435 (11 bytes)
2022-09-04T09:45:58.937Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:58.959Z CNTRLR [Node 043] [~] [Battery] level: 100 => 100 [Endpoint 0]
2022-09-04T09:45:58.960Z CNTRLR [Node 043] [~] [Battery] isLow: false => false [Endpoint 0]
2022-09-04T09:45:58.961Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[BatteryCCReport]
level: 100
is low: false
2022-09-04T09:45:59.239Z SERIAL « 0x01090004002b038003643d (11 bytes)
2022-09-04T09:45:59.242Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:59.245Z CNTRLR [Node 043] [~] [Battery] level: 100 => 100 [Endpoint 0]
2022-09-04T09:45:59.247Z CNTRLR [Node 043] [~] [Battery] isLow: false => false [Endpoint 0]
2022-09-04T09:45:59.248Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[BatteryCCReport]
level: 100
is low: false
2022-09-04T09:45:59.399Z SERIAL « 0x010700130e000033d6 (9 bytes)
2022-09-04T09:45:59.400Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:59.404Z DRIVER « [REQ] [SendData]
callback id: 14
transmit status: OK
2022-09-04T09:45:59.411Z CNTRLR [Node 038] The node is alive.
2022-09-04T09:45:59.412Z CNTRLR [Node 038] The node is ready to be used
2022-09-04T09:45:59.419Z CNTRLR « [Node 038] ping successful
2022-09-04T09:45:59.426Z SERIAL » 0x010800132a0100250fe5 (10 bytes)
2022-09-04T09:45:59.427Z DRIVER » [Node 042] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 15
└─[NoOperationCC]
2022-09-04T09:45:59.437Z SERIAL « [ACK] (0x06)
2022-09-04T09:45:59.444Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:45:59.445Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:59.450Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:45:59.811Z SERIAL « 0x010c0004002b063105030a0007e0 (14 bytes)
2022-09-04T09:45:59.813Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:59.821Z CNTRLR [Node 043] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-09-04T09:45:59.823Z CNTRLR [Node 043] [~] [Multilevel Sensor] Illuminance: 7 => 7 [Endpoint 0]
2022-09-04T09:45:59.825Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Lux
value: 7
2022-09-04T09:45:59.869Z SERIAL « 0x010c0004082b06310505013400d6 (14 bytes)
2022-09-04T09:45:59.870Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:59.874Z CNTRLR [Node 043] [Multilevel Sensor] Humidity: metadata updated [Endpoint 0]
2022-09-04T09:45:59.876Z CNTRLR [Node 043] [~] [Multilevel Sensor] Humidity: 52 => 52 [Endpoint 0]
2022-09-04T09:45:59.878Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[MultilevelSensorCCReport]
type: Humidity
scale: Percentage value
value: 52
2022-09-04T09:45:59.890Z SERIAL « 0x010c0004002b06310505013400de (14 bytes)
2022-09-04T09:45:59.891Z SERIAL » [ACK] (0x06)
2022-09-04T09:45:59.897Z CNTRLR [Node 043] [Multilevel Sensor] Humidity: metadata updated [Endpoint 0]
2022-09-04T09:45:59.898Z CNTRLR [Node 043] [~] [Multilevel Sensor] Humidity: 52 => 52 [Endpoint 0]
2022-09-04T09:45:59.900Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Humidity
scale: Percentage value
value: 52
2022-09-04T09:46:00.002Z SERIAL « 0x010700130f010039dc (9 bytes)
2022-09-04T09:46:00.003Z SERIAL » [ACK] (0x06)
2022-09-04T09:46:00.005Z DRIVER « [REQ] [SendData]
callback id: 15
transmit status: NoAck
2022-09-04T09:46:00.012Z CNTRLR [Node 042] The node did not respond after 1 attempts, it is presumed dead
2022-09-04T09:46:00.014Z CNTRLR [Node 042] The node is dead.
2022-09-04T09:46:00.032Z CNTRLR [Node 042] ping failed: Failed to send the command after 1 attempts (Status No
Ack) (ZW0204)
2022-09-04T09:46:00.038Z SERIAL » 0x010800132b01002510fb (10 bytes)
2022-09-04T09:46:00.039Z DRIVER » [Node 043] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 16
└─[NoOperationCC]
2022-09-04T09:46:00.051Z SERIAL « [ACK] (0x06)
2022-09-04T09:46:00.067Z SERIAL « 0x0104011300e9 (6 bytes)
2022-09-04T09:46:00.068Z SERIAL » [ACK] (0x06)
2022-09-04T09:46:00.079Z DRIVER « [RES] [SendData]
was sent: false
2022-09-04T09:46:00.083Z CNTRLR The controller response indicated failure after 1/3 attempts. Scheduling next
try in 100 ms.
2022-09-04T09:46:00.108Z SERIAL « 0x010c0004002b063105012200d914 (14 bytes)
2022-09-04T09:46:00.110Z SERIAL » [ACK] (0x06)
2022-09-04T09:46:00.112Z CNTRLR [Node 043] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-09-04T09:46:00.113Z CNTRLR [Node 043] [~] [Multilevel Sensor] Air temperature: 21.7 => 21.7 [Endpoint 0]
2022-09-04T09:46:00.115Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 21.7
2022-09-04T09:46:00.185Z SERIAL » 0x010800132b01002510fb (10 bytes)
2022-09-04T09:46:00.187Z DRIVER » [Node 043] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 16
└─[NoOperationCC]
2022-09-04T09:46:00.194Z SERIAL « [ACK] (0x06)
2022-09-04T09:46:00.197Z SERIAL « 0x0104011300e9 (6 bytes)
2022-09-04T09:46:00.198Z SERIAL » [ACK] (0x06)
2022-09-04T09:46:00.204Z DRIVER « [RES] [SendData]
was sent: false
2022-09-04T09:46:00.208Z CNTRLR The controller response indicated failure after 2/3 attempts. Scheduling next
try in 1100 ms.
2022-09-04T09:46:01.309Z SERIAL » 0x010800132b01002510fb (10 bytes)
2022-09-04T09:46:01.311Z DRIVER » [Node 043] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 16
└─[NoOperationCC]
2022-09-04T09:46:01.558Z SERIAL « [ACK] (0x06)
2022-09-04T09:46:01.565Z SERIAL « 0x0104011300e9 (6 bytes)
2022-09-04T09:46:01.566Z SERIAL » [ACK] (0x06)
2022-09-04T09:46:01.568Z DRIVER « [RES] [SendData]
was sent: false
2022-09-04T09:46:01.578Z CNTRLR [Node 043] ping failed: Failed to send the command after 1 attempts. Transmiss
ion queue full (ZW0202)
2022-09-04T09:46:01.582Z SERIAL » 0x01040060049f (6 bytes)
2022-09-04T09:46:01.583Z DRIVER » [Node 004] [REQ] [RequestNodeInfo]
payload: 0x04
2022-09-04T09:46:01.590Z SERIAL « [ACK] (0x06)
2022-09-04T09:46:01.592Z SERIAL « 0x01040160009a (6 bytes)
2022-09-04T09:46:01.593Z SERIAL » [ACK] (0x06)
2022-09-04T09:46:01.595Z DRIVER « [RES] [RequestNodeInfo]
payload: 0x00
2022-09-04T09:46:01.598Z CNTRLR The controller response indicated failure after 1/3 attempts. Scheduling next
try in 100 ms.
2022-09-04T09:46:01.701Z SERIAL » 0x01040060049f (6 bytes)
2022-09-04T09:46:01.703Z DRIVER » [Node 004] [REQ] [RequestNodeInfo]
payload: 0x04
2022-09-04T09:46:01.707Z SERIAL « [ACK] (0x06)
2022-09-04T09:46:01.709Z SERIAL « 0x01040160009a (6 bytes)
2022-09-04T09:46:01.709Z SERIAL » [ACK] (0x06)
2022-09-04T09:46:01.711Z DRIVER « [RES] [RequestNodeInfo]
payload: 0x00
2022-09-04T09:46:01.713Z CNTRLR The controller response indicated failure after 2/3 attempts. Scheduling next
try in 1100 ms.
2022-09-04T09:46:01.926Z SERIAL « 0x0107001310010025df (9 bytes)
2022-09-04T09:46:01.927Z SERIAL » [ACK] (0x06)
2022-09-04T09:46:01.928Z DRIVER « [REQ] [SendData]
callback id: 16
transmit status: NoAck
2022-09-04T09:46:01.930Z DRIVER handling request SendData (19)
2022-09-04T09:46:01.930Z DRIVER no handlers registered!
2022-09-04T09:46:02.816Z SERIAL » 0x01040060049f (6 bytes)
2022-09-04T09:46:02.817Z DRIVER » [Node 004] [REQ] [RequestNodeInfo]
payload: 0x04
2022-09-04T09:46:02.820Z SERIAL « [ACK] (0x06)
2022-09-04T09:46:02.827Z SERIAL « 0x01040160019b (6 bytes)
2022-09-04T09:46:02.828Z SERIAL » [ACK] (0x06)
2022-09-04T09:46:02.829Z DRIVER « [RES] [RequestNodeInfo]
payload: 0x01
2022-09-04T09:47:07.846Z CNTRLR [Node 004] Interview attempt 1/5 failed, retrying in 5000 ms...
2022-09-04T09:47:07.857Z SERIAL » 0x010a00131d0326010a2511e1 (12 bytes)
2022-09-04T09:47:07.859Z DRIVER » [Node 029] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 17
└─[MultilevelSwitchCCSet]
target value: 10
2022-09-04T09:47:07.860Z CNTRLR » [Node 004] Assigning SUC return route...
2022-09-04T09:47:09.868Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-09-04T09:47:09.970Z SERIAL » 0x010a00131d0326010a2511e1 (12 bytes)
2022-09-04T09:47:09.971Z DRIVER » [Node 029] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 17
└─[MultilevelSwitchCCSet]
target value: 10
2022-09-04T09:47:11.976Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-09-04T09:47:12.853Z CNTRLR [Node 004] Beginning interview - last completed stage: ProtocolInfo
2022-09-04T09:47:12.855Z CNTRLR » [Node 004] pinging the node...
2022-09-04T09:47:13.078Z SERIAL » 0x010a00131d0326010a2511e1 (12 bytes)
2022-09-04T09:47:13.079Z DRIVER » [Node 029] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 17
└─[MultilevelSwitchCCSet]
target value: 10
2022-09-04T09:47:15.084Z CNTRLR [Node 029] did not respond after 1/5 attempts. Scheduling next try in 500 ms.
2022-09-04T09:47:15.180Z SERIAL « [ACK] (0x06)
2022-09-04T09:47:15.194Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:47:15.194Z SERIAL » [ACK] (0x06)
2022-09-04T09:47:15.196Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:47:15.198Z DRIVER « [RES] [SendData] [unexpected]
was sent: true
2022-09-04T09:47:15.198Z DRIVER unexpected response, discarding...
2022-09-04T09:47:15.199Z SERIAL « [CAN] (0x18)
2022-09-04T09:47:15.201Z SERIAL « [CAN] (0x18)
2022-09-04T09:47:15.202Z SERIAL « 0x010c000400110656018407cc39c1 (14 bytes)
2022-09-04T09:47:15.205Z SERIAL » [ACK] (0x06)
2022-09-04T09:47:15.206Z DRIVER « [Node 017] [REQ] [ApplicationCommand]
└─[CRC16CCCommandEncapsulation]
└─[WakeUpCCWakeUpNotification]
2022-09-04T09:47:15.209Z CNTRLR « [Node 017] received wakeup notification
2022-09-04T09:47:15.210Z CNTRLR [Node 017] The node is now awake.
2022-09-04T09:47:15.371Z SERIAL « 0x0107001311000012e8 (9 bytes)
2022-09-04T09:47:15.371Z SERIAL » [ACK] (0x06)
2022-09-04T09:47:15.372Z DRIVER « [REQ] [SendData]
callback id: 17
transmit status: OK
2022-09-04T09:47:15.374Z DRIVER handling request SendData (19)
2022-09-04T09:47:15.374Z DRIVER no handlers registered!
2022-09-04T09:47:15.595Z SERIAL » 0x010a00131d0326010a2511e1 (12 bytes)
2022-09-04T09:47:15.597Z DRIVER » [Node 029] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 17
└─[MultilevelSwitchCCSet]
target value: 10
2022-09-04T09:47:15.601Z SERIAL « [ACK] (0x06)
2022-09-04T09:47:15.608Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:47:15.611Z SERIAL » [ACK] (0x06)
2022-09-04T09:47:15.615Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:47:15.668Z SERIAL « 0x0107001311000007fd (9 bytes)
2022-09-04T09:47:15.669Z SERIAL » [ACK] (0x06)
2022-09-04T09:47:15.670Z DRIVER « [REQ] [SendData]
callback id: 17
transmit status: OK
2022-09-04T09:47:15.679Z CNTRLR [Node 029] [~] [Multilevel Switch] currentValue: 8 => 10 [Endpoint 0]
2022-09-04T09:47:15.687Z SERIAL » 0x010800130401002512d6 (10 bytes)
2022-09-04T09:47:15.688Z DRIVER » [Node 004] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 18
└─[NoOperationCC]
2022-09-04T09:47:15.693Z SERIAL « [ACK] (0x06)
2022-09-04T09:47:15.698Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:47:15.699Z SERIAL » [ACK] (0x06)
2022-09-04T09:47:15.700Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:47:16.213Z CNTRLR » [Node 017] Sending node back to sleep...
2022-09-04T09:48:20.708Z SERIAL » 0x01030016ea (5 bytes)
2022-09-04T09:48:20.709Z DRIVER » [REQ] [SendDataAbort]
2022-09-04T09:48:20.714Z CNTRLR [Node 004] ping failed: Timeout while waiting for a callback from the controll
er (ZW0200)
2022-09-04T09:48:20.716Z CNTRLR » [Node 004] querying node info...
2022-09-04T09:48:22.721Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-09-04T09:48:22.824Z SERIAL » 0x01030016ea (5 bytes)
2022-09-04T09:48:22.826Z DRIVER » [REQ] [SendDataAbort]
2022-09-04T09:48:24.841Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-09-04T09:48:25.943Z SERIAL » 0x01030016ea (5 bytes)
2022-09-04T09:48:25.944Z DRIVER » [REQ] [SendDataAbort]
2022-09-04T09:48:26.349Z CNTRLR [Node 029] Beginning interview - last completed stage: None
2022-09-04T09:48:26.350Z CNTRLR [Node 029] new node, doing a full interview...
2022-09-04T09:48:26.351Z CNTRLR » [Node 029] querying protocol info...
2022-09-04T09:48:27.955Z SERIAL » 0x010900131102840824005e (11 bytes)
2022-09-04T09:48:27.956Z DRIVER » [Node 017] [REQ] [SendData]
│ transmit options: 0x24
│ callback id: 0
└─[WakeUpCCNoMoreInformation]
2022-09-04T09:48:28.006Z SERIAL « [ACK] (0x06)
2022-09-04T09:48:28.010Z SERIAL « [ACK] (0x06)
2022-09-04T09:48:28.013Z SERIAL « [ACK] (0x06)
2022-09-04T09:48:28.016Z SERIAL « [ACK] (0x06)
2022-09-04T09:48:28.020Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:48:28.021Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:28.023Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:48:28.040Z CNTRLR [Node 017] The node is now asleep.
2022-09-04T09:48:28.051Z SERIAL » 0x010400411da7 (6 bytes)
2022-09-04T09:48:28.053Z DRIVER » [REQ] [GetNodeProtocolInfo]
payload: 0x1d
2022-09-04T09:48:28.076Z SERIAL « [ACK] (0x06)
2022-09-04T09:48:28.079Z SERIAL « 0x01090141d39c00041106ea (11 bytes)
2022-09-04T09:48:28.082Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:28.085Z DRIVER « [RES] [GetNodeProtocolInfo]
payload: 0xd39c00041106
2022-09-04T09:48:28.103Z CNTRLR « [Node 029] received response for protocol info:
basic device class: Routing Slave
generic device class: Multilevel Switch
specific device class: Motor Control Class B
node type: End Node
is always listening: true
is frequent listening: false
can route messages: true
supports security: false
supports beaming: true
maximum data rate: 40000 kbps
protocol version: 3
2022-09-04T09:48:28.104Z CNTRLR [Node 029] Interview stage completed: ProtocolInfo
2022-09-04T09:48:28.105Z CNTRLR » [Node 029] querying node info...
2022-09-04T09:48:28.111Z SERIAL » 0x010500510413bc (7 bytes)
2022-09-04T09:48:28.112Z DRIVER » [Node 004] [REQ] [AssignSUCReturnRoute]
payload: 0x0413
2022-09-04T09:48:28.115Z SERIAL « [ACK] (0x06)
2022-09-04T09:48:28.119Z SERIAL « 0x0104015101aa (6 bytes)
2022-09-04T09:48:28.121Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:28.122Z DRIVER « [RES] [AssignSUCReturnRoute]
was executed: true
2022-09-04T09:48:28.128Z SERIAL « 0x010500001302eb (7 bytes)
2022-09-04T09:48:28.128Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:28.129Z DRIVER « [REQ] [undefined]
payload: 0x1302
2022-09-04T09:48:28.132Z DRIVER handling request undefined (0)
2022-09-04T09:48:28.132Z DRIVER no handlers registered!
2022-09-04T09:48:28.946Z SERIAL « 0x01090004082b0380036435 (11 bytes)
2022-09-04T09:48:28.948Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:28.951Z CNTRLR [Node 043] [~] [Battery] level: 100 => 100 [Endpoint 0]
2022-09-04T09:48:28.954Z CNTRLR [Node 043] [~] [Battery] isLow: false => false [Endpoint 0]
2022-09-04T09:48:28.956Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[BatteryCCReport]
level: 100
is low: false
2022-09-04T09:48:28.965Z SERIAL « 0x01090004002b038003643d (11 bytes)
2022-09-04T09:48:28.967Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:28.970Z CNTRLR [Node 043] [~] [Battery] level: 100 => 100 [Endpoint 0]
2022-09-04T09:48:28.973Z CNTRLR [Node 043] [~] [Battery] isLow: false => false [Endpoint 0]
2022-09-04T09:48:28.975Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[BatteryCCReport]
level: 100
is low: false
2022-09-04T09:48:29.039Z SERIAL « 0x010c0004082b063105030a0007e8 (14 bytes)
2022-09-04T09:48:29.040Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:29.042Z CNTRLR [Node 043] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-09-04T09:48:29.043Z CNTRLR [Node 043] [~] [Multilevel Sensor] Illuminance: 7 => 7 [Endpoint 0]
2022-09-04T09:48:29.044Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Lux
value: 7
2022-09-04T09:48:29.052Z SERIAL « 0x010c0004002b063105030a0007e0 (14 bytes)
2022-09-04T09:48:29.053Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:29.055Z CNTRLR [Node 043] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-09-04T09:48:29.056Z CNTRLR [Node 043] [~] [Multilevel Sensor] Illuminance: 7 => 7 [Endpoint 0]
2022-09-04T09:48:29.057Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Lux
value: 7
2022-09-04T09:48:29.129Z SERIAL « 0x010c0004082b06310505013400d6 (14 bytes)
2022-09-04T09:48:29.130Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:29.132Z CNTRLR [Node 043] [Multilevel Sensor] Humidity: metadata updated [Endpoint 0]
2022-09-04T09:48:29.134Z CNTRLR [Node 043] [~] [Multilevel Sensor] Humidity: 52 => 52 [Endpoint 0]
2022-09-04T09:48:29.136Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[MultilevelSensorCCReport]
type: Humidity
scale: Percentage value
value: 52
2022-09-04T09:48:29.143Z SERIAL « 0x010c0004002b06310505013400de (14 bytes)
2022-09-04T09:48:29.144Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:29.146Z CNTRLR [Node 043] [Multilevel Sensor] Humidity: metadata updated [Endpoint 0]
2022-09-04T09:48:29.148Z CNTRLR [Node 043] [~] [Multilevel Sensor] Humidity: 52 => 52 [Endpoint 0]
2022-09-04T09:48:29.149Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Humidity
scale: Percentage value
value: 52
2022-09-04T09:48:29.220Z SERIAL « 0x010c0004082b063105012200d91c (14 bytes)
2022-09-04T09:48:29.221Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:29.223Z CNTRLR [Node 043] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-09-04T09:48:29.224Z CNTRLR [Node 043] [~] [Multilevel Sensor] Air temperature: 21.7 => 21.7 [Endpoint 0]
2022-09-04T09:48:29.225Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 21.7
2022-09-04T09:48:29.232Z SERIAL « 0x010c0004002b063105012200d914 (14 bytes)
2022-09-04T09:48:29.234Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:29.236Z CNTRLR [Node 043] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-09-04T09:48:29.239Z CNTRLR [Node 043] [~] [Multilevel Sensor] Air temperature: 21.7 => 21.7 [Endpoint 0]
2022-09-04T09:48:29.240Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 21.7
2022-09-04T09:48:31.588Z SERIAL « 0x0106004981000031 (8 bytes)
2022-09-04T09:48:31.591Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:31.593Z DRIVER « [REQ] [ApplicationUpdateRequest]
payload: 0x0000
2022-09-04T09:48:31.597Z DRIVER no handlers registered!
2022-09-04T09:48:32.124Z SERIAL « 0x010700130001019c77 (9 bytes)
2022-09-04T09:48:32.125Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:32.126Z DRIVER « [REQ] [SendData]
callback id: 0
transmit status: NoAck
2022-09-04T09:48:32.129Z DRIVER handling request SendData (19)
2022-09-04T09:48:32.129Z DRIVER no handlers registered!
2022-09-04T09:48:58.949Z SERIAL « 0x01090004082b0380036435 (11 bytes)
2022-09-04T09:48:58.950Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:58.951Z CNTRLR [Node 043] [~] [Battery] level: 100 => 100 [Endpoint 0]
2022-09-04T09:48:58.952Z CNTRLR [Node 043] [~] [Battery] isLow: false => false [Endpoint 0]
2022-09-04T09:48:58.953Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[BatteryCCReport]
level: 100
is low: false
2022-09-04T09:48:58.962Z SERIAL « 0x01090004002b038003643d (11 bytes)
2022-09-04T09:48:58.963Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:58.964Z CNTRLR [Node 043] [~] [Battery] level: 100 => 100 [Endpoint 0]
2022-09-04T09:48:58.965Z CNTRLR [Node 043] [~] [Battery] isLow: false => false [Endpoint 0]
2022-09-04T09:48:58.966Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[BatteryCCReport]
level: 100
is low: false
2022-09-04T09:48:59.042Z SERIAL « 0x010c0004082b063105030a0007e8 (14 bytes)
2022-09-04T09:48:59.043Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:59.044Z CNTRLR [Node 043] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-09-04T09:48:59.046Z CNTRLR [Node 043] [~] [Multilevel Sensor] Illuminance: 7 => 7 [Endpoint 0]
2022-09-04T09:48:59.046Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Lux
value: 7
2022-09-04T09:48:59.054Z SERIAL « 0x010c0004002b063105030a0007e0 (14 bytes)
2022-09-04T09:48:59.055Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:59.057Z CNTRLR [Node 043] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-09-04T09:48:59.058Z CNTRLR [Node 043] [~] [Multilevel Sensor] Illuminance: 7 => 7 [Endpoint 0]
2022-09-04T09:48:59.059Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Lux
value: 7
2022-09-04T09:48:59.132Z SERIAL « 0x010c0004082b06310505013400d6 (14 bytes)
2022-09-04T09:48:59.133Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:59.136Z CNTRLR [Node 043] [Multilevel Sensor] Humidity: metadata updated [Endpoint 0]
2022-09-04T09:48:59.137Z CNTRLR [Node 043] [~] [Multilevel Sensor] Humidity: 52 => 52 [Endpoint 0]
2022-09-04T09:48:59.139Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[MultilevelSensorCCReport]
type: Humidity
scale: Percentage value
value: 52
2022-09-04T09:48:59.145Z SERIAL « 0x010c0004002b06310505013400de (14 bytes)
2022-09-04T09:48:59.146Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:59.148Z CNTRLR [Node 043] [Multilevel Sensor] Humidity: metadata updated [Endpoint 0]
2022-09-04T09:48:59.149Z CNTRLR [Node 043] [~] [Multilevel Sensor] Humidity: 52 => 52 [Endpoint 0]
2022-09-04T09:48:59.151Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Humidity
scale: Percentage value
value: 52
2022-09-04T09:48:59.222Z SERIAL « 0x010c0004082b063105012200da1f (14 bytes)
2022-09-04T09:48:59.223Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:59.225Z CNTRLR [Node 043] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-09-04T09:48:59.226Z CNTRLR [Node 043] [~] [Multilevel Sensor] Air temperature: 21.7 => 21.8 [Endpoint 0]
2022-09-04T09:48:59.228Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 21.8
2022-09-04T09:48:59.236Z SERIAL « 0x010c0004002b063105012200da17 (14 bytes)
2022-09-04T09:48:59.237Z SERIAL » [ACK] (0x06)
2022-09-04T09:48:59.239Z CNTRLR [Node 043] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-09-04T09:48:59.240Z CNTRLR [Node 043] [~] [Multilevel Sensor] Air temperature: 21.8 => 21.8 [Endpoint 0]
2022-09-04T09:48:59.242Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 21.8
2022-09-04T09:49:28.952Z SERIAL « 0x01090004082b0380036435 (11 bytes)
2022-09-04T09:49:28.953Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:28.955Z CNTRLR [Node 043] [~] [Battery] level: 100 => 100 [Endpoint 0]
2022-09-04T09:49:28.956Z CNTRLR [Node 043] [~] [Battery] isLow: false => false [Endpoint 0]
2022-09-04T09:49:28.957Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[BatteryCCReport]
level: 100
is low: false
2022-09-04T09:49:28.964Z SERIAL « 0x01090004002b038003643d (11 bytes)
2022-09-04T09:49:28.965Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:28.967Z CNTRLR [Node 043] [~] [Battery] level: 100 => 100 [Endpoint 0]
2022-09-04T09:49:28.968Z CNTRLR [Node 043] [~] [Battery] isLow: false => false [Endpoint 0]
2022-09-04T09:49:28.969Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[BatteryCCReport]
level: 100
is low: false
2022-09-04T09:49:29.044Z SERIAL « 0x010c0004082b063105030a0007e8 (14 bytes)
2022-09-04T09:49:29.045Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:29.047Z CNTRLR [Node 043] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-09-04T09:49:29.048Z CNTRLR [Node 043] [~] [Multilevel Sensor] Illuminance: 7 => 7 [Endpoint 0]
2022-09-04T09:49:29.049Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Lux
value: 7
2022-09-04T09:49:29.057Z SERIAL « 0x010c0004002b063105030a0007e0 (14 bytes)
2022-09-04T09:49:29.058Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:29.060Z CNTRLR [Node 043] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-09-04T09:49:29.061Z CNTRLR [Node 043] [~] [Multilevel Sensor] Illuminance: 7 => 7 [Endpoint 0]
2022-09-04T09:49:29.062Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Lux
value: 7
2022-09-04T09:49:29.136Z SERIAL « 0x010c0004082b06310505013400d6 (14 bytes)
2022-09-04T09:49:29.137Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:29.139Z CNTRLR [Node 043] [Multilevel Sensor] Humidity: metadata updated [Endpoint 0]
2022-09-04T09:49:29.141Z CNTRLR [Node 043] [~] [Multilevel Sensor] Humidity: 52 => 52 [Endpoint 0]
2022-09-04T09:49:29.143Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[MultilevelSensorCCReport]
type: Humidity
scale: Percentage value
value: 52
2022-09-04T09:49:29.148Z SERIAL « 0x010c0004002b06310505013400de (14 bytes)
2022-09-04T09:49:29.150Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:29.153Z CNTRLR [Node 043] [Multilevel Sensor] Humidity: metadata updated [Endpoint 0]
2022-09-04T09:49:29.155Z CNTRLR [Node 043] [~] [Multilevel Sensor] Humidity: 52 => 52 [Endpoint 0]
2022-09-04T09:49:29.156Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Humidity
scale: Percentage value
value: 52
2022-09-04T09:49:29.227Z SERIAL « 0x010c0004082b063105012200d91c (14 bytes)
2022-09-04T09:49:29.228Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:29.230Z CNTRLR [Node 043] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-09-04T09:49:29.232Z CNTRLR [Node 043] [~] [Multilevel Sensor] Air temperature: 21.8 => 21.7 [Endpoint 0]
2022-09-04T09:49:29.233Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
│ type: multicast
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 21.7
2022-09-04T09:49:29.240Z SERIAL « 0x010c0004002b063105012200d914 (14 bytes)
2022-09-04T09:49:29.241Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:29.246Z CNTRLR [Node 043] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-09-04T09:49:29.248Z CNTRLR [Node 043] [~] [Multilevel Sensor] Air temperature: 21.7 => 21.7 [Endpoint 0]
2022-09-04T09:49:29.249Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 21.7
2022-09-04T09:49:33.142Z CNTRLR [Node 004] Assigning SUC return route failed: Timeout while waiting for a call
back from the controller (ZW0200)
2022-09-04T09:49:33.153Z SERIAL » 0x010900131d0226052514e8 (11 bytes)
2022-09-04T09:49:33.155Z DRIVER » [Node 029] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 20
└─[MultilevelSwitchCCStopLevelChange]
2022-09-04T09:49:33.158Z SERIAL « [ACK] (0x06)
2022-09-04T09:49:33.163Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:49:33.165Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:33.167Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:49:33.225Z SERIAL « 0x0107001314000007f8 (9 bytes)
2022-09-04T09:49:33.226Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:33.227Z DRIVER « [REQ] [SendData]
callback id: 20
transmit status: OK
2022-09-04T09:49:33.244Z SERIAL » 0x010900131d0226022515ee (11 bytes)
2022-09-04T09:49:33.245Z DRIVER » [Node 029] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 21
└─[MultilevelSwitchCCGet]
2022-09-04T09:49:33.254Z SERIAL « [ACK] (0x06)
2022-09-04T09:49:33.257Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:49:33.258Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:33.259Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:49:33.316Z SERIAL « 0x0107001315000007f9 (9 bytes)
2022-09-04T09:49:33.317Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:33.318Z DRIVER « [REQ] [SendData]
callback id: 21
transmit status: OK
2022-09-04T09:49:33.363Z SERIAL « 0x01090004001d0326030ac3 (11 bytes)
2022-09-04T09:49:33.366Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:33.370Z CNTRLR [Node 029] [Multilevel Switch] targetValue: metadata updated [Endpoint 0]
2022-09-04T09:49:33.371Z CNTRLR [Node 029] [Multilevel Switch] duration: metadata updated [Endpoint 0]
2022-09-04T09:49:33.373Z CNTRLR [Node 029] [Multilevel Switch] currentValue: metadata updated [Endpoint 0]
2022-09-04T09:49:33.374Z CNTRLR [Node 029] [+] [Multilevel Switch] currentValue: 10 [Endpoint 0]
2022-09-04T09:49:33.375Z DRIVER « [Node 029] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 10
2022-09-04T09:49:33.386Z SERIAL » 0x010a00131d032601082516e4 (12 bytes)
2022-09-04T09:49:33.387Z DRIVER » [Node 029] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 22
└─[MultilevelSwitchCCSet]
target value: 8
2022-09-04T09:49:33.392Z SERIAL « [ACK] (0x06)
2022-09-04T09:49:33.395Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-04T09:49:33.396Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:33.397Z DRIVER « [RES] [SendData]
was sent: true
2022-09-04T09:49:33.506Z SERIAL « 0x010700131600000cf1 (9 bytes)
2022-09-04T09:49:33.507Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:33.508Z DRIVER « [REQ] [SendData]
callback id: 22
transmit status: OK
2022-09-04T09:49:33.519Z CNTRLR [Node 029] [~] [Multilevel Switch] currentValue: 10 => 8 [Endpoint 0]
2022-09-04T09:49:33.529Z SERIAL » 0x010400601982 (6 bytes)
2022-09-04T09:49:33.530Z DRIVER » [Node 025] [REQ] [RequestNodeInfo]
payload: 0x19
2022-09-04T09:49:33.534Z SERIAL « [ACK] (0x06)
2022-09-04T09:49:38.727Z SERIAL « 0x01040160019b (6 bytes)
2022-09-04T09:49:38.728Z SERIAL » [ACK] (0x06)
2022-09-04T09:49:38.729Z DRIVER « [RES] [RequestNodeInfo]
payload: 0x01
2022-09-04T09:49:43.718Z DRIVER destroying driver instance...
2022-09-04T09:49:43.803Z DRIVER driver instance destroyed
Es ist jetzt 12:10 am Sonntag. Und, oh Wunder - alles funktioniert jetzt wieder. Und das nach etwa 7-8 Minuten nach dem Update. Irgend etwas hast du jetzt stark verbessert. Ich würde sogar sagen, das mit 3.0.2 der merkwürdige Bug behoben ist - die Verzögerungen liegen wohl eher am Z-Wave Protokoll, das läuft ja anfänglich eher langsam ab mit hohen Timeouts, Interviewes aller Nodes usw. Ich bin beeindruckt. Genau wie meine Frau :)
Verzögerungen liegen wohl eher am Z-Wave Protokoll, das läuft ja anfänglich eher langsam ab mit hohen Timeouts, Interviewes aller Nodes usw
Eigentlich sollte da nach einem Update gar nichts interviewen. Außer natürlich es war vorher in nem halbfertigen Zustand durch die vorherigen Probleme.
Übrigens sieht man in deinem Log, dass sich der Stick wieder ständig aufhängt. Irgendwas ist da wirklich nicht koscher - ich würde ggf. mal die Spannungsversorgung überprüfen.
Eigentlich sollte da nach einem Update gar nichts interviewen. Außer natürlich es war vorher in nem halbfertigen Zustand durch die vorherigen Probleme.
Ich hatte bei Node29 das Interview manuell neu gestartet. Alle anderen Interview-Anfragen kamen vom Adapter bzw. System.
Übrigens sieht man in deinem Log, dass sich der Stick wieder ständig aufhängt. Irgendwas ist da wirklich nicht koscher - ich würde ggf. mal die Spannungsversorgung überprüfen.
Hmm, das ist ein Meanwell Netzteil mit 5.5V bei 6.5A - ist alles stabil am RPi4 .. ich könnte aber mal auf 5.6V oder 5.7V hochgehen und sehen ob es dann besser wird.
Was soll ich sagen - das Update auf 3.0.3 verlief problemlos. Das aktuelle Update auf 3.0.4 hat exakt die gleichen Probleme wie oben geschildert. Nach manuellem Interview erscheinen wieder die folgenden Log-Einträge (Node 29 ist mein Fibaro Shutter Controller am Dachfenster):
Multilevel Switch: "duration" is not a supported property (ZW0322)
Node 29 does not support the Command Class Multilevel Switch! (ZW0302)
Die Multilevel Switch Datenpunkte sind wieder alle (null) mit Ausnahme von Current und Target. Ich werde jetzt mal wieder alles stromlos schalten und dann neu starten.
Am besten lässt du in Zukunft das Z-Wave Log laufen, dass du es gleich mitliefern kannst. So sieht man leider gar nicht, wo das Problem liegt, oder ob einfach nur dein Stick mal wieder hängt.
Da haste natürlich Recht - ich dachte es wäre aktiviert. Aber Fehlanzeige, die Option war aus. Achja, die Versorgungsspannung habe ich vor Wochen schon etwas erhöht - knapp 5,85V zeigt das Multimeter an. Mehr geht bei mir nicht. Ich kann mir auch nicht vorstellen, das es am Stick liegt - der lief jetzt 14 Tage problemlos vor sich hin. Vor dem nächsten Update schalte ich das Log ein und hänge ein Digital-Oszi mit Speicher an die Spannungsversorgung.
Hat sich eh erledigt. Ich bin auf Home Assistant umgestiegen - gleiches System, gleiche Hardware und alles funktioniert seit Monaten problemlos. Von daher - meine Probleme sind gelöst.
Dann kanns eigentlich nur noch am Betriebssystem liegen. HA verwendet die exakt gleiche Z-Wave library um mit dem Stick zu sprechen, und dazwischen hat es ja die ganze Zeit gehakt.
Sicher möglich. Nur was soll ich als 'normaler' Anwender da ausrichten? Wie schon gesagt - HA auf SSD installiert, eingerichtet und konfiguriert. Lief (fast) alles auf Anhieb - außer das ich YAML hasse :) Aber davon abgesehen bin ich sehr zufrieden und ich kann mich wieder der Visualisierung und der eigentlichen Automation widmen.
Hauptsache es läuft
Nach dem Update auf 3.0.0 funktioniert nichts mehr. Runterfahren, neustart bringt nichts, auch ein Downgrade auf 2.6.0 ergibt keine Änderung. Auch ein Einspielen des aktuellen Backups von heute morgen - keine Änderung.
Meine Z-Wave Datenpunkte sehen alle so aus wie exemplarisch im angehängten Bild zu sehen ist. Wenn ich manuell Werte schreibe (Roller Shutter) dann werden diese entweder gar nicht oder mit einer Verzögerung bis zu zwei Minuten(!) umgesetzt. Bewegungsmelder bleiben stumm - keine State-Änderung. Irgendeine Idee wie ich dies Problem lösen kann?
Ich habe auch schon alles stromlos gemacht, den USB-Dongle raus und wieder rein. Keine Änderung. Die Einträge im Log suggerieren, das alles in Ordnung ist. Aber keiner der Nodes funktioniert derzeit. Manuelles Aufwachen der Geräte bzw. Re-Interview habe ich auch schon durch - keine Änderung. Die States der Bewegungsmelder bleiben stumm.
Im Admin gibt es auch keine Geräteliste mehr wo ich Geräte interviewen, inkludieren oder entfernen kann. Soll das so sein oder fehlt hier etwas?
Ein Screenshot vom Adapter:
Im Log ist folgendes zu finden:
Exemplarisches Bild für meine Z-Wave Datenpunkte:
Mein aktuelles System:
System: ioBroker 6.2.18 Beta Repo Hostname: Casper Platform: Linux arm64 @ Raspberry Pi 4 Memory: 4 GB Node.js: 14.20.0 NPM: 6.14.17 Admin Adapter: 6.2.18 JS-Controller: 4.0.23 JS Script Engine: 6.0.0 Z-Wave Adapter: 3.0.0 (alt: 2.6.0) Zigbee Adapter: 1.7.6 influxDB Adapter: 3.1.8 MQTT Adapter: 4.0.7 (Broker) DasWetter.com: 3.1.4 DWD: 2.8.3 IoT: 1.11.9 Shelly: 6.0.0 Sonoff: 2.5.1 socket.io: 6.1.10 Visualisierung: 1.4.15 WEB-Server: 5.2.5 Web Socket: 2.1.5 Z-Wave Controller: USB ZME-UZB1 Zigbee Controller: CC2652P v3.x
Z-Wave:
7 x Roller Shutter Controller: Fibaro FGRM-222 1 x Multisensor: Aotec MS ZW100 2 x Multisensor: DB5 4 x Multisensor: Fibaro FGMS-001 1 x Siren: Everspring SE812 1 x Water Sensor: Everspring ST812 1 x Water Sensor: Fibaro FGFS-101 3 x Dimmer: Fibaro FGD-212 2 x Main Switches: Greenwave NS310 1 x Window Sensor: Schwaiger ZHS09 1 x Smoke Detector: Vision ZS6101
Zigbee:
1 x Mueller Color LED A60 ZBT-Extended Color 2 x Philips Hue Motion Sensor SML001 6 x Philips Hue White Single Bulb B22 LWB010 1 x Philips Hue White Ambience E14 LTW012 1 x Philips Hue White and Color LCT010 3 x Philips Hue White A60 LWA001
WiFi:
9 x Shelly 1 Switch 1 x Shelly 2.5 Roller Shutter 1 x Logitech Harmony Hub
MQTT | Sonoff (Tasmota):
1 x Weather Station (WiFi) 2 x ESP8266 Radar Motion Sensor (WiFi) 1 x ESP8266 EMS Boiler Controller (WiFi) 1 x ESP8266 Gassensor | Smartmeter | Gas Counter 1 x ESP32 Camserver for Water meter 2 x ESP32 Flood Sensor & LED Controller (WiFi) 1 x ESP32 Ambilight Controller @ Kodi (WiFi) 2 x 10.1" Touch Display @ Raspberry Pi 3+ (WiFi) 1 x 8" Touch Display @ Odroid C2 (OctoPi) 2 x Kodi Mediacenter @ Raspberry 3+ 1 x Vero 4K Mediacenter with OSMC (Kodi)