Snippet content copied to clipboard.
Are you sure to delete this snippet? No, don't delete
  1. 2025-08-10 21:56:52.651 CNTRLR » [Node 130] Association group #2: Querying name... [Endpoint 2]
  2. 2025-08-10 21:56:53.207 CNTRLR « [Node 130] Association group #2 has name "K2BasicSet" [Endpoint 2]
  3. 2025-08-10 21:56:53.207 CNTRLR » [Node 130] Association group #2: Querying command list... [Endpoint 2]
  4. 2025-08-10 21:56:53.739 CNTRLR » [Node 130] Association group #3: Querying name... [Endpoint 2]
  5. 2025-08-10 21:56:54.306 CNTRLR « [Node 130] Association group #3 has name "K2SwitchReport" [Endpoint 2]
  6. 2025-08-10 21:56:54.306 CNTRLR » [Node 130] Association group #3: Querying command list... [Endpoint 2]
  7. 2025-08-10 21:56:54.833 CNTRLR » [Node 130] Association group #4: Querying name... [Endpoint 2]
  8. 2025-08-10 21:56:55.385 CNTRLR « [Node 130] Association group #4 has name "K2Meter" [Endpoint 2]
  9. 2025-08-10 21:56:55.385 CNTRLR » [Node 130] Association group #4: Querying command list... [Endpoint 2]
  10. 2025-08-10 21:56:55.915 CNTRLR » [Node 130] Association group #1: Querying info... [Endpoint 2]
  11. 2025-08-10 21:56:56.459 CNTRLR « [Node 130] Received info for association group #1: [Endpoint 2]
  12. info is dynamic: false
  13. profile: General: Lifeline
  14. 2025-08-10 21:56:56.459 CNTRLR » [Node 130] Association group #2: Querying info... [Endpoint 2]
  15. 2025-08-10 21:56:57.000 CNTRLR « [Node 130] Received info for association group #2: [Endpoint 2]
  16. info is dynamic: false
  17. profile: Control: Key 01
  18. 2025-08-10 21:56:57.000 CNTRLR » [Node 130] Association group #3: Querying info... [Endpoint 2]
  19. 2025-08-10 21:56:57.546 CNTRLR « [Node 130] Received info for association group #3: [Endpoint 2]
  20. info is dynamic: false
  21. profile: General: N/A
  22. 2025-08-10 21:56:57.546 CNTRLR » [Node 130] Association group #4: Querying info... [Endpoint 2]
  23. 2025-08-10 21:56:58.085 CNTRLR « [Node 130] Received info for association group #4: [Endpoint 2]
  24. info is dynamic: false
  25. profile: Meter: Electric
  26. 2025-08-10 21:56:58.086 CNTRLR [Node 130] Interviewing Binary Switch...
  27. 2025-08-10 21:56:58.086 CNTRLR » [Node 130] querying Binary Switch state...
  28. 2025-08-10 21:56:58.590 CNTRLR « [Node 130] received Binary Switch state:
  29. current value: true
  30. 2025-08-10 21:56:58.590 CNTRLR [Node 130] Interviewing Meter...
  31. 2025-08-10 21:56:58.590 CNTRLR » [Node 130] querying meter support...
  32. 2025-08-10 21:56:59.089 CNTRLR « [Node 130] received meter support:
  33. type: Electric
  34. supported scales:
  35. · kWh
  36. · W
  37. supported rate types:
  38. supports reset: true
  39. 2025-08-10 21:56:59.089 CNTRLR » [Node 130] querying meter value (type = Electric, scale = kWh)...
  40. 2025-08-10 21:56:59.631 CNTRLR » [Node 130] querying meter value (type = Electric, scale = W)...
  41. 2025-08-10 21:57:00.158 CNTRLR [Node 130] Interviewing Configuration...
  42. 2025-08-10 21:57:00.158 CNTRLR [Node 130] ConfigurationCC: Loading configuration parameters from device confi
  43. g
  44. 2025-08-10 21:57:00.161 CNTRLR » [Node 130] querying parameter #1 value...
  45. 2025-08-10 21:57:00.674 CNTRLR « [Node 130] parameter #1 has value: 1
  46. 2025-08-10 21:57:00.674 CNTRLR » [Node 130] querying parameter #2 value...
  47. 2025-08-10 21:57:01.190 CNTRLR « [Node 130] parameter #2 has value: 1
  48. 2025-08-10 21:57:01.191 CNTRLR » [Node 130] querying parameter #10 value...
  49. 2025-08-10 21:57:01.708 CNTRLR « [Node 130] parameter #10 has value: 255
  50. 2025-08-10 21:57:01.709 CNTRLR » [Node 130] querying parameter #11 value...
  51. 2025-08-10 21:57:02.223 CNTRLR « [Node 130] parameter #11 has value: 0
  52. 2025-08-10 21:57:02.224 CNTRLR » [Node 130] querying parameter #12 value...
  53. 2025-08-10 21:57:02.746 CNTRLR « [Node 130] parameter #12 has value: 0
  54. 2025-08-10 21:57:02.746 CNTRLR » [Node 130] querying parameter #13 value...
  55. 2025-08-10 21:57:03.266 CNTRLR « [Node 130] parameter #13 has value: 0
  56. 2025-08-10 21:57:03.266 CNTRLR » [Node 130] querying parameter #14 value...
  57. 2025-08-10 21:57:03.780 CNTRLR « [Node 130] parameter #14 has value: 0
  58. 2025-08-10 21:57:03.780 CNTRLR » [Node 130] querying parameter #15 value...
  59. 2025-08-10 21:57:04.296 CNTRLR « [Node 130] parameter #15 has value: 0
  60. 2025-08-10 21:57:04.296 CNTRLR » [Node 130] querying parameter #30 value...
  61. 2025-08-10 21:57:04.810 CNTRLR « [Node 130] parameter #30 has value: 0
  62. 2025-08-10 21:57:04.810 CNTRLR » [Node 130] querying parameter #40 value...
  63. 2025-08-10 21:57:05.327 CNTRLR « [Node 130] parameter #40 has value: 10
  64. 2025-08-10 21:57:05.327 CNTRLR » [Node 130] querying parameter #41 value...
  65. 2025-08-10 21:57:05.846 CNTRLR « [Node 130] parameter #41 has value: 10
  66. 2025-08-10 21:57:05.846 CNTRLR » [Node 130] querying parameter #42 value...
  67. 2025-08-10 21:57:06.354 CNTRLR « [Node 130] parameter #42 has value: 600
  68. 2025-08-10 21:57:06.354 CNTRLR » [Node 130] querying parameter #43 value...
  69. 2025-08-10 21:57:06.873 CNTRLR « [Node 130] parameter #43 has value: 600
  70. 2025-08-10 21:57:06.873 CNTRLR » [Node 130] querying parameter #63 value...
  71. 2025-08-10 21:57:07.390 CNTRLR « [Node 130] parameter #63 has value: 0
  72. 2025-08-10 21:57:07.390 CNTRLR » [Node 130] querying parameter #64 value...
  73. 2025-08-10 21:57:07.905 CNTRLR « [Node 130] parameter #64 has value: 0
  74. 2025-08-10 21:57:07.905 CNTRLR » [Node 130] querying parameter #110 value...
  75. 2025-08-10 21:57:08.423 CNTRLR « [Node 130] parameter #110 has value: 32536
  76. 2025-08-10 21:57:08.423 CNTRLR » [Node 130] querying parameter #120 value...
  77. 2025-08-10 21:57:08.936 CNTRLR « [Node 130] parameter #120 has value: 5
  78. 2025-08-10 21:57:08.936 CNTRLR [Node 130] Interview stage completed: CommandClasses
  79. 2025-08-10 21:57:08.937 CNTRLR [Node 130] Interview stage completed: OverwriteConfig
  80. 2025-08-10 21:57:08.939 CNTRLR [Node 130] Interview completed
  81. 2025-08-10 21:57:08.939 CNTRLR [Node 130] The node is ready to be used
  82. 2025-08-10 21:57:40.068 CNTRLR « [Node 007] received wakeup notification
  83. 2025-08-10 21:57:40.068 CNTRLR [Node 007] The node is now awake.
  84. 2025-08-10 21:57:40.319 CNTRLR » [Node 007] Sending node back to sleep...
  85. 2025-08-10 21:57:40.373 CNTRLR [Node 007] The node is now asleep.
  86. 2025-08-10 21:59:23.926 CNTRLR « [Node 012] received wakeup notification
  87. s6-rc: info: service legacy-services: stopping
  88. Shutting down
  89. Closing server...
  90. Client disconnected
  91. Code 1000:
  92. Server closed
  93. [20:03:09] INFO: Service restart after closing
  94. s6-rc: info: service legacy-services successfully stopped
  95. s6-rc: info: service legacy-cont-init: stopping
  96. s6-rc: info: service legacy-cont-init successfully stopped
  97. s6-rc: info: service fix-attrs: stopping
  98. s6-rc: info: service fix-attrs successfully stopped
  99. s6-rc: info: service s6rc-oneshot-runner: stopping
  100. s6-rc: info: service s6rc-oneshot-runner successfully stopped
  101. s6-rc: info: service s6rc-oneshot-runner: starting
  102. s6-rc: info: service s6rc-oneshot-runner successfully started
  103. s6-rc: info: service fix-attrs: starting
  104. s6-rc: info: service fix-attrs successfully started
  105. s6-rc: info: service legacy-cont-init: starting
  106. cont-init: info: running /etc/cont-init.d/config.sh
  107. [22:03:39] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok.
  108. [22:03:39] INFO: RF region set to Automatic: Europe
  109. [22:03:39] INFO: Setting RF region to (Europe)
  110. [22:03:39] INFO: Soft-reset set to automatic
  111. [22:03:39] INFO: Virtual Machine detected, disabling soft-reset
  112. cont-init: info: /etc/cont-init.d/config.sh exited 0
  113. cont-init: info: running /etc/cont-init.d/structure.sh
  114. cont-init: info: /etc/cont-init.d/structure.sh exited 0
  115. s6-rc: info: service legacy-cont-init successfully started
  116. s6-rc: info: service legacy-services: starting
  117. services-up: info: copying legacy longrun zwave_js (no readiness notification)
  118. s6-rc: info: service legacy-services successfully started
  119. [22:03:39] INFO: Successfully send discovery information to Home Assistant.
  120. 2025-08-10 22:03:40.378 DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
  121. ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
  122. ███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
  123. ███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
  124. ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
  125. ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
  126. 2025-08-10 22:03:40.380 DRIVER version 15.10.0
  127. 2025-08-10 22:03:40.380 DRIVER
  128. 2025-08-10 22:03:40.380 DRIVER starting driver...
  129. 2025-08-10 22:03:40.380 DRIVER opening serial port /dev/ttyACM0
  130. 2025-08-10 22:03:40.636 DRIVER serial port opened
  131. 2025-08-10 22:03:40.637 SERIAL » 0x15 (1 bytes)
  132. 2025-08-10 22:03:41.640 DRIVER loading configuration...
  133. 2025-08-10 22:03:41.645 CONFIG Using external configuration dir /data/db
  134. 2025-08-10 22:03:41.645 CONFIG version 15.10.0
  135. 2025-08-10 22:03:41.859 DRIVER beginning interview...
  136. 2025-08-10 22:03:41.860 DRIVER added request handler for SetLearnMode (0x50)...
  137. 1 registered
  138. 2025-08-10 22:03:41.861 CNTRLR querying Serial API capabilities...
  139. 2025-08-10 22:03:41.946 DRIVER » [REQ] [GetSerialApiCapabilities]
  140. 2025-08-10 22:03:41.946 SERIAL » 0x01030007fb (5 bytes)
  141. 2025-08-10 22:03:41.949 SERIAL « [ACK] (0x06)
  142. 2025-08-10 22:03:41.964 SERIAL « 0x012b0107010200860001005afe877f88cf7fc04ffbdffde067008080008086000 (45 bytes)
  143. 100e87300800f000060000090
  144. 2025-08-10 22:03:41.965 SERIAL » [ACK] (0x06)
  145. 2025-08-10 22:03:41.965 DRIVER « [RES] [GetSerialApiCapabilities]
  146. 2025-08-10 22:03:41.966 CNTRLR received API capabilities:
  147. firmware version: 1.2
  148. manufacturer ID: 0x86
  149. product type: 0x01
  150. product ID: 0x5a
  151. supported functions:
  152. · GetSerialApiInitData (0x02)
  153. · SetApplicationNodeInformation (0x03)
  154. · ApplicationCommand (0x04)
  155. · GetControllerCapabilities (0x05)
  156. · SetSerialApiTimeouts (0x06)
  157. · GetSerialApiCapabilities (0x07)
  158. · SoftReset (0x08)
  159. · GetProtocolVersion (0x09)
  160. · SerialAPIStarted (0x0a)
  161. · SerialAPISetup (0x0b)
  162. · SetRFReceiveMode (0x10)
  163. · UNKNOWN_FUNC_SET_SLEEP_MODE (0x11)
  164. · SendNodeInformation (0x12)
  165. · SendData (0x13)
  166. · SendDataMulticast (0x14)
  167. · GetControllerVersion (0x15)
  168. · SendDataAbort (0x16)
  169. · FUNC_ID_ZW_R_F_POWER_LEVEL_SET (0x17)
  170. · FUNC_ID_ZW_GET_RANDOM (0x1c)
  171. · GetControllerId (0x20)
  172. · UNKNOWN_FUNC_MEMORY_GET_BYTE (0x21)
  173. · UNKNOWN_FUNC_MEMORY_PUT_BYTE (0x22)
  174. · UNKNOWN_FUNC_MEMORY_GET_BUFFER (0x23)
  175. · UNKNOWN_FUNC_MEMORY_PUT_BUFFER (0x24)
  176. · EnterBootloader (0x27)
  177. · UNKNOWN_FUNC_UNKNOWN_0x28 (0x28)
  178. · GetNVMId (0x29)
  179. · ExtNVMReadLongBuffer (0x2a)
  180. · ExtNVMWriteLongBuffer (0x2b)
  181. · ExtNVMReadLongByte (0x2c)
  182. · ExtExtWriteLongByte (0x2d)
  183. · NVMOperations (0x2e)
  184. · undefined (0x2f)
  185. · ClearTxTimers (0x37)
  186. · GetTxTimers (0x38)
  187. · ClearNetworkStats (0x39)
  188. · GetNetworkStats (0x3a)
  189. · GetBackgroundRSSI (0x3b)
  190. · SetListenBeforeTalkThreshold (0x3c)
  191. · RemoveSpecificNodeIdFromNetwork (0x3f)
  192. · GetNodeProtocolInfo (0x41)
  193. · HardReset (0x42)
  194. · FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
  195. · FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
  196. · AssignReturnRoute (0x46)
  197. · DeleteReturnRoute (0x47)
  198. · RequestNodeNeighborUpdate (0x48)
  199. · ApplicationUpdateRequest (0x49)
  200. · AddNodeToNetwork (0x4a)
  201. · RemoveNodeFromNetwork (0x4b)
  202. · AddControllerAndAssignPrimary (0x4c)
  203. · AddPrimaryController (0x4d)
  204. · AssignPriorityReturnRoute (0x4f)
  205. · SetLearnMode (0x50)
  206. · AssignSUCReturnRoute (0x51)
  207. · RequestNetworkUpdate (0x53)
  208. · SetSUCNodeId (0x54)
  209. · DeleteSUCReturnRoute (0x55)
  210. · GetSUCNodeId (0x56)
  211. · SendSUCNodeId (0x57)
  212. · AssignPrioritySUCReturnRoute (0x58)
  213. · ExploreRequestInclusion (0x5e)
  214. · ExploreRequestExclusion (0x5f)
  215. · RequestNodeInfo (0x60)
  216. · RemoveFailedNode (0x61)
  217. · IsFailedNode (0x62)
  218. · ReplaceFailedNode (0x63)
  219. · UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
  220. · UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
  221. · FirmwareUpdateNVM (0x78)
  222. · GetRoutingInfo (0x80)
  223. · LockUnlockLastRoute (0x90)
  224. · GetPriorityRoute (0x92)
  225. · SetPriorityRoute (0x93)
  226. · UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
  227. · FUNC_ID_APPLICATION_SLAVE_COMMAND_HANDLER (0xa1)
  228. · undefined (0xb4)
  229. · EnableWatchdog500 (0xb6)
  230. · DisableWatchdog500 (0xb7)
  231. · KickWatchdog500 (0xb8)
  232. · UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
  233. · UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
  234. · GetLibrary (0xbd)
  235. · SendTestFrame (0xbe)
  236. · GetProtocolStatus (0xbf)
  237. · FUNC_ID_ZW_SET_PROMISCUOUS_MODE (0xd0)
  238. · FUNC_ID_PROMISCUOUS_APPLICATION_COMMAND_HANDLER (0xd1)
  239. · StartWatchdog (0xd2)
  240. · StopWatchdog (0xd3)
  241. · SetMaximumRoutingAttempts (0xd4)
  242. · undefined (0xee)
  243. · undefined (0xef)
  244. 2025-08-10 22:03:41.966 CNTRLR querying additional controller information...
  245. 2025-08-10 22:03:41.967 DRIVER » [REQ] [GetSerialApiInitData]
  246. 2025-08-10 22:03:41.967 SERIAL » 0x01030002fe (5 bytes)
  247. 2025-08-10 22:03:41.969 SERIAL « [ACK] (0x06)
  248. 2025-08-10 22:03:42.079 SERIAL « 0x0125010208081ddfcfaf0a44d065f8672f0e659c018e02c393070000000000000 (39 bytes)
  249. 0000000050018
  250. 2025-08-10 22:03:42.080 SERIAL » [ACK] (0x06)
  251. 2025-08-10 22:03:42.080 DRIVER « [RES] [GetSerialApiInitData]
  252. 2025-08-10 22:03:42.081 CNTRLR received additional controller information:
  253. Z-Wave API version: 8 (legacy)
  254. Z-Wave chip type: ZW050x
  255. node type Controller
  256. controller role: primary
  257. controller is the SIS: true
  258. controller supports timers: false
  259. Z-Wave Classic nodes: 1, 2, 3, 4, 5, 7, 8, 9, 10, 11, 12, 15, 16, 17,
  260. 18, 19, 20, 22, 24, 26, 28, 35, 39, 45, 47, 48, 49, 51, 54, 55, 60, 61, 62, 63
  261. , 64, 65, 66, 67, 70, 71, 73, 74, 75, 76, 78, 82, 83, 84, 89, 91, 94, 95, 99,
  262. 100, 101, 104, 105, 114, 115, 116, 120, 122, 129, 130, 135, 136, 137, 138, 141
  263. , 144, 145, 146, 147
  264. 2025-08-10 22:03:42.081 CNTRLR querying version info...
  265. 2025-08-10 22:03:42.081 DRIVER » [REQ] [GetControllerVersion]
  266. 2025-08-10 22:03:42.081 SERIAL » 0x01030015e9 (5 bytes)
  267. 2025-08-10 22:03:42.083 SERIAL « [ACK] (0x06)
  268. 2025-08-10 22:03:42.092 SERIAL « 0x011001155a2d5761766520362e3037000197 (18 bytes)
  269. 2025-08-10 22:03:42.092 SERIAL » [ACK] (0x06)
  270. 2025-08-10 22:03:42.093 DRIVER « [RES] [GetControllerVersion]
  271. 2025-08-10 22:03:42.093 CNTRLR received version info:
  272. controller type: Static Controller
  273. library version: Z-Wave 6.07
  274. 2025-08-10 22:03:42.093 CNTRLR querying protocol version info...
  275. 2025-08-10 22:03:42.093 DRIVER » [REQ] [GetProtocolVersion]
  276. 2025-08-10 22:03:42.093 SERIAL » 0x01030009f5 (5 bytes)
  277. 2025-08-10 22:03:42.095 SERIAL « [ACK] (0x06)
  278. 2025-08-10 22:03:42.100 SERIAL « 0x010901090006070000619e (11 bytes)
  279. 2025-08-10 22:03:42.100 SERIAL » [ACK] (0x06)
  280. 2025-08-10 22:03:42.101 DRIVER « [RES] [GetProtocolVersion]
  281. 2025-08-10 22:03:42.101 CNTRLR received protocol version info:
  282. protocol type: Z-Wave
  283. protocol version: 6.7.0
  284. appl. framework build no.: 97
  285. 2025-08-10 22:03:42.101 CNTRLR querying controller capabilities...
  286. 2025-08-10 22:03:42.101 DRIVER » [REQ] [GetControllerCapabilities]
  287. 2025-08-10 22:03:42.101 SERIAL » 0x01030005f9 (5 bytes)
  288. 2025-08-10 22:03:42.103 SERIAL « [ACK] (0x06)
  289. 2025-08-10 22:03:42.107 SERIAL « 0x010401051ce3 (6 bytes)
  290. 2025-08-10 22:03:42.107 SERIAL » [ACK] (0x06)
  291. 2025-08-10 22:03:42.108 DRIVER « [RES] [GetControllerCapabilities]
  292. 2025-08-10 22:03:42.108 CNTRLR received controller capabilities:
  293. controller role: Primary
  294. is the SUC: true
  295. started this network: true
  296. SIS is present: true
  297. was real primary: true
  298. 2025-08-10 22:03:42.108 CNTRLR querying serial API setup capabilities...
  299. 2025-08-10 22:03:42.108 DRIVER » [REQ] [SerialAPISetup]
  300. command: GetSupportedCommands
  301. 2025-08-10 22:03:42.109 SERIAL » 0x0104000b01f1 (6 bytes)
  302. 2025-08-10 22:03:42.110 SERIAL « [ACK] (0x06)
  303. 2025-08-10 22:03:42.117 SERIAL « 0x0105010b011eef (7 bytes)
  304. 2025-08-10 22:03:42.118 SERIAL » [ACK] (0x06)
  305. 2025-08-10 22:03:42.118 DRIVER « [RES] [SerialAPISetup]
  306. command: GetSupportedCommands
  307. 2025-08-10 22:03:42.118 CNTRLR supported serial API setup commands:
  308. · GetSupportedCommands
  309. · SetTxStatusReport
  310. · SetPowerlevel
  311. · GetPowerlevel
  312. · GetMaximumPayloadSize
  313. 2025-08-10 22:03:42.118 CNTRLR querying max. payload size...
  314. 2025-08-10 22:03:42.119 DRIVER » [REQ] [SerialAPISetup]
  315. command: GetMaximumPayloadSize
  316. 2025-08-10 22:03:42.119 SERIAL » 0x0104000b10e0 (6 bytes)
  317. 2025-08-10 22:03:42.121 SERIAL « [ACK] (0x06)
  318. 2025-08-10 22:03:42.122 SERIAL « 0x0105010b102ece (7 bytes)
  319. 2025-08-10 22:03:42.123 SERIAL » [ACK] (0x06)
  320. 2025-08-10 22:03:42.123 DRIVER « [RES] [SerialAPISetup]
  321. command: GetMaximumPayloadSize
  322. maximum payload size: 46 bytes
  323. 2025-08-10 22:03:42.123 CNTRLR maximum payload size: 46 bytes
  324. 2025-08-10 22:03:42.123 CNTRLR supported Z-Wave features:
  325. · SmartStart
  326. 2025-08-10 22:03:42.124 CNTRLR Querying configured powerlevel...
  327. 2025-08-10 22:03:42.124 DRIVER » [REQ] [SerialAPISetup]
  328. command: GetPowerlevel
  329. 2025-08-10 22:03:42.124 SERIAL » 0x0104000b08f8 (6 bytes)
  330. 2025-08-10 22:03:42.125 SERIAL « [ACK] (0x06)
  331. 2025-08-10 22:03:42.129 SERIAL « 0x010b010b08000a00000a0000f6 (13 bytes)
  332. 2025-08-10 22:03:42.129 SERIAL » [ACK] (0x06)
  333. 2025-08-10 22:03:42.129 DRIVER « [RES] [SerialAPISetup]
  334. command: GetPowerlevel
  335. normal powerlevel: 0.0 dBm
  336. output power at 0 dBm: 1.0 dBm
  337. 2025-08-10 22:03:42.130 CNTRLR The powerlevel is 0 dBm (1 dBm calibration)
  338. 2025-08-10 22:03:42.130 CNTRLR querying controller IDs...
  339. 2025-08-10 22:03:42.130 DRIVER » [REQ] [GetControllerId]
  340. 2025-08-10 22:03:42.131 SERIAL » 0x01030020dc (5 bytes)
  341. 2025-08-10 22:03:42.132 SERIAL « [ACK] (0x06)
  342. 2025-08-10 22:03:42.137 SERIAL « 0x01080120db2ec6610185 (10 bytes)
  343. 2025-08-10 22:03:42.137 SERIAL » [ACK] (0x06)
  344. 2025-08-10 22:03:42.138 DRIVER « [RES] [GetControllerId]
  345. home ID: 0xdb2ec661
  346. own node ID: 1
  347. 2025-08-10 22:03:42.138 CNTRLR received controller IDs:
  348. home ID: 0xdb2ec661
  349. own node ID: 1
  350. 2025-08-10 22:03:42.138 CNTRLR Enabling TX status report...
  351. 2025-08-10 22:03:42.139 DRIVER » [REQ] [SerialAPISetup]
  352. command: SetTxStatusReport
  353. enabled: true
  354. 2025-08-10 22:03:42.139 SERIAL » 0x0105000b02ff0c (7 bytes)
  355. 2025-08-10 22:03:42.140 SERIAL « [ACK] (0x06)
  356. 2025-08-10 22:03:42.143 SERIAL « 0x0105010b0201f3 (7 bytes)
  357. 2025-08-10 22:03:42.144 SERIAL » [ACK] (0x06)
  358. 2025-08-10 22:03:42.144 DRIVER « [RES] [SerialAPISetup]
  359. command: SetTxStatusReport
  360. success: true
  361. 2025-08-10 22:03:42.144 CNTRLR Enabling TX status report successful...
  362. 2025-08-10 22:03:42.144 CNTRLR finding SUC...
  363. 2025-08-10 22:03:42.144 DRIVER » [REQ] [GetSUCNodeId]
  364. 2025-08-10 22:03:42.144 SERIAL » 0x01030056aa (5 bytes)
  365. 2025-08-10 22:03:42.146 SERIAL « [ACK] (0x06)
  366. 2025-08-10 22:03:42.151 SERIAL « 0x0104015601ad (6 bytes)
  367. 2025-08-10 22:03:42.151 SERIAL » [ACK] (0x06)
  368. 2025-08-10 22:03:42.151 DRIVER « [RES] [GetSUCNodeId]
  369. 2025-08-10 22:03:42.151 CNTRLR This is the SUC
  370. 2025-08-10 22:03:42.151 CNTRLR setting serial API timeouts: ack = 1600 ms, byte = 150 ms
  371. 2025-08-10 22:03:42.152 DRIVER » [REQ] [SetSerialApiTimeouts]
  372. 2025-08-10 22:03:42.152 SERIAL » 0x01050006a00f53 (7 bytes)
  373. 2025-08-10 22:03:42.154 SERIAL « [ACK] (0x06)
  374. 2025-08-10 22:03:42.157 SERIAL « 0x01050106a00f52 (7 bytes)
  375. 2025-08-10 22:03:42.157 SERIAL » [ACK] (0x06)
  376. 2025-08-10 22:03:42.157 DRIVER « [RES] [SetSerialApiTimeouts]
  377. 2025-08-10 22:03:42.157 CNTRLR serial API timeouts overwritten. The old values were: ack = 1600 ms, byte = 15
  378. 0 ms
  379. 2025-08-10 22:03:42.158 DRIVER all queues idle
  380. 2025-08-10 22:03:42.249 DRIVER Cache file for homeId 0xdb2ec661 found, attempting to restore the network from
  381. cache...
  382. 2025-08-10 22:03:42.279 CNTRLR [Node 002] Embedded device config loaded
  383. 2025-08-10 22:03:42.280 CNTRLR [Node 003] No device config found
  384. 2025-08-10 22:03:42.283 CNTRLR [Node 004] Embedded device config loaded
  385. 2025-08-10 22:03:42.303 CNTRLR [Node 005] Embedded device config loaded
  386. 2025-08-10 22:03:42.306 CNTRLR [Node 007] Embedded device config loaded
  387. 2025-08-10 22:03:42.310 CNTRLR [Node 008] Embedded device config loaded
  388. 2025-08-10 22:03:42.314 CNTRLR [Node 009] Embedded device config loaded
  389. 2025-08-10 22:03:42.321 CNTRLR [Node 010] Embedded device config loaded
  390. 2025-08-10 22:03:42.325 CNTRLR [Node 011] Embedded device config loaded
  391. 2025-08-10 22:03:42.335 CNTRLR [Node 012] Embedded device config loaded
  392. 2025-08-10 22:03:42.337 CNTRLR [Node 015] Embedded device config loaded
  393. 2025-08-10 22:03:42.340 CNTRLR [Node 016] Embedded device config loaded
  394. 2025-08-10 22:03:42.341 CNTRLR [Node 017] Embedded device config loaded
  395. 2025-08-10 22:03:42.343 CNTRLR [Node 018] Embedded device config loaded
  396. 2025-08-10 22:03:42.344 CNTRLR [Node 019] Embedded device config loaded
  397. 2025-08-10 22:03:42.347 CNTRLR [Node 020] Embedded device config loaded
  398. 2025-08-10 22:03:42.349 CNTRLR [Node 022] Embedded device config loaded
  399. 2025-08-10 22:03:42.352 CNTRLR [Node 024] Embedded device config loaded
  400. 2025-08-10 22:03:42.356 CNTRLR [Node 026] Embedded device config loaded
  401. 2025-08-10 22:03:42.359 CNTRLR [Node 028] Embedded device config loaded
  402. 2025-08-10 22:03:42.362 CNTRLR [Node 035] Embedded device config loaded
  403. 2025-08-10 22:03:42.364 CNTRLR [Node 039] Embedded device config loaded
  404. 2025-08-10 22:03:42.366 CNTRLR [Node 045] Embedded device config loaded
  405. 2025-08-10 22:03:42.367 CNTRLR [Node 047] Embedded device config loaded
  406. 2025-08-10 22:03:42.370 CNTRLR [Node 048] Embedded device config loaded
  407. 2025-08-10 22:03:42.373 CNTRLR [Node 049] Embedded device config loaded
  408. 2025-08-10 22:03:42.377 CNTRLR [Node 051] Embedded device config loaded
  409. 2025-08-10 22:03:42.381 CNTRLR [Node 054] Embedded device config loaded
  410. 2025-08-10 22:03:42.382 CNTRLR [Node 055] Embedded device config loaded
  411. 2025-08-10 22:03:42.383 CNTRLR [Node 060] Embedded device config loaded
  412. 2025-08-10 22:03:42.384 CNTRLR [Node 061] Embedded device config loaded
  413. 2025-08-10 22:03:42.386 CNTRLR [Node 062] Embedded device config loaded
  414. 2025-08-10 22:03:42.388 CNTRLR [Node 063] Embedded device config loaded
  415. 2025-08-10 22:03:42.390 CNTRLR [Node 064] Embedded device config loaded
  416. 2025-08-10 22:03:42.392 CNTRLR [Node 065] Embedded device config loaded
  417. 2025-08-10 22:03:42.395 CNTRLR [Node 066] Embedded device config loaded
  418. 2025-08-10 22:03:42.396 CNTRLR [Node 067] Embedded device config loaded
  419. 2025-08-10 22:03:42.398 CNTRLR [Node 070] Embedded device config loaded
  420. 2025-08-10 22:03:42.400 CNTRLR [Node 071] Embedded device config loaded
  421. 2025-08-10 22:03:42.402 CNTRLR [Node 073] Embedded device config loaded
  422. 2025-08-10 22:03:42.403 CNTRLR [Node 074] Embedded device config loaded
  423. 2025-08-10 22:03:42.409 CNTRLR [Node 075] Embedded device config loaded
  424. 2025-08-10 22:03:42.410 CNTRLR [Node 076] Embedded device config loaded
  425. 2025-08-10 22:03:42.413 CNTRLR [Node 078] Embedded device config loaded
  426. 2025-08-10 22:03:42.423 CNTRLR [Node 082] Embedded device config loaded
  427. 2025-08-10 22:03:42.425 CNTRLR [Node 083] Embedded device config loaded
  428. 2025-08-10 22:03:42.427 CNTRLR [Node 084] Embedded device config loaded
  429. 2025-08-10 22:03:42.429 CNTRLR [Node 089] Embedded device config loaded
  430. 2025-08-10 22:03:42.430 CNTRLR [Node 091] Embedded device config loaded
  431. 2025-08-10 22:03:42.433 CNTRLR [Node 094] Embedded device config loaded
  432. 2025-08-10 22:03:42.434 CNTRLR [Node 095] Embedded device config loaded
  433. 2025-08-10 22:03:42.435 CNTRLR [Node 099] Embedded device config loaded
  434. 2025-08-10 22:03:42.436 CNTRLR [Node 100] Embedded device config loaded
  435. 2025-08-10 22:03:42.441 CNTRLR [Node 101] Embedded device config loaded
  436. 2025-08-10 22:03:42.444 CNTRLR [Node 104] Embedded device config loaded
  437. 2025-08-10 22:03:42.445 CNTRLR [Node 105] Embedded device config loaded
  438. 2025-08-10 22:03:42.448 CNTRLR [Node 114] Embedded device config loaded
  439. 2025-08-10 22:03:42.449 CNTRLR [Node 115] Embedded device config loaded
  440. 2025-08-10 22:03:42.451 CNTRLR [Node 116] Embedded device config loaded
  441. 2025-08-10 22:03:42.453 CNTRLR [Node 120] Embedded device config loaded
  442. 2025-08-10 22:03:42.455 CNTRLR [Node 122] Embedded device config loaded
  443. 2025-08-10 22:03:42.457 CNTRLR [Node 129] Embedded device config loaded
  444. 2025-08-10 22:03:42.459 CNTRLR [Node 130] Embedded device config loaded
  445. 2025-08-10 22:03:42.460 CNTRLR [Node 135] Embedded device config loaded
  446. 2025-08-10 22:03:42.462 CNTRLR [Node 136] Embedded device config loaded
  447. 2025-08-10 22:03:42.463 CNTRLR [Node 137] Embedded device config loaded
  448. 2025-08-10 22:03:42.466 CNTRLR [Node 138] Embedded device config loaded
  449. 2025-08-10 22:03:42.469 CNTRLR [Node 141] Embedded device config loaded
  450. 2025-08-10 22:03:42.472 CNTRLR [Node 144] Embedded device config loaded
  451. 2025-08-10 22:03:42.473 CNTRLR [Node 145] Embedded device config loaded
  452. 2025-08-10 22:03:42.474 CNTRLR [Node 146] Embedded device config loaded
  453. 2025-08-10 22:03:42.476 CNTRLR [Node 147] Embedded device config loaded
  454. 2025-08-10 22:03:42.477 DRIVER Restoring the network from cache was successful!
  455. 2025-08-10 22:03:42.478 CNTRLR [Node 001] [Manufacturer Specific] manufacturerId: metadata updated
  456. 2025-08-10 22:03:42.478 CNTRLR [Node 001] [Manufacturer Specific] productType: metadata updated
  457. 2025-08-10 22:03:42.478 CNTRLR [Node 001] [Manufacturer Specific] productId: metadata updated
  458. 2025-08-10 22:03:42.478 CNTRLR [Node 001] [~] [Manufacturer Specific] manufacturerId: 134 => 134
  459. 2025-08-10 22:03:42.479 CNTRLR [Node 001] [~] [Manufacturer Specific] productType: 1 => 1
  460. 2025-08-10 22:03:42.479 CNTRLR [Node 001] [~] [Manufacturer Specific] productId: 90 => 90
  461. 2025-08-10 22:03:42.479 CNTRLR [Node 001] [Version] firmwareVersions: metadata updated
  462. 2025-08-10 22:03:42.479 CNTRLR [Node 001] [~] [Version] firmwareVersions: 1.2 => 1.2
  463. 2025-08-10 22:03:42.479 CNTRLR [Node 001] [Version] zWaveProtocolVersion: metadata updated
  464. 2025-08-10 22:03:42.480 CNTRLR [Node 001] [~] [Version] zWaveProtocolVersion: "6.7.0" => "6.7.0"
  465. 2025-08-10 22:03:42.480 CNTRLR [Node 001] [Version] sdkVersion: metadata updated
  466. 2025-08-10 22:03:42.480 CNTRLR [Node 001] [~] [Version] sdkVersion: "6.81.6" => "6.81.6"
  467. 2025-08-10 22:03:42.482 CNTRLR [Node 001] Embedded device config loaded
  468. 2025-08-10 22:03:42.482 CNTRLR Interview completed
  469. 2025-08-10 22:03:42.482 DRIVER Network key for S0 configured, enabling S0 security manager...
  470. 2025-08-10 22:03:42.482 DRIVER At least one network key for S2 configured, enabling S2 security manager...
  471. 2025-08-10 22:03:42.484 DRIVER At least one network key for Z-Wave Long Range configured, enabling security m
  472. anager...
  473. 2025-08-10 22:03:42.484 DRIVER driver ready
  474. Starting server on <all interfaces>:3000
  475. 2025-08-10 22:03:42.489 CNTRLR [Node 001] The node is alive.
  476. 2025-08-10 22:03:42.489 CNTRLR [Node 001] The node is ready to be used
  477. 2025-08-10 22:03:42.491 CNTRLR Interviewing nodes and/or determining their status: 84, 71, 62, 130, 75, 64, 7
  478. 6, 146, 12, 67, 78, 91, 65, 61, 55, 11, 49, 136, 74, 28, 114, 94, 70, 5, 95, 6
  479. 3, 48, 83, 66, 47, 141, 26, 73, 45, 24, 51, 147, 145, 100, 99, 54, 138, 82, 16
  480. , 7, 122, 144, 2, 104, 116, 60, 39, 89, 8, 9, 15, 20, 18, 19, 105, 101, 115, 1
  481. 35, 137, 4, 17, 10, 35, 129, 120, 22, 3
  482. 2025-08-10 22:03:42.492 CNTRLR » [Node 084] pinging the node...
  483. 2025-08-10 22:03:42.507 CNTRLR » [Node 071] pinging the node...
  484. 2025-08-10 22:03:42.508 CNTRLR » [Node 062] pinging the node...
  485. 2025-08-10 22:03:42.510 CNTRLR » [Node 130] pinging the node...
  486. 2025-08-10 22:03:42.511 CNTRLR » [Node 075] pinging the node...
  487. 2025-08-10 22:03:42.511 CNTRLR » [Node 064] pinging the node...
  488. 2025-08-10 22:03:42.512 CNTRLR » [Node 076] pinging the node...
  489. 2025-08-10 22:03:42.513 CNTRLR » [Node 146] pinging the node...
  490. 2025-08-10 22:03:42.514 CNTRLR » [Node 012] pinging the node...
  491. 2025-08-10 22:03:42.514 CNTRLR » [Node 067] pinging the node...
  492. 2025-08-10 22:03:42.514 CNTRLR » [Node 078] pinging the node...
  493. 2025-08-10 22:03:42.515 CNTRLR » [Node 091] pinging the node...
  494. 2025-08-10 22:03:42.515 CNTRLR » [Node 065] pinging the node...
  495. 2025-08-10 22:03:42.515 CNTRLR » [Node 061] pinging the node...
  496. 2025-08-10 22:03:42.516 CNTRLR » [Node 055] pinging the node...
  497. 2025-08-10 22:03:42.516 CNTRLR » [Node 011] pinging the node...
  498. 2025-08-10 22:03:42.516 CNTRLR » [Node 049] pinging the node...
  499. 2025-08-10 22:03:42.516 CNTRLR » [Node 136] pinging the node...
  500. 2025-08-10 22:03:42.517 CNTRLR » [Node 074] pinging the node...
  501. 2025-08-10 22:03:42.517 CNTRLR » [Node 028] pinging the node...
  502. 2025-08-10 22:03:42.520 CNTRLR » [Node 114] pinging the node...
  503. 2025-08-10 22:03:42.520 CNTRLR » [Node 094] pinging the node...
  504. 2025-08-10 22:03:42.521 CNTRLR » [Node 070] pinging the node...
  505. 2025-08-10 22:03:42.521 CNTRLR » [Node 005] pinging the node...
  506. 2025-08-10 22:03:42.521 CNTRLR » [Node 095] pinging the node...
  507. 2025-08-10 22:03:42.521 CNTRLR » [Node 063] pinging the node...
  508. 2025-08-10 22:03:42.522 CNTRLR » [Node 048] pinging the node...
  509. 2025-08-10 22:03:42.522 CNTRLR » [Node 083] pinging the node...
  510. 2025-08-10 22:03:42.522 CNTRLR » [Node 066] pinging the node...
  511. 2025-08-10 22:03:42.522 CNTRLR » [Node 047] pinging the node...
  512. 2025-08-10 22:03:42.523 CNTRLR » [Node 141] pinging the node...
  513. 2025-08-10 22:03:42.523 CNTRLR » [Node 026] pinging the node...
  514. 2025-08-10 22:03:42.523 CNTRLR » [Node 073] pinging the node...
  515. 2025-08-10 22:03:42.523 CNTRLR » [Node 045] pinging the node...
  516. 2025-08-10 22:03:42.523 CNTRLR » [Node 024] pinging the node...
  517. 2025-08-10 22:03:42.524 CNTRLR » [Node 051] pinging the node...
  518. 2025-08-10 22:03:42.524 CNTRLR » [Node 147] pinging the node...
  519. 2025-08-10 22:03:42.524 CNTRLR » [Node 145] pinging the node...
  520. 2025-08-10 22:03:42.525 CNTRLR » [Node 100] pinging the node...
  521. 2025-08-10 22:03:42.525 CNTRLR » [Node 099] pinging the node...
  522. 2025-08-10 22:03:42.525 CNTRLR » [Node 054] pinging the node...
  523. 2025-08-10 22:03:42.525 CNTRLR » [Node 138] pinging the node...
  524. 2025-08-10 22:03:42.526 CNTRLR » [Node 082] pinging the node...
  525. 2025-08-10 22:03:42.526 CNTRLR » [Node 016] pinging the node...
  526. 2025-08-10 22:03:42.527 CNTRLR [Node 007] The node is asleep.
  527. 2025-08-10 22:03:42.528 CNTRLR [Node 007] The node is ready to be used
  528. 2025-08-10 22:03:42.528 CNTRLR [Node 122] The node is asleep.
  529. 2025-08-10 22:03:42.528 CNTRLR [Node 122] The node is ready to be used
  530. 2025-08-10 22:03:42.528 CNTRLR [Node 144] The node is asleep.
  531. 2025-08-10 22:03:42.528 CNTRLR [Node 144] The node is ready to be used
  532. 2025-08-10 22:03:42.528 CNTRLR [Node 002] The node is asleep.
  533. 2025-08-10 22:03:42.528 CNTRLR [Node 002] The node is ready to be used
  534. 2025-08-10 22:03:42.528 CNTRLR [Node 104] The node is asleep.
  535. 2025-08-10 22:03:42.528 CNTRLR [Node 104] The node is ready to be used
  536. 2025-08-10 22:03:42.529 CNTRLR [Node 116] The node is asleep.
  537. 2025-08-10 22:03:42.529 CNTRLR [Node 116] The node is ready to be used
  538. 2025-08-10 22:03:42.529 CNTRLR [Node 060] The node is asleep.
  539. 2025-08-10 22:03:42.529 CNTRLR [Node 060] The node is ready to be used
  540. 2025-08-10 22:03:42.529 CNTRLR [Node 039] The node is asleep.
  541. 2025-08-10 22:03:42.529 CNTRLR [Node 039] The node is ready to be used
  542. 2025-08-10 22:03:42.529 CNTRLR [Node 089] The node is asleep.
  543. 2025-08-10 22:03:42.529 CNTRLR [Node 089] The node is ready to be used
  544. 2025-08-10 22:03:42.529 CNTRLR [Node 008] The node is asleep.
  545. 2025-08-10 22:03:42.529 CNTRLR [Node 008] The node is ready to be used
  546. 2025-08-10 22:03:42.529 CNTRLR [Node 009] The node is asleep.
  547. 2025-08-10 22:03:42.529 CNTRLR [Node 009] The node is ready to be used
  548. 2025-08-10 22:03:42.529 CNTRLR [Node 015] The node is asleep.
  549. 2025-08-10 22:03:42.529 CNTRLR [Node 015] The node is ready to be used
  550. 2025-08-10 22:03:42.530 CNTRLR [Node 020] The node is asleep.
  551. 2025-08-10 22:03:42.530 CNTRLR [Node 020] The node is ready to be used
  552. 2025-08-10 22:03:42.530 CNTRLR [Node 018] The node is asleep.
  553. 2025-08-10 22:03:42.530 CNTRLR [Node 018] The node is ready to be used
  554. 2025-08-10 22:03:42.530 CNTRLR [Node 019] The node is asleep.
  555. 2025-08-10 22:03:42.530 CNTRLR [Node 019] The node is ready to be used
  556. 2025-08-10 22:03:42.530 CNTRLR [Node 105] The node is asleep.
  557. 2025-08-10 22:03:42.530 CNTRLR [Node 105] The node is ready to be used
  558. 2025-08-10 22:03:42.530 CNTRLR [Node 101] The node is asleep.
  559. 2025-08-10 22:03:42.530 CNTRLR [Node 101] The node is ready to be used
  560. 2025-08-10 22:03:42.530 CNTRLR [Node 115] The node is asleep.
  561. 2025-08-10 22:03:42.530 CNTRLR [Node 115] The node is ready to be used
  562. 2025-08-10 22:03:42.530 CNTRLR [Node 135] The node is asleep.
  563. 2025-08-10 22:03:42.530 CNTRLR [Node 135] The node is ready to be used
  564. 2025-08-10 22:03:42.530 CNTRLR [Node 137] The node is asleep.
  565. 2025-08-10 22:03:42.530 CNTRLR [Node 137] The node is ready to be used
  566. 2025-08-10 22:03:42.530 CNTRLR [Node 004] The node is asleep.
  567. 2025-08-10 22:03:42.531 CNTRLR [Node 004] The node is ready to be used
  568. 2025-08-10 22:03:42.531 CNTRLR [Node 017] The node is asleep.
  569. 2025-08-10 22:03:42.531 CNTRLR [Node 017] The node is ready to be used
  570. 2025-08-10 22:03:42.531 CNTRLR [Node 010] The node is asleep.
  571. 2025-08-10 22:03:42.531 CNTRLR [Node 010] The node is ready to be used
  572. 2025-08-10 22:03:42.531 CNTRLR [Node 035] The node is asleep.
  573. 2025-08-10 22:03:42.531 CNTRLR [Node 035] The node is ready to be used
  574. 2025-08-10 22:03:42.531 CNTRLR [Node 129] The node is asleep.
  575. 2025-08-10 22:03:42.531 CNTRLR [Node 129] The node is ready to be used
  576. 2025-08-10 22:03:42.531 CNTRLR [Node 120] The node is asleep.
  577. 2025-08-10 22:03:42.531 CNTRLR [Node 120] The node is ready to be used
  578. 2025-08-10 22:03:42.531 CNTRLR [Node 022] The node is asleep.
  579. 2025-08-10 22:03:42.531 CNTRLR [Node 022] The node is ready to be used
  580. 2025-08-10 22:03:42.532 CNTRLR [Node 003] The node is asleep.
  581. 2025-08-10 22:03:42.532 CNTRLR [Node 003] The node is ready to be used
  582. 2025-08-10 22:03:42.532 DRIVER one or more queues busy
  583. 2025-08-10 22:03:42.533 DRIVER » [Node 084] [REQ] [SendData]
  584. │ transmit options: 0x01
  585. │ callback id: 13
  586. └─[NoOperationCC]
  587. 2025-08-10 22:03:42.533 SERIAL » 0x01080013540100010dbd (10 bytes)
  588. ZwaveJS server listening on <all interfaces>:3000
  589. 2025-08-10 22:03:42.536 SERIAL « [ACK] (0x06)
  590. 2025-08-10 22:03:42.544 SERIAL « 0x0104011301e8 (6 bytes)
  591. 2025-08-10 22:03:42.544 SERIAL » [ACK] (0x06)
  592. 2025-08-10 22:03:42.544 DRIVER « [RES] [SendData]
  593. was sent: true
  594. 2025-08-10 22:03:42.577 SERIAL « 0x011800130d00000300d07f7f7f7f01010300000000020100002a (26 bytes)
  595. 2025-08-10 22:03:42.578 SERIAL » [ACK] (0x06)
  596. 2025-08-10 22:03:42.578 DRIVER « [REQ] [SendData]
  597. callback id: 13
  598. transmit status: OK, took 30 ms
  599. routing attempts: 1
  600. protocol & route speed: Z-Wave, 40 kbit/s
  601. routing scheme: LWR
  602. ACK RSSI: -48 dBm
  603. ACK channel no.: 1
  604. TX channel no.: 1
  605. 2025-08-10 22:03:42.579 CNTRLR [Node 084] The node is alive.
  606. 2025-08-10 22:03:42.579 CNTRLR [Node 084] The node is ready to be used
  607. 2025-08-10 22:03:42.579 CNTRLR « [Node 084] ping successful
  608. 2025-08-10 22:03:42.580 DRIVER » [Node 071] [REQ] [SendData]
  609. │ transmit options: 0x01
  610. │ callback id: 14
  611. └─[NoOperationCC]
  612. 2025-08-10 22:03:42.580 SERIAL » 0x01080013470100010ead (10 bytes)
  613. 2025-08-10 22:03:42.581 SERIAL « [ACK] (0x06)
  614. 2025-08-10 22:03:42.588 SERIAL « 0x0104011301e8 (6 bytes)
  615. 2025-08-10 22:03:42.588 SERIAL » [ACK] (0x06)
  616. 2025-08-10 22:03:42.588 DRIVER « [RES] [SendData]
  617. was sent: true
  618. 2025-08-10 22:03:42.614 SERIAL « 0x011800130e000002007e7f7f7f7f000003000000000301000087 (26 bytes)
  619. 2025-08-10 22:03:42.614 SERIAL » [ACK] (0x06)
  620. 2025-08-10 22:03:42.614 DRIVER « [REQ] [SendData]
  621. callback id: 14
  622. transmit status: OK, took 20 ms
  623. routing attempts: 1
  624. protocol & route speed: Z-Wave, 100 kbit/s
  625. routing scheme: LWR
  626. ACK RSSI: Receiver saturated
  627. ACK channel no.: 0
  628. TX channel no.: 0
  629. 2025-08-10 22:03:42.615 CNTRLR [Node 071] The node is alive.
  630. 2025-08-10 22:03:42.615 CNTRLR [Node 071] The node is ready to be used
  631. 2025-08-10 22:03:42.615 CNTRLR « [Node 071] ping successful
  632. 2025-08-10 22:03:42.615 DRIVER » [Node 062] [REQ] [SendData]
  633. │ transmit options: 0x01
  634. │ callback id: 15
  635. └─[NoOperationCC]
  636. 2025-08-10 22:03:42.615 SERIAL » 0x010800133e0100010fd5 (10 bytes)
  637. 2025-08-10 22:03:42.617 SERIAL « [ACK] (0x06)
  638. 2025-08-10 22:03:42.624 SERIAL « 0x0104011301e8 (6 bytes)
  639. 2025-08-10 22:03:42.625 SERIAL » [ACK] (0x06)
  640. 2025-08-10 22:03:42.626 DRIVER « [RES] [SendData]
  641. was sent: true
  642. 2025-08-10 22:03:42.649 SERIAL « 0x011800130f00000200b37f7f7f7f01010300000000020100004a (26 bytes)
  643. 2025-08-10 22:03:42.649 SERIAL » [ACK] (0x06)
  644. 2025-08-10 22:03:42.649 DRIVER « [REQ] [SendData]
  645. callback id: 15
  646. transmit status: OK, took 20 ms
  647. routing attempts: 1
  648. protocol & route speed: Z-Wave, 40 kbit/s
  649. routing scheme: LWR
  650. ACK RSSI: -77 dBm
  651. ACK channel no.: 1
  652. TX channel no.: 1
  653. 2025-08-10 22:03:42.650 CNTRLR [Node 062] The node is alive.
  654. 2025-08-10 22:03:42.650 CNTRLR [Node 062] The node is ready to be used
  655. 2025-08-10 22:03:42.650 CNTRLR « [Node 062] ping successful
  656. 2025-08-10 22:03:42.650 DRIVER » [Node 130] [REQ] [SendData]
  657. │ transmit options: 0x01
  658. │ callback id: 16
  659. └─[NoOperationCC]
  660. 2025-08-10 22:03:42.650 SERIAL » 0x01080013820100011076 (10 bytes)
  661. 2025-08-10 22:03:42.652 SERIAL « [ACK] (0x06)
  662. 2025-08-10 22:03:42.661 SERIAL « 0x0104011301e8 (6 bytes)
  663. 2025-08-10 22:03:42.661 SERIAL » [ACK] (0x06)
  664. 2025-08-10 22:03:42.661 DRIVER « [RES] [SendData]
  665. was sent: true
  666. 2025-08-10 22:03:42.876 SERIAL « 0x011800131000001502c47f7f7f7f0101034a0b00000101000075 (26 bytes)
  667. 2025-08-10 22:03:42.877 SERIAL » [ACK] (0x06)
  668. 2025-08-10 22:03:42.877 DRIVER « [REQ] [SendData]
  669. callback id: 16
  670. transmit status: OK, took 210 ms
  671. repeater node IDs: 74, 11
  672. routing attempts: 1
  673. protocol & route speed: Z-Wave, 9.6 kbit/s
  674. routing scheme: LWR
  675. ACK RSSI: -60 dBm
  676. ACK RSSI on repeaters: N/A, N/A
  677. ACK channel no.: 1
  678. TX channel no.: 1
  679. 2025-08-10 22:03:42.878 CNTRLR [Node 130] The node is alive.
  680. 2025-08-10 22:03:42.878 CNTRLR [Node 130] The node is ready to be used
  681. 2025-08-10 22:03:42.878 CNTRLR « [Node 130] ping successful
  682. 2025-08-10 22:03:42.878 DRIVER » [Node 075] [REQ] [SendData]
  683. │ transmit options: 0x01
  684. │ callback id: 17
  685. └─[NoOperationCC]
  686. 2025-08-10 22:03:42.878 SERIAL » 0x010800134b01000111be (10 bytes)
  687. 2025-08-10 22:03:42.880 SERIAL « [ACK] (0x06)
  688. 2025-08-10 22:03:42.886 SERIAL « 0x0104011301e8 (6 bytes)
  689. 2025-08-10 22:03:42.886 SERIAL » [ACK] (0x06)
  690. 2025-08-10 22:03:42.886 DRIVER « [RES] [SendData]
  691. was sent: true
  692. 2025-08-10 22:03:42.925 SERIAL « 0x011800131100000400c77f7f7f7f010103000000000201000026 (26 bytes)
  693. 2025-08-10 22:03:42.925 SERIAL » [ACK] (0x06)
  694. 2025-08-10 22:03:42.926 DRIVER « [REQ] [SendData]
  695. callback id: 17
  696. transmit status: OK, took 40 ms
  697. routing attempts: 1
  698. protocol & route speed: Z-Wave, 40 kbit/s
  699. routing scheme: LWR
  700. ACK RSSI: -57 dBm
  701. ACK channel no.: 1
  702. TX channel no.: 1
  703. 2025-08-10 22:03:42.926 CNTRLR [Node 075] The node is alive.
  704. 2025-08-10 22:03:42.926 CNTRLR [Node 075] The node is ready to be used
  705. 2025-08-10 22:03:42.926 CNTRLR « [Node 075] ping successful
  706. 2025-08-10 22:03:42.926 DRIVER » [Node 064] [REQ] [SendData]
  707. │ transmit options: 0x01
  708. │ callback id: 18
  709. └─[NoOperationCC]
  710. 2025-08-10 22:03:42.926 SERIAL » 0x010800134001000112b6 (10 bytes)
  711. 2025-08-10 22:03:42.929 SERIAL « [ACK] (0x06)
  712. 2025-08-10 22:03:42.936 SERIAL « 0x0104011301e8 (6 bytes)
  713. 2025-08-10 22:03:42.936 SERIAL » [ACK] (0x06)
  714. 2025-08-10 22:03:42.936 DRIVER « [RES] [SendData]
  715. was sent: true
  716. 2025-08-10 22:03:42.961 SERIAL « 0x011800131200000300b17f7f7f7f010103000000000201000054 (26 bytes)
  717. 2025-08-10 22:03:42.961 SERIAL » [ACK] (0x06)
  718. 2025-08-10 22:03:42.961 DRIVER « [REQ] [SendData]
  719. callback id: 18
  720. transmit status: OK, took 30 ms
  721. routing attempts: 1
  722. protocol & route speed: Z-Wave, 40 kbit/s
  723. routing scheme: LWR
  724. ACK RSSI: -79 dBm
  725. ACK channel no.: 1
  726. TX channel no.: 1
  727. 2025-08-10 22:03:42.961 CNTRLR [Node 064] The node is alive.
  728. 2025-08-10 22:03:42.961 CNTRLR [Node 064] The node is ready to be used
  729. 2025-08-10 22:03:42.961 CNTRLR « [Node 064] ping successful
  730. 2025-08-10 22:03:42.961 DRIVER » [Node 076] [REQ] [SendData]
  731. │ transmit options: 0x01
  732. │ callback id: 19
  733. └─[NoOperationCC]
  734. 2025-08-10 22:03:42.962 SERIAL » 0x010800134c01000113bb (10 bytes)
  735. 2025-08-10 22:03:42.964 SERIAL « [ACK] (0x06)
  736. 2025-08-10 22:03:42.971 SERIAL « 0x0104011301e8 (6 bytes)
  737. 2025-08-10 22:03:42.972 SERIAL » [ACK] (0x06)
  738. 2025-08-10 22:03:42.972 DRIVER « [RES] [SendData]
  739. was sent: true
  740. 2025-08-10 22:03:43.026 SERIAL « 0x011800131300000501d87f7f7f7f010103490000000201000072 (26 bytes)
  741. 2025-08-10 22:03:43.026 SERIAL » [ACK] (0x06)
  742. 2025-08-10 22:03:43.026 DRIVER « [REQ] [SendData]
  743. callback id: 19
  744. transmit status: OK, took 50 ms
  745. repeater node IDs: 73
  746. routing attempts: 1
  747. protocol & route speed: Z-Wave, 40 kbit/s
  748. routing scheme: LWR
  749. ACK RSSI: -40 dBm
  750. ACK RSSI on repeaters: N/A
  751. ACK channel no.: 1
  752. TX channel no.: 1
  753. 2025-08-10 22:03:43.026 CNTRLR [Node 076] The node is alive.
  754. 2025-08-10 22:03:43.026 CNTRLR [Node 076] The node is ready to be used
  755. 2025-08-10 22:03:43.027 CNTRLR « [Node 076] ping successful
  756. 2025-08-10 22:03:43.027 DRIVER » [Node 146] [REQ] [SendData]
  757. │ transmit options: 0x01
  758. │ callback id: 20
  759. └─[NoOperationCC]
  760. 2025-08-10 22:03:43.027 SERIAL » 0x01080013920100011462 (10 bytes)
  761. 2025-08-10 22:03:43.030 SERIAL « [ACK] (0x06)
  762. 2025-08-10 22:03:43.038 SERIAL « 0x0104011301e8 (6 bytes)
  763. 2025-08-10 22:03:43.038 SERIAL » [ACK] (0x06)
  764. 2025-08-10 22:03:43.039 DRIVER « [RES] [SendData]
  765. was sent: true
  766. 2025-08-10 22:03:43.090 SERIAL « 0x011800131400000401c97f7f7f7f0000032d0000000301000000 (26 bytes)
  767. 2025-08-10 22:03:43.090 SERIAL » [ACK] (0x06)
  768. 2025-08-10 22:03:43.090 DRIVER « [REQ] [SendData]
  769. callback id: 20
  770. transmit status: OK, took 40 ms
  771. repeater node IDs: 45
  772. routing attempts: 1
  773. protocol & route speed: Z-Wave, 100 kbit/s
  774. routing scheme: LWR
  775. ACK RSSI: -55 dBm
  776. ACK RSSI on repeaters: N/A
  777. ACK channel no.: 0
  778. TX channel no.: 0
  779. 2025-08-10 22:03:43.090 CNTRLR [Node 146] The node is alive.
  780. 2025-08-10 22:03:43.090 CNTRLR [Node 146] The node is ready to be used
  781. 2025-08-10 22:03:43.091 CNTRLR « [Node 146] ping successful
  782. 2025-08-10 22:03:43.091 DRIVER » [Node 012] [REQ] [SendData]
  783. │ transmit options: 0x01
  784. │ callback id: 21
  785. └─[NoOperationCC]
  786. 2025-08-10 22:03:43.091 SERIAL » 0x010800130c01000115fd (10 bytes)
  787. 2025-08-10 22:03:43.093 SERIAL « [ACK] (0x06)
  788. 2025-08-10 22:03:43.101 SERIAL « 0x0104011301e8 (6 bytes)
  789. 2025-08-10 22:03:43.101 SERIAL » [ACK] (0x06)
  790. 2025-08-10 22:03:43.101 DRIVER « [RES] [SendData]
  791. was sent: true
  792. 2025-08-10 22:03:43.320 SERIAL « 0x011800131500001502b37f7f7f7f0101034e050000010100000d (26 bytes)
  793. 2025-08-10 22:03:43.321 SERIAL » [ACK] (0x06)
  794. 2025-08-10 22:03:43.321 DRIVER « [REQ] [SendData]
  795. callback id: 21
  796. transmit status: OK, took 210 ms
  797. repeater node IDs: 78, 5
  798. routing attempts: 1
  799. protocol & route speed: Z-Wave, 9.6 kbit/s
  800. routing scheme: LWR
  801. ACK RSSI: -77 dBm
  802. ACK RSSI on repeaters: N/A, N/A
  803. ACK channel no.: 1
  804. TX channel no.: 1
  805. 2025-08-10 22:03:43.322 CNTRLR [Node 012] The node is alive.
  806. 2025-08-10 22:03:43.322 CNTRLR [Node 012] The node is ready to be used
  807. 2025-08-10 22:03:43.322 CNTRLR « [Node 012] ping successful
  808. 2025-08-10 22:03:43.322 DRIVER » [Node 067] [REQ] [SendData]
  809. │ transmit options: 0x01
  810. │ callback id: 22
  811. └─[NoOperationCC]
  812. 2025-08-10 22:03:43.322 SERIAL » 0x010800134301000116b1 (10 bytes)
  813. 2025-08-10 22:03:43.325 SERIAL « [ACK] (0x06)
  814. 2025-08-10 22:03:43.334 SERIAL « 0x0104011301e8 (6 bytes)
  815. 2025-08-10 22:03:43.334 SERIAL » [ACK] (0x06)
  816. 2025-08-10 22:03:43.335 DRIVER « [RES] [SendData]
  817. was sent: true
  818. 2025-08-10 22:03:43.358 SERIAL « 0x011800131600000300b87f7f7f7f010103000000000201000059 (26 bytes)
  819. 2025-08-10 22:03:43.358 SERIAL » [ACK] (0x06)
  820. 2025-08-10 22:03:43.358 DRIVER « [REQ] [SendData]
  821. callback id: 22
  822. transmit status: OK, took 30 ms
  823. routing attempts: 1
  824. protocol & route speed: Z-Wave, 40 kbit/s
  825. routing scheme: LWR
  826. ACK RSSI: -72 dBm
  827. ACK channel no.: 1
  828. TX channel no.: 1
  829. 2025-08-10 22:03:43.359 CNTRLR [Node 067] The node is alive.
  830. 2025-08-10 22:03:43.359 CNTRLR [Node 067] The node is ready to be used
  831. 2025-08-10 22:03:43.359 CNTRLR « [Node 067] ping successful
  832. 2025-08-10 22:03:43.359 DRIVER » [Node 078] [REQ] [SendData]
  833. │ transmit options: 0x01
  834. │ callback id: 23
  835. └─[NoOperationCC]
  836. 2025-08-10 22:03:43.359 SERIAL » 0x010800134e01000117bd (10 bytes)
  837. 2025-08-10 22:03:43.361 SERIAL « [ACK] (0x06)
  838. 2025-08-10 22:03:43.367 SERIAL « 0x0104011301e8 (6 bytes)
  839. 2025-08-10 22:03:43.367 SERIAL » [ACK] (0x06)
  840. 2025-08-10 22:03:43.367 DRIVER « [RES] [SendData]
  841. was sent: true
  842. 2025-08-10 22:03:43.582 SERIAL « 0x0118001317000015027e7f7f7f7f010103474a00000101000084 (26 bytes)
  843. 2025-08-10 22:03:43.583 SERIAL » [ACK] (0x06)
  844. 2025-08-10 22:03:43.583 DRIVER « [REQ] [SendData]
  845. callback id: 23
  846. transmit status: OK, took 210 ms
  847. repeater node IDs: 71, 74
  848. routing attempts: 1
  849. protocol & route speed: Z-Wave, 9.6 kbit/s
  850. routing scheme: LWR
  851. ACK RSSI: Receiver saturated
  852. ACK RSSI on repeaters: N/A, N/A
  853. ACK channel no.: 1
  854. TX channel no.: 1
  855. 2025-08-10 22:03:43.583 CNTRLR [Node 078] The node is alive.
  856. 2025-08-10 22:03:43.583 CNTRLR [Node 078] The node is ready to be used
  857. 2025-08-10 22:03:43.583 CNTRLR « [Node 078] ping successful
  858. 2025-08-10 22:03:43.584 DRIVER » [Node 091] [REQ] [SendData]
  859. │ transmit options: 0x01
  860. │ callback id: 24
  861. └─[NoOperationCC]
  862. 2025-08-10 22:03:43.584 SERIAL » 0x010800135b01000118a7 (10 bytes)
  863. 2025-08-10 22:03:43.586 SERIAL « [ACK] (0x06)
  864. 2025-08-10 22:03:43.592 SERIAL « 0x0104011301e8 (6 bytes)
  865. 2025-08-10 22:03:43.592 SERIAL » [ACK] (0x06)
  866. 2025-08-10 22:03:43.592 DRIVER « [RES] [SendData]
  867. was sent: true
  868. 2025-08-10 22:03:43.631 SERIAL « 0x011800131800000400c17f7f7f7f010103000000000201000029 (26 bytes)
  869. 2025-08-10 22:03:43.632 SERIAL » [ACK] (0x06)
  870. 2025-08-10 22:03:43.632 DRIVER « [REQ] [SendData]
  871. callback id: 24
  872. transmit status: OK, took 40 ms
  873. routing attempts: 1
  874. protocol & route speed: Z-Wave, 40 kbit/s
  875. routing scheme: LWR
  876. ACK RSSI: -63 dBm
  877. ACK channel no.: 1
  878. TX channel no.: 1
  879. 2025-08-10 22:03:43.632 CNTRLR [Node 091] The node is alive.
  880. 2025-08-10 22:03:43.632 CNTRLR [Node 091] The node is ready to be used
  881. 2025-08-10 22:03:43.632 CNTRLR « [Node 091] ping successful
  882. 2025-08-10 22:03:43.632 DRIVER » [Node 065] [REQ] [SendData]
  883. │ transmit options: 0x01
  884. │ callback id: 25
  885. └─[NoOperationCC]
  886. 2025-08-10 22:03:43.632 SERIAL » 0x010800134101000119bc (10 bytes)
  887. 2025-08-10 22:03:43.635 SERIAL « [ACK] (0x06)
  888. 2025-08-10 22:03:43.642 SERIAL « 0x0104011301e8 (6 bytes)
  889. 2025-08-10 22:03:43.643 SERIAL » [ACK] (0x06)
  890. 2025-08-10 22:03:43.643 DRIVER « [RES] [SendData]
  891. was sent: true
  892. 2025-08-10 22:03:43.664 SERIAL « 0x011800131900000200b97f7f7f7f010103000000000201000056 (26 bytes)
  893. 2025-08-10 22:03:43.664 SERIAL » [ACK] (0x06)
  894. 2025-08-10 22:03:43.664 DRIVER « [REQ] [SendData]
  895. callback id: 25
  896. transmit status: OK, took 20 ms
  897. routing attempts: 1
  898. protocol & route speed: Z-Wave, 40 kbit/s
  899. routing scheme: LWR
  900. ACK RSSI: -71 dBm
  901. ACK channel no.: 1
  902. TX channel no.: 1
  903. 2025-08-10 22:03:43.665 CNTRLR [Node 065] The node is alive.
  904. 2025-08-10 22:03:43.665 CNTRLR [Node 065] The node is ready to be used
  905. 2025-08-10 22:03:43.665 CNTRLR « [Node 065] ping successful
  906. 2025-08-10 22:03:43.665 DRIVER » [Node 061] [REQ] [SendData]
  907. │ transmit options: 0x01
  908. │ callback id: 26
  909. └─[NoOperationCC]
  910. 2025-08-10 22:03:43.665 SERIAL » 0x010800133d0100011ac3 (10 bytes)
  911. 2025-08-10 22:03:43.668 SERIAL « [ACK] (0x06)
  912. 2025-08-10 22:03:43.674 SERIAL « 0x0104011301e8 (6 bytes)
  913. 2025-08-10 22:03:43.674 SERIAL » [ACK] (0x06)
  914. 2025-08-10 22:03:43.674 DRIVER « [RES] [SendData]
  915. was sent: true
  916. 2025-08-10 22:03:43.697 SERIAL « 0x011800131a00000200b37f7f7f7f01010300000000020100005f (26 bytes)
  917. 2025-08-10 22:03:43.697 SERIAL » [ACK] (0x06)
  918. 2025-08-10 22:03:43.697 DRIVER « [REQ] [SendData]
  919. callback id: 26
  920. transmit status: OK, took 20 ms
  921. routing attempts: 1
  922. protocol & route speed: Z-Wave, 40 kbit/s
  923. routing scheme: LWR
  924. ACK RSSI: -77 dBm
  925. ACK channel no.: 1
  926. TX channel no.: 1
  927. 2025-08-10 22:03:43.697 CNTRLR [Node 061] The node is alive.
  928. 2025-08-10 22:03:43.697 CNTRLR [Node 061] The node is ready to be used
  929. 2025-08-10 22:03:43.697 CNTRLR « [Node 061] ping successful
  930. 2025-08-10 22:03:43.697 DRIVER » [Node 055] [REQ] [SendData]
  931. │ transmit options: 0x01
  932. │ callback id: 27
  933. └─[NoOperationCC]
  934. 2025-08-10 22:03:43.697 SERIAL » 0x01080013370100011bc8 (10 bytes)
  935. 2025-08-10 22:03:43.699 SERIAL « [ACK] (0x06)
  936. 2025-08-10 22:03:43.706 SERIAL « 0x0104011301e8 (6 bytes)
  937. 2025-08-10 22:03:43.706 SERIAL » [ACK] (0x06)
  938. 2025-08-10 22:03:43.706 DRIVER « [RES] [SendData]
  939. was sent: true
  940. 2025-08-10 22:03:43.756 SERIAL « 0x011800131b00000501cf7f7f7f7f0101038800000002010000ac (26 bytes)
  941. 2025-08-10 22:03:43.757 SERIAL » [ACK] (0x06)
  942. 2025-08-10 22:03:43.757 DRIVER « [REQ] [SendData]
  943. callback id: 27
  944. transmit status: OK, took 50 ms
  945. repeater node IDs: 136
  946. routing attempts: 1
  947. protocol & route speed: Z-Wave, 40 kbit/s
  948. routing scheme: LWR
  949. ACK RSSI: -49 dBm
  950. ACK RSSI on repeaters: N/A
  951. ACK channel no.: 1
  952. TX channel no.: 1
  953. 2025-08-10 22:03:43.757 CNTRLR [Node 055] The node is alive.
  954. 2025-08-10 22:03:43.757 CNTRLR [Node 055] The node is ready to be used
  955. 2025-08-10 22:03:43.757 CNTRLR « [Node 055] ping successful
  956. 2025-08-10 22:03:43.757 DRIVER » [Node 011] [REQ] [SendData]
  957. │ transmit options: 0x01
  958. │ callback id: 28
  959. └─[NoOperationCC]
  960. 2025-08-10 22:03:43.757 SERIAL » 0x010800130b0100011cf3 (10 bytes)
  961. 2025-08-10 22:03:43.760 SERIAL « [ACK] (0x06)
  962. 2025-08-10 22:03:43.766 SERIAL « 0x0104011301e8 (6 bytes)
  963. 2025-08-10 22:03:43.766 SERIAL » [ACK] (0x06)
  964. 2025-08-10 22:03:43.767 DRIVER « [RES] [SendData]
  965. was sent: true
  966. 2025-08-10 22:03:43.931 SERIAL « 0x011800131c00001101c47f7f7f7f0101034a0000000101000075 (26 bytes)
  967. 2025-08-10 22:03:43.932 SERIAL » [ACK] (0x06)
  968. 2025-08-10 22:03:43.932 DRIVER « [REQ] [SendData]
  969. callback id: 28
  970. transmit status: OK, took 170 ms
  971. repeater node IDs: 74
  972. routing attempts: 1
  973. protocol & route speed: Z-Wave, 9.6 kbit/s
  974. routing scheme: LWR
  975. ACK RSSI: -60 dBm
  976. ACK RSSI on repeaters: N/A
  977. ACK channel no.: 1
  978. TX channel no.: 1
  979. 2025-08-10 22:03:43.932 CNTRLR [Node 011] The node is alive.
  980. 2025-08-10 22:03:43.932 CNTRLR [Node 011] The node is ready to be used
  981. 2025-08-10 22:03:43.932 CNTRLR « [Node 011] ping successful
  982. 2025-08-10 22:03:43.932 DRIVER » [Node 049] [REQ] [SendData]
  983. │ transmit options: 0x01
  984. │ callback id: 29
  985. └─[NoOperationCC]
  986. 2025-08-10 22:03:43.932 SERIAL » 0x01080013310100011dc8 (10 bytes)
  987. 2025-08-10 22:03:43.935 SERIAL « [ACK] (0x06)
  988. 2025-08-10 22:03:43.940 SERIAL « 0x0104011301e8 (6 bytes)
  989. 2025-08-10 22:03:43.940 SERIAL » [ACK] (0x06)
  990. 2025-08-10 22:03:43.940 DRIVER « [RES] [SendData]
  991. was sent: true
  992. 2025-08-10 22:03:44.096 SERIAL « 0x011800131d00000f01c97f7f7f7f0101032d0000000101000000 (26 bytes)
  993. 2025-08-10 22:03:44.097 SERIAL » [ACK] (0x06)
  994. 2025-08-10 22:03:44.097 DRIVER « [REQ] [SendData]
  995. callback id: 29
  996. transmit status: OK, took 150 ms
  997. repeater node IDs: 45
  998. routing attempts: 1
  999. protocol & route speed: Z-Wave, 9.6 kbit/s
  1000. routing scheme: LWR
  1001. ACK RSSI: -55 dBm
  1002. ACK RSSI on repeaters: N/A
  1003. ACK channel no.: 1
  1004. TX channel no.: 1
  1005. 2025-08-10 22:03:44.097 CNTRLR [Node 049] The node is alive.
  1006. 2025-08-10 22:03:44.097 CNTRLR [Node 049] The node is ready to be used
  1007. 2025-08-10 22:03:44.097 CNTRLR « [Node 049] ping successful
  1008. 2025-08-10 22:03:44.097 DRIVER » [Node 136] [REQ] [SendData]
  1009. │ transmit options: 0x01
  1010. │ callback id: 30
  1011. └─[NoOperationCC]
  1012. 2025-08-10 22:03:44.097 SERIAL » 0x01080013880100011e72 (10 bytes)
  1013. 2025-08-10 22:03:44.100 SERIAL « [ACK] (0x06)
  1014. 2025-08-10 22:03:44.107 SERIAL « 0x0104011301e8 (6 bytes)
  1015. 2025-08-10 22:03:44.107 SERIAL » [ACK] (0x06)
  1016. 2025-08-10 22:03:44.107 DRIVER « [RES] [SendData]
  1017. was sent: true
  1018. 2025-08-10 22:03:44.144 SERIAL « 0x011800131e00000400cf7f7f7f7f000003000000000301000020 (26 bytes)
  1019. 2025-08-10 22:03:44.144 SERIAL » [ACK] (0x06)
  1020. 2025-08-10 22:03:44.144 DRIVER « [REQ] [SendData]
  1021. callback id: 30
  1022. transmit status: OK, took 40 ms
  1023. routing attempts: 1
  1024. protocol & route speed: Z-Wave, 100 kbit/s
  1025. routing scheme: LWR
  1026. ACK RSSI: -49 dBm
  1027. ACK channel no.: 0
  1028. TX channel no.: 0
  1029. 2025-08-10 22:03:44.144 CNTRLR [Node 136] The node is alive.
  1030. 2025-08-10 22:03:44.144 CNTRLR [Node 136] The node is ready to be used
  1031. 2025-08-10 22:03:44.144 CNTRLR « [Node 136] ping successful
  1032. 2025-08-10 22:03:44.144 DRIVER » [Node 074] [REQ] [SendData]
  1033. │ transmit options: 0x01
  1034. │ callback id: 31
  1035. └─[NoOperationCC]
  1036. 2025-08-10 22:03:44.144 SERIAL » 0x010800134a0100011fb1 (10 bytes)
  1037. 2025-08-10 22:03:44.146 SERIAL « [ACK] (0x06)
  1038. 2025-08-10 22:03:44.153 SERIAL « 0x0104011301e8 (6 bytes)
  1039. 2025-08-10 22:03:44.153 SERIAL » [ACK] (0x06)
  1040. 2025-08-10 22:03:44.153 DRIVER « [RES] [SendData]
  1041. was sent: true
  1042. 2025-08-10 22:03:44.273 SERIAL « 0x011800131f00000c04c37f7f7f7f010103180b3649020100004c (26 bytes)
  1043. 2025-08-10 22:03:44.273 SERIAL » [ACK] (0x06)
  1044. 2025-08-10 22:03:44.273 DRIVER « [REQ] [SendData]
  1045. callback id: 31
  1046. transmit status: OK, took 120 ms
  1047. repeater node IDs: 24, 11, 54, 73
  1048. routing attempts: 1
  1049. protocol & route speed: Z-Wave, 40 kbit/s
  1050. routing scheme: LWR
  1051. ACK RSSI: -61 dBm
  1052. ACK RSSI on repeaters: N/A, N/A, N/A, N/A
  1053. ACK channel no.: 1
  1054. TX channel no.: 1
  1055. 2025-08-10 22:03:44.273 CNTRLR [Node 074] The node is alive.
  1056. 2025-08-10 22:03:44.274 CNTRLR [Node 074] The node is ready to be used
  1057. 2025-08-10 22:03:44.274 CNTRLR « [Node 074] ping successful
  1058. 2025-08-10 22:03:44.275 DRIVER » [Node 028] [REQ] [SendData]
  1059. │ transmit options: 0x01
  1060. │ callback id: 32
  1061. └─[NoOperationCC]
  1062. 2025-08-10 22:03:44.275 SERIAL » 0x010800131c01000120d8 (10 bytes)
  1063. 2025-08-10 22:03:44.277 SERIAL « [ACK] (0x06)
  1064. 2025-08-10 22:03:44.286 SERIAL « 0x0104011301e8 (6 bytes)
  1065. 2025-08-10 22:03:44.286 SERIAL » [ACK] (0x06)
  1066. 2025-08-10 22:03:44.287 DRIVER « [RES] [SendData]
  1067. was sent: true
  1068. 2025-08-10 22:03:44.353 SERIAL « 0x011800132000000702db7f7f7f7f010103498d000002010000ce (26 bytes)
  1069. 2025-08-10 22:03:44.353 SERIAL » [ACK] (0x06)
  1070. 2025-08-10 22:03:44.353 DRIVER « [REQ] [SendData]
  1071. callback id: 32
  1072. transmit status: OK, took 70 ms
  1073. repeater node IDs: 73, 141
  1074. routing attempts: 1
  1075. protocol & route speed: Z-Wave, 40 kbit/s
  1076. routing scheme: LWR
  1077. ACK RSSI: -37 dBm
  1078. ACK RSSI on repeaters: N/A, N/A
  1079. ACK channel no.: 1
  1080. TX channel no.: 1
  1081. 2025-08-10 22:03:44.353 CNTRLR [Node 028] The node is alive.
  1082. 2025-08-10 22:03:44.354 CNTRLR [Node 028] The node is ready to be used
  1083. 2025-08-10 22:03:44.354 CNTRLR « [Node 028] ping successful
  1084. 2025-08-10 22:03:44.354 DRIVER » [Node 114] [REQ] [SendData]
  1085. │ transmit options: 0x01
  1086. │ callback id: 33
  1087. └─[NoOperationCC]
  1088. 2025-08-10 22:03:44.354 SERIAL » 0x010800137201000121b7 (10 bytes)
  1089. 2025-08-10 22:03:44.356 SERIAL « [ACK] (0x06)
  1090. 2025-08-10 22:03:44.363 SERIAL « 0x0104011301e8 (6 bytes)
  1091. 2025-08-10 22:03:44.363 SERIAL » [ACK] (0x06)
  1092. 2025-08-10 22:03:44.363 DRIVER « [RES] [SendData]
  1093. was sent: true
  1094. 2025-08-10 22:03:44.440 SERIAL « 0x011800132100000800b37f7f7f7f01010300000000020200006d (26 bytes)
  1095. 2025-08-10 22:03:44.440 SERIAL » [ACK] (0x06)
  1096. 2025-08-10 22:03:44.440 DRIVER « [REQ] [SendData]
  1097. callback id: 33
  1098. transmit status: OK, took 80 ms
  1099. routing attempts: 2
  1100. protocol & route speed: Z-Wave, 40 kbit/s
  1101. routing scheme: LWR
  1102. ACK RSSI: -77 dBm
  1103. ACK channel no.: 1
  1104. TX channel no.: 1
  1105. 2025-08-10 22:03:44.440 CNTRLR [Node 114] The node is alive.
  1106. 2025-08-10 22:03:44.441 CNTRLR [Node 114] The node is ready to be used
  1107. 2025-08-10 22:03:44.441 CNTRLR « [Node 114] ping successful
  1108. 2025-08-10 22:03:44.441 DRIVER » [Node 094] [REQ] [SendData]
  1109. │ transmit options: 0x01
  1110. │ callback id: 34
  1111. └─[NoOperationCC]
  1112. 2025-08-10 22:03:44.441 SERIAL » 0x010800135e0100012298 (10 bytes)
  1113. 2025-08-10 22:03:44.443 SERIAL « [ACK] (0x06)
  1114. 2025-08-10 22:03:44.448 SERIAL « 0x0104011301e8 (6 bytes)
  1115. 2025-08-10 22:03:44.449 SERIAL » [ACK] (0x06)
  1116. 2025-08-10 22:03:44.449 DRIVER « [RES] [SendData]
  1117. was sent: true
  1118. 2025-08-10 22:03:44.473 SERIAL « 0x011800132200000200bf7f7f7f7f01010300000000020100006b (26 bytes)
  1119. 2025-08-10 22:03:44.474 SERIAL » [ACK] (0x06)
  1120. 2025-08-10 22:03:44.474 DRIVER « [REQ] [SendData]
  1121. callback id: 34
  1122. transmit status: OK, took 20 ms
  1123. routing attempts: 1
  1124. protocol & route speed: Z-Wave, 40 kbit/s
  1125. routing scheme: LWR
  1126. ACK RSSI: -65 dBm
  1127. ACK channel no.: 1
  1128. TX channel no.: 1
  1129. 2025-08-10 22:03:44.474 CNTRLR [Node 094] The node is alive.
  1130. 2025-08-10 22:03:44.474 CNTRLR [Node 094] The node is ready to be used
  1131. 2025-08-10 22:03:44.474 CNTRLR « [Node 094] ping successful
  1132. 2025-08-10 22:03:44.474 DRIVER » [Node 070] [REQ] [SendData]
  1133. │ transmit options: 0x01
  1134. │ callback id: 35
  1135. └─[NoOperationCC]
  1136. 2025-08-10 22:03:44.474 SERIAL » 0x01080013460100012381 (10 bytes)
  1137. 2025-08-10 22:03:44.476 SERIAL « [ACK] (0x06)
  1138. 2025-08-10 22:03:44.483 SERIAL « 0x0104011301e8 (6 bytes)
  1139. 2025-08-10 22:03:44.483 SERIAL » [ACK] (0x06)
  1140. 2025-08-10 22:03:44.483 DRIVER « [RES] [SendData]
  1141. was sent: true
  1142. 2025-08-10 22:03:44.504 SERIAL « 0x011800132300000200cf7f7f7f7f01010300000000020100001a (26 bytes)
  1143. 2025-08-10 22:03:44.504 SERIAL » [ACK] (0x06)
  1144. 2025-08-10 22:03:44.505 DRIVER « [REQ] [SendData]
  1145. callback id: 35
  1146. transmit status: OK, took 20 ms
  1147. routing attempts: 1
  1148. protocol & route speed: Z-Wave, 40 kbit/s
  1149. routing scheme: LWR
  1150. ACK RSSI: -49 dBm
  1151. ACK channel no.: 1
  1152. TX channel no.: 1
  1153. 2025-08-10 22:03:44.505 CNTRLR [Node 070] The node is alive.
  1154. 2025-08-10 22:03:44.505 CNTRLR [Node 070] The node is ready to be used
  1155. 2025-08-10 22:03:44.505 CNTRLR « [Node 070] ping successful
  1156. 2025-08-10 22:03:44.505 DRIVER » [Node 005] [REQ] [SendData]
  1157. │ transmit options: 0x01
  1158. │ callback id: 36
  1159. └─[NoOperationCC]
  1160. 2025-08-10 22:03:44.506 SERIAL » 0x010800130501000124c5 (10 bytes)
  1161. 2025-08-10 22:03:44.507 SERIAL « [ACK] (0x06)
  1162. 2025-08-10 22:03:44.514 SERIAL « 0x0104011301e8 (6 bytes)
  1163. 2025-08-10 22:03:44.514 SERIAL » [ACK] (0x06)
  1164. 2025-08-10 22:03:44.514 DRIVER « [RES] [SendData]
  1165. was sent: true
  1166. 2025-08-10 22:03:44.539 SERIAL « 0x011800132400000300bc7f7f7f7f01010300000000020100006f (26 bytes)
  1167. 2025-08-10 22:03:44.539 SERIAL » [ACK] (0x06)
  1168. 2025-08-10 22:03:44.539 DRIVER « [REQ] [SendData]
  1169. callback id: 36
  1170. transmit status: OK, took 30 ms
  1171. routing attempts: 1
  1172. protocol & route speed: Z-Wave, 40 kbit/s
  1173. routing scheme: LWR
  1174. ACK RSSI: -68 dBm
  1175. ACK channel no.: 1
  1176. TX channel no.: 1
  1177. 2025-08-10 22:03:44.539 CNTRLR [Node 005] The node is alive.
  1178. 2025-08-10 22:03:44.540 CNTRLR [Node 005] The node is ready to be used
  1179. 2025-08-10 22:03:44.540 CNTRLR « [Node 005] ping successful
  1180. 2025-08-10 22:03:44.540 DRIVER » [Node 095] [REQ] [SendData]
  1181. │ transmit options: 0x01
  1182. │ callback id: 37
  1183. └─[NoOperationCC]
  1184. 2025-08-10 22:03:44.540 SERIAL » 0x010800135f010001259e (10 bytes)
  1185. 2025-08-10 22:03:44.542 SERIAL « [ACK] (0x06)
  1186. 2025-08-10 22:03:44.551 SERIAL « 0x0104011301e8 (6 bytes)
  1187. 2025-08-10 22:03:44.551 SERIAL » [ACK] (0x06)
  1188. 2025-08-10 22:03:44.551 DRIVER « [RES] [SendData]
  1189. was sent: true
  1190. 2025-08-10 22:03:44.577 SERIAL « 0x011800132500000200c47f7f7f7f010103000000000201000017 (26 bytes)
  1191. 2025-08-10 22:03:44.577 SERIAL » [ACK] (0x06)
  1192. 2025-08-10 22:03:44.577 DRIVER « [REQ] [SendData]
  1193. callback id: 37
  1194. transmit status: OK, took 20 ms
  1195. routing attempts: 1
  1196. protocol & route speed: Z-Wave, 40 kbit/s
  1197. routing scheme: LWR
  1198. ACK RSSI: -60 dBm
  1199. ACK channel no.: 1
  1200. TX channel no.: 1
  1201. 2025-08-10 22:03:44.577 CNTRLR [Node 095] The node is alive.
  1202. 2025-08-10 22:03:44.577 CNTRLR [Node 095] The node is ready to be used
  1203. 2025-08-10 22:03:44.577 CNTRLR « [Node 095] ping successful
  1204. 2025-08-10 22:03:44.577 DRIVER » [Node 063] [REQ] [SendData]
  1205. │ transmit options: 0x01
  1206. │ callback id: 38
  1207. └─[NoOperationCC]
  1208. 2025-08-10 22:03:44.578 SERIAL » 0x010800133f01000126fd (10 bytes)
  1209. 2025-08-10 22:03:44.579 SERIAL « [ACK] (0x06)
  1210. 2025-08-10 22:03:44.584 SERIAL « 0x0104011301e8 (6 bytes)
  1211. 2025-08-10 22:03:44.585 SERIAL » [ACK] (0x06)
  1212. 2025-08-10 22:03:44.585 DRIVER « [RES] [SendData]
  1213. was sent: true
  1214. 2025-08-10 22:03:44.608 SERIAL « 0x011800132600000300b07f7f7f7f010103000000000201000061 (26 bytes)
  1215. 2025-08-10 22:03:44.608 SERIAL » [ACK] (0x06)
  1216. 2025-08-10 22:03:44.608 DRIVER « [REQ] [SendData]
  1217. callback id: 38
  1218. transmit status: OK, took 30 ms
  1219. routing attempts: 1
  1220. protocol & route speed: Z-Wave, 40 kbit/s
  1221. routing scheme: LWR
  1222. ACK RSSI: -80 dBm
  1223. ACK channel no.: 1
  1224. TX channel no.: 1
  1225. 2025-08-10 22:03:44.608 CNTRLR [Node 063] The node is alive.
  1226. 2025-08-10 22:03:44.608 CNTRLR [Node 063] The node is ready to be used
  1227. 2025-08-10 22:03:44.608 CNTRLR « [Node 063] ping successful
  1228. 2025-08-10 22:03:44.608 DRIVER » [Node 048] [REQ] [SendData]
  1229. │ transmit options: 0x01
  1230. │ callback id: 39
  1231. └─[NoOperationCC]
  1232. 2025-08-10 22:03:44.608 SERIAL » 0x010800133001000127f3 (10 bytes)
  1233. 2025-08-10 22:03:44.611 SERIAL « [ACK] (0x06)
  1234. 2025-08-10 22:03:44.619 SERIAL « 0x0104011301e8 (6 bytes)
  1235. 2025-08-10 22:03:44.619 SERIAL » [ACK] (0x06)
  1236. 2025-08-10 22:03:44.619 DRIVER « [RES] [SendData]
  1237. was sent: true
  1238. 2025-08-10 22:03:44.640 SERIAL « 0x011800132700000200b07f7f7f7f010103000000000201000061 (26 bytes)
  1239. 2025-08-10 22:03:44.640 SERIAL » [ACK] (0x06)
  1240. 2025-08-10 22:03:44.640 DRIVER « [REQ] [SendData]
  1241. callback id: 39
  1242. transmit status: OK, took 20 ms
  1243. routing attempts: 1
  1244. protocol & route speed: Z-Wave, 40 kbit/s
  1245. routing scheme: LWR
  1246. ACK RSSI: -80 dBm
  1247. ACK channel no.: 1
  1248. TX channel no.: 1
  1249. 2025-08-10 22:03:44.640 CNTRLR [Node 048] The node is alive.
  1250. 2025-08-10 22:03:44.640 CNTRLR [Node 048] The node is ready to be used
  1251. 2025-08-10 22:03:44.641 CNTRLR « [Node 048] ping successful
  1252. 2025-08-10 22:03:44.641 DRIVER » [Node 083] [REQ] [SendData]
  1253. │ transmit options: 0x01
  1254. │ callback id: 40
  1255. └─[NoOperationCC]
  1256. 2025-08-10 22:03:44.641 SERIAL » 0x0108001353010001289f (10 bytes)
  1257. 2025-08-10 22:03:44.643 SERIAL « [ACK] (0x06)
  1258. 2025-08-10 22:03:44.649 SERIAL « 0x0104011301e8 (6 bytes)
  1259. 2025-08-10 22:03:44.649 SERIAL » [ACK] (0x06)
  1260. 2025-08-10 22:03:44.649 DRIVER « [RES] [SendData]
  1261. was sent: true
  1262. 2025-08-10 22:03:44.709 SERIAL « 0x011800132800000600aa7f7f7f7f010103000000000202000073 (26 bytes)
  1263. 2025-08-10 22:03:44.709 SERIAL » [ACK] (0x06)
  1264. 2025-08-10 22:03:44.710 DRIVER « [REQ] [SendData]
  1265. callback id: 40
  1266. transmit status: OK, took 60 ms
  1267. routing attempts: 2
  1268. protocol & route speed: Z-Wave, 40 kbit/s
  1269. routing scheme: LWR
  1270. ACK RSSI: -86 dBm
  1271. ACK channel no.: 1
  1272. TX channel no.: 1
  1273. 2025-08-10 22:03:44.710 CNTRLR [Node 083] The node is alive.
  1274. 2025-08-10 22:03:44.710 CNTRLR [Node 083] The node is ready to be used
  1275. 2025-08-10 22:03:44.710 CNTRLR « [Node 083] ping successful
  1276. 2025-08-10 22:03:44.710 DRIVER » [Node 066] [REQ] [SendData]
  1277. │ transmit options: 0x01
  1278. │ callback id: 41
  1279. └─[NoOperationCC]
  1280. 2025-08-10 22:03:44.710 SERIAL » 0x0108001342010001298f (10 bytes)
  1281. 2025-08-10 22:03:44.713 SERIAL « [ACK] (0x06)
  1282. 2025-08-10 22:03:44.719 SERIAL « 0x0104011301e8 (6 bytes)
  1283. 2025-08-10 22:03:44.719 SERIAL » [ACK] (0x06)
  1284. 2025-08-10 22:03:44.719 DRIVER « [RES] [SendData]
  1285. was sent: true
  1286. 2025-08-10 22:03:44.741 SERIAL « 0x011800132900000200cc7f7f7f7f010103000000000201000013 (26 bytes)
  1287. 2025-08-10 22:03:44.741 SERIAL » [ACK] (0x06)
  1288. 2025-08-10 22:03:44.741 DRIVER « [REQ] [SendData]
  1289. callback id: 41
  1290. transmit status: OK, took 20 ms
  1291. routing attempts: 1
  1292. protocol & route speed: Z-Wave, 40 kbit/s
  1293. routing scheme: LWR
  1294. ACK RSSI: -52 dBm
  1295. ACK channel no.: 1
  1296. TX channel no.: 1
  1297. 2025-08-10 22:03:44.742 CNTRLR [Node 066] The node is alive.
  1298. 2025-08-10 22:03:44.742 CNTRLR [Node 066] The node is ready to be used
  1299. 2025-08-10 22:03:44.742 CNTRLR « [Node 066] ping successful
  1300. 2025-08-10 22:03:44.742 DRIVER » [Node 047] [REQ] [SendData]
  1301. │ transmit options: 0x01
  1302. │ callback id: 42
  1303. └─[NoOperationCC]
  1304. 2025-08-10 22:03:44.742 SERIAL » 0x010800132f0100012ae1 (10 bytes)
  1305. 2025-08-10 22:03:44.744 SERIAL « [ACK] (0x06)
  1306. 2025-08-10 22:03:44.749 SERIAL « 0x0104011301e8 (6 bytes)
  1307. 2025-08-10 22:03:44.749 SERIAL » [ACK] (0x06)
  1308. 2025-08-10 22:03:44.749 DRIVER « [RES] [SendData]
  1309. was sent: true
  1310. 2025-08-10 22:03:44.893 SERIAL « 0x011800132a00000e01bc7f7f7f7f0101035e0000000201000033 (26 bytes)
  1311. 2025-08-10 22:03:44.894 SERIAL » [ACK] (0x06)
  1312. 2025-08-10 22:03:44.894 DRIVER « [REQ] [SendData]
  1313. callback id: 42
  1314. transmit status: OK, took 140 ms
  1315. repeater node IDs: 94
  1316. routing attempts: 1
  1317. protocol & route speed: Z-Wave, 40 kbit/s
  1318. routing scheme: LWR
  1319. ACK RSSI: -68 dBm
  1320. ACK RSSI on repeaters: N/A
  1321. ACK channel no.: 1
  1322. TX channel no.: 1
  1323. 2025-08-10 22:03:44.894 CNTRLR [Node 047] The node is alive.
  1324. 2025-08-10 22:03:44.894 CNTRLR [Node 047] The node is ready to be used
  1325. 2025-08-10 22:03:44.894 CNTRLR « [Node 047] ping successful
  1326. 2025-08-10 22:03:44.894 DRIVER » [Node 141] [REQ] [SendData]
  1327. │ transmit options: 0x01
  1328. │ callback id: 43
  1329. └─[NoOperationCC]
  1330. 2025-08-10 22:03:44.894 SERIAL » 0x010800138d0100012b42 (10 bytes)
  1331. 2025-08-10 22:03:44.897 SERIAL « [ACK] (0x06)
  1332. 2025-08-10 22:03:44.906 SERIAL « 0x0104011301e8 (6 bytes)
  1333. 2025-08-10 22:03:44.906 SERIAL » [ACK] (0x06)
  1334. 2025-08-10 22:03:44.906 DRIVER « [RES] [SendData]
  1335. was sent: true
  1336. 2025-08-10 22:03:44.923 SERIAL « 0x011800132b00000200cf7f7f7f7f000003000000000301000013 (26 bytes)
  1337. 2025-08-10 22:03:44.924 SERIAL » [ACK] (0x06)
  1338. 2025-08-10 22:03:44.924 DRIVER « [REQ] [SendData]
  1339. callback id: 43
  1340. transmit status: OK, took 20 ms
  1341. routing attempts: 1
  1342. protocol & route speed: Z-Wave, 100 kbit/s
  1343. routing scheme: LWR
  1344. ACK RSSI: -49 dBm
  1345. ACK channel no.: 0
  1346. TX channel no.: 0
  1347. 2025-08-10 22:03:44.924 CNTRLR [Node 141] The node is alive.
  1348. 2025-08-10 22:03:44.924 CNTRLR [Node 141] The node is ready to be used
  1349. 2025-08-10 22:03:44.924 CNTRLR « [Node 141] ping successful
  1350. 2025-08-10 22:03:44.925 DRIVER » [Node 026] [REQ] [SendData]
  1351. │ transmit options: 0x01
  1352. │ callback id: 44
  1353. └─[NoOperationCC]
  1354. 2025-08-10 22:03:44.925 SERIAL » 0x010800131a0100012cd2 (10 bytes)
  1355. 2025-08-10 22:03:44.927 SERIAL « [ACK] (0x06)
  1356. 2025-08-10 22:03:44.932 SERIAL « 0x0104011301e8 (6 bytes)
  1357. 2025-08-10 22:03:44.932 SERIAL » [ACK] (0x06)
  1358. 2025-08-10 22:03:44.932 DRIVER « [RES] [SendData]
  1359. was sent: true
  1360. 2025-08-10 22:03:44.959 SERIAL « 0x011800132c00000300ca7f7f7f7f010103000000000201000011 (26 bytes)
  1361. 2025-08-10 22:03:44.959 SERIAL » [ACK] (0x06)
  1362. 2025-08-10 22:03:44.959 DRIVER « [REQ] [SendData]
  1363. callback id: 44
  1364. transmit status: OK, took 30 ms
  1365. routing attempts: 1
  1366. protocol & route speed: Z-Wave, 40 kbit/s
  1367. routing scheme: LWR
  1368. ACK RSSI: -54 dBm
  1369. ACK channel no.: 1
  1370. TX channel no.: 1
  1371. 2025-08-10 22:03:44.960 CNTRLR [Node 026] The node is alive.
  1372. 2025-08-10 22:03:44.960 CNTRLR [Node 026] The node is ready to be used
  1373. 2025-08-10 22:03:44.960 CNTRLR « [Node 026] ping successful
  1374. 2025-08-10 22:03:44.960 DRIVER » [Node 073] [REQ] [SendData]
  1375. │ transmit options: 0x01
  1376. │ callback id: 45
  1377. └─[NoOperationCC]
  1378. 2025-08-10 22:03:44.960 SERIAL » 0x01080013490100012d80 (10 bytes)
  1379. 2025-08-10 22:03:44.962 SERIAL « [ACK] (0x06)
  1380. 2025-08-10 22:03:44.969 SERIAL « 0x0104011301e8 (6 bytes)
  1381. 2025-08-10 22:03:44.969 SERIAL » [ACK] (0x06)
  1382. 2025-08-10 22:03:44.970 DRIVER « [RES] [SendData]
  1383. was sent: true
  1384. New client
  1385. 2025-08-10 22:03:45.007 SERIAL « 0x011800132d00000200db7f7f7f7f010103000000000201000000 (26 bytes)
  1386. 2025-08-10 22:03:45.008 SERIAL » [ACK] (0x06)
  1387. 2025-08-10 22:03:45.009 DRIVER « [REQ] [SendData]
  1388. callback id: 45
  1389. transmit status: OK, took 20 ms
  1390. routing attempts: 1
  1391. protocol & route speed: Z-Wave, 40 kbit/s
  1392. routing scheme: LWR
  1393. ACK RSSI: -37 dBm
  1394. ACK channel no.: 1
  1395. TX channel no.: 1
  1396. 2025-08-10 22:03:45.009 CNTRLR [Node 073] The node is alive.
  1397. 2025-08-10 22:03:45.009 CNTRLR [Node 073] The node is ready to be used
  1398. 2025-08-10 22:03:45.016 CNTRLR « [Node 073] ping successful
  1399. 2025-08-10 22:03:45.017 DRIVER » [Node 045] [REQ] [SendData]
  1400. │ transmit options: 0x01
  1401. │ callback id: 46
  1402. └─[NoOperationCC]
  1403. 2025-08-10 22:03:45.017 SERIAL » 0x010800132d0100012ee7 (10 bytes)
  1404. 2025-08-10 22:03:45.019 SERIAL « [ACK] (0x06)
  1405. 2025-08-10 22:03:45.145 SERIAL « 0x0104011301e8 (6 bytes)
  1406. 2025-08-10 22:03:45.146 SERIAL » [ACK] (0x06)
  1407. 2025-08-10 22:03:45.146 DRIVER « [RES] [SendData]
  1408. was sent: true
  1409. 2025-08-10 22:03:45.165 SERIAL « 0x011800132e00000200c97f7f7f7f000003000000000301000010 (26 bytes)
  1410. 2025-08-10 22:03:45.166 SERIAL » [ACK] (0x06)
  1411. 2025-08-10 22:03:45.166 DRIVER « [REQ] [SendData]
  1412. callback id: 46
  1413. transmit status: OK, took 20 ms
  1414. routing attempts: 1
  1415. protocol & route speed: Z-Wave, 100 kbit/s
  1416. routing scheme: LWR
  1417. ACK RSSI: -55 dBm
  1418. ACK channel no.: 0
  1419. TX channel no.: 0
  1420. 2025-08-10 22:03:45.166 CNTRLR [Node 045] The node is alive.
  1421. 2025-08-10 22:03:45.166 CNTRLR [Node 045] The node is ready to be used
  1422. 2025-08-10 22:03:45.168 CNTRLR « [Node 045] ping successful
  1423. 2025-08-10 22:03:45.169 DRIVER » [Node 024] [REQ] [SendData]
  1424. │ transmit options: 0x01
  1425. │ callback id: 47
  1426. └─[NoOperationCC]
  1427. 2025-08-10 22:03:45.169 SERIAL » 0x01080013180100012fd3 (10 bytes)
  1428. 2025-08-10 22:03:45.171 SERIAL « [ACK] (0x06)
  1429. 2025-08-10 22:03:45.178 SERIAL « 0x0104011301e8 (6 bytes)
  1430. 2025-08-10 22:03:45.178 SERIAL » [ACK] (0x06)
  1431. 2025-08-10 22:03:45.179 DRIVER « [RES] [SendData]
  1432. was sent: true
  1433. 2025-08-10 22:03:45.393 SERIAL « 0x011800132f00001502b37f7f7f7f0101034e0c0000010100003e (26 bytes)
  1434. 2025-08-10 22:03:45.393 SERIAL » [ACK] (0x06)
  1435. 2025-08-10 22:03:45.393 DRIVER « [REQ] [SendData]
  1436. callback id: 47
  1437. transmit status: OK, took 210 ms
  1438. repeater node IDs: 78, 12
  1439. routing attempts: 1
  1440. protocol & route speed: Z-Wave, 9.6 kbit/s
  1441. routing scheme: LWR
  1442. ACK RSSI: -77 dBm
  1443. ACK RSSI on repeaters: N/A, N/A
  1444. ACK channel no.: 1
  1445. TX channel no.: 1
  1446. 2025-08-10 22:03:45.393 CNTRLR [Node 024] The node is alive.
  1447. 2025-08-10 22:03:45.393 CNTRLR [Node 024] The node is ready to be used
  1448. 2025-08-10 22:03:45.398 CNTRLR « [Node 024] ping successful
  1449. 2025-08-10 22:03:45.398 DRIVER » [Node 051] [REQ] [SendData]
  1450. │ transmit options: 0x01
  1451. │ callback id: 48
  1452. └─[NoOperationCC]
  1453. 2025-08-10 22:03:45.398 SERIAL » 0x010800133301000130e7 (10 bytes)
  1454. 2025-08-10 22:03:45.401 SERIAL « [ACK] (0x06)
  1455. 2025-08-10 22:03:45.411 SERIAL « 0x0104011301e8 (6 bytes)
  1456. 2025-08-10 22:03:45.411 SERIAL » [ACK] (0x06)
  1457. 2025-08-10 22:03:45.411 DRIVER « [RES] [SendData]
  1458. was sent: true
  1459. 2025-08-10 22:03:45.626 SERIAL « 0x011800133000001502b57f7f7f7f0101034e1800000101000033 (26 bytes)
  1460. 2025-08-10 22:03:45.626 SERIAL » [ACK] (0x06)
  1461. 2025-08-10 22:03:45.626 DRIVER « [REQ] [SendData]
  1462. callback id: 48
  1463. transmit status: OK, took 210 ms
  1464. repeater node IDs: 78, 24
  1465. routing attempts: 1
  1466. protocol & route speed: Z-Wave, 9.6 kbit/s
  1467. routing scheme: LWR
  1468. ACK RSSI: -75 dBm
  1469. ACK RSSI on repeaters: N/A, N/A
  1470. ACK channel no.: 1
  1471. TX channel no.: 1
  1472. 2025-08-10 22:03:45.627 CNTRLR [Node 051] The node is alive.
  1473. 2025-08-10 22:03:45.627 CNTRLR [Node 051] The node is ready to be used
  1474. 2025-08-10 22:03:45.630 CNTRLR « [Node 051] ping successful
  1475. 2025-08-10 22:03:45.630 DRIVER » [Node 147] [REQ] [SendData]
  1476. │ transmit options: 0x01
  1477. │ callback id: 49
  1478. └─[NoOperationCC]
  1479. 2025-08-10 22:03:45.631 SERIAL » 0x01080013930100013146 (10 bytes)
  1480. 2025-08-10 22:03:45.632 SERIAL « [ACK] (0x06)
  1481. 2025-08-10 22:03:45.642 SERIAL « 0x0104011301e8 (6 bytes)
  1482. 2025-08-10 22:03:45.642 SERIAL » [ACK] (0x06)
  1483. 2025-08-10 22:03:45.642 DRIVER « [RES] [SendData]
  1484. was sent: true
  1485. 2025-08-10 22:03:45.685 SERIAL « 0x011800133100000300c17f7f7f7f010103000000000201000007 (26 bytes)
  1486. 2025-08-10 22:03:45.686 SERIAL » [ACK] (0x06)
  1487. 2025-08-10 22:03:45.686 DRIVER « [REQ] [SendData]
  1488. callback id: 49
  1489. transmit status: OK, took 30 ms
  1490. routing attempts: 1
  1491. protocol & route speed: Z-Wave, 40 kbit/s
  1492. routing scheme: LWR
  1493. ACK RSSI: -63 dBm
  1494. ACK channel no.: 1
  1495. TX channel no.: 1
  1496. 2025-08-10 22:03:45.686 CNTRLR [Node 147] The node is alive.
  1497. 2025-08-10 22:03:45.686 CNTRLR [Node 147] The node is ready to be used
  1498. 2025-08-10 22:03:45.694 CNTRLR « [Node 147] ping successful
  1499. 2025-08-10 22:03:45.694 DRIVER » [Node 145] [REQ] [SendData]
  1500. │ transmit options: 0x01
  1501. │ callback id: 50
  1502. └─[NoOperationCC]
  1503. 2025-08-10 22:03:45.694 SERIAL » 0x01080013910100013247 (10 bytes)
  1504. 2025-08-10 22:03:45.697 SERIAL « [ACK] (0x06)
  1505. 2025-08-10 22:03:45.706 SERIAL « 0x0104011301e8 (6 bytes)
  1506. 2025-08-10 22:03:45.706 SERIAL » [ACK] (0x06)
  1507. 2025-08-10 22:03:45.706 DRIVER « [RES] [SendData]
  1508. was sent: true
  1509. 2025-08-10 22:03:45.738 SERIAL « 0x011800133200000200c47f7f7f7f000003000000000301000001 (26 bytes)
  1510. 2025-08-10 22:03:45.738 SERIAL » [ACK] (0x06)
  1511. 2025-08-10 22:03:45.739 DRIVER « [REQ] [SendData]
  1512. callback id: 50
  1513. transmit status: OK, took 20 ms
  1514. routing attempts: 1
  1515. protocol & route speed: Z-Wave, 100 kbit/s
  1516. routing scheme: LWR
  1517. ACK RSSI: -60 dBm
  1518. ACK channel no.: 0
  1519. TX channel no.: 0
  1520. 2025-08-10 22:03:45.739 CNTRLR [Node 145] The node is alive.
  1521. 2025-08-10 22:03:45.739 CNTRLR [Node 145] The node is ready to be used
  1522. 2025-08-10 22:03:45.741 CNTRLR « [Node 145] ping successful
  1523. 2025-08-10 22:03:45.742 DRIVER » [Node 100] [REQ] [SendData]
  1524. │ transmit options: 0x01
  1525. │ callback id: 51
  1526. └─[NoOperationCC]
  1527. 2025-08-10 22:03:45.742 SERIAL » 0x010800136401000133b3 (10 bytes)
  1528. 2025-08-10 22:03:45.745 SERIAL « [ACK] (0x06)
  1529. 2025-08-10 22:03:45.755 SERIAL « 0x0104011301e8 (6 bytes)
  1530. 2025-08-10 22:03:45.755 SERIAL » [ACK] (0x06)
  1531. 2025-08-10 22:03:45.756 DRIVER « [RES] [SendData]
  1532. was sent: true
  1533. 2025-08-10 22:03:45.787 SERIAL « 0x011800133300000200db7f7f7f7f00000300000000030100001f (26 bytes)
  1534. 2025-08-10 22:03:45.788 SERIAL » [ACK] (0x06)
  1535. 2025-08-10 22:03:45.788 DRIVER « [REQ] [SendData]
  1536. callback id: 51
  1537. transmit status: OK, took 20 ms
  1538. routing attempts: 1
  1539. protocol & route speed: Z-Wave, 100 kbit/s
  1540. routing scheme: LWR
  1541. ACK RSSI: -37 dBm
  1542. ACK channel no.: 0
  1543. TX channel no.: 0
  1544. 2025-08-10 22:03:45.788 CNTRLR [Node 100] The node is alive.
  1545. 2025-08-10 22:03:45.788 CNTRLR [Node 100] The node is ready to be used
  1546. 2025-08-10 22:03:45.790 CNTRLR « [Node 100] ping successful
  1547. 2025-08-10 22:03:45.790 DRIVER » [Node 099] [REQ] [SendData]
  1548. │ transmit options: 0x01
  1549. │ callback id: 52
  1550. └─[NoOperationCC]
  1551. 2025-08-10 22:03:45.791 SERIAL » 0x010800136301000134b3 (10 bytes)
  1552. 2025-08-10 22:03:45.793 SERIAL « [ACK] (0x06)
  1553. 2025-08-10 22:03:45.803 SERIAL « 0x0104011301e8 (6 bytes)
  1554. 2025-08-10 22:03:45.803 SERIAL » [ACK] (0x06)
  1555. 2025-08-10 22:03:45.804 DRIVER « [RES] [SendData]
  1556. was sent: true
  1557. 2025-08-10 22:03:45.834 SERIAL « 0x011800133400000200cf7f7f7f7f00000300000000030100000c (26 bytes)
  1558. 2025-08-10 22:03:45.834 SERIAL » [ACK] (0x06)
  1559. 2025-08-10 22:03:45.835 DRIVER « [REQ] [SendData]
  1560. callback id: 52
  1561. transmit status: OK, took 20 ms
  1562. routing attempts: 1
  1563. protocol & route speed: Z-Wave, 100 kbit/s
  1564. routing scheme: LWR
  1565. ACK RSSI: -49 dBm
  1566. ACK channel no.: 0
  1567. TX channel no.: 0
  1568. 2025-08-10 22:03:45.835 CNTRLR [Node 099] The node is alive.
  1569. 2025-08-10 22:03:45.835 CNTRLR [Node 099] The node is ready to be used
  1570. 2025-08-10 22:03:45.841 CNTRLR « [Node 099] ping successful
  1571. 2025-08-10 22:03:45.841 DRIVER » [Node 054] [REQ] [SendData]
  1572. │ transmit options: 0x01
  1573. │ callback id: 53
  1574. └─[NoOperationCC]
  1575. 2025-08-10 22:03:45.842 SERIAL » 0x010800133601000135e7 (10 bytes)
  1576. 2025-08-10 22:03:45.844 SERIAL « [ACK] (0x06)
  1577. 2025-08-10 22:03:45.852 SERIAL « 0x0104011301e8 (6 bytes)
  1578. 2025-08-10 22:03:45.852 SERIAL » [ACK] (0x06)
  1579. 2025-08-10 22:03:45.853 DRIVER « [RES] [SendData]
  1580. was sent: true
  1581. 2025-08-10 22:03:45.886 SERIAL « 0x011800133500000200b87f7f7f7f01010300000000020100007b (26 bytes)
  1582. 2025-08-10 22:03:45.886 SERIAL » [ACK] (0x06)
  1583. 2025-08-10 22:03:45.887 DRIVER « [REQ] [SendData]
  1584. callback id: 53
  1585. transmit status: OK, took 20 ms
  1586. routing attempts: 1
  1587. protocol & route speed: Z-Wave, 40 kbit/s
  1588. routing scheme: LWR
  1589. ACK RSSI: -72 dBm
  1590. ACK channel no.: 1
  1591. TX channel no.: 1
  1592. 2025-08-10 22:03:45.887 CNTRLR [Node 054] The node is alive.
  1593. 2025-08-10 22:03:45.887 CNTRLR [Node 054] The node is ready to be used
  1594. 2025-08-10 22:03:45.889 CNTRLR « [Node 054] ping successful
  1595. 2025-08-10 22:03:45.889 DRIVER » [Node 138] [REQ] [SendData]
  1596. │ transmit options: 0x01
  1597. │ callback id: 54
  1598. └─[NoOperationCC]
  1599. 2025-08-10 22:03:45.889 SERIAL » 0x010800138a0100013658 (10 bytes)
  1600. 2025-08-10 22:03:45.893 SERIAL « [ACK] (0x06)
  1601. 2025-08-10 22:03:45.904 SERIAL « 0x0104011301e8 (6 bytes)
  1602. 2025-08-10 22:03:45.904 SERIAL » [ACK] (0x06)
  1603. 2025-08-10 22:03:45.905 DRIVER « [RES] [SendData]
  1604. was sent: true
  1605. 2025-08-10 22:03:45.932 SERIAL « 0x011800133600000200c97f7f7f7f000003000000000301000008 (26 bytes)
  1606. 2025-08-10 22:03:45.933 SERIAL » [ACK] (0x06)
  1607. 2025-08-10 22:03:45.933 DRIVER « [REQ] [SendData]
  1608. callback id: 54
  1609. transmit status: OK, took 20 ms
  1610. routing attempts: 1
  1611. protocol & route speed: Z-Wave, 100 kbit/s
  1612. routing scheme: LWR
  1613. ACK RSSI: -55 dBm
  1614. ACK channel no.: 0
  1615. TX channel no.: 0
  1616. 2025-08-10 22:03:45.933 CNTRLR [Node 138] The node is alive.
  1617. 2025-08-10 22:03:45.933 CNTRLR [Node 138] The node is ready to be used
  1618. 2025-08-10 22:03:45.940 CNTRLR « [Node 138] ping successful
  1619. 2025-08-10 22:03:45.940 DRIVER » [Node 082] [REQ] [SendData]
  1620. │ transmit options: 0x01
  1621. │ callback id: 55
  1622. └─[NoOperationCC]
  1623. 2025-08-10 22:03:45.940 SERIAL » 0x01080013520100013781 (10 bytes)
  1624. 2025-08-10 22:03:45.943 SERIAL « [ACK] (0x06)
  1625. 2025-08-10 22:03:45.952 SERIAL « 0x0104011301e8 (6 bytes)
  1626. 2025-08-10 22:03:45.952 SERIAL » [ACK] (0x06)
  1627. 2025-08-10 22:03:45.953 DRIVER « [RES] [SendData]
  1628. was sent: true
  1629. 2025-08-10 22:03:46.184 SERIAL « 0x011800133700001502c37f7f7f7f0101034a0b00000101000055 (26 bytes)
  1630. 2025-08-10 22:03:46.184 SERIAL » [ACK] (0x06)
  1631. 2025-08-10 22:03:46.185 DRIVER « [REQ] [SendData]
  1632. callback id: 55
  1633. transmit status: OK, took 210 ms
  1634. repeater node IDs: 74, 11
  1635. routing attempts: 1
  1636. protocol & route speed: Z-Wave, 9.6 kbit/s
  1637. routing scheme: LWR
  1638. ACK RSSI: -61 dBm
  1639. ACK RSSI on repeaters: N/A, N/A
  1640. ACK channel no.: 1
  1641. TX channel no.: 1
  1642. 2025-08-10 22:03:46.185 CNTRLR [Node 082] The node is alive.
  1643. 2025-08-10 22:03:46.185 CNTRLR [Node 082] The node is ready to be used
  1644. 2025-08-10 22:03:46.195 CNTRLR « [Node 082] ping successful
  1645. 2025-08-10 22:03:46.195 DRIVER » [Node 016] [REQ] [SendData]
  1646. │ transmit options: 0x01
  1647. │ callback id: 56
  1648. └─[NoOperationCC]
  1649. 2025-08-10 22:03:46.195 SERIAL » 0x010800131001000138cc (10 bytes)
  1650. 2025-08-10 22:03:46.200 SERIAL « [ACK] (0x06)
  1651. 2025-08-10 22:03:46.211 SERIAL « 0x0104011301e8 (6 bytes)
  1652. 2025-08-10 22:03:46.211 SERIAL » [ACK] (0x06)
  1653. 2025-08-10 22:03:46.212 DRIVER « [RES] [SendData]
  1654. was sent: true
  1655. 2025-08-10 22:03:47.475 SERIAL « 0x011800133800007f00c67f7f7f7f010103000000004204000030 (26 bytes)
  1656. 2025-08-10 22:03:47.476 SERIAL » [ACK] (0x06)
  1657. 2025-08-10 22:03:47.476 DRIVER « [REQ] [SendData]
  1658. callback id: 56
  1659. transmit status: OK, took 1270 ms
  1660. routing attempts: 4
  1661. protocol & route speed: Z-Wave, 40 kbit/s
  1662. routing scheme: LWR
  1663. ACK RSSI: -58 dBm
  1664. ACK channel no.: 1
  1665. TX channel no.: 1
  1666. beam: 1000 ms
  1667. 2025-08-10 22:03:47.476 CNTRLR [Node 016] The node is alive.
  1668. 2025-08-10 22:03:47.477 CNTRLR [Node 016] The node is ready to be used
  1669. 2025-08-10 22:03:47.477 CNTRLR All nodes are ready to be used
  1670. 2025-08-10 22:03:47.480 CNTRLR « [Node 016] ping successful
  1671. 2025-08-10 22:03:47.481 DRIVER all queues idle
  1672. 2025-08-10 22:03:47.915 DRIVER Usage statistics sent - next transmission scheduled in 23 hours.
  1673. 2025-08-10 22:03:52.483 DRIVER one or more queues busy
  1674. 2025-08-10 22:03:52.483 DRIVER » [REQ] [GetBackgroundRSSI]
  1675. 2025-08-10 22:03:52.483 SERIAL » 0x0103003bc7 (5 bytes)
  1676. 2025-08-10 22:03:52.485 SERIAL « [ACK] (0x06)
  1677. 2025-08-10 22:03:52.485 SERIAL « 0x0105013ba7aacd (7 bytes)
  1678. 2025-08-10 22:03:52.486 SERIAL » [ACK] (0x06)
  1679. 2025-08-10 22:03:52.486 DRIVER « [RES] [GetBackgroundRSSI]
  1680. channel 0: -89 dBm
  1681. channel 1: -86 dBm
  1682. 2025-08-10 22:03:52.487 DRIVER all queues idle
  1683. 2025-08-10 22:03:54.960 SERIAL « 0x01160004000b0e600d0100320221340000000f0000c70069 (24 bytes)
  1684. 2025-08-10 22:03:54.962 SERIAL » [ACK] (0x06)
  1685. 2025-08-10 22:03:54.963 CNTRLR [Node 011] [Meter] value[66049]: metadata updated [Endpoint 1]
  1686. 2025-08-10 22:03:54.963 CNTRLR [Node 011] [~] [Meter] value[66049]: 1.6 => 1.5 [Endpoint 1]
  1687. 2025-08-10 22:03:54.964 DRIVER « [Node 011] [REQ] [ApplicationCommand]
  1688. └─[MultiChannelCCCommandEncapsulation]
  1689. │ source: 1
  1690. │ destination: 0
  1691. └─[MeterCCReport]
  1692. meter type: Electric
  1693. scale: W
  1694. rate type: Consumed
  1695. value: 1.5
  1696. time delta: 0 seconds
  1697. 2025-08-10 22:04:08.653 SERIAL « 0x0116000400820e600d020032022134000000080000c700e4 (24 bytes)
  1698. 2025-08-10 22:04:08.654 SERIAL » [ACK] (0x06)
  1699. 2025-08-10 22:04:08.654 CNTRLR [Node 130] [Meter] value[66049]: metadata updated [Endpoint 2]
  1700. 2025-08-10 22:04:08.655 CNTRLR [Node 130] [~] [Meter] value[66049]: 0.6 => 0.8 [Endpoint 2]
  1701. 2025-08-10 22:04:08.655 DRIVER « [Node 130] [REQ] [ApplicationCommand]
  1702. └─[MultiChannelCCCommandEncapsulation]
  1703. │ source: 2
  1704. │ destination: 0
  1705. └─[MeterCCReport]
  1706. meter type: Electric
  1707. scale: W
  1708. rate type: Consumed
  1709. value: 0.8
  1710. time delta: 0 seconds
  1711. 2025-08-10 22:04:17.084 DRIVER one or more queues busy
  1712. 2025-08-10 22:04:17.085 DRIVER » [Node 074] [REQ] [SendData]
  1713. │ transmit options: 0x25
  1714. │ callback id: 58
  1715. └─[BinarySwitchCCSet]
  1716. target value: true
  1717. 2025-08-10 22:04:17.086 SERIAL » 0x010b00134a042501ffff253a92 (13 bytes)
  1718. 2025-08-10 22:04:17.088 SERIAL « [ACK] (0x06)
  1719. 2025-08-10 22:04:17.096 SERIAL « 0x0104011301e8 (6 bytes)
  1720. 2025-08-10 22:04:17.097 SERIAL » [ACK] (0x06)
  1721. 2025-08-10 22:04:17.097 DRIVER « [RES] [SendData]
  1722. was sent: true
  1723. 2025-08-10 22:04:17.243 SERIAL « 0x011800133a00000e04c37f7f7f7f010103180b3649020100006b (26 bytes)
  1724. 2025-08-10 22:04:17.243 SERIAL » [ACK] (0x06)
  1725. 2025-08-10 22:04:17.244 DRIVER « [REQ] [SendData]
  1726. callback id: 58
  1727. transmit status: OK, took 140 ms
  1728. repeater node IDs: 24, 11, 54, 73
  1729. routing attempts: 1
  1730. protocol & route speed: Z-Wave, 40 kbit/s
  1731. routing scheme: LWR
  1732. ACK RSSI: -61 dBm
  1733. ACK RSSI on repeaters: N/A, N/A, N/A, N/A
  1734. ACK channel no.: 1
  1735. TX channel no.: 1
  1736. 2025-08-10 22:04:17.245 CNTRLR [Node 074] [~] [Binary Switch] currentValue: true => true [Endpoint 0]
  1737. 2025-08-10 22:04:17.246 DRIVER all queues idle
  1738. 2025-08-10 22:04:17.523 SERIAL « 0x010b0004004a032503ffc100a1 (13 bytes)
  1739. 2025-08-10 22:04:17.526 SERIAL » [ACK] (0x06)
  1740. 2025-08-10 22:04:17.528 CNTRLR [Node 074] [~] [Binary Switch] currentValue: true => true [Endpoint 0]
  1741. 2025-08-10 22:04:17.528 CNTRLR [Node 074] Scheduled poll canceled because expected value was received
  1742. 2025-08-10 22:04:17.529 DRIVER « [Node 074] [REQ] [ApplicationCommand]
  1743. └─[BinarySwitchCCReport]
  1744. current value: true
  1745. 2025-08-10 22:04:19.324 SERIAL « 0x010e0004007a063105012200e9d000a7 (16 bytes)
  1746. 2025-08-10 22:04:19.325 SERIAL » [ACK] (0x06)
  1747. 2025-08-10 22:04:19.326 CNTRLR [Node 122] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
  1748. 2025-08-10 22:04:19.326 CNTRLR [Node 122] [~] [Multilevel Sensor] Air temperature: 23.8 => 23.3 [Endpoint 0]
  1749. 2025-08-10 22:04:19.327 DRIVER « [Node 122] [REQ] [ApplicationCommand]
  1750. └─[MultilevelSensorCCReport]
  1751. sensor type: Air temperature
  1752. scale: Celsius
  1753. value: 23.3
  1754. 2025-08-10 22:04:21.900 CNTRLR Backing up NVM...
  1755. 2025-08-10 22:04:21.900 CNTRLR Turning RF off...
  1756. 2025-08-10 22:04:21.901 DRIVER one or more queues busy
  1757. 2025-08-10 22:04:21.901 DRIVER » [REQ] [SetRFReceiveMode]
  1758. enabled: false
  1759. 2025-08-10 22:04:21.901 SERIAL » 0x0104001000eb (6 bytes)
  1760. 2025-08-10 22:04:21.903 SERIAL « [ACK] (0x06)
  1761. 2025-08-10 22:04:21.905 SERIAL « 0x0104011001eb (6 bytes)
  1762. 2025-08-10 22:04:21.906 SERIAL » [ACK] (0x06)
  1763. 2025-08-10 22:04:21.906 DRIVER « [RES] [SetRFReceiveMode]
  1764. success: true
  1765. 2025-08-10 22:04:21.906 CNTRLR Stopping hardware watchdog...
  1766. 2025-08-10 22:04:21.907 DRIVER » [REQ] [StopWatchdog]
  1767. 2025-08-10 22:04:21.907 SERIAL » 0x010300d32f (5 bytes)
  1768. 2025-08-10 22:04:21.907 DRIVER » [REQ] [GetNVMId]
  1769. 2025-08-10 22:04:21.907 SERIAL » 0x01030029d5 (5 bytes)
  1770. 2025-08-10 22:04:21.908 SERIAL « [ACK] (0x06)
  1771. 2025-08-10 22:04:21.910 SERIAL « [ACK] (0x06)
  1772. 2025-08-10 22:04:21.913 SERIAL « 0x01070129031f81125f (9 bytes)
  1773. 2025-08-10 22:04:21.913 SERIAL » [ACK] (0x06)
  1774. 2025-08-10 22:04:21.914 DRIVER « [RES] [GetNVMId]
  1775. manufacturer: 0x1f
  1776. memory type: DataFlash
  1777. memory size: 256KB
  1778. 2025-08-10 22:04:21.914 DRIVER » [REQ] [ExtNVMReadLongBuffer]
  1779. offset: 0x00
  1780. length: 65535
  1781. 2025-08-10 22:04:21.914 SERIAL » 0x0108002a000000ffffdd (10 bytes)
  1782. 2025-08-10 22:04:21.916 SERIAL « [ACK] (0x06)
  1783. 2025-08-10 22:04:23.528 SERIAL « 0x01ab012a385f2fd059730000db2ec661ffffffff000000000054a50000000000 (173 bytes)
  1784. 000000000000000000000000000000000000000000000000000000000000000000000000000000
  1785. 001000000001000000000000000000000000000000000000000000000000000000000000000000
  1786. 00000000000000000000000000000000000000000000000000007f01ab012a385f2fd059730000
  1787. db2ec661ffffffff000000000054a5000000000000000000
  1788. 2025-08-10 22:04:23.528 SERIAL « [DISCARDED] invalid data 0x0000000000000000000000000000000000000000 (40 bytes)
  1789. 0000000000000000000000000000000010000000
  1790. 2025-08-10 22:04:23.528 SERIAL « 0x0100 (2 bytes)
  1791. 2025-08-10 22:04:23.528 SERIAL « [DISCARDED] invalid data 0x00000000 (4 bytes)
  1792. 2025-08-10 22:04:23.529 DRIVER Dropping message because it contains invalid data
  1793. 2025-08-10 22:04:23.529 SERIAL » [NAK] (0x15)
  1794. 2025-08-10 22:04:23.529 DRIVER Dropping message because it contains invalid data
  1795. 2025-08-10 22:04:23.529 SERIAL » [NAK] (0x15)
  1796. 2025-08-10 22:04:23.530 SERIAL « [DISCARDED] invalid data 0x000000000000 (6 bytes)
  1797. 2025-08-10 22:04:23.530 SERIAL « [DISCARDED] invalid data 0x000000000000 (6 bytes)
  1798. 2025-08-10 22:04:23.530 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1799. 2025-08-10 22:04:23.530 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1800. 2025-08-10 22:04:23.530 SERIAL « [DISCARDED] invalid data 0x0000000000000000000000000000000000000000 (24 bytes)
  1801. 00000000
  1802. 2025-08-10 22:04:23.531 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1803. 2025-08-10 22:04:23.531 SERIAL « [DISCARDED] invalid data 0x0000 (2 bytes)
  1804. 2025-08-10 22:04:23.531 SERIAL « [DISCARDED] invalid data 0x0000000000000000 (8 bytes)
  1805. 2025-08-10 22:04:23.531 SERIAL « [DISCARDED] invalid data 0x0000 (2 bytes)
  1806. 2025-08-10 22:04:23.531 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1807. 2025-08-10 22:04:23.532 SERIAL « [DISCARDED] invalid data 0x00000000007f (6 bytes)
  1808. 2025-08-10 22:04:23.544 SERIAL « 0x01ab012a385f2fd059730000db2ec661ffffffff000000000054a50000000000 (173 bytes)
  1809. 000000000000000000000000000000000000000000000000000000000000000000000000000000
  1810. 001000000001000000000000000000000000000000000000000000000000000000000000000000
  1811. 000000000000000000000000000000000000000000000000000000000000000000000000000000
  1812. 00000000000000000000000000000000000000000000007f
  1813. 2025-08-10 22:04:23.545 SERIAL » [ACK] (0x06)
  1814. 2025-08-10 22:04:23.545 DRIVER « [RES] [ExtNVMReadLongBuffer]
  1815. buffer: (168 bytes)
  1816. 2025-08-10 22:04:23.546 DRIVER » [REQ] [ExtNVMReadLongBuffer]
  1817. offset: 0xa8
  1818. length: 168
  1819. 2025-08-10 22:04:23.546 SERIAL » 0x0108002a0000a800a8dd (10 bytes)
  1820. 2025-08-10 22:04:23.558 SERIAL « 0x01ab012a385f2fd059730000db2ec661ffffffff000000000054a50000000000 (173 bytes)
  1821. 000000000000000000000000000000000000000000000000000000000000000000000000000000
  1822. 001000000001000000000000000000000000000000000000000000000000000000000000000000
  1823. 000000000000000000000000000000000000000000000000000000000000000000000000000000
  1824. 0000000000000000000000000000000000000000007f0601
  1825. 2025-08-10 22:04:23.559 SERIAL « [DISCARDED] invalid data 0xab (1 bytes)
  1826. 2025-08-10 22:04:23.559 DRIVER Dropping message because it contains invalid data
  1827. 2025-08-10 22:04:23.559 SERIAL » [NAK] (0x15)
  1828. 2025-08-10 22:04:23.561 SERIAL « 0x012a0000000000000000000000000000000000000000000000000000000000000 (44 bytes)
  1829. 00000000000000000000000
  1830. 2025-08-10 22:04:23.561 SERIAL « [DISCARDED] invalid data 0x000000000000 (6 bytes)
  1831. 2025-08-10 22:04:23.561 DRIVER Dropping message because it contains invalid data
  1832. 2025-08-10 22:04:23.561 SERIAL » [NAK] (0x15)
  1833. 2025-08-10 22:04:23.561 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1834. 2025-08-10 22:04:23.561 SERIAL « [DISCARDED] invalid data 0x00000000 (4 bytes)
  1835. 2025-08-10 22:04:23.561 SERIAL « [DISCARDED] invalid data 0x00000000 (4 bytes)
  1836. 2025-08-10 22:04:23.562 SERIAL « [DISCARDED] invalid data 0x0000 (2 bytes)
  1837. 2025-08-10 22:04:23.562 SERIAL « [DISCARDED] invalid data 0x0000 (2 bytes)
  1838. 2025-08-10 22:04:23.562 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1839. 2025-08-10 22:04:23.563 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1840. 2025-08-10 22:04:23.564 SERIAL « [DISCARDED] invalid data 0x00000000000000000000000000000000009316 (19 bytes)
  1841. 2025-08-10 22:04:23.564 SERIAL « 0x01020153 (4 bytes)
  1842. 2025-08-10 22:04:23.564 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1843. 2025-08-10 22:04:23.564 SERIAL « 0x010701539c01070153 (9 bytes)
  1844. 2025-08-10 22:04:23.564 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1845. 2025-08-10 22:04:23.564 DRIVER Dropping message because it contains invalid data
  1846. 2025-08-10 22:04:23.564 SERIAL » [NAK] (0x15)
  1847. 2025-08-10 22:04:23.565 DRIVER Dropping message because it contains invalid data
  1848. 2025-08-10 22:04:23.565 SERIAL » [NAK] (0x15)
  1849. 2025-08-10 22:04:23.567 SERIAL « 0x011801d39c010f010000000000539c010701539c010701539c01 (26 bytes)
  1850. 2025-08-10 22:04:23.567 SERIAL « [DISCARDED] invalid data 0x07 (1 bytes)
  1851. 2025-08-10 22:04:23.568 DRIVER Dropping message because it contains invalid data
  1852. 2025-08-10 22:04:23.568 SERIAL » [NAK] (0x15)
  1853. 2025-08-10 22:04:23.570 SERIAL « 0x01539c011801d39c011001d39c01210100000000000000000000539c01070153d (85 bytes)
  1854. c011005539c010701539c011401ab012a000000000000000000000000000000000000000000000
  1855. 000000000000000000000000000
  1856. 2025-08-10 22:04:23.571 DRIVER Dropping message because it contains invalid data
  1857. 2025-08-10 22:04:23.571 SERIAL » [NAK] (0x15)
  1858. 2025-08-10 22:04:23.571 SERIAL « [DISCARDED] invalid data 0x000000 (3 bytes)
  1859. 2025-08-10 22:04:23.572 SERIAL « [DISCARDED] invalid data 0x0000000000000000000000000000000000000000 (23 bytes)
  1860. 000000
  1861. 2025-08-10 22:04:23.572 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1862. 2025-08-10 22:04:23.572 SERIAL « [DISCARDED] invalid data 0x000000 (3 bytes)
  1863. 2025-08-10 22:04:23.572 SERIAL « [DISCARDED] invalid data 0x0000 (2 bytes)
  1864. 2025-08-10 22:04:23.572 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1865. 2025-08-10 22:04:23.573 SERIAL « [DISCARDED] invalid data 0x00000000 (4 bytes)
  1866. 2025-08-10 22:04:23.573 SERIAL « [DISCARDED] invalid data 0x000000 (3 bytes)
  1867. 2025-08-10 22:04:23.574 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1868. 2025-08-10 22:04:23.576 SERIAL « [DISCARDED] invalid data 0x0000009316 (5 bytes)
  1869. 2025-08-10 22:04:23.576 SERIAL « 0x01020153 (4 bytes)
  1870. 2025-08-10 22:04:23.576 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1871. 2025-08-10 22:04:23.576 SERIAL « 0x010701539c01070153 (9 bytes)
  1872. 2025-08-10 22:04:23.576 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1873. 2025-08-10 22:04:23.577 DRIVER Dropping message because it contains invalid data
  1874. 2025-08-10 22:04:23.577 SERIAL » [NAK] (0x15)
  1875. 2025-08-10 22:04:23.577 DRIVER Dropping message because it contains invalid data
  1876. 2025-08-10 22:04:23.577 SERIAL » [NAK] (0x15)
  1877. 2025-08-10 22:04:23.578 SERIAL « 0x011801d39c010f010000000000539c010701539c010701539c01 (26 bytes)
  1878. 2025-08-10 22:04:23.579 SERIAL « [DISCARDED] invalid data 0x07 (1 bytes)
  1879. 2025-08-10 22:04:23.579 DRIVER Dropping message because it contains invalid data
  1880. 2025-08-10 22:04:23.579 SERIAL » [NAK] (0x15)
  1881. 2025-08-10 22:04:23.589 SERIAL « 0x01539c011801d39c011001d39c01210100000000000000000000539c01070153d (85 bytes)
  1882. c011005539c010701539c011401ab012a000000000000000000000000000000000000000000000
  1883. 00016010201539c010701539c01
  1884. 2025-08-10 22:04:23.589 SERIAL « [DISCARDED] invalid data 0x07 (1 bytes)
  1885. 2025-08-10 22:04:23.590 DRIVER Dropping message because it contains invalid data
  1886. 2025-08-10 22:04:23.590 SERIAL » [NAK] (0x15)
  1887. 2025-08-10 22:04:25.148 DRIVER » [REQ] [ExtNVMReadLongBuffer]
  1888. offset: 0xa8
  1889. length: 168
  1890. 2025-08-10 22:04:25.148 SERIAL » 0x0108002a0000a800a8dd (10 bytes)
  1891. 2025-08-10 22:04:25.155 SERIAL « 0x01539c011801d39c010f010000000000539c010701539c010701539c010701539 (85 bytes)
  1892. c011801d39c011001d39c01210100000000000000000000539c01070153dc011005539c0107015
  1893. 39c01140601ab012a0000000000
  1894. 2025-08-10 22:04:25.156 DRIVER Dropping message because it contains invalid data
  1895. 2025-08-10 22:04:25.156 SERIAL » [NAK] (0x15)
  1896. 2025-08-10 22:04:25.156 SERIAL « [DISCARDED] invalid data 0x0000 (2 bytes)
  1897. 2025-08-10 22:04:25.157 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1898. 2025-08-10 22:04:25.157 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1899. 2025-08-10 22:04:25.158 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1900. 2025-08-10 22:04:25.159 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1901. 2025-08-10 22:04:25.160 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1902. 2025-08-10 22:04:25.162 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1903. 2025-08-10 22:04:25.163 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1904. 2025-08-10 22:04:25.164 SERIAL « [DISCARDED] invalid data 0x0000000000000000000000000000000000000000 (64 bytes)
  1905. 000000000000000000000000000000000000000000000000000000000000000000000000000000
  1906. 0000000000
  1907. 2025-08-10 22:04:25.164 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1908. 2025-08-10 22:04:25.164 SERIAL « [DISCARDED] invalid data 0x0000 (2 bytes)
  1909. 2025-08-10 22:04:25.164 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1910. 2025-08-10 22:04:25.165 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1911. 2025-08-10 22:04:25.165 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1912. 2025-08-10 22:04:25.165 SERIAL « [DISCARDED] invalid data 0x0000 (2 bytes)
  1913. 2025-08-10 22:04:25.165 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1914. 2025-08-10 22:04:25.165 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1915. 2025-08-10 22:04:25.166 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1916. 2025-08-10 22:04:25.167 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1917. 2025-08-10 22:04:25.168 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1918. 2025-08-10 22:04:25.170 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1919. 2025-08-10 22:04:25.171 SERIAL « [DISCARDED] invalid data 0x0000000000000000000000000000000000000000 (37 bytes)
  1920. 0000000000000000000000000000009316
  1921. 2025-08-10 22:04:25.171 SERIAL « 0x01020153 (4 bytes)
  1922. 2025-08-10 22:04:25.171 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1923. 2025-08-10 22:04:25.171 SERIAL « 0x010701539c01070153 (9 bytes)
  1924. 2025-08-10 22:04:25.171 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1925. 2025-08-10 22:04:25.171 DRIVER Dropping message because it contains invalid data
  1926. 2025-08-10 22:04:25.171 SERIAL » [NAK] (0x15)
  1927. 2025-08-10 22:04:25.172 DRIVER Dropping message because it contains invalid data
  1928. 2025-08-10 22:04:25.172 SERIAL » [NAK] (0x15)
  1929. 2025-08-10 22:04:25.177 SERIAL « 0x011801d39c010f0100000001ab012a0000000000000000000000 (26 bytes)
  1930. 2025-08-10 22:04:25.177 DRIVER Dropping message because it contains invalid data
  1931. 2025-08-10 22:04:25.178 SERIAL » [NAK] (0x15)
  1932. 2025-08-10 22:04:25.178 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1933. 2025-08-10 22:04:25.179 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1934. 2025-08-10 22:04:25.179 SERIAL « [DISCARDED] invalid data 0x0000000000000000000000000000000000000000 (66 bytes)
  1935. 000000000000000000000000000000000000000000000000000000000000000000000000000000
  1936. 00000000000000
  1937. 2025-08-10 22:04:25.179 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1938. 2025-08-10 22:04:25.180 SERIAL « [DISCARDED] invalid data 0x0053 (2 bytes)
  1939. 2025-08-10 22:04:25.180 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1940. 2025-08-10 22:04:25.181 SERIAL « 0x01070153dc01100553 (9 bytes)
  1941. 2025-08-10 22:04:25.181 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1942. 2025-08-10 22:04:25.181 SERIAL « 0x010701539c011401ab (9 bytes)
  1943. 2025-08-10 22:04:25.182 DRIVER Dropping message because it contains invalid data
  1944. 2025-08-10 22:04:25.182 SERIAL » [NAK] (0x15)
  1945. 2025-08-10 22:04:25.182 DRIVER Dropping message because it contains invalid data
  1946. 2025-08-10 22:04:25.182 SERIAL » [NAK] (0x15)
  1947. 2025-08-10 22:04:25.183 SERIAL « 0x012a0000000000000000000000000000000000000000000000000000000000000 (44 bytes)
  1948. 00000000000000000000000
  1949. 2025-08-10 22:04:25.184 DRIVER Dropping message because it contains invalid data
  1950. 2025-08-10 22:04:25.184 SERIAL » [NAK] (0x15)
  1951. 2025-08-10 22:04:25.184 SERIAL « [DISCARDED] invalid data 0x0000000000000000 (8 bytes)
  1952. 2025-08-10 22:04:25.184 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1953. 2025-08-10 22:04:25.184 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1954. 2025-08-10 22:04:25.184 SERIAL « [DISCARDED] invalid data 0x0000 (2 bytes)
  1955. 2025-08-10 22:04:25.185 SERIAL « [DISCARDED] invalid data 0x0000000000000000000000000000000000000000 (22 bytes)
  1956. 0000
  1957. 2025-08-10 22:04:25.186 SERIAL « [DISCARDED] invalid data 0x0000 (2 bytes)
  1958. 2025-08-10 22:04:25.186 SERIAL « [DISCARDED] invalid data 0x00 (1 bytes)
  1959. 2025-08-10 22:04:25.186 SERIAL « [DISCARDED] invalid data 0x0093 (2 bytes)
  1960. 2025-08-10 22:04:25.186 SERIAL « [DISCARDED] invalid data 0x16 (1 bytes)
  1961. 2025-08-10 22:04:25.186 SERIAL « 0x01020153 (4 bytes)
  1962. 2025-08-10 22:04:25.186 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1963. 2025-08-10 22:04:25.186 DRIVER Dropping message because it contains invalid data
  1964. 2025-08-10 22:04:25.186 SERIAL » [NAK] (0x15)
  1965. 2025-08-10 22:04:25.187 SERIAL « 0x010701539c01070153 (9 bytes)
  1966. 2025-08-10 22:04:25.188 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1967. 2025-08-10 22:04:25.188 DRIVER Dropping message because it contains invalid data
  1968. 2025-08-10 22:04:25.188 SERIAL » [NAK] (0x15)
  1969. 2025-08-10 22:04:25.188 SERIAL « 0x011801d39c010f010000000000539c010701539c010701539c01 (26 bytes)
  1970. 2025-08-10 22:04:25.188 DRIVER Dropping message because it contains invalid data
  1971. 2025-08-10 22:04:25.188 SERIAL » [NAK] (0x15)
  1972. 2025-08-10 22:04:25.189 SERIAL « [DISCARDED] invalid data 0x07 (1 bytes)
  1973. 2025-08-10 22:04:26.749 DRIVER » [REQ] [ExtNVMReadLongBuffer]
  1974. offset: 0xa8
  1975. length: 168
  1976. 2025-08-10 22:04:26.749 SERIAL » 0x0108002a0000a800a8dd (10 bytes)
  1977. 2025-08-10 22:04:26.760 SERIAL « 0x01539c011801d39c011001d39c01210100000000000000000000539c01070153d (85 bytes)
  1978. c011005539c010701539c01140601ab012a0000000000000000000000000000000000000000000
  1979. 000000000000000000000000000
  1980. 2025-08-10 22:04:26.760 SERIAL « [DISCARDED] invalid data 0x0000000000000000000000000000000000000000 (41 bytes)
  1981. 000000000000000000000000000000000000000000
  1982. 2025-08-10 22:04:26.761 DRIVER Dropping message because it contains invalid data
  1983. 2025-08-10 22:04:26.761 SERIAL » [NAK] (0x15)
  1984. 2025-08-10 22:04:26.762 SERIAL « [DISCARDED] invalid data 0x000000 (3 bytes)
  1985. 2025-08-10 22:04:26.762 SERIAL « [DISCARDED] invalid data 0x009316 (3 bytes)
  1986. 2025-08-10 22:04:26.765 SERIAL « 0x01020153 (4 bytes)
  1987. 2025-08-10 22:04:26.765 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1988. 2025-08-10 22:04:26.765 DRIVER Dropping message because it contains invalid data
  1989. 2025-08-10 22:04:26.765 SERIAL » [NAK] (0x15)
  1990. 2025-08-10 22:04:26.766 SERIAL « 0x010701539c01070153 (9 bytes)
  1991. 2025-08-10 22:04:26.767 SERIAL « [DISCARDED] invalid data 0x9c (1 bytes)
  1992. 2025-08-10 22:04:26.767 SERIAL « 0x011801d39c010f010000000000539c010701539c010701539c01 (26 bytes)
  1993. 2025-08-10 22:04:26.767 SERIAL « [DISCARDED] invalid data 0x07 (1 bytes)
  1994. 2025-08-10 22:04:26.767 DRIVER Dropping message because it contains invalid data
  1995. 2025-08-10 22:04:26.767 SERIAL » [NAK] (0x15)
  1996. 2025-08-10 22:04:26.767 DRIVER Dropping message because it contains invalid data
  1997. 2025-08-10 22:04:26.767 SERIAL » [NAK] (0x15)
  1998. 2025-08-10 22:04:26.775 SERIAL « 0x01539c011801d39c011001d39c012101000000000000000000000000000000000 (85 bytes)
  1999. 000000000000000000000000000000000000000000000000000000000000000000000000000000
  2000. 000000000009316010201539c01
  2001. 2025-08-10 22:04:26.775 SERIAL « [DISCARDED] invalid data 0x07 (1 bytes)
  2002. 2025-08-10 22:04:26.776 DRIVER Dropping message because it contains invalid data
  2003. 2025-08-10 22:04:26.776 SERIAL » [NAK] (0x15)
  2004. 2025-08-10 22:04:26.786 SERIAL « 0x01539c010701539c011801d39c010f01000000000000000000000000000000000 (85 bytes)
  2005. 00000000000000000000000009316010201539c010701539c010701539c011801d39c010f01000
  2006. 0000000539c010701539c010701
  2007. 2025-08-10 22:04:26.786 SERIAL « [DISCARDED] invalid data 0x539c (2 bytes)
  2008. 2025-08-10 22:04:26.786 SERIAL « 0x010701539c011801d3 (9 bytes)
  2009. 2025-08-10 22:04:26.786 SERIAL « [DISCARDED] invalid data 0x07 (1 bytes)
  2010. 2025-08-10 22:04:26.786 DRIVER Dropping message because it contains invalid data
  2011. 2025-08-10 22:04:26.786 SERIAL » [NAK] (0x15)
  2012. 2025-08-10 22:04:26.786 DRIVER Dropping message because it contains invalid data
  2013. 2025-08-10 22:04:26.786 SERIAL » [NAK] (0x15)
  2014. 2025-08-10 22:04:28.350 DRIVER Attempting to recover unresponsive controller by reopening the serial port...
  2015. 2025-08-10 22:04:28.352 DRIVER all queues idle
  2016. 2025-08-10 22:04:29.604 DRIVER Serial port reopened. Returning to normal operation and hoping for the best...
  2017. 2025-08-10 22:04:33.353 DRIVER one or more queues busy
  2018. 2025-08-10 22:04:33.353 DRIVER » [REQ] [GetBackgroundRSSI]
  2019. 2025-08-10 22:04:33.353 SERIAL » 0x0103003bc7 (5 bytes)
  2020. 2025-08-10 22:04:33.356 SERIAL « [ACK] (0x06)
  2021. 2025-08-10 22:04:33.356 SERIAL « 0x0105013baea4ca (7 bytes)
  2022. 2025-08-10 22:04:33.357 SERIAL » [ACK] (0x06)
  2023. 2025-08-10 22:04:33.357 DRIVER « [RES] [GetBackgroundRSSI]
  2024. channel 0: -82 dBm
  2025. channel 1: -92 dBm
  2026. 2025-08-10 22:04:33.357 DRIVER all queues idle
  2027. 2025-08-10 22:05:03.353 DRIVER one or more queues busy
  2028. 2025-08-10 22:05:03.353 DRIVER » [REQ] [GetBackgroundRSSI]
  2029. 2025-08-10 22:05:03.353 SERIAL » 0x0103003bc7 (5 bytes)
  2030. 2025-08-10 22:05:03.355 SERIAL « [ACK] (0x06)
  2031. 2025-08-10 22:05:03.359 SERIAL « 0x0105013baea4ca (7 bytes)
  2032. 2025-08-10 22:05:03.359 SERIAL » [ACK] (0x06)
  2033. 2025-08-10 22:05:03.359 DRIVER « [RES] [GetBackgroundRSSI]
  2034. channel 0: -82 dBm
  2035. channel 1: -92 dBm
  2036. 2025-08-10 22:05:03.360 DRIVER all queues idle
  2037. 2025-08-10 22:05:33.353 DRIVER one or more queues busy
  2038. 2025-08-10 22:05:33.353 DRIVER » [REQ] [GetBackgroundRSSI]
  2039. 2025-08-10 22:05:33.354 SERIAL » 0x0103003bc7 (5 bytes)
  2040. 2025-08-10 22:05:33.356 SERIAL « [ACK] (0x06)
  2041. 2025-08-10 22:05:33.358 SERIAL « 0x0105013baea4ca (7 bytes)
  2042. 2025-08-10 22:05:33.358 SERIAL » [ACK] (0x06)
  2043. 2025-08-10 22:05:33.358 DRIVER « [RES] [GetBackgroundRSSI]
  2044. channel 0: -82 dBm
  2045. channel 1: -92 dBm
  2046. 2025-08-10 22:05:33.359 DRIVER all queues idle

Edit this Snippet