Danke für die schnelle Antwort!
Ich hatte die anderen Modi schon getestet:

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