Monatsrückblick Januar/Februar 2026 ist online!

[meute]

Hallo,

bei mir läuft eine modbus-Instanz und fragt die Sensoren der Wallbox ab.
Nach einem ioBroker-Neustart loggt die modbus-Instanz Fehler.
Wenn ich danach die modbus-Instanz stoppe und starte ist alles schick.

Wo könnte das Problem liegen?
Müsste die modbus-Instanz vll. verzögert starten?

Error nach ioBroker-Neustart:

2026-03-07 17:09:55.755 - error: modbus.0 (463) Socket Error Error: connect ECONNREFUSED 192.168.23.189:502
2026-03-07 17:09:55.756 - error: modbus.0 (463) Client in error state.
2026-03-07 17:09:55.756 - warn: modbus.0 (463) Connection refused 192.168.23.189:502
2026-03-07 17:11:08.046 - error: modbus.0 (463) Socket Error Error: connect ECONNREFUSED 192.168.23.189:502
2026-03-07 17:11:08.047 - error: modbus.0 (463) Client in error state.
2026-03-07 17:11:08.047 - warn: modbus.0 (463) Connection refused 192.168.23.189:502
2026-03-07 17:12:09.126 - error: modbus.0 (463) Socket Error Error: connect ECONNREFUSED 192.168.23.189:502
2026-03-07 17:12:09.126 - error: modbus.0 (463) Client in error state.
2026-03-07 17:12:09.127 - warn: modbus.0 (463) Connection refused 192.168.23.189:502
2026-03-07 17:13:10.131 - error: modbus.0 (463) Socket Error Error: connect ECONNREFUSED 192.168.23.189:502
2026-03-07 17:13:10.131 - error: modbus.0 (463) Client in error state.
2026-03-07 17:13:10.132 - warn: modbus.0 (463) Connection refused 192.168.23.189:502
2026-03-07 17:14:11.137 - error: modbus.0 (463) Socket Error Error: connect ECONNREFUSED 192.168.23.189:502
2026-03-07 17:14:11.138 - error: modbus.0 (463) Client in error state.
2026-03-07 17:14:11.138 - warn: modbus.0 (463) Connection refused 192.168.23.189:502
2026-03-07 17:15:12.144 - error: modbus.0 (463) Socket Error Error: connect ECONNREFUSED 192.168.23.189:502
2026-03-07 17:15:12.144 - error: modbus.0 (463) Client in error state.
2026-03-07 17:15:12.144 - warn: modbus.0 (463) Connection refused 192.168.23.189:502
2026-03-07 17:16:24.570 - error: modbus.0 (463) Socket Error Error: connect ECONNREFUSED 192.168.23.189:502
2026-03-07 17:16:24.571 - error: modbus.0 (463) Client in error state.
2026-03-07 17:16:24.572 - warn: modbus.0 (463) Connection refused 192.168.23.189:502
2026-03-07 17:17:28.059 - error: modbus.0 (463) Socket Error Error: connect ECONNREFUSED 192.168.23.189:502
2026-03-07 17:17:28.060 - error: modbus.0 (463) Client in error state.
2026-03-07 17:17:28.060 - warn: modbus.0 (463) Connection refused 192.168.23.189:502

Alle i.O. nach modbus-Instanz stopp/start:

2026-03-07 17:17:44.664 - info: host.iobroker84 "system.adapter.modbus.0" disabled
2026-03-07 17:17:44.666 - info: host.iobroker84 stopInstance system.adapter.modbus.0 (force=false, process=true)
2026-03-07 17:17:44.670 - info: modbus.0 (463) Got terminate signal TERMINATE_YOURSELF
2026-03-07 17:17:44.709 - info: host.iobroker84 stopInstance system.adapter.modbus.0 send kill signal
2026-03-07 17:17:44.709 - info: modbus.0 (463) terminating
2026-03-07 17:17:44.710 - info: modbus.0 (463) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-07 17:17:45.172 - info: modbus.0 (463) terminating
2026-03-07 17:17:45.267 - info: host.iobroker84 instance system.adapter.modbus.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-07 17:17:53.529 - info: host.iobroker84 "system.adapter.modbus.0" enabled
2026-03-07 17:17:54.061 - info: host.iobroker84 instance system.adapter.modbus.0 in version "7.0.6" started with pid 657
2026-03-07 17:17:55.499 - info: modbus.0 (657) starting. Version 7.0.6 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.1, js-controller: 7.0.7
2026-03-07 17:17:55.807 - info: modbus.0 (657) Connected to slave 192.168.23.189