[Aufruf] Adapter: M-Bus
-
Ich meine den Gerätescan im konfig Fenster. Findet der den 10er? Müsste dann aber eine andere ID Listen. `
Ich habe immer genau diesen Gerätescan verwendet.
Die vier Wäremkostenzähler mit der Adresse 1 - 4 werden vom M-Bus Adapter über den Gerätescan in der Konfiguration gefunden, der Zwischenzähler mit der Adresse 10 jedoch nicht. Zum Ausprobieren habe ich deshalb den mbus1 angelegt.
Und so sieht der Log für mbus1 aus:
! ` > host.iobroker-1 2018-06-29 04:39:01.148 info instance system.adapter.mbus.1 terminated with code 0 (OK)
Caught 2018-06-29 04:39:01.148 error by controller[107]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.148 error by controller[106]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.148 error by controller[105]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.148 error by controller[104]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.148 error by controller[103]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.148 error by controller[102]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.148 error by controller[101]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.148 error by controller[100]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.147 error by controller[99]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.147 error by controller[98]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.147 error by controller[97]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.147 error by controller[96]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.147 error by controller[95]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.147 error by controller[94]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.146 error by controller[93]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.146 error by controller[92]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.146 error by controller[91]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.146 error by controller[90]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.145 error by controller[89]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.145 error by controller[88]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.145 error by controller[87]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.145 error by controller[86]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.141 error by controller[85]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.141 error by controller[84]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.141 error by controller[83]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.141 error by controller[82]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.141 error by controller[81]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.140 error by controller[80]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.140 error by controller[79]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.140 error by controller[78]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.140 error by controller[77]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.140 error by controller[76]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.140 error by controller[75]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.140 error by controller[74]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.140 error by controller[73]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.139 error by controller[72]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.139 error by controller[71]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.139 error by controller[70]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.139 error by controller[69]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.139 error by controller[68]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.139 error by controller[67]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.139 error by controller[66]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.139 error by controller[65]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.138 error by controller[64]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.138 error by controller[63]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.137 error by controller[62]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.137 error by controller[61]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.137 error by controller[60]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.137 error by controller[59]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.137 error by controller[58]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.137 error by controller[57]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.137 error by controller[56]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.136 error by controller[55]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.136 error by controller[54]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.136 error by controller[53]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.136 error by controller[52]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.136 error by controller[51]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.136 error by controller[50]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.136 error by controller[49]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.136 error by controller[48]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.136 error by controller[47]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.135 error by controller[46]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.135 error by controller[45]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.135 error by controller[44]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.135 error by controller[43]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.135 error by controller[42]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.135 error by controller[41]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.134 error by controller[40]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.133 error by controller[39]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.133 error by controller[38]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.133 error by controller[37]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.133 error by controller[36]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.133 error by controller[35]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.133 error by controller[34]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.133 error by controller[33]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.132 error by controller[32]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.132 error by controller[31]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.132 error by controller[30]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.132 error by controller[29]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.132 error by controller[28]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.132 error by controller[27]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.132 error by controller[26]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.132 error by controller[25]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.131 error by controller[24]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.131 error by controller[23]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.131 error by controller[22]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.131 error by controller[21]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.131 error by controller[20]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.131 error by controller[19]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.131 error by controller[19]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.131 error by controller[19]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.131 error by controller[18]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.130 error by controller[17]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.130 error by controller[16]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.130 error by controller[15]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.130 error by controller[14]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.130 error by controller[13]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 04:39:01.130 error by controller[12]: mbus_send_ping_frame: failed to send mbus frame.
mbus.1 2018-06-29 04:39:00.966 info terminating
host.iobroker-1 2018-06-29 04:39:00.458 info stopInstance system.adapter.mbus.1 killing pid 225
host.iobroker-1 2018-06-29 04:39:00.458 info stopInstance system.adapter.mbus.1
host.iobroker-1 2018-06-29 04:39:00.458 info object change system.adapter.mbus.1
mbus.1 2018-06-29 04:38:57.666 info Process: 10
mbus.1 2018-06-29 04:38:57.666 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:57.664 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:57.664 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:57.664 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:57.663 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:57.661 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:57.651 info Process: 10
mbus.1 2018-06-29 04:38:57.651 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:57.647 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:57.647 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:57.646 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:57.646 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:57.646 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:57.635 info Process: 10
mbus.1 2018-06-29 04:38:57.635 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:57.633 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:57.630 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:57.630 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:57.630 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:57.629 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:57.620 info Process: 10
mbus.1 2018-06-29 04:38:57.620 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:57.619 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:57.613 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:57.613 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:57.613 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:57.613 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:57.601 info Process: 10
mbus.1 2018-06-29 04:38:57.601 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:57.600 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:57.599 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:57.599 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:57.599 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:57.599 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:57.585 info Process: 10
mbus.1 2018-06-29 04:38:57.585 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:57.582 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:57.582 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:57.581 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:57.581 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:57.580 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:57.572 info Process: 10
mbus.1 2018-06-29 04:38:57.572 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:57.571 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:57.570 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:57.570 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:57.570 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:57.570 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:57.559 info Process: 10
mbus.1 2018-06-29 04:38:57.559 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:57.557 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:57.557 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:57.557 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:57.557 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:57.556 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:57.546 info Process: 10
mbus.1 2018-06-29 04:38:57.546 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:57.542 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:57.542 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:57.541 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:57.541 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:57.541 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:57.534 info Process: 10
mbus.1 2018-06-29 04:38:57.533 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:57.531 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:57.531 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:57.530 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:57.530 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:57.530 error M-Bus ID 10 err: Error: Error: Failed to receive M-Bus response frame[10].
mbus.1 2018-06-29 04:38:54.075 info Process: 10
mbus.1 2018-06-29 04:38:54.075 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:54.074 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:54.073 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:54.073 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:54.073 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:54.072 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:54.063 info Process: 10
mbus.1 2018-06-29 04:38:54.063 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:54.061 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:54.061 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:54.061 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:54.061 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:54.061 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:54.050 info Process: 10
mbus.1 2018-06-29 04:38:54.050 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:54.046 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:54.046 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:54.046 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:54.046 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:54.045 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:54.038 info Process: 10
mbus.1 2018-06-29 04:38:54.038 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:54.036 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:54.035 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:54.035 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:54.035 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:54.034 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:54.020 info Process: 10
mbus.1 2018-06-29 04:38:54.020 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:54.014 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:54.014 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:54.014 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:54.014 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:54.013 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:54.007 info Process: 10
mbus.1 2018-06-29 04:38:54.007 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:54.000 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:54.000 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:54.000 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:54.000 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:54.000 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:53.995 info Process: 10
mbus.1 2018-06-29 04:38:53.995 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:53.992 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:53.991 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:53.991 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:53.991 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:53.991 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:53.983 info Process: 10
mbus.1 2018-06-29 04:38:53.982 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:53.981 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:53.980 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:53.980 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:53.980 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:53.980 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:53.969 info Process: 10
mbus.1 2018-06-29 04:38:53.969 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:53.965 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:53.965 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:53.964 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:53.964 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:53.964 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:53.956 info Process: 10
mbus.1 2018-06-29 04:38:53.956 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:53.952 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:53.951 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:53.951 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:53.951 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:53.951 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:53.944 info Process: 10
mbus.1 2018-06-29 04:38:53.943 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:53.941 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:53.940 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:53.940 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:53.940 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:53.940 error M-Bus ID 10 err: Error: Error: Failed to receive M-Bus response frame[10].
mbus.1 2018-06-29 04:38:50.452 info Process: 10
mbus.1 2018-06-29 04:38:50.452 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:50.449 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:50.449 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:50.449 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:50.449 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:50.448 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:50.434 info Process: 10
mbus.1 2018-06-29 04:38:50.434 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:50.428 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:50.428 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:50.427 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:50.427 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:50.426 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:50.422 info Process: 10
mbus.1 2018-06-29 04:38:50.422 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:50.416 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:50.415 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:50.415 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:50.415 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:50.415 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:50.411 info Process: 10
mbus.1 2018-06-29 04:38:50.410 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:50.408 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:50.408 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:50.407 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:50.407 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:50.407 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:50.396 info Process: 10
mbus.1 2018-06-29 04:38:50.396 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:50.387 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:50.387 info Default Update Interval: 0
mbus.1 2018-06-29 04:38:50.386 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 04:38:50.386 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 04:38:50.386 error M-Bus ID 10 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 04:38:50.383 info Process: 10
mbus.1 2018-06-29 04:38:50.383 info Schedule initialization for M-Bus-ID 10 with update interval 0
mbus.1 2018-06-29 04:38:50.381 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 1000
mbus.1 2018-06-29 04:38:50.381 info Default Update Interval: 0 `
Ich habe dem Wechselstromzwischenzähler nun die Adresse 5 gegeben. Mit der M-Bus Auslesesoftware der Fa, Relay funktioniert das Auslesen, mit dem M-Busadapter nicht.
! ````
mbus.0 2018-06-29 05:11:49.276 info Process: 1
mbus.0 2018-06-29 05:11:21.026 info Process: 4
mbus.0 2018-06-29 05:10:59.417 info Process: 3
mbus.0 2018-06-29 05:10:37.734 info Process: 2
mbus.0 2018-06-29 05:10:16.105 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:16.105 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:16.105 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:16.105 info Process: 1
mbus.0 2018-06-29 05:10:16.105 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:16.105 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:16.104 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:16.104 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:16.104 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:16.104 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:10:15.091 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:15.091 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:15.091 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:15.091 info Process: 1
mbus.0 2018-06-29 05:10:15.091 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:15.091 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:15.091 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:15.091 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:15.091 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:15.091 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:10:15.091 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:15.091 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:15.090 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:15.090 info Process: 1
mbus.0 2018-06-29 05:10:15.090 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:15.090 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:15.090 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:15.090 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:15.088 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:15.088 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:10:15.055 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:15.055 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:15.055 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:15.055 info Process: 1
mbus.0 2018-06-29 05:10:15.055 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:15.055 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:15.055 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:15.055 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:15.055 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:15.055 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:10:15.039 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:15.039 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:15.039 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:15.039 info Process: 1
mbus.0 2018-06-29 05:10:15.038 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:15.038 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:15.038 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:15.038 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:15.038 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:15.038 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:10:15.027 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:15.027 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:15.027 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:15.026 info Process: 1
mbus.0 2018-06-29 05:10:15.026 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:15.026 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:15.026 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:15.026 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:15.026 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:15.026 error M-Bus ID 1 err: Error: Error: Failed to send M-Bus request frame[1].
host.iobroker-1 2018-06-29 05:10:09.486 info instance system.adapter.mbus.1 terminated with code 0 (OK)
Caught 2018-06-29 05:10:09.486 error by controller[52]: mbus_send_request_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.486 error by controller[51]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.486 error by controller[51]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.486 error by controller[50]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.486 error by controller[49]: mbus_send_request_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.486 error by controller[48]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.485 error by controller[47]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.485 error by controller[46]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.485 error by controller[45]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.485 error by controller[44]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.485 error by controller[43]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.485 error by controller[42]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.483 error by controller[41]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.483 error by controller[40]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.483 error by controller[39]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.483 error by controller[38]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.483 error by controller[37]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.483 error by controller[36]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.482 error by controller[35]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.482 error by controller[34]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.482 error by controller[33]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.482 error by controller[32]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.482 error by controller[31]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.482 error by controller[30]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.482 error by controller[29]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.482 error by controller[28]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.481 error by controller[27]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.481 error by controller[26]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.481 error by controller[25]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.481 error by controller[24]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.481 error by controller[23]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.481 error by controller[22]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.481 error by controller[21]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.481 error by controller[20]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.480 error by controller[19]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.480 error by controller[18]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.480 error by controller[17]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.480 error by controller[16]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.480 error by controller[15]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.480 error by controller[14]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.480 error by controller[13]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.480 error by controller[12]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.479 error by controller[11]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.479 error by controller[10]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.479 error by controller[9]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.479 error by controller[8]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.479 error by controller[8]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.479 error by controller[7]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.479 error by controller[6]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.479 error by controller[6]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.478 error by controller[6]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.478 error by controller[5]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.478 error by controller[4]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.478 error by controller[3]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.478 error by controller[2]: mbus_send_ping_frame: failed to send mbus frame.
Caught 2018-06-29 05:10:09.478 error by controller[1]: mbus_send_request_frame: failed to send mbus frame.
mbus.0 2018-06-29 05:10:04.943 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:04.943 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:04.942 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:03.939 info Process: 1
mbus.0 2018-06-29 05:10:03.939 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:03.935 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:03.935 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:03.935 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:03.934 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:03.933 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:10:03.931 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:03.930 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:03.930 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:03.926 info Process: 1
mbus.0 2018-06-29 05:10:03.926 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:03.924 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:03.924 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:03.924 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:03.923 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:03.921 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:10:03.913 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:03.913 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:03.913 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:03.910 info Process: 1
mbus.0 2018-06-29 05:10:03.910 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:03.908 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:03.908 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:03.907 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:03.907 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:03.907 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:10:03.898 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:03.898 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:03.898 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:03.893 info Process: 1
mbus.0 2018-06-29 05:10:03.893 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:03.889 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:03.889 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:03.888 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:03.888 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:03.888 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:10:03.883 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:10:03.883 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:10:03.883 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:10:03.880 info Process: 1
mbus.0 2018-06-29 05:10:03.880 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:10:03.878 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:10:03.878 info Default Update Interval: 0
mbus.0 2018-06-29 05:10:03.878 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:10:03.878 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:10:03.877 error M-Bus ID 1 err: Error: Error: Failed to send M-Bus request frame[1].
mbus.1 2018-06-29 05:10:03.305 info terminating
host.iobroker-1 2018-06-29 05:10:02.799 info stopInstance system.adapter.mbus.1 killing pid 169
host.iobroker-1 2018-06-29 05:10:02.799 info stopInstance system.adapter.mbus.1
host.iobroker-1 2018-06-29 05:10:02.799 info object change system.adapter.mbus.1
mbus.1 2018-06-29 05:09:58.393 info Process: 5
mbus.1 2018-06-29 05:09:58.393 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:58.388 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:58.388 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:58.388 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:58.387 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:58.387 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:58.381 info Process: 5
mbus.1 2018-06-29 05:09:58.381 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:58.379 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:58.379 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:58.378 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:58.378 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:58.378 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:58.368 info Process: 5
mbus.1 2018-06-29 05:09:58.368 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:58.364 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:58.364 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:58.363 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:58.363 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:58.363 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:58.355 info Process: 5
mbus.1 2018-06-29 05:09:58.355 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:58.353 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:58.353 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:58.353 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:58.352 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:58.352 error M-Bus ID 5 err: Error: Error: Failed to send M-Bus request frame[5].
mbus.0 2018-06-29 05:09:53.807 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:09:53.807 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:09:53.807 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:09:52.804 info Process: 1
mbus.0 2018-06-29 05:09:52.803 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:09:52.799 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:09:52.799 info Default Update Interval: 0
mbus.0 2018-06-29 05:09:52.799 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:09:52.799 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:09:52.798 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:09:52.795 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:09:52.795 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:09:52.795 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:09:52.790 info Process: 1
mbus.0 2018-06-29 05:09:52.790 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:09:52.789 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:09:52.789 info Default Update Interval: 0
mbus.0 2018-06-29 05:09:52.789 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:09:52.788 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:09:52.788 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:09:52.783 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:09:52.782 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:09:52.782 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:09:52.779 info Process: 1
mbus.0 2018-06-29 05:09:52.779 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:09:52.776 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:09:52.775 info Default Update Interval: 0
mbus.0 2018-06-29 05:09:52.775 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:09:52.774 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:09:52.773 error M-Bus ID 1 err: Error: Error: Failed to init slaves.
mbus.0 2018-06-29 05:09:52.768 info Schedule initialization for M-Bus-ID 4 with update interval 0
mbus.0 2018-06-29 05:09:52.768 info Schedule initialization for M-Bus-ID 3 with update interval 0
mbus.0 2018-06-29 05:09:52.768 info Schedule initialization for M-Bus-ID 2 with update interval 0
mbus.0 2018-06-29 05:09:52.765 info Process: 1
mbus.0 2018-06-29 05:09:52.765 info Schedule initialization for M-Bus-ID 1 with update interval 0
mbus.0 2018-06-29 05:09:52.763 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.0 2018-06-29 05:09:52.763 info Default Update Interval: 0
mbus.0 2018-06-29 05:09:52.763 error All M-Bus devices could not be read, reinitialize and start over
mbus.0 2018-06-29 05:09:52.762 error M-Bus Devices errored: 4 from 4
mbus.0 2018-06-29 05:09:52.762 error M-Bus ID 1 err: Error: Error: Failed to send M-Bus request frame[1].
mbus.1 2018-06-29 05:09:47.283 info Process: 5
mbus.1 2018-06-29 05:09:47.283 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.282 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.281 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.281 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.281 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.281 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.267 info Process: 5
mbus.1 2018-06-29 05:09:47.267 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.259 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.259 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.259 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.259 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.258 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.254 info Process: 5
mbus.1 2018-06-29 05:09:47.254 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.248 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.248 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.247 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.247 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.247 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.242 info Process: 5
mbus.1 2018-06-29 05:09:47.242 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.239 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.239 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.238 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.238 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.238 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.229 info Process: 5
mbus.1 2018-06-29 05:09:47.229 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.228 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.228 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.227 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.227 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.227 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.215 info Process: 5
mbus.1 2018-06-29 05:09:47.215 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.214 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.213 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.209 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.209 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.207 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.197 info Process: 5
mbus.1 2018-06-29 05:09:47.196 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.194 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.194 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.191 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.191 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.191 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.183 info Process: 5
mbus.1 2018-06-29 05:09:47.183 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.180 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.179 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.179 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.179 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.178 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.168 info Process: 5
mbus.1 2018-06-29 05:09:47.168 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.165 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.165 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.165 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.164 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.164 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.154 info Process: 5
mbus.1 2018-06-29 05:09:47.154 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.152 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.151 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.149 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.149 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.149 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.143 info Process: 5
mbus.1 2018-06-29 05:09:47.143 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.140 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.140 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.140 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.140 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.139 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.122 info Process: 5
mbus.1 2018-06-29 05:09:47.122 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.121 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.121 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.120 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.120 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.120 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.109 info Process: 5
mbus.1 2018-06-29 05:09:47.109 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.103 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.103 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.103 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.103 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.102 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.097 info Process: 5
mbus.1 2018-06-29 05:09:47.096 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.095 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.095 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.095 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.094 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.094 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.084 info Process: 5
mbus.1 2018-06-29 05:09:47.083 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.081 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.080 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.080 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.080 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.080 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.038 info Process: 5
mbus.1 2018-06-29 05:09:47.037 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.033 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.033 info Default Update Interval: 0
mbus.1 2018-06-29 05:09:47.033 error All M-Bus devices could not be read, reinitialize and start over
mbus.1 2018-06-29 05:09:47.033 error M-Bus Devices errored: 1 from 1
mbus.1 2018-06-29 05:09:47.032 error M-Bus ID 5 err: Error: Error: Failed to init slaves.
mbus.1 2018-06-29 05:09:47.025 info Process: 5
mbus.1 2018-06-29 05:09:47.025 info Schedule initialization for M-Bus-ID 5 with update interval 0
mbus.1 2018-06-29 05:09:47.023 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout 10000
mbus.1 2018-06-29 05:09:47.023 info Default Update Interval: 0Und hier das Scanergebnis mit einem Raspi wo libmbus von rSCADA installiert ist:  Und hier das Ausleseergebnis: >! ```` pi@raspberrypi:~/libmbus-0.8.0 $ mbus-tcp-request-data 192.168.xxx.xx 1001 5 <mbusdata><slaveinformation><id>100993</id> <manufacturer>SBC</manufacturer> <version>36</version> <productname></productname> <medium>Electricity</medium> <accessnumber>145</accessnumber> <status>00</status> <signature>0000</signature></slaveinformation> >! <datarecord id="0"><function>Instantaneous value</function> <unit>Energy (10 Wh)</unit> <value>252</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord> >! <datarecord id="1"><function>Instantaneous value</function> <unit>Energy (10 Wh)</unit> <value>252</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord> >! <datarecord id="2"><function>Instantaneous value</function> <unit> V</unit> <value>240</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord> >! <datarecord id="3"><function>Instantaneous value</function> <unit>1e-1 A</unit> <value>2</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord> >! <datarecord id="4"><function>Instantaneous value</function> <unit>Power (10 W)</unit> <value>2</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord> >! <datarecord id="5"><function>Instantaneous value</function> <unit>Power (10 W)</unit> <value>0</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord></mbusdata> >! ```` -
Hast du mal versucht den problematischen Zähler per libmbus auszulesen? Geht es da?
Der gerätescan den der Adapter Machtposition ein secondary Scan. Das heißt da sollten an sich ander IDs außer 1..10 kommen. Aber am finden scheint es ja nicht zu liegen.
Hast du auch mal den timeout erhöht wie angefragt?
Gesendet vom Handy …
-
Hast du mal versucht den problematischen Zähler per libmbus auszulesen? Geht es da? `
Ja, geht ohne Probleme. Das Ergebnis habe ich dem obigen Post angeheftet. Scan mit libmbus und Auslesen kein Problem. Ich baue mir wohl mit NodeRed wohl besser eine eigene Lösung? Wenn mir jemand verständlich erklären würde wie ich den libmbus in einem Javascript einbinden kann, dann wäre es sicher die optimale Lösung. Bisher hatte ich mal Versuchsweise mit NodeRed die xml Datei schreiben lassen und dann aus dem File die Daten ausgelesen.
pi@raspberrypi:~/libmbus-0.8.0 $ mbus-tcp-request-data 192.168.xxx.xx 1001 5 <mbusdata><slaveinformation><id>100993</id> <manufacturer>SBC</manufacturer> <version>36</version> <productname></productname> <medium>Electricity</medium> <accessnumber>145</accessnumber> <status>00</status> <signature>0000</signature></slaveinformation> <datarecord id="0"><function>Instantaneous value</function> <unit>Energy (10 Wh)</unit> <value>252</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord> <datarecord id="1"><function>Instantaneous value</function> <unit>Energy (10 Wh)</unit> <value>252</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord> <datarecord id="2"><function>Instantaneous value</function> <unit> V</unit> <value>240</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord> <datarecord id="3"><function>Instantaneous value</function> <unit>1e-1 A</unit> <value>2</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord> <datarecord id="4"><function>Instantaneous value</function> <unit>Power (10 W)</unit> <value>2</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord> <datarecord id="5"><function>Instantaneous value</function> <unit>Power (10 W)</unit> <value>0</value> <timestamp>2018-06-29T04:27:26</timestamp></datarecord></mbusdata>Hast du auch mal den timeout erhöht wie angefragt? `
Ja, auf 10000> mbus.0 2018-06-29 05:10:16.105 info Initialize M-Bus TCP to 192.168.xxx.xx:1001 with timeout ****10000**** -
Der Adapter verwendet intern auch nichts anderes wie libmbus! … und da wirds jetzt hochinteressant.
Und auch der Log von deiner instanz 0 ist strange weil auch viele Fehler!! Da hab ich nichts erfolgreiches gesehen! Bitte mal beide instanzen in "debug" Loglevel setzen (Instanzen -> Expertenmodus -> Spalte Loglevel) und dann nochmal Log von mbus.0 und mbis .1 instanz posten.
Der Versuch mit libmbus direkt ist auf dem gleichen host wie der Adapter läuft?
Und nein die Lösung ist die Ursache für den Fehler zu finden im Adapter :-))
Also bitte mal:
-
auf dem iobroker Rechner in /opt/iobroker/node_modules/iobroker.mbus/ gehen
-
npm install --debug node-mbus
-
Instanz 0+1 in ioBroker stoppen
-
Ausführen: node main.js --force --logs
Und dann die Ausgabe bitte schicken.
Aber wir hören hier im Forum auf, bitte als Giuthub Issue beim Adapter weitermachen, also log dahin bitte. Danke
Wäre doch gelacht wenn wir da keine Lösung finden
-
-
Aber wir hören hier im Forum auf, bitte als Giuthub Issue beim Adapter weitermachen, also log dahin bitte. Danke `
Wäre wirklich Schade, denn dann ist für mich dann hier Schluß. Ich bin bei Github nicht angemeldet und werde dies auf absehbarer Zeit auch nicht machen.
@apollon77:Wäre doch gelacht wenn wir da keine Lösung finden `
Diese Einstellung gefällt mir und würde ich auch gerne nach Kräften unterstützen. Allerdings habe ich Moment doch div. Zeitprobleme. Ich bin in NodeRed schon ziemlich weit, das Auslesen des Zählers mit der ID2 steht schon und für die restlichen Adressen habe ich auch schon die Erzeugung der xml Datei stehen. Da gibt es nur noch Schwierigkeiten mit der Zuordnung der Werte. Das kriege ich aber heute sicher noch in den Griff.
@apollon77:Der Versuch mit libmbus direkt ist auf dem gleichen host wie der Adapter läuft? `
Nein, ist ein Raspi3. Der Raspi stellt den MQTT Broker zur Verfügung und ist Dreh- und Angelpunkt für mein Modbus-Netzwerk. Versuchsweise hatte ich vor Monaten den libmbus auf dem Raspi installiert. ioBroker läuft in docker auf einer NAS.
@apollon77:Und auch der Log von deiner instanz 0 ist strange weil auch viele Fehler!! ` Jepp. Das Teil humpelt in den letzten Wochen auch ständig rum und insbesondere der Zähler mit der ID001 ist manchmal nicht mehr zu erreichen. Dann stoppe ich in docker ioBroker und starte dann neu. Dann funktioniert wieder alles.
Ich brauche jedoch täglich eine zuverlässige Auslesung der Zähler. Deshalb schaffe ich mir jetzt erst einmal eine zuverlässige Lösung und schaue mir dann mal an, was Du von mir haben möchtest und ob ich das hinbekomme.
-
Deine GitHub-Abstinenz finde ich schade, weil das der Platz ist wo alle Adapter von ioBroker "leben", dort gibt es die Adapter-Requests.
Da das Forum für Kommunikation super, aber für Bugs oder Issues nur bedingt sinnvoll funktioniert bewegt sich gerade alles mehr Richtung GitHub was Fehler oder Feature-Requests angeht.
Überdenke bitte nochmal Deine Einstellung.
Im Notfall machen wir halt im Forum in nem eigenen Thread weiter … ich persönlich wäre aber über GitHub glücklicher weil für mich als Entwickler besser handhabbar und besser in meine Abläufe und Arbeitsweise einbindbar.
Es wäre sehr interessant (vor allem auch noch wegen Docker und kram) mal ein libmbus in dem Docker-Container zu haben. Wenn das dann nämlich auch nicht gescheit tut dann suchen wir auf ner ganz anderen Ebene weiter.
Die Alternative für Ausschlussverfahren wäre ioBroker als Slave mit dem mbus-Adapter auf den Raspi wo es geht um zu schauen ob es da stabiler tut.
Weil mit der Info sage ich ehrlich das ich nicht weiss ob es an libmbus, meiner node-Library mit libmbus oder dem Adapter ODER Docker und gedöhns liegt und das macht die Fehlersucht extrem schwierig.
Vor allem macht mich die Info "manchmal spinnt auch mbus.0. und nach restart geht es wieder" sehr stutzig.
-
Überdenke bitte nochmal Deine Einstellung. ` No way. Hat aber absolut nichts mit Github zu tun. Ich möchte mich nur nicht noch irgendwo anmelden. Ich habe so schon den Überblick verloren.
@apollon77:Im Notfall machen wir halt im Forum in nem eigenen Thread weiter … ich persönlich wäre aber über GitHub glücklicher weil für mich als Entwickler besser handhabbar und besser in meine Abläufe und Arbeitsweise einbindbar. `
Absolut nachvollziehbar. Wir müssen halt einen Weg finden. Vielleicht auch per E-Mail, da lassen sich dann auch die Screenshot viel einfacher und schneller einbinden.Der Raspi ist allerdings tabu, da kommt kein ioBroker drauf. Aber ich habe hier noch einen Ersatzraspi3 und den Raspi3+ rumliegen. Damit experimentiere ich immer rum und erst wenn alles fehlerfrei läuft kommt dies auch auf dem in Betrieb befindlichen Raspi zum Einsatz.
In Node Red bin ich schon fertig. Alle M-Bus Teilnehmer liefern ihre Werte und schreiben diese auf Anforderung in den MQTT Broker, von wo aus das Dashboard dann seine Anzeigewerte erhält. Und dies alles ohne eine einzige Fehlermeldung, ich bin total begeistert. :lol:
Nur zur Ergänzung, das Dashboard läuft auf einem RevolutionPi.
Und da bin ich bei dir, wir sollten herausfinden warum es zu diesen seltsamen Fehlern kommt. Vielleicht stellen sich ja auch noch Probleme mit meiner Node Red Lösung ein. :?: In einigen Wochen wissen wir mehr.
-
Im Notfall machen wir halt im Forum in nem eigenen Thread weiter … ich persönlich wäre aber über GitHub glücklicher weil für mich als Entwickler besser handhabbar und besser in meine Abläufe und Arbeitsweise einbindbar.
Absolut nachvollziehbar. Wir müssen halt einen Weg finden. Vielleicht auch per E-Mail, da lassen sich dann auch die Screenshot viel einfacher und schneller einbinden.Dann Forum … leider ...
Dann wäre die Idee das Du mal den Adapter auf den test-raspi bringst und auch libmbus ... dann kann man mal schauen ob Sie sich da gleich verhalten.
-
Das kannst du aber trotzdem vorab auf dem ioBroker host machen
` > Also bitte mal:
-
auf dem iobroker Rechner in /opt/iobroker/node_modules/iobroker.mbus/ gehen
-
npm install –debug node-mbus
-
Instanz 0+1 in ioBroker stoppen
-
Ausführen: node main.js --force --logs
Und dann die Ausgabe bitte schicken. `
-
-
Wir müssen halt einen Weg finden. Vielleicht auch per E-Mail, da lassen sich dann auch die Screenshot viel einfacher und schneller einbinden. `
Um ein bisschen Öl ins Feuer zu gießen: Bei GitHub kannste Screenshots einfach per Drag&Drop einfügen :twisted: -
Wir müssen halt einen Weg finden. Vielleicht auch per E-Mail, da lassen sich dann auch die Screenshot viel einfacher und schneller einbinden.
Um ein bisschen Öl ins Feuer zu gießen: Bei GitHub kannste Screenshots einfach per Drag&Drop einfügen :twisted:oder sogar per Strg+V
-
Ich persönlich finde den Unwille bei github zu registrieren wie eine Beleidigung und Missachtung.
Man investiert Stunden und Tagen um das System kostenlos für DICH zur Verfügung zu stellen und jetzt vom Jemanden zu hören, dass er 3 Minuten nicht hat um so eine Form mit 3 Felder zu befüllen:
Hm…..
-
Hallo Leute,
hab seit gestern einen Letrika SMI260 Wechselrichter, und würde dessen Daten gerne im ioBroker haben. Was ist die günstigste und direkteste Möglichkeit dazu? Geht das über diesen M-Bus Adapter?
Das Solarmodul ist logischer Weise draußen, und ein Kabel nach drinnen ist schwierig, wenn ich es aber richtig verstanden habe, funkt der auch? Aber der offizielle Stick kostet 80 € UND … ich weiß nicht ob der Hilft weil ich bezweifle dass man über diesen die Daten in den ioBroker bekommt?
Danke für eure Hilfe
-
Hallo Leute,
hab seit gestern einen Letrika SMI260 Wechselrichter, und würde dessen Daten gerne im ioBroker haben. Was ist die günstigste und direkteste Möglichkeit dazu? Geht das über diesen M-Bus Adapter?
Das Solarmodul ist logischer Weise draußen, und ein Kabel nach drinnen ist schwierig, wenn ich es aber richtig verstanden habe, funkt der auch? Aber der offizielle Stick kostet 80 € UND … ich weiß nicht ob der Hilft weil ich bezweifle dass man über diesen die Daten in den ioBroker bekommt?
Danke für eure Hilfe `
Heute morgen erst beschrieben, mit einem Umweg über Homematic/CuxD:
viewtopic.php?f=8&t=1347&start=220#p175167
Kostenpunkt 120 € für iM871A Stick und Lizenz.
Wenn man mit dem iM871A Stick und dem Adapter direkt die SMI260 auslesen könnte würde man den Umweg über CuxD sparen.
-
iobroker hat den wm-bus Adapter für Wireless MBus … geht das nicht?
-
iobroker hat den wm-bus Adapter für Wireless MBus … geht das nicht? `
Keine Ahnung,
Kann ich nicht probieren weil mein iobroker als Docker auf der Synology läuft und nicht auf einem Raspi.
Ich könnte bei Gelegenheit mal einen Raspi mit jungfräulichem iobroker aufsetzen.
Also den Stick dann einstecken, M-Bus Adapter installieren und dann sollte es klappen? Ich müsste wahrscheinlich irgendwo die Seriennummer vom SMI260 eingeben können.
-
Habe jetzt keine Ahnung vom Strick, aber Achtung: kabelgebunden -> mbus, Funk -> Wireless mbus !!!
Gesendet vom Handy …
-
Ah, dann klappt das nicht.
Der SMI260 spricht per Wireless MBus mit dem USB-Adapter iM871A.
Gut, dann brauche ich das gar nicht erst testen. Dan gilt für den SMI260 nach wie vor der Weg über CuxD mittels einer Lizenz wie hier beschrieben: viewtopic.php?f=8&t=1347&start=220#p175167
-
-
Hi apollon77,
ja das war meine Hoffnung … heißt das also, dass ich deniM871A Stick kaufen muss, an dem RasPi einstecken muss auf dem der ioBroker läuft und dann kann ich wireless mit dem Letrika SMI260 Wechselrichter abfragen? (--> Kosten 49,90 €)
Oder brauche ich dazu noch diese Lizenz? Muss ich von Letrika noch iwas kaufen an Lizenzen oder AES-schlüssel erfragen oder ... wie klappt das?
Vielen Dank für die Antwort
