Hallo ich brauch mal bitte einen Tip von euch.
Immer nach Reset oder Stromausfall an meinem Raspie bekomme ich im IoBroker diese fehler.
023
Log-Größe: 4.8 KB
Zeit
Nachricht
host.raspberrypi
2024-02-19 14:10:00.053 warn instance system.adapter.ebus.0 already running with pid 1185
ebus.0
2024-02-19 14:00:05.580 warn sent read -f Date , received ERR: element not found for {"active":true,"circuit":"","name":"Date","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.576 warn sent read -f ActualRoomTempDesiredHc1 , received ERR: element not found for {"active":true,"circuit":"","name":"ActualRoomTempDesiredHc1","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.572 warn sent read -f RoomTemp , received ERR: element not found for {"active":true,"circuit":"","name":"RoomTemp","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.568 warn sent read -f Hc1RoomTempSwitchOn , received ERR: element not found for {"active":true,"circuit":"","name":"Hc1RoomTempSwitchOn","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.565 warn sent read -f HwcOpMode , received ERR: element not found for {"active":true,"circuit":"","name":"HwcOpMode","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.561 warn sent read -f Time , received ERR: element not found for {"active":true,"circuit":"","name":"Time","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.557 warn sent read -f Hc1Pump , received ERR: element not found for {"active":true,"circuit":"","name":"Hc1Pump","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.553 warn sent read -f DisplayedRoomTemp , received ERR: element not found for {"active":true,"circuit":"","name":"DisplayedRoomTemp","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.550 warn sent read -f StorageTemp , received ERR: element not found for {"active":true,"circuit":"","name":"StorageTemp","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.546 warn sent read -f ReturnTemp , received ERR: element not found for {"active":true,"circuit":"","name":"ReturnTemp","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.542 warn sent read -f OutsideTemp , received ERR: element not found for {"active":true,"circuit":"","name":"OutsideTemp","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.538 warn sent read -f WaterPressure , received ERR: element not found for {"active":true,"circuit":"","name":"WaterPressure","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.534 warn sent read -f PumpHours , received ERR: element not found for {"active":true,"circuit":"","name":"PumpHours","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.531 warn sent read -f FanHours , received ERR: element not found for {"active":true,"circuit":"","name":"FanHours","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.527 warn sent read -f HwcHours , received ERR: element not found for {"active":true,"circuit":"","name":"HwcHours","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.523 warn sent read -f HcHours , received ERR: element not found for {"active":true,"circuit":"","name":"HcHours","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.519 warn sent read -f DisplayedHc1RoomTempDesired , received ERR: element not found for {"active":true,"circuit":"","name":"DisplayedHc1RoomTempDesired","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.515 warn sent read -f FlowTemp , received ERR: element not found for {"active":true,"circuit":"","name":"FlowTemp","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.512 warn sent read -f Hc1ManualOPRoomTempDesired , received ERR: element not found for {"active":true,"circuit":"","name":"Hc1ManualOPRoomTempDesired","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.507 warn sent read -f Hc1OpMode , received ERR: element not found for {"active":true,"circuit":"","name":"Hc1OpMode","parameter":""} please check ebusd logs for details!
ebus.0
2024-02-19 14:00:05.504 warn sent read -f HC1HeatCurve , received ERR: element not found for {"active":true,"circuit":"","name":"HC1HeatCurve","parameter":""} please check ebusd logs for details!
host.raspberrypi
2024-02-19 14:00:00.048 warn instance system.adapter.ebus.0 already running with pid 1185
Das sind meine abgefragten Werte und am Schluss steht "instance system.adapter.ebus.0 already running with pid 1185"
Ich muss dann auf die Konsole und den Service mit /etc/init.d/ebusd stop aus- und mit /etc/init.d/ebusd start wieder einschalten. Danach läuft wieder alles problemlos bis zum nächsten Stromausfall was leider grad öffters passiert.
Kann es sein, dass der ebus doppelt gestartet wird und wo könnte ich da genau nachsehen und das bereinigen?
Danke schon mal für eure Hilfe.
LG Horst
I