2023-08-08 19:17:44.800 - info: admin.0 (3185) ==> Connected system.user.admin from ::ffff:192.168.178.69
2023-08-08 19:17:44.876 - silly: wireless-mbus.0 (205502) States system redis pmessage io.messagebox.system.adapter.wireless-mbus.0/io.messagebox.system.adapter.wireless-mbus.0:{"command":"listUart","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":611,"ack":false,"time":1691515064874},"_id":93719370}
2023-08-08 19:17:44.893 - silly: wireless-mbus.0 (205502) States system redis pmessage io.messagebox.system.adapter.wireless-mbus.0/io.messagebox.system.adapter.wireless-mbus.0:{"command":"listReceiver","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":612,"ack":false,"time":1691515064876},"_id":93719371}
2023-08-08 19:17:44.895 - silly: wireless-mbus.0 (205502) sendTo "listReceiver" to system.adapter.admin.0 from system.adapter.wireless-mbus.0
2023-08-08 19:17:44.897 - silly: wireless-mbus.0 (205502) States system redis pmessage io.messagebox.system.adapter.wireless-mbus.0/io.messagebox.system.adapter.wireless-mbus.0:{"command":"needsKey","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":613,"ack":false,"time":1691515064884},"_id":93719372}
2023-08-08 19:17:44.898 - silly: wireless-mbus.0 (205502) sendTo "needsKey" to system.adapter.admin.0 from system.adapter.wireless-mbus.0
2023-08-08 19:17:45.092 - info: wireless-mbus.0 (205502) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"Silicon Labs","serialNumber":"027591BF","pnpId":"usb-Silicon_Labs_WiMOD_iM871A-usb_027591BF-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyAMA0"}]
2023-08-08 19:17:45.093 - silly: wireless-mbus.0 (205502) sendTo "listUart" to system.adapter.admin.0 from system.adapter.wireless-mbus.0
2023-08-08 19:17:52.603 - info: admin.0 (3185) <== Disconnect system.user.admin from ::ffff:192.168.178.69
2023-08-08 19:17:54.774 - info: host.iobroker stopInstance system.adapter.wireless-mbus.0 (force=false, process=true)
2023-08-08 19:17:54.784 - silly: wireless-mbus.0 (205502) States system redis pmessage system.adapter.wireless-mbus.0.sigKill/system.adapter.wireless-mbus.0.sigKill:{"val":-1,"ack":false,"ts":1691515074779,"q":0,"from":"system.host.iobroker","lc":1691515074779}
2023-08-08 19:17:54.787 - info: wireless-mbus.0 (205502) Got terminate signal TERMINATE_YOURSELF
2023-08-08 19:17:54.796 - info: wireless-mbus.0 (205502) terminating
2023-08-08 19:17:54.799 - info: wireless-mbus.0 (205502) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-08-08 19:17:54.837 - info: host.iobroker stopInstance system.adapter.wireless-mbus.0 send kill signal
2023-08-08 19:17:55.372 - info: host.iobroker instance system.adapter.wireless-mbus.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-08-08 19:17:57.915 - info: host.iobroker instance system.adapter.wireless-mbus.0 started with pid 205677
2023-08-08 19:17:59.372 - debug: wireless-mbus.0 (205677) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-08-08 19:17:59.425 - debug: wireless-mbus.0 (205677) Objects client ready ... initialize now
2023-08-08 19:17:59.427 - debug: wireless-mbus.0 (205677) Objects create System PubSub Client
2023-08-08 19:17:59.429 - debug: wireless-mbus.0 (205677) Objects create User PubSub Client
2023-08-08 19:17:59.500 - debug: wireless-mbus.0 (205677) Objects client initialize lua scripts
2023-08-08 19:17:59.508 - debug: wireless-mbus.0 (205677) Objects connected to redis: 127.0.0.1:9001
2023-08-08 19:17:59.512 - silly: wireless-mbus.0 (205677) redis psubscribe cfg.o.system.user.*
2023-08-08 19:17:59.538 - silly: wireless-mbus.0 (205677) redis psubscribe cfg.o.enum.*
2023-08-08 19:17:59.544 - silly: wireless-mbus.0 (205677) objectDB connected
2023-08-08 19:17:59.548 - debug: wireless-mbus.0 (205677) Redis States: Use Redis connection: 127.0.0.1:9000
2023-08-08 19:17:59.571 - debug: wireless-mbus.0 (205677) States create System PubSub Client
2023-08-08 19:17:59.572 - debug: wireless-mbus.0 (205677) States create User PubSub Client
2023-08-08 19:17:59.642 - debug: wireless-mbus.0 (205677) States connected to redis: 127.0.0.1:9000
2023-08-08 19:17:59.643 - silly: wireless-mbus.0 (205677) statesDB connected
2023-08-08 19:17:59.849 - info: wireless-mbus.0 (205677) starting. Version 0.9.1 in /opt/iobroker/node_modules/iobroker.wireless-mbus, node: v18.17.0, js-controller: 4.0.24
2023-08-08 19:17:59.904 - silly: wireless-mbus.0 (205677) States system redis pmessage system.adapter.wireless-mbus.0.logLevel/system.adapter.wireless-mbus.0.logLevel:{"val":"silly","ack":true,"ts":1691515079886,"q":0,"from":"system.adapter.wireless-mbus.0","lc":1691514881187}
2023-08-08 19:17:59.920 - debug: wireless-mbus.0 (205677) Created device of type: IMST iM871A
2023-08-08 19:17:59.932 - debug: wireless-mbus.0 (205677) IMST: TX: a5810306000300070800d9b5
2023-08-08 19:17:59.957 - debug: wireless-mbus.0 (205677) IMST: RX: a58104009cf7
2023-08-08 19:17:59.961 - info: wireless-mbus.0 (205677) IMST: Receiver set to CB-MODE
2023-08-08 19:17:59.967 - debug: wireless-mbus.0 (205677) connected set to true
2023-08-08 19:18:00.017 - debug: wireless-mbus.0 (205677) connected set to true
2023-08-08 19:18:13.921 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a300030a5c49e2cbc94c88e53eb446db4041af0fbea4433c051355672daf1b2af9cc6bb9461ec4867d813822095582d2b2e19897f0c79475738228726
2023-08-08 19:18:13.923 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a300030a5c49e2cbc94c88e53eb446db4041af0fbea4433c051355672daf1b2af9cc6bb9461ec4867d813822095582d2b2e19897f0c79475738228726
2023-08-08 19:18:13.927 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 19:18:13.929 - debug: wireless-mbus.0 (205677) 444497260501122300047a300030a5c49e2cbc94c88e53eb446db4041af0fbea4433c051355672daf1b2af9cc6bb9461ec4867d813822095582d2b2e19897f0c7947573822
2023-08-08 19:18:13.936 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: 55ed read: 3822
2023-08-08 19:18:13.937 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 19:23:13.464 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a310030a511efc080d923b5f2df02c1a47dc0c4409638d282dff0217cc67eddba8abb9d6b5d79405c6ee14642e98ff4e1bb5cd1d70c79475738224780
2023-08-08 19:23:13.467 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a310030a511efc080d923b5f2df02c1a47dc0c4409638d282dff0217cc67eddba8abb9d6b5d79405c6ee14642e98ff4e1bb5cd1d70c79475738224780
2023-08-08 19:23:13.469 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 19:23:13.470 - debug: wireless-mbus.0 (205677) 444497260501122300047a310030a511efc080d923b5f2df02c1a47dc0c4409638d282dff0217cc67eddba8abb9d6b5d79405c6ee14642e98ff4e1bb5cd1d70c7947573822
2023-08-08 19:23:13.471 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: dfb3 read: 3822
2023-08-08 19:23:13.471 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 19:28:14.036 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a320030a513d8bdd1a3c94a908d7ea1fc8f6df4784271243a07c7f90de8fe9af00013872c98a7a523bab8b2fe9e3fb6d36543c3180c7947573822a882
2023-08-08 19:28:14.038 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a320030a513d8bdd1a3c94a908d7ea1fc8f6df4784271243a07c7f90de8fe9af00013872c98a7a523bab8b2fe9e3fb6d36543c3180c7947573822a882
2023-08-08 19:28:14.039 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 19:28:14.040 - debug: wireless-mbus.0 (205677) 444497260501122300047a320030a513d8bdd1a3c94a908d7ea1fc8f6df4784271243a07c7f90de8fe9af00013872c98a7a523bab8b2fe9e3fb6d36543c3180c7947573822
2023-08-08 19:28:14.041 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: d7ee read: 3822
2023-08-08 19:28:14.043 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 19:33:13.659 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a330030a54b722f73d44537483b41d91aa1a3e8c795c74947a3745df28ff45d0b7ed780e4732cc3884c563be1fd09a1ee494947d40c7947573822a8cc
2023-08-08 19:33:13.660 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a330030a54b722f73d44537483b41d91aa1a3e8c795c74947a3745df28ff45d0b7ed780e4732cc3884c563be1fd09a1ee494947d40c7947573822a8cc
2023-08-08 19:33:13.661 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 19:33:13.664 - debug: wireless-mbus.0 (205677) 444497260501122300047a330030a54b722f73d44537483b41d91aa1a3e8c795c74947a3745df28ff45d0b7ed780e4732cc3884c563be1fd09a1ee494947d40c7947573822
2023-08-08 19:33:13.665 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: 28e4 read: 3822
2023-08-08 19:33:13.666 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 19:38:13.891 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a340030a5ab7c9d466b3a9f1ad0f53db8bcdf61693998f7144c6104748a25db2eb9cccf86ec5fefaec916c3fa5992d884dc38678a0c79475738226255
2023-08-08 19:38:13.894 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a340030a5ab7c9d466b3a9f1ad0f53db8bcdf61693998f7144c6104748a25db2eb9cccf86ec5fefaec916c3fa5992d884dc38678a0c79475738226255
2023-08-08 19:38:13.895 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 19:38:13.896 - debug: wireless-mbus.0 (205677) 444497260501122300047a340030a5ab7c9d466b3a9f1ad0f53db8bcdf61693998f7144c6104748a25db2eb9cccf86ec5fefaec916c3fa5992d884dc38678a0c7947573822
2023-08-08 19:38:13.897 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: c559 read: 3822
2023-08-08 19:38:13.897 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 19:43:14.264 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a350030a5a5dd477f6793aabdc8e961017828c0529aefbe4258103e93eed066fd0220d9caf3688f74c10bd570ec90c4cd43d0c07e0c7947573822195e
2023-08-08 19:43:14.265 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a350030a5a5dd477f6793aabdc8e961017828c0529aefbe4258103e93eed066fd0220d9caf3688f74c10bd570ec90c4cd43d0c07e0c7947573822195e
2023-08-08 19:43:14.266 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 19:43:14.267 - debug: wireless-mbus.0 (205677) 444497260501122300047a350030a5a5dd477f6793aabdc8e961017828c0529aefbe4258103e93eed066fd0220d9caf3688f74c10bd570ec90c4cd43d0c07e0c7947573822
2023-08-08 19:43:14.270 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: f5dc read: 3822
2023-08-08 19:43:14.271 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 19:48:13.727 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a360030a513d1ae332ad6e288c54397a5d60741fe9b88bce4dc40332473cad591736e770be0dc2a50edbd88063075dfc1f6afcd480c7947573822f3d9
2023-08-08 19:48:13.728 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a360030a513d1ae332ad6e288c54397a5d60741fe9b88bce4dc40332473cad591736e770be0dc2a50edbd88063075dfc1f6afcd480c7947573822f3d9
2023-08-08 19:48:13.729 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 19:48:13.730 - debug: wireless-mbus.0 (205677) 444497260501122300047a360030a513d1ae332ad6e288c54397a5d60741fe9b88bce4dc40332473cad591736e770be0dc2a50edbd88063075dfc1f6afcd480c7947573822
2023-08-08 19:48:13.731 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: bcb5 read: 3822
2023-08-08 19:48:13.732 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 19:53:13.660 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a370030a59df40458862c3043e258cfb033edf75934a0cdb4a0044cb5d73b18e3c38deebc4e78d7a1123825ce1e83e33ef62adc210c7947573822bd02
2023-08-08 19:53:13.661 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a370030a59df40458862c3043e258cfb033edf75934a0cdb4a0044cb5d73b18e3c38deebc4e78d7a1123825ce1e83e33ef62adc210c7947573822bd02
2023-08-08 19:53:13.662 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 19:53:13.663 - debug: wireless-mbus.0 (205677) 444497260501122300047a370030a59df40458862c3043e258cfb033edf75934a0cdb4a0044cb5d73b18e3c38deebc4e78d7a1123825ce1e83e33ef62adc210c7947573822
2023-08-08 19:53:13.664 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: 6862 read: 3822
2023-08-08 19:53:13.665 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 19:58:13.532 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a380030a5c7239b1df388f59297f0ffaa3b4569d2245996668f94c7624109ed0e73c818efa7caf45a06048ee8a80e7584b0837e940c7947573822bc20
2023-08-08 19:58:13.534 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a380030a5c7239b1df388f59297f0ffaa3b4569d2245996668f94c7624109ed0e73c818efa7caf45a06048ee8a80e7584b0837e940c7947573822bc20
2023-08-08 19:58:13.536 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 19:58:13.537 - debug: wireless-mbus.0 (205677) 444497260501122300047a380030a5c7239b1df388f59297f0ffaa3b4569d2245996668f94c7624109ed0e73c818efa7caf45a06048ee8a80e7584b0837e940c7947573822
2023-08-08 19:58:13.538 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: 9b99 read: 3822
2023-08-08 19:58:13.539 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 20:03:13.675 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a390030a5cb896299570ca0d0133f7dd63f865d9735f625135aebb48b0d8bd7c3c761fd939c75f834d9b9b6f8e399d6949cc4f0660c79475738222352
2023-08-08 20:03:13.676 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a390030a5cb896299570ca0d0133f7dd63f865d9735f625135aebb48b0d8bd7c3c761fd939c75f834d9b9b6f8e399d6949cc4f0660c79475738222352
2023-08-08 20:03:13.677 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 20:03:13.678 - debug: wireless-mbus.0 (205677) 444497260501122300047a390030a5cb896299570ca0d0133f7dd63f865d9735f625135aebb48b0d8bd7c3c761fd939c75f834d9b9b6f8e399d6949cc4f0660c7947573822
2023-08-08 20:03:13.679 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: 5c83 read: 3822
2023-08-08 20:03:13.680 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 20:05:46.857 - info: admin.0 (3185) <== Disconnect system.user.admin from ::ffff:192.168.178.69 admin
2023-08-08 20:08:14.227 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a3a0030a5dd01913a212d0db909537b94bbd0fee3b8558f66a4899b4f404a19f8a058d45c5d221443c1863f113d979b8b700d24490c7947573822ae65
2023-08-08 20:08:14.229 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a3a0030a5dd01913a212d0db909537b94bbd0fee3b8558f66a4899b4f404a19f8a058d45c5d221443c1863f113d979b8b700d24490c7947573822ae65
2023-08-08 20:08:14.230 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 20:08:14.230 - debug: wireless-mbus.0 (205677) 444497260501122300047a3a0030a5dd01913a212d0db909537b94bbd0fee3b8558f66a4899b4f404a19f8a058d45c5d221443c1863f113d979b8b700d24490c7947573822
2023-08-08 20:08:14.231 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: 2913 read: 3822
2023-08-08 20:08:14.232 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 20:13:13.700 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a3b0030a5ad5550f2dfd92552100da4dc313e956231eead92f2ce56ca5566728f4c22e7e013dd382cfecb520dd83ba24ee9a23f8c0c7947573822ebc8
2023-08-08 20:13:13.701 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a3b0030a5ad5550f2dfd92552100da4dc313e956231eead92f2ce56ca5566728f4c22e7e013dd382cfecb520dd83ba24ee9a23f8c0c7947573822ebc8
2023-08-08 20:13:13.704 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 20:13:13.705 - debug: wireless-mbus.0 (205677) 444497260501122300047a3b0030a5ad5550f2dfd92552100da4dc313e956231eead92f2ce56ca5566728f4c22e7e013dd382cfecb520dd83ba24ee9a23f8c0c7947573822
2023-08-08 20:13:13.706 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: f6a0 read: 3822
2023-08-08 20:13:13.706 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 20:17:11.461 - info: admin.0 (3185) ==> Connected system.user.admin from ::ffff:192.168.178.69
2023-08-08 20:17:26.462 - info: admin.0 (3185) <== Disconnect system.user.admin from ::ffff:192.168.178.69 admin
2023-08-08 20:18:14.281 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a3c0030a56c4a7d10189c6cdadb0bce99db2e0d4235083d44193e7771d40bc7fbd8975d1e7ac02cf370f777957b3bfe1e550f7fe90c79475738229a4b
2023-08-08 20:18:14.282 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a3c0030a56c4a7d10189c6cdadb0bce99db2e0d4235083d44193e7771d40bc7fbd8975d1e7ac02cf370f777957b3bfe1e550f7fe90c79475738229a4b
2023-08-08 20:18:14.283 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 20:18:14.284 - debug: wireless-mbus.0 (205677) 444497260501122300047a3c0030a56c4a7d10189c6cdadb0bce99db2e0d4235083d44193e7771d40bc7fbd8975d1e7ac02cf370f777957b3bfe1e550f7fe90c7947573822
2023-08-08 20:18:14.285 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: 941b read: 3822
2023-08-08 20:18:14.286 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 20:23:13.852 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a3d0030a5d0b8657295545f584e1841f8f31cf625d5a4783a224a19d462e1ddfb4cceb8125014954f4420b417fc208c74d1b438d80c794757382222f8
2023-08-08 20:23:13.853 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a3d0030a5d0b8657295545f584e1841f8f31cf625d5a4783a224a19d462e1ddfb4cceb8125014954f4420b417fc208c74d1b438d80c794757382222f8
2023-08-08 20:23:13.854 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 20:23:13.855 - debug: wireless-mbus.0 (205677) 444497260501122300047a3d0030a5d0b8657295545f584e1841f8f31cf625d5a4783a224a19d462e1ddfb4cceb8125014954f4420b417fc208c74d1b438d80c7947573822
2023-08-08 20:23:13.855 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: dc1 read: 3822
2023-08-08 20:23:13.856 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 20:28:14.213 - debug: wireless-mbus.0 (205677) IMST: RX: a58203444497260501122300047a3e0030a5b09ac619337c06e8bdc4369d6c2c9d8c02a9e6085d872e51afbae58a355ae6ecd6aa64784b5b37328241b5f2e78d7bf30c7947573822a490
2023-08-08 20:28:14.214 - debug: wireless-mbus.0 (205677) IMST: Message received: a58203444497260501122300047a3e0030a5b09ac619337c06e8bdc4369d6c2c9d8c02a9e6085d872e51afbae58a355ae6ecd6aa64784b5b37328241b5f2e78d7bf30c7947573822a490
2023-08-08 20:28:14.215 - debug: wireless-mbus.0 (205677) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 20:28:14.216 - debug: wireless-mbus.0 (205677) 444497260501122300047a3e0030a5b09ac619337c06e8bdc4369d6c2c9d8c02a9e6085d872e51afbae58a355ae6ecd6aa64784b5b37328241b5f2e78d7bf30c7947573822
2023-08-08 20:28:14.217 - error: wireless-mbus.0 (205677) CRC for frame type B block 1+2 failed! calc: 43e9 read: 3822
2023-08-08 20:28:14.217 - debug: wireless-mbus.0 (205677) Parser failed to parse telegram from device ITW-23120105
2023-08-08 20:31:14.149 - info: admin.0 (3185) ==> Connected system.user.admin from ::ffff:192.168.178.69
2023-08-08 20:31:40.131 - info: admin.0 (3185) ==> Connected system.user.admin from ::ffff:192.168.178.69
2023-08-08 20:31:40.192 - silly: wireless-mbus.0 (205677) States system redis pmessage io.messagebox.system.adapter.wireless-mbus.0/io.messagebox.system.adapter.wireless-mbus.0:{"command":"listUart","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":619,"ack":false,"time":1691519500190},"_id":93719378}
2023-08-08 20:31:40.216 - silly: wireless-mbus.0 (205677) States system redis pmessage io.messagebox.system.adapter.wireless-mbus.0/io.messagebox.system.adapter.wireless-mbus.0:{"command":"listReceiver","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":620,"ack":false,"time":1691519500195},"_id":93719379}
2023-08-08 20:31:40.219 - silly: wireless-mbus.0 (205677) sendTo "listReceiver" to system.adapter.admin.0 from system.adapter.wireless-mbus.0
2023-08-08 20:31:40.222 - silly: wireless-mbus.0 (205677) States system redis pmessage io.messagebox.system.adapter.wireless-mbus.0/io.messagebox.system.adapter.wireless-mbus.0:{"command":"needsKey","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":621,"ack":false,"time":1691519500199},"_id":93719380}
2023-08-08 20:31:40.223 - silly: wireless-mbus.0 (205677) sendTo "needsKey" to system.adapter.admin.0 from system.adapter.wireless-mbus.0
2023-08-08 20:31:40.440 - info: wireless-mbus.0 (205677) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"Silicon Labs","serialNumber":"027591BF","pnpId":"usb-Silicon_Labs_WiMOD_iM871A-usb_027591BF-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyAMA0"}]
2023-08-08 20:31:40.441 - silly: wireless-mbus.0 (205677) sendTo "listUart" to system.adapter.admin.0 from system.adapter.wireless-mbus.0
2023-08-08 20:31:56.638 - info: host.iobroker stopInstance system.adapter.wireless-mbus.0 (force=false, process=true)
2023-08-08 20:31:56.642 - silly: wireless-mbus.0 (205677) States system redis pmessage system.adapter.wireless-mbus.0.sigKill/system.adapter.wireless-mbus.0.sigKill:{"val":-1,"ack":false,"ts":1691519516640,"q":0,"from":"system.host.iobroker","lc":1691519516640}
2023-08-08 20:31:56.642 - info: wireless-mbus.0 (205677) Got terminate signal TERMINATE_YOURSELF
2023-08-08 20:31:56.646 - info: wireless-mbus.0 (205677) terminating
2023-08-08 20:31:56.647 - info: wireless-mbus.0 (205677) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-08-08 20:31:56.695 - info: host.iobroker stopInstance system.adapter.wireless-mbus.0 send kill signal
2023-08-08 20:31:56.932 - info: admin.0 (3185) <== Disconnect system.user.admin from ::ffff:192.168.178.69
2023-08-08 20:31:57.208 - info: host.iobroker instance system.adapter.wireless-mbus.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-08-08 20:31:59.801 - info: host.iobroker instance system.adapter.wireless-mbus.0 started with pid 208951
2023-08-08 20:32:01.266 - debug: wireless-mbus.0 (208951) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-08-08 20:32:01.317 - debug: wireless-mbus.0 (208951) Objects client ready ... initialize now
2023-08-08 20:32:01.320 - debug: wireless-mbus.0 (208951) Objects create System PubSub Client
2023-08-08 20:32:01.322 - debug: wireless-mbus.0 (208951) Objects create User PubSub Client
2023-08-08 20:32:01.389 - debug: wireless-mbus.0 (208951) Objects client initialize lua scripts
2023-08-08 20:32:01.398 - debug: wireless-mbus.0 (208951) Objects connected to redis: 127.0.0.1:9001
2023-08-08 20:32:01.401 - silly: wireless-mbus.0 (208951) redis psubscribe cfg.o.system.user.*
2023-08-08 20:32:01.429 - silly: wireless-mbus.0 (208951) redis psubscribe cfg.o.enum.*
2023-08-08 20:32:01.436 - silly: wireless-mbus.0 (208951) objectDB connected
2023-08-08 20:32:01.439 - debug: wireless-mbus.0 (208951) Redis States: Use Redis connection: 127.0.0.1:9000
2023-08-08 20:32:01.458 - debug: wireless-mbus.0 (208951) States create System PubSub Client
2023-08-08 20:32:01.459 - debug: wireless-mbus.0 (208951) States create User PubSub Client
2023-08-08 20:32:01.534 - debug: wireless-mbus.0 (208951) States connected to redis: 127.0.0.1:9000
2023-08-08 20:32:01.536 - silly: wireless-mbus.0 (208951) statesDB connected
2023-08-08 20:32:01.737 - info: wireless-mbus.0 (208951) starting. Version 0.9.1 in /opt/iobroker/node_modules/iobroker.wireless-mbus, node: v18.17.0, js-controller: 4.0.24
2023-08-08 20:32:01.791 - silly: wireless-mbus.0 (208951) States system redis pmessage system.adapter.wireless-mbus.0.logLevel/system.adapter.wireless-mbus.0.logLevel:{"val":"silly","ack":true,"ts":1691519521774,"q":0,"from":"system.adapter.wireless-mbus.0","lc":1691514881187}
2023-08-08 20:32:01.806 - debug: wireless-mbus.0 (208951) Created device of type: IMST iM871A
2023-08-08 20:32:01.813 - debug: wireless-mbus.0 (208951) IMST: TX: a581030600030006080005ef
2023-08-08 20:32:01.831 - debug: wireless-mbus.0 (208951) IMST: RX: a58104009cf7
2023-08-08 20:32:01.833 - info: wireless-mbus.0 (208951) IMST: Receiver set to CA-MODE
2023-08-08 20:32:01.835 - debug: wireless-mbus.0 (208951) connected set to true
2023-08-08 20:32:01.883 - debug: wireless-mbus.0 (208951) connected set to true
2023-08-08 20:33:13.565 - debug: wireless-mbus.0 (208951) IMST: RX: a58203444497260501122300047a3f0030a537853289978ff4e2b2d6196f4ea2e0d103a588062c9544042ecc2d4ce43a2a3af3ca7afa97dbfe46d8a84102aa3e7d710c7947573822c7c5
2023-08-08 20:33:13.570 - debug: wireless-mbus.0 (208951) IMST: Message received: a58203444497260501122300047a3f0030a537853289978ff4e2b2d6196f4ea2e0d103a588062c9544042ecc2d4ce43a2a3af3ca7afa97dbfe46d8a84102aa3e7d710c7947573822c7c5
2023-08-08 20:33:13.575 - debug: wireless-mbus.0 (208951) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 20:33:13.577 - debug: wireless-mbus.0 (208951) 444497260501122300047a3f0030a537853289978ff4e2b2d6196f4ea2e0d103a588062c9544042ecc2d4ce43a2a3af3ca7afa97dbfe46d8a84102aa3e7d710c7947573822
2023-08-08 20:33:13.586 - debug: wireless-mbus.0 (208951) Short header
2023-08-08 20:33:13.588 - debug: wireless-mbus.0 (208951) encrypted payload: 37853289978ff4e2b2d6196f4ea2e0d103a588062c9544042ecc2d4ce43a2a3af3ca7afa97dbfe46d8a84102aa3e7d71
2023-08-08 20:33:13.591 - debug: wireless-mbus.0 (208951) IV: 97260501122300043f3f3f3f3f3f3f3f
2023-08-08 20:33:13.595 - debug: wireless-mbus.0 (208951) decrypted payload 42cc324a5f12a9e8eca970f9a5f5db4d779830247412f0ef996298715494ada79e5b152035af644427b7535e69bf1d6c0c7947573822
2023-08-08 20:33:13.596 - error: wireless-mbus.0 (208951) 42cc324a5f12a9e8eca970f9a5f5db4d779830247412f0ef996298715494ada79e5b152035af644427b7535e69bf1d6c0c7947573822
2023-08-08 20:33:13.598 - debug: wireless-mbus.0 (208951) Parser failed to parse telegram from device ITW-23120105
2023-08-08 20:38:14.217 - debug: wireless-mbus.0 (208951) IMST: RX: a58203444497260501122300047a400030a5fb11f2459dfbfb801e283350e1a6c0e948548dce97f9f7a819466c4ada112b69693b11e571ed0b32b8ae957acfc6de190c79475738221c20
2023-08-08 20:38:14.218 - debug: wireless-mbus.0 (208951) IMST: Message received: a58203444497260501122300047a400030a5fb11f2459dfbfb801e283350e1a6c0e948548dce97f9f7a819466c4ada112b69693b11e571ed0b32b8ae957acfc6de190c79475738221c20
2023-08-08 20:38:14.220 - debug: wireless-mbus.0 (208951) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 20:38:14.221 - debug: wireless-mbus.0 (208951) 444497260501122300047a400030a5fb11f2459dfbfb801e283350e1a6c0e948548dce97f9f7a819466c4ada112b69693b11e571ed0b32b8ae957acfc6de190c7947573822
2023-08-08 20:38:14.222 - debug: wireless-mbus.0 (208951) Short header
2023-08-08 20:38:14.224 - debug: wireless-mbus.0 (208951) encrypted payload: fb11f2459dfbfb801e283350e1a6c0e948548dce97f9f7a819466c4ada112b69693b11e571ed0b32b8ae957acfc6de19
2023-08-08 20:38:14.225 - debug: wireless-mbus.0 (208951) IV: 97260501122300044040404040404040
2023-08-08 20:38:14.226 - debug: wireless-mbus.0 (208951) decrypted payload 22239901a3d82c15d46f0bfbc8171cdb4dbc2229f6e1dd13e5ce78537f1ef5752503f0248b7059e4d9bc7e41ccbf2a6f0c7947573822
2023-08-08 20:38:14.227 - error: wireless-mbus.0 (208951) 22239901a3d82c15d46f0bfbc8171cdb4dbc2229f6e1dd13e5ce78537f1ef5752503f0248b7059e4d9bc7e41ccbf2a6f0c7947573822
2023-08-08 20:38:14.228 - debug: wireless-mbus.0 (208951) Parser failed to parse telegram from device ITW-23120105
2023-08-08 20:43:13.958 - debug: wireless-mbus.0 (208951) IMST: RX: a58203444497260501122300047a410030a508a3acceeaef398bdde682bead4e3b584c8699da760a45d300ad46cbd35f5ef8e5b7c227937ecacdb659b16c9878bc510c794757382285e6
2023-08-08 20:43:13.959 - debug: wireless-mbus.0 (208951) IMST: Message received: a58203444497260501122300047a410030a508a3acceeaef398bdde682bead4e3b584c8699da760a45d300ad46cbd35f5ef8e5b7c227937ecacdb659b16c9878bc510c794757382285e6
2023-08-08 20:43:13.960 - debug: wireless-mbus.0 (208951) Found AES key: C5C0367B51FB2755C7A7925B5DE2D4E8
2023-08-08 20:43:13.960 - debug: wireless-mbus.0 (208951) 444497260501122300047a410030a508a3acceeaef398bdde682bead4e3b584c8699da760a45d300ad46cbd35f5ef8e5b7c227937ecacdb659b16c9878bc510c7947573822
2023-08-08 20:43:13.961 - debug: wireless-mbus.0 (208951) Short header
2023-08-08 20:43:13.961 - debug: wireless-mbus.0 (208951) encrypted payload: 08a3acceeaef398bdde682bead4e3b584c8699da760a45d300ad46cbd35f5ef8e5b7c227937ecacdb659b16c9878bc51
2023-08-08 20:43:13.961 - debug: wireless-mbus.0 (208951) IV: 97260501122300044141414141414141
2023-08-08 20:43:13.962 - debug: wireless-mbus.0 (208951) decrypted payload a8737a17371ccaf40930e0610ae2e10276396abbe2b8e8b222962d5894ebc5b2a1c3e6101a1d96c587158eeed2b8dea30c7947573822
2023-08-08 20:43:13.962 - error: wireless-mbus.0 (208951) a8737a17371ccaf40930e0610ae2e10276396abbe2b8e8b222962d5894ebc5b2a1c3e6101a1d96c587158eeed2b8dea30c7947573822
2023-08-08 20:43:13.962 - debug: wireless-mbus.0 (208951) Parser failed to parse telegram from device ITW-23120105