Test Adapter sun2000 v0.1.x - Huawei Wechselrichter
-
Ich kenne nur das IO Broker Log, anbei die Zeilen die auf der Stufe Info den Sun 2000 Adapter betreffen. Gibt es noch ein anderes Log?
Sun2000Log.txtUnd die beiden Screenshots mit den Einstellungen
@Plotter123 deine Einstellungen sind soweit ok.
Es tauchen keine TimeOuts auf - allerdings schafft der Adapter nicht alle Register im Intervall zu lesen. Das ist ungewöhnlich. Dann hast du sicher einen alten sDongle siehe: https://github.com/evcc-io/evcc/discussions/22534 -
oder ein langsames WLAN?
Dann musst du den Intervall successive erhöhen bis die Meldung nicht mehr auftaucht. Ich habe auch einen sDongle und kann den mit einem Intervall 5Sekunden ohne Probleme lesen.
Vielleicht sollte ich Log-Meldung etwas anpassen ...Stephan
-
Ich kenne nur das IO Broker Log, anbei die Zeilen die auf der Stufe Info den Sun 2000 Adapter betreffen. Gibt es noch ein anderes Log?
Sun2000Log.txtUnd die beiden Screenshots mit den Einstellungen
-
@bolliy
Hallo bei mir stürzt der Adapter mit der V2.7.2
Immer ab wenn ich in die 2 Datenpunktesun2000.0.inverter.0.control.battery.maximumDischargingPower
sun2000.0.inverter.0.control.battery.maximumChargingPowerdie Werte ändere, das war bei der v2.6.2 nicht der fall.
Bin wieder zurück auf 2.6.2
Bis jetzt habe ich die Werte immer in W angegeben max 5000 oder 500 wie ich es halt im Skript angelegt hatte.
Weiß da jemand was muss ich es jetzt anders eintragen?
MfG Jürgen -
@Plotter123 deine Einstellungen sind soweit ok.
Es tauchen keine TimeOuts auf - allerdings schafft der Adapter nicht alle Register im Intervall zu lesen. Das ist ungewöhnlich. Dann hast du sicher einen alten sDongle siehe: https://github.com/evcc-io/evcc/discussions/22534 -
oder ein langsames WLAN?
Dann musst du den Intervall successive erhöhen bis die Meldung nicht mehr auftaucht. Ich habe auch einen sDongle und kann den mit einem Intervall 5Sekunden ohne Probleme lesen.
Vielleicht sollte ich Log-Meldung etwas anpassen ...Stephan
@bolliy
Ja, ich habe den alten Dongle 005. WLAN nutze ich nicht, der Dongle ist per LAN angeschlossen. Der Wechselrichter hat keinen Zugang zum Internet, auch eine Fusion App nutze ich nicht.Auch mit NodeRed kommen die Daten sehr langsam. Darum habe ich bei evcc auch nicht den Wechselrichter zur Steuerung hinterlegt, sondern den am Stromzähler angeschlossenen Lesekopf.
Nachdem ich das Intervall auf 20 Sekunden verlängert hatte kamen auch keine Fehlermeldungen mehr, alle Ordner enthalten Werte und ich vermisse nichts mehr.
Mit der Beta Version 2.7.2 bekomme ich aber auch bei 25 Sekunden vereinzelt Meldungen dass nicht alles gelesen werden kann.
Eigentlich plane ich aber keine zeitkritischen Aktionen. Ich wollte mich nur (ab der nächsten Saison) netzdienlicher verhalten und bei guter Wetterprognose den Akku nicht schon am frühen Morgen laden sondern erst ab der Mittagszeit. Das geht doch über das Setzen von
sun2000.0.inverter.0.control.battery.chargingCutoffCapacity
Im Moment ist das bei mir Rot und nicht änderbar. Muss ich da noch etwas am WR konfigurieren damit ich nicht nur lesen sondern auch schreiben kann?
-
@bolliy
Hallo bei mir stürzt der Adapter mit der V2.7.2
Immer ab wenn ich in die 2 Datenpunktesun2000.0.inverter.0.control.battery.maximumDischargingPower
sun2000.0.inverter.0.control.battery.maximumChargingPowerdie Werte ändere, das war bei der v2.6.2 nicht der fall.
Bin wieder zurück auf 2.6.2
Bis jetzt habe ich die Werte immer in W angegeben max 5000 oder 500 wie ich es halt im Skript angelegt hatte.
Weiß da jemand was muss ich es jetzt anders eintragen?
MfG Jürgen -
@bolliy
Ja, ich habe den alten Dongle 005. WLAN nutze ich nicht, der Dongle ist per LAN angeschlossen. Der Wechselrichter hat keinen Zugang zum Internet, auch eine Fusion App nutze ich nicht.Auch mit NodeRed kommen die Daten sehr langsam. Darum habe ich bei evcc auch nicht den Wechselrichter zur Steuerung hinterlegt, sondern den am Stromzähler angeschlossenen Lesekopf.
Nachdem ich das Intervall auf 20 Sekunden verlängert hatte kamen auch keine Fehlermeldungen mehr, alle Ordner enthalten Werte und ich vermisse nichts mehr.
Mit der Beta Version 2.7.2 bekomme ich aber auch bei 25 Sekunden vereinzelt Meldungen dass nicht alles gelesen werden kann.
Eigentlich plane ich aber keine zeitkritischen Aktionen. Ich wollte mich nur (ab der nächsten Saison) netzdienlicher verhalten und bei guter Wetterprognose den Akku nicht schon am frühen Morgen laden sondern erst ab der Mittagszeit. Das geht doch über das Setzen von
sun2000.0.inverter.0.control.battery.chargingCutoffCapacity
Im Moment ist das bei mir Rot und nicht änderbar. Muss ich da noch etwas am WR konfigurieren damit ich nicht nur lesen sondern auch schreiben kann?
sun2000.0.inverter.0.control.battery.chargingCutoffCapacity
rot bedeutet: Wert wurde noch nicht gesetzt. Einfach einen Wert eintragen ...
Es dauert etwas bis der Adapter nach einem Neustart die Werte verarbeitet. Danach im Log schauen ob er den Wert annimmt und an den WR übertragen kann. Das sieht dann so aus:sun2000.0 2026-10-06 17:08:57.362 info inverter 0 control: write state inverter.0.control.battery.chargingCutoffCapacity : 95 ack: true sun2000.0 2026-10-06 17:08:54.994 info inverter 0 control: Event - state: inverter.0.control.battery.chargingCutoffCapacity changed: 95 ack: false -
@juggi1962 oh, danke für den Hinweis.
Schaue ich gleich mal nach ...
Edit: Fehler gefunden. Klammer falsch gesetzt.
Gibt bald wieder eine neue Testversion...Stephan
-
@bolliy
Ja, ich habe den alten Dongle 005. WLAN nutze ich nicht, der Dongle ist per LAN angeschlossen. Der Wechselrichter hat keinen Zugang zum Internet, auch eine Fusion App nutze ich nicht.Auch mit NodeRed kommen die Daten sehr langsam. Darum habe ich bei evcc auch nicht den Wechselrichter zur Steuerung hinterlegt, sondern den am Stromzähler angeschlossenen Lesekopf.
Nachdem ich das Intervall auf 20 Sekunden verlängert hatte kamen auch keine Fehlermeldungen mehr, alle Ordner enthalten Werte und ich vermisse nichts mehr.
Mit der Beta Version 2.7.2 bekomme ich aber auch bei 25 Sekunden vereinzelt Meldungen dass nicht alles gelesen werden kann.
Eigentlich plane ich aber keine zeitkritischen Aktionen. Ich wollte mich nur (ab der nächsten Saison) netzdienlicher verhalten und bei guter Wetterprognose den Akku nicht schon am frühen Morgen laden sondern erst ab der Mittagszeit. Das geht doch über das Setzen von
sun2000.0.inverter.0.control.battery.chargingCutoffCapacity
Im Moment ist das bei mir Rot und nicht änderbar. Muss ich da noch etwas am WR konfigurieren damit ich nicht nur lesen sondern auch schreiben kann?
-
Neue Testversion sun2000 Adapter Version v2.7.3 released.
Die Installation erfolgt über npm oder morgen über das Beta Repository.
Die neue beta Version 2.7.3 ist verfügbar. Kleiner Fehler; große Wirkung. Der control wert
control.battery.maximumDischargingPowerkonnte durch eine falsch gesetzte Klammer nicht verabeitet werden. Der Adapter stürzte ab!LG Stephan
-
Neue Testversion sun2000 Adapter Version v2.7.3 released.
Die Installation erfolgt über npm oder morgen über das Beta Repository.
Die neue beta Version 2.7.3 ist verfügbar. Kleiner Fehler; große Wirkung. Der control wert
control.battery.maximumDischargingPowerkonnte durch eine falsch gesetzte Klammer nicht verabeitet werden. Der Adapter stürzte ab!LG Stephan
-
Hallo,
ich habe nun seit letzter Woche meinen zweiten Wechselrichter in Betrieb und habe dazu auch schon extra den neuen Sdongle installieren lassen (siehe https://github.com/evcc-io/evcc/discussions/22534), da ich mir nicht sicher war ob der Fehler von dort kommt. Aber selbst mit meuen Dongle habe ich weiterhin Probleme. Kann mir jemand eine Tipp geben was ich dagegen tun kann:Meine Version ist die 2.7.3
sun2000.0 2026-10-22 17:22:12.273 warn Error while reading from 192.168.178.181 [Reg: 32000, Len: 11, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-22 17:22:12.244 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-22 17:22:12.106 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-22 17:22:10.105 info Open Connection... sun2000.0 2026-10-22 17:22:10.104 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-22 17:21:52.246 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-22 17:21:52.121 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-22 17:21:50.119 info Open Connection... sun2000.0 2026-10-22 17:21:50.119 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-22 17:21:32.341 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-22 17:21:32.106 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-22 17:21:30.104 info Open Connection... sun2000.0 2026-10-22 17:21:30.104 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-22 17:20:04.212 info inverter 0 control: Service queue initialized sun2000.0 2026-10-22 17:19:50.610 info inverter 1 control: Service queue initialized sun2000.0 2026-10-22 17:18:51.444 info Identified a Huawei SUN2000-5K-MAP0 model 1001 for modbus ID 2 sun2000.0 2026-10-22 17:18:48.943 info Identified a Huawei SUN2000-10KTL-M1 model 429 for modbus ID 1 sun2000.0 2026-10-22 17:18:46.705 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-22 17:18:44.703 info Open Connection... -
Hallo,
ich habe nun seit letzter Woche meinen zweiten Wechselrichter in Betrieb und habe dazu auch schon extra den neuen Sdongle installieren lassen (siehe https://github.com/evcc-io/evcc/discussions/22534), da ich mir nicht sicher war ob der Fehler von dort kommt. Aber selbst mit meuen Dongle habe ich weiterhin Probleme. Kann mir jemand eine Tipp geben was ich dagegen tun kann:Meine Version ist die 2.7.3
sun2000.0 2026-10-22 17:22:12.273 warn Error while reading from 192.168.178.181 [Reg: 32000, Len: 11, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-22 17:22:12.244 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-22 17:22:12.106 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-22 17:22:10.105 info Open Connection... sun2000.0 2026-10-22 17:22:10.104 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-22 17:21:52.246 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-22 17:21:52.121 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-22 17:21:50.119 info Open Connection... sun2000.0 2026-10-22 17:21:50.119 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-22 17:21:32.341 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-22 17:21:32.106 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-22 17:21:30.104 info Open Connection... sun2000.0 2026-10-22 17:21:30.104 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-22 17:20:04.212 info inverter 0 control: Service queue initialized sun2000.0 2026-10-22 17:19:50.610 info inverter 1 control: Service queue initialized sun2000.0 2026-10-22 17:18:51.444 info Identified a Huawei SUN2000-5K-MAP0 model 1001 for modbus ID 2 sun2000.0 2026-10-22 17:18:48.943 info Identified a Huawei SUN2000-10KTL-M1 model 429 for modbus ID 1 sun2000.0 2026-10-22 17:18:46.705 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-22 17:18:44.703 info Open Connection...@Christian-Kohlöffel hast du einen weiteren Client (zB. evcc) der neben dem sun2000 Adapter auf den Wechselrichter/sDongle per modbus zugreift?
Ist die Firmware aller Geräteeinheiten auf aktuellem Stand?
Welche Einstellung des Intervalls?
Welche modbus Timing Einstellungen des Adapters?
Stephan
-
@Christian-Kohlöffel hast du einen weiteren Client (zB. evcc) der neben dem sun2000 Adapter auf den Wechselrichter/sDongle per modbus zugreift?
Ist die Firmware aller Geräteeinheiten auf aktuellem Stand?
Welche Einstellung des Intervalls?
Welche modbus Timing Einstellungen des Adapters?
Stephan
Ich kann aktuell nur die FW der Sdongles anschauen, die ist: V200R025C00SPC110
Master Wechselrichter: SUN2000-10KTL-M1 SW Version: V100R001C00SPC178
Slave Wechselrichter: SUN2000-5K-MAP0: V200R024C00SPC110Ich habe nur iobroker der noch ein anderes Gerät auf dem Modbus auswertet, sollte aber nicht auf die selbe IP zugreifen. Also nichts was ich extra so angegeben habe.
Ob das aktuell ist kann ich nicht sagen, sollte aber so sein, da SW Updates zur Inbetriebnahme nötig waren:
Hier die Intervalleinstellungen:
Hier die Einstellungen vom Adapter. Automatische Anpassung hatte auch keine Verbesserung zur Folge.
-
Ich kann aktuell nur die FW der Sdongles anschauen, die ist: V200R025C00SPC110
Master Wechselrichter: SUN2000-10KTL-M1 SW Version: V100R001C00SPC178
Slave Wechselrichter: SUN2000-5K-MAP0: V200R024C00SPC110Ich habe nur iobroker der noch ein anderes Gerät auf dem Modbus auswertet, sollte aber nicht auf die selbe IP zugreifen. Also nichts was ich extra so angegeben habe.
Ob das aktuell ist kann ich nicht sagen, sollte aber so sein, da SW Updates zur Inbetriebnahme nötig waren:
Hier die Intervalleinstellungen:
Hier die Einstellungen vom Adapter. Automatische Anpassung hatte auch keine Verbesserung zur Folge.
@Christian-Kohlöffel bitte sDongle FW updaten.
Deine Version ist veraltet.
https://wattkraft-de.zendesk.com/hc/de-de/articles/18525839524114-Update-SDongle
LG Stephan -
Alles klar, Danke. Dann werde ich das durchführen und berichten.
-
Ich kann aktuell nur die FW der Sdongles anschauen, die ist: V200R025C00SPC110
Master Wechselrichter: SUN2000-10KTL-M1 SW Version: V100R001C00SPC178
Slave Wechselrichter: SUN2000-5K-MAP0: V200R024C00SPC110Ich habe nur iobroker der noch ein anderes Gerät auf dem Modbus auswertet, sollte aber nicht auf die selbe IP zugreifen. Also nichts was ich extra so angegeben habe.
Ob das aktuell ist kann ich nicht sagen, sollte aber so sein, da SW Updates zur Inbetriebnahme nötig waren:
Hier die Intervalleinstellungen:
Hier die Einstellungen vom Adapter. Automatische Anpassung hatte auch keine Verbesserung zur Folge.
Ich habe nur iobroker der noch ein anderes Gerät auf dem Modbus auswertet, sollte aber nicht auf die selbe IP zugreifen. Also nichts was ich extra so angegeben habe.
Deine Aussage verstehe ich nicht. Was greift bei dir per modbus wo zu?
Stephan
-
Ich habe nur iobroker der noch ein anderes Gerät auf dem Modbus auswertet, sollte aber nicht auf die selbe IP zugreifen. Also nichts was ich extra so angegeben habe.
Deine Aussage verstehe ich nicht. Was greift bei dir per modbus wo zu?
Stephan
Guten Morgen,
jetzt hat mein Installateur den Smartdongle aktualisiert, mein SW Version ist nun: V200R025C00SPC141Deine Aussage verstehe ich nicht. Was greift bei dir per modbus wo zu?
Das sollte nur heißen, dass ich noch ein weiteres Gerät habe das im Netzt per Modbus kommuniziert (meine WP),. Aber die hat ja eine andere IP, hierzu verwende ich den iobroker Modbus Adapter. Soweit ich weiß hab ich kein Gerät ausser den sun2000 adapter der auf den Sdongle zugreift.
Selbst mit dem neuen SW Update sieht es im Log immernoch ähnlich aus, siehe Anhang.
sun2000.0 2026-10-24 10:22:36.089 info terminating sun2000.0 2026-10-24 10:22:36.089 info terminating sun2000.0 2026-10-24 10:22:35.586 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason sun2000.0 2026-10-24 10:22:35.586 debug Plugin sentry destroyed sun2000.0 2026-10-24 10:22:35.585 info terminating sun2000.0 2026-10-24 10:22:35.585 info cleaned everything up... sun2000.0 2026-10-24 10:22:35.585 info Got terminate signal TERMINATE_YOURSELF sun2000.0 2026-10-24 10:22:22.200 debug Fetched collected.consumptionToday, val=7.9018499547 sun2000.0 2026-10-24 10:22:22.159 debug Fetched sdongle.totalActivePower, val=0.62 sun2000.0 2026-10-24 10:22:22.158 debug Fetched collected.dailySolarYield, val=1.4724151487 sun2000.0 2026-10-24 10:22:22.158 debug Fetched sdongle.totalBatteryPower, val=0.455 sun2000.0 2026-10-24 10:22:22.157 debug Fetched sdongle.gridPower, val=0.043 sun2000.0 2026-10-24 10:22:22.157 debug Fetched collected.dailyInputYield, val=1.1266908131 sun2000.0 2026-10-24 10:22:22.157 debug Fetched sdongle.loadPower, val=0.663 sun2000.0 2026-10-24 10:22:22.156 debug Fetched sdongle.totalInputPower, val=1.045 sun2000.0 2026-10-24 10:22:22.156 debug Fetched inverter.1.derived.dailyActiveEnergy, val=0.39464287 sun2000.0 2026-10-24 10:22:22.156 debug ### DataPolling STOP ### sun2000.0 2026-10-24 10:22:22.153 debug Fetched inverter.1.derived.dailySolarYield, val=0.3863279756 sun2000.0 2026-10-24 10:22:22.153 debug Fetched inverter.1.derived.dailyInputYield, val=0.393708095 sun2000.0 2026-10-24 10:22:22.152 debug Fetched collected.surplus.usablePower, val=0.435 sun2000.0 2026-10-24 10:22:22.152 debug Fetched collected.surplus.power, val=0.435 sun2000.0 2026-10-24 10:22:22.151 debug Fetched collected.chargeDischargePower, val=0.455 sun2000.0 2026-10-24 10:22:22.151 debug Fetched collected.houseConsumption, val=0.628 sun2000.0 2026-10-24 10:22:22.151 debug Try to read data from id/address 100/37498/medium/Power data sun2000.0 2026-10-24 10:22:22.151 debug Last read reg for 54015 ms - SDongle Device Search Status sun2000.0 2026-10-24 10:22:22.151 debug Update loop stopped sun2000.0 2026-10-24 10:22:22.151 warn Error while reading from 192.168.178.181 [Reg: 32000, Len: 11, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:22:22.151 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:22:22.150 debug Fetched collected.activePower, val=0.608 sun2000.0 2026-10-24 10:22:22.150 debug Fetched collected.inputPowerWithEfficiencyLoss, val=0.9684 sun2000.0 2026-10-24 10:22:22.149 debug Fetched collected.inputPower, val=1.076 sun2000.0 2026-10-24 10:22:22.149 debug Fetched inverter.0.derived.dailyActiveEnergy, val=2.2972070847 sun2000.0 2026-10-24 10:22:22.148 debug Fetched collected.sumDaily.feed-outPower, val=5.2010527708 sun2000.0 2026-10-24 10:22:22.148 debug Fetched collected.sumDaily.chargePower, val=0.7108348908 sun2000.0 2026-10-24 10:22:22.148 debug Fetched inverter.0.derived.dailySolarYield, val=1.0860871731 sun2000.0 2026-10-24 10:22:22.148 debug Fetched statistics.jsonToday, val={"consumption":{"value":7.899,"unit":"kWh","baseValue":7.899},"solarYield":{"value":1.467,"unit":"kWh"},"inputYield":{"value":1.123,"unit":"kWh"},"externalYield":{"value":0,"unit":"kWh"},"energyYield":{"value":2.87,"unit":"kWh"},"SOC":{"value":6,"unit":"%"},"chargeCapacity":{"value":0.63,"unit":"kWh"},"dischargeCapacity":{"value":2.11,"unit":"kWh"},"gridExport":{"value":0,"unit":"kWh"},"gridImport":{"value":5.21,"unit":"kWh"},"selfSufficiency":{"value":34,"unit":"%"},"selfConsumption":{"value":100,"unit":"%"},"updatedAt":"2026-10-24T10:22:22.000+02:00"} sun2000.0 2026-10-24 10:22:22.147 debug Fetched collected.sumDaily.inputPower, val=1.6121400325 sun2000.0 2026-10-24 10:22:22.147 debug Fetched inverter.0.derived.dailyInputYield, val=0.7329827181 sun2000.0 2026-10-24 10:22:22.147 debug Fetched collected.sumDaily.activePower, val=2.6840488628 sun2000.0 2026-10-24 10:22:22.147 debug Fetched collected.sumDaily.houseConsumption, val=7.8695903261 sun2000.0 2026-10-24 10:22:22.146 debug Fetched inverter.1.inputPower, val=0.291 sun2000.0 2026-10-24 10:22:22.146 debug Try to read data from id/address 2/32000/low/inverter status sun2000.0 2026-10-24 10:22:22.146 debug Update loop stopped sun2000.0 2026-10-24 10:22:22.146 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:22:22.146 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:22:22.141 debug Fetched inverter.1.activePower, val=0.278 sun2000.0 2026-10-24 10:22:22.139 debug Try to read data from id/address 1/47075/low/additional battery information sun2000.0 2026-10-24 10:22:22.139 debug Last read reg for 53915 ms - battery information sun2000.0 2026-10-24 10:22:22.139 debug Last read reg for 53920 ms - battery information sun2000.0 2026-10-24 10:22:22.139 debug Last read reg for 53925 ms - battery Pack max/min Temperature of unit 1 sun2000.0 2026-10-24 10:22:22.139 debug statistics: jsonToday updated sun2000.0 2026-10-24 10:22:22.139 debug ### Caculate usableSurplus power 0.435 bufferOn false soc 6 minSoc 0 bufferSoc 0 threshold 0 sun2000.0 2026-10-24 10:22:22.139 debug activePower 0.278 !== inputPower 0.291-chargePower 0 sun2000.0 2026-10-24 10:22:22.130 debug Try to read data from id/address 2/32064/high/Input Power sun2000.0 2026-10-24 10:22:22.109 debug Fetched inverter.0.battery.chargeDischargePower, val=0.455 sun2000.0 2026-10-24 10:22:22.109 debug Fetched inverter.0.derived.inputPowerWithEfficiencyLoss, val=0.7065 sun2000.0 2026-10-24 10:22:22.108 debug Fetched inverter.0.inputPower, val=0.785 sun2000.0 2026-10-24 10:22:22.107 debug Fetched inverter.0.activePower, val=0.33 sun2000.0 2026-10-24 10:22:22.106 debug Try to read data from id/address 2/32080/high/Inverter Activ Power sun2000.0 2026-10-24 10:22:22.106 debug Update loop stopped sun2000.0 2026-10-24 10:22:22.106 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:22:22.106 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:22:22.101 debug Try to read data from id/address 1/37000/high/battery Unit1 information sun2000.0 2026-10-24 10:22:22.096 debug Try to read data from id/address 1/32064/high/Input Power sun2000.0 2026-10-24 10:22:22.089 debug Try to read data from id/address 1/37765/high/Battery Charge And Discharge Power sun2000.0 2026-10-24 10:22:22.086 debug Fetched collected.consumptionToday, val=7.8988908131 sun2000.0 2026-10-24 10:22:22.086 debug Fetched collected.dailySolarYield, val=1.4672000377 sun2000.0 2026-10-24 10:22:22.045 debug Fetched collected.dailyInputYield, val=1.1233186919 sun2000.0 2026-10-24 10:22:22.044 debug Fetched inverter.1.derived.dailyActiveEnergy, val=0.393708095 sun2000.0 2026-10-24 10:22:22.044 debug Fetched inverter.1.derived.dailySolarYield, val=0.3854470458 sun2000.0 2026-10-24 10:22:22.044 debug Fetched inverter.1.derived.dailyInputYield, val=0.392358095 sun2000.0 2026-10-24 10:22:22.043 debug Try to read data from id/address 1/32080/high/Inverter Activ Power sun2000.0 2026-10-24 10:22:22.043 debug Interval 22.043 sec sun2000.0 2026-10-24 10:22:22.043 debug ### DataPolling START 22 sec ### sun2000.0 2026-10-24 10:22:22.042 debug ### DataPolling STOP ### sun2000.0 2026-10-24 10:22:22.042 debug Last read reg for 29940 ms - Power data sun2000.0 2026-10-24 10:22:22.042 debug Last read reg for 53906 ms - SDongle Device Search Status sun2000.0 2026-10-24 10:22:22.042 debug Update loop stopped sun2000.0 2026-10-24 10:22:22.042 warn Error while reading from 192.168.178.181 [Reg: 32000, Len: 11, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:22:22.042 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:22:22.034 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:22:20.033 debug Fetched inverter.0.derived.dailyActiveEnergy, val=2.2951827181 sun2000.0 2026-10-24 10:22:20.033 debug Fetched inverter.0.derived.dailySolarYield, val=1.0817529919 sun2000.0 2026-10-24 10:22:20.032 debug Fetched inverter.0.derived.dailyInputYield, val=0.7309605969 sun2000.0 2026-10-24 10:22:20.031 info Open Connection... sun2000.0 2026-10-24 10:22:20.031 debug Try to read data from id/address 2/32000/low/inverter status sun2000.0 2026-10-24 10:22:20.031 debug ### Duration: 3 used time: 10.001 sun2000.0 2026-10-24 10:22:20.031 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Timed out sun2000.0 2026-10-24 10:22:20.031 debug Modbus error: {"name":"TransactionTimedOutError","message":"Timed out","errno":"ETIMEDOUT"} sun2000.0 2026-10-24 10:22:10.078 debug Fetched collected.surplus.usablePower, val=0.381 sun2000.0 2026-10-24 10:22:10.078 debug Fetched collected.surplus.power, val=0.381 sun2000.0 2026-10-24 10:22:10.077 debug Fetched collected.chargeDischargePower, val=0.401 sun2000.0 2026-10-24 10:22:10.076 debug Fetched collected.houseConsumption, val=0.654 sun2000.0 2026-10-24 10:22:10.076 debug Fetched collected.activePower, val=0.634 sun2000.0 2026-10-24 10:22:10.075 debug Fetched collected.inputPowerWithEfficiencyLoss, val=0.9567 sun2000.0 2026-10-24 10:22:10.075 debug Fetched collected.inputPower, val=1.063 sun2000.0 2026-10-24 10:22:10.074 debug Fetched collected.sumDaily.feed-outPower, val=5.2009854986 sun2000.0 2026-10-24 10:22:10.074 debug Fetched collected.sumDaily.chargePower, val=0.7093044478 sun2000.0 2026-10-24 10:22:10.073 debug Fetched statistics.jsonToday, val={"consumption":{"value":7.896,"unit":"kWh","baseValue":7.896},"solarYield":{"value":1.462,"unit":"kWh"},"inputYield":{"value":1.12,"unit":"kWh"},"externalYield":{"value":0,"unit":"kWh"},"energyYield":{"value":2.87,"unit":"kWh"},"SOC":{"value":6,"unit":"%"},"chargeCapacity":{"value":0.63,"unit":"kWh"},"dischargeCapacity":{"value":2.11,"unit":"kWh"},"gridExport":{"value":0,"unit":"kWh"},"gridImport":{"value":5.21,"unit":"kWh"},"selfSufficiency":{"value":34,"unit":"%"},"selfConsumption":{"value":100,"unit":"%"},"updatedAt":"2026-10-24T10:22:10.000+02:00"} sun2000.0 2026-10-24 10:22:10.073 debug Fetched collected.sumDaily.inputPower, val=1.6085207869 sun2000.0 2026-10-24 10:22:10.073 debug Fetched collected.sumDaily.activePower, val=2.6820037872 sun2000.0 2026-10-24 10:22:10.072 debug Fetched collected.sumDaily.houseConsumption, val=7.8674779783 sun2000.0 2026-10-24 10:22:10.032 debug Fetched inverter.1.derived.inputPowerWithEfficiencyLoss, val=0.2619 sun2000.0 2026-10-24 10:22:10.031 debug Fetched inverter.1.inputPower, val=0.291 sun2000.0 2026-10-24 10:22:10.031 debug Try to read data from id/address 1/47075/low/additional battery information sun2000.0 2026-10-24 10:22:10.031 debug Last read reg for 41806 ms - battery information sun2000.0 2026-10-24 10:22:10.031 debug Last read reg for 41811 ms - battery information sun2000.0 2026-10-24 10:22:10.031 debug Last read reg for 41816 ms - battery Pack max/min Temperature of unit 1 sun2000.0 2026-10-24 10:22:10.030 debug statistics: jsonToday updated sun2000.0 2026-10-24 10:22:10.030 debug ### Caculate usableSurplus power 0.381 bufferOn false soc 6 minSoc 0 bufferSoc 0 threshold 0 sun2000.0 2026-10-24 10:22:10.030 debug activePower 0.27 !== inputPower 0.291-chargePower 0 sun2000.0 2026-10-24 10:22:10.027 debug Fetched inverter.0.battery.unit.1.chargeDischargePower, val=457 sun2000.0 2026-10-24 10:22:10.027 debug Fetched inverter.0.battery.chargeDischargePower, val=0.401 sun2000.0 2026-10-24 10:22:10.026 debug Fetched inverter.1.activePower, val=0.27 sun2000.0 2026-10-24 10:22:10.026 debug Fetched meter.derived.feed-inPower, val=-0.02 sun2000.0 2026-10-24 10:22:10.026 debug Fetched meter.activePowerL2, val=59 sun2000.0 2026-10-24 10:22:10.025 debug Try to read data from id/address 2/32064/high/Input Power sun2000.0 2026-10-24 10:22:10.025 debug Fetched meter.activePowerL1, val=-51 sun2000.0 2026-10-24 10:22:10.025 debug Fetched meter.voltageL3-L1, val=411.3 sun2000.0 2026-10-24 10:22:10.024 debug Fetched meter.voltageL2-L3, val=410.2 sun2000.0 2026-10-24 10:22:10.024 debug Fetched meter.voltageL1-L2, val=412.2 sun2000.0 2026-10-24 10:22:10.024 debug Fetched meter.powerFactor, val=-0.07 sun2000.0 2026-10-24 10:22:10.023 debug Fetched meter.activePower, val=-0.02 sun2000.0 2026-10-24 10:22:10.023 debug Fetched meter.currentL3, val=0.8 sun2000.0 2026-10-24 10:22:10.023 debug Fetched meter.currentL2, val=0.65 sun2000.0 2026-10-24 10:22:10.022 debug Fetched meter.voltageL3, val=236.3 sun2000.0 2026-10-24 10:22:10.022 debug Fetched meter.voltageL2, val=237.3 sun2000.0 2026-10-24 10:22:10.022 debug Fetched inverter.0.inputPower, val=0.772 sun2000.0 2026-10-24 10:22:10.021 debug Fetched inverter.0.activePower, val=0.364 sun2000.0 2026-10-24 10:22:10.020 debug Try to read data from id/address 2/32080/high/Inverter Activ Power sun2000.0 2026-10-24 10:22:10.020 debug activePower 0.364 !== inputPower 0.772-chargePower 0.401 sun2000.0 2026-10-24 10:22:10.017 debug Try to read data from id/address 1/37100/high/meter info sun2000.0 2026-10-24 10:22:00.016 debug Try to read data from id/address 1/37000/high/battery Unit1 information sun2000.0 2026-10-24 10:22:00.010 debug Try to read data from id/address 1/32064/high/Input Power sun2000.0 2026-10-24 10:22:00.005 debug Try to read data from id/address 1/37765/high/Battery Charge And Discharge Power sun2000.0 2026-10-24 10:22:00.000 debug Try to read data from id/address 1/32080/high/Inverter Activ Power sun2000.0 2026-10-24 10:22:00.000 debug ### DataPolling START 20 sec ### sun2000.0 2026-10-24 10:21:52.149 debug Fetched collected.consumptionToday, val=7.8955186919 sun2000.0 2026-10-24 10:21:52.149 debug Fetched sdongle.totalActivePower, val=0.602 sun2000.0 2026-10-24 10:21:52.105 debug Fetched collected.dailySolarYield, val=1.4620301517 sun2000.0 2026-10-24 10:21:52.105 debug Fetched sdongle.totalBatteryPower, val=0.423 sun2000.0 2026-10-24 10:21:52.104 debug Fetched sdongle.gridPower, val=0.03 sun2000.0 2026-10-24 10:21:52.104 debug Fetched collected.dailyInputYield, val=1.1203328716 sun2000.0 2026-10-24 10:21:52.104 debug Fetched sdongle.loadPower, val=0.632 sun2000.0 2026-10-24 10:21:52.103 debug Fetched sdongle.totalInputPower, val=1.032 sun2000.0 2026-10-24 10:21:52.103 debug Fetched inverter.1.string.PV1Power, val=304 sun2000.0 2026-10-24 10:21:52.102 debug ### DataPolling STOP ### sun2000.0 2026-10-24 10:21:52.082 debug Fetched inverter.1.string.PV1Current, val=1.53 sun2000.0 2026-10-24 10:21:52.082 debug Fetched inverter.1.string.PV1Voltage, val=198.5 sun2000.0 2026-10-24 10:21:52.082 debug Fetched inverter.1.derived.dailyActiveEnergy, val=0.392358095 sun2000.0 2026-10-24 10:21:52.081 debug Fetched inverter.1.derived.dailySolarYield, val=0.3841375458 sun2000.0 2026-10-24 10:21:52.081 debug Fetched inverter.1.derived.dailyInputYield, val=0.3906046047 sun2000.0 2026-10-24 10:21:52.080 debug Fetched collected.surplus.usablePower, val=0.403 sun2000.0 2026-10-24 10:21:52.080 debug Try to read data from id/address 100/37498/medium/Power data sun2000.0 2026-10-24 10:21:52.080 debug Last read reg for 23944 ms - SDongle Device Search Status sun2000.0 2026-10-24 10:21:52.080 debug Update loop stopped sun2000.0 2026-10-24 10:21:52.080 warn Error while reading from 192.168.178.181 [Reg: 32066, Len: 50, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:21:52.080 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:21:52.077 debug Try to read data from id/address 2/32066/low/inverter status sun2000.0 2026-10-24 10:21:52.077 debug Last read reg for 25910 ms - inverter deviceStatus sun2000.0 2026-10-24 10:21:52.042 debug Fetched collected.surplus.power, val=0.403 sun2000.0 2026-10-24 10:21:52.041 debug Fetched collected.chargeDischargePower, val=0.392 sun2000.0 2026-10-24 10:21:52.040 debug Fetched collected.houseConsumption, val=0.628 sun2000.0 2026-10-24 10:21:52.040 debug Fetched collected.activePower, val=0.639 sun2000.0 2026-10-24 10:21:52.039 debug Fetched collected.inputPowerWithEfficiencyLoss, val=0.9477 sun2000.0 2026-10-24 10:21:52.039 debug Fetched collected.inputPower, val=1.053 sun2000.0 2026-10-24 10:21:52.038 debug Fetched inverter.0.derived.dailyActiveEnergy, val=2.2931605969 sun2000.0 2026-10-24 10:21:52.038 debug Fetched collected.sumDaily.feed-inPower, val=0.0185113075 sun2000.0 2026-10-24 10:21:52.038 debug Fetched collected.sumDaily.chargePower, val=0.7072994478 sun2000.0 2026-10-24 10:21:52.037 debug Fetched inverter.0.derived.dailySolarYield, val=1.0778926059 sun2000.0 2026-10-24 10:21:52.037 debug Fetched statistics.jsonToday, val={"consumption":{"value":7.893,"unit":"kWh","baseValue":7.893},"solarYield":{"value":1.458,"unit":"kWh"},"inputYield":{"value":1.116,"unit":"kWh"},"externalYield":{"value":0,"unit":"kWh"},"energyYield":{"value":2.87,"unit":"kWh"},"SOC":{"value":6,"unit":"%"},"chargeCapacity":{"value":0.63,"unit":"kWh"},"dischargeCapacity":{"value":2.11,"unit":"kWh"},"gridExport":{"value":0,"unit":"kWh"},"gridImport":{"value":5.21,"unit":"kWh"},"selfSufficiency":{"value":34,"unit":"%"},"selfConsumption":{"value":100,"unit":"%"},"updatedAt":"2026-10-24T10:21:52.000+02:00"} sun2000.0 2026-10-24 10:21:52.037 debug Fetched collected.sumDaily.inputPower, val=1.6032057869 sun2000.0 2026-10-24 10:21:52.037 debug Fetched inverter.0.derived.dailyInputYield, val=0.7297282669 sun2000.0 2026-10-24 10:21:52.036 debug Fetched collected.sumDaily.activePower, val=2.6788337872 sun2000.0 2026-10-24 10:21:52.036 debug Fetched collected.sumDaily.houseConsumption, val=7.8642079783 sun2000.0 2026-10-24 10:21:52.035 debug Fetched inverter.1.derived.inputPowerWithEfficiencyLoss, val=0.2529 sun2000.0 2026-10-24 10:21:52.035 debug Try to read data from id/address 2/32016/medium/inverter PV strings sun2000.0 2026-10-24 10:21:52.035 debug Last read reg for 53039 ms - inverter status sun2000.0 2026-10-24 10:21:52.035 debug Update loop stopped sun2000.0 2026-10-24 10:21:52.035 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:21:52.035 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:21:52.031 debug Fetched inverter.1.inputPower, val=0.281 sun2000.0 2026-10-24 10:21:52.030 debug Try to read data from id/address 1/47075/low/additional battery information sun2000.0 2026-10-24 10:21:52.030 debug Last read reg for 23806 ms - battery information sun2000.0 2026-10-24 10:21:52.030 debug Last read reg for 23811 ms - battery information sun2000.0 2026-10-24 10:21:52.030 debug Last read reg for 23816 ms - battery Pack max/min Temperature of unit 1 sun2000.0 2026-10-24 10:21:52.030 debug statistics: jsonToday updated sun2000.0 2026-10-24 10:21:52.030 debug ### Caculate usableSurplus power 0.403 bufferOn false soc 6 minSoc 0 bufferSoc 0 threshold 0 sun2000.0 2026-10-24 10:21:52.030 debug activePower 0.265 !== inputPower 0.281-chargePower 0 sun2000.0 2026-10-24 10:21:52.027 debug Fetched inverter.0.battery.chargeDischargePower, val=0.392 sun2000.0 2026-10-24 10:21:52.026 debug Fetched inverter.1.activePower, val=0.265 sun2000.0 2026-10-24 10:21:52.026 debug Fetched meter.derived.feed-inPower, val=0.011 sun2000.0 2026-10-24 10:21:52.026 debug Fetched meter.activePowerL3, val=-27 sun2000.0 2026-10-24 10:21:52.026 debug Fetched meter.activePowerL2, val=88 sun2000.0 2026-10-24 10:21:52.025 debug Fetched meter.activePowerL1, val=-49 sun2000.0 2026-10-24 10:21:52.025 debug Try to read data from id/address 2/32064/high/Input Power sun2000.0 2026-10-24 10:21:52.025 debug Fetched meter.voltageL3-L1, val=411 sun2000.0 2026-10-24 10:21:52.024 debug Fetched meter.voltageL2-L3, val=409.6 sun2000.0 2026-10-24 10:21:52.024 debug Fetched meter.voltageL1-L2, val=412 sun2000.0 2026-10-24 10:21:52.023 debug Fetched meter.powerFactor, val=-0.063 sun2000.0 2026-10-24 10:21:52.023 debug Fetched meter.reactivePower, val=190 sun2000.0 2026-10-24 10:21:52.023 debug Fetched meter.activePower, val=0.011 sun2000.0 2026-10-24 10:21:52.022 debug Fetched meter.currentL2, val=0.69 sun2000.0 2026-10-24 10:21:52.022 debug Fetched meter.currentL1, val=-0.84 sun2000.0 2026-10-24 10:21:52.022 debug Fetched meter.voltageL2, val=237.1 sun2000.0 2026-10-24 10:21:52.021 debug Fetched meter.voltageL1, val=238.6 sun2000.0 2026-10-24 10:21:52.021 debug Fetched inverter.0.inputPower, val=0.772 sun2000.0 2026-10-24 10:21:52.021 debug Fetched inverter.0.activePower, val=0.374 sun2000.0 2026-10-24 10:21:52.020 debug Try to read data from id/address 2/32080/high/Inverter Activ Power sun2000.0 2026-10-24 10:21:52.020 debug activePower 0.374 !== inputPower 0.772-chargePower 0.392 sun2000.0 2026-10-24 10:21:52.015 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:21:50.014 info Open Connection... sun2000.0 2026-10-24 10:21:50.014 debug Try to read data from id/address 1/37100/high/meter info sun2000.0 2026-10-24 10:21:50.014 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 10:21:50.014 debug Modbus error: {"name":"TransactionTimedOutError","message":"Timed out","errno":"ETIMEDOUT"} sun2000.0 2026-10-24 10:21:49.631 debug {"timeout":10000,"delay":0,"connectDelay":2000,"modbusAdjust":false,"min":0,"max":6000,"maxDelay":200,"stat":{"successSumCounter":192,"errorSumCounter":100,"errorRate":34,"ETIMEDOUT":10},"adjust":{"successLevel":0,"successCounter":2,"errorCounter":0,"lastLength":2,"SuccessDelay":0,"ErrorDelay":0}} sun2000.0 2026-10-24 10:16:32.044 warn Error while reading from 192.168.178.181 [Reg: 38242, Len: 10, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:16:32.039 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:16:32.019 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:16:30.019 info Open Connection... sun2000.0 2026-10-24 10:16:30.018 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 10:16:12.154 warn Error while reading from 192.168.178.181 [Reg: 38242, Len: 10, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:16:12.108 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:16:12.105 info inverter 0 control: Service queue initialized sun2000.0 2026-10-24 10:16:12.019 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:16:10.018 info Open Connection... sun2000.0 2026-10-24 10:16:10.017 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 10:15:52.724 warn Error while reading from 192.168.178.181 [Reg: 38242, Len: 10, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:15:52.716 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:15:50.715 info Open Connection... sun2000.0 2026-10-24 10:15:50.715 info inverter 1 control: Service queue initialized sun2000.0 2026-10-24 10:15:50.655 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Timed out sun2000.0 2026-10-24 10:15:10.996 info Identified a Huawei SUN2000-5K-MAP0 model 1001 for modbus ID 2 sun2000.0 2026-10-24 10:15:05.400 info Identified a Huawei SUN2000-10KTL-M1 model 429 for modbus ID 1 sun2000.0 2026-10-24 10:14:51.734 warn Error while reading from 192.168.178.181 [Reg: 30000, Len: 71, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:14:51.734 error Can not connect to Huawei inverter for modbus ID 2! sun2000.0 2026-10-24 10:14:51.689 warn Error while reading from 192.168.178.181 [Reg: 30000, Len: 71, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:14:51.689 error Can not connect to Huawei inverter for modbus ID 1! sun2000.0 2026-10-24 10:14:51.679 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:14:49.678 info Open Connection... sun2000.0 2026-10-24 10:14:49.595 info starting. Version 2.7.3 in /opt/iobroker/node_modules/iobroker.sun2000, node: v22.23.3, js-controller: 7.2.5 sun2000.0 2026-10-24 10:14:45.749 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason sun2000.0 2026-10-24 10:14:45.749 info terminating sun2000.0 2026-10-24 10:14:45.749 info cleaned everything up... sun2000.0 2026-10-24 10:14:45.748 info Got terminate signal TERMINATE_YOURSELF sun2000.0 2026-10-24 10:14:45.702 info New modbus settings are stored. sun2000.0 2026-10-24 10:14:45.701 info Adjustment: It was completed successfully with delay value 0 ms sun2000.0 2026-10-24 10:14:29.730 info inverter 1 control: Service queue initialized sun2000.0 2026-10-24 10:14:29.667 info Adjustment: It has reached the step 9 with delay value 0 ms sun2000.0 2026-10-24 10:14:24.517 info inverter 0 control: Service queue initialized sun2000.0 2026-10-24 10:14:24.422 info Adjustment: It has reached the step 8 with delay value 0 ms sun2000.0 2026-10-24 10:14:16.730 info Adjustment: It has reached the step 7 with delay value 0 ms sun2000.0 2026-10-24 10:14:00.053 info Adjustment: It has reached the step 6 with delay value 0 ms sun2000.0 2026-10-24 10:14:00.028 info Adjustment: It has reached the step 5 with delay value 0 ms sun2000.0 2026-10-24 10:14:00.003 info Adjustment: It has reached the step 4 with delay value 0 ms sun2000.0 2026-10-24 10:13:46.268 info Adjustment: It has reached the step 3 with delay value 0 ms sun2000.0 2026-10-24 10:13:39.858 info Adjustment: It has reached the step 2 with delay value 0 ms sun2000.0 2026-10-24 10:13:39.748 info Adjustment: It has reached the step 1 with delay value 0 ms sun2000.0 2026-10-24 10:13:39.678 info Identified a Huawei SUN2000-5K-MAP0 model 1001 for modbus ID 2 sun2000.0 2026-10-24 10:13:32.035 info Identified a Huawei SUN2000-10KTL-M1 model 429 for modbus ID 1 sun2000.0 2026-10-24 10:13:23.676 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:13:18.674 info Open Connection... sun2000.0 2026-10-24 10:13:18.617 info Adjustment: It starts for the Modbus connection... sun2000.0 2026-10-24 10:13:18.591 info starting. Version 2.7.3 in /opt/iobroker/node_modules/iobroker.sun2000, node: v22.23.3, js-controller: 7.2.5 -
Guten Morgen,
jetzt hat mein Installateur den Smartdongle aktualisiert, mein SW Version ist nun: V200R025C00SPC141Deine Aussage verstehe ich nicht. Was greift bei dir per modbus wo zu?
Das sollte nur heißen, dass ich noch ein weiteres Gerät habe das im Netzt per Modbus kommuniziert (meine WP),. Aber die hat ja eine andere IP, hierzu verwende ich den iobroker Modbus Adapter. Soweit ich weiß hab ich kein Gerät ausser den sun2000 adapter der auf den Sdongle zugreift.
Selbst mit dem neuen SW Update sieht es im Log immernoch ähnlich aus, siehe Anhang.
sun2000.0 2026-10-24 10:22:36.089 info terminating sun2000.0 2026-10-24 10:22:36.089 info terminating sun2000.0 2026-10-24 10:22:35.586 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason sun2000.0 2026-10-24 10:22:35.586 debug Plugin sentry destroyed sun2000.0 2026-10-24 10:22:35.585 info terminating sun2000.0 2026-10-24 10:22:35.585 info cleaned everything up... sun2000.0 2026-10-24 10:22:35.585 info Got terminate signal TERMINATE_YOURSELF sun2000.0 2026-10-24 10:22:22.200 debug Fetched collected.consumptionToday, val=7.9018499547 sun2000.0 2026-10-24 10:22:22.159 debug Fetched sdongle.totalActivePower, val=0.62 sun2000.0 2026-10-24 10:22:22.158 debug Fetched collected.dailySolarYield, val=1.4724151487 sun2000.0 2026-10-24 10:22:22.158 debug Fetched sdongle.totalBatteryPower, val=0.455 sun2000.0 2026-10-24 10:22:22.157 debug Fetched sdongle.gridPower, val=0.043 sun2000.0 2026-10-24 10:22:22.157 debug Fetched collected.dailyInputYield, val=1.1266908131 sun2000.0 2026-10-24 10:22:22.157 debug Fetched sdongle.loadPower, val=0.663 sun2000.0 2026-10-24 10:22:22.156 debug Fetched sdongle.totalInputPower, val=1.045 sun2000.0 2026-10-24 10:22:22.156 debug Fetched inverter.1.derived.dailyActiveEnergy, val=0.39464287 sun2000.0 2026-10-24 10:22:22.156 debug ### DataPolling STOP ### sun2000.0 2026-10-24 10:22:22.153 debug Fetched inverter.1.derived.dailySolarYield, val=0.3863279756 sun2000.0 2026-10-24 10:22:22.153 debug Fetched inverter.1.derived.dailyInputYield, val=0.393708095 sun2000.0 2026-10-24 10:22:22.152 debug Fetched collected.surplus.usablePower, val=0.435 sun2000.0 2026-10-24 10:22:22.152 debug Fetched collected.surplus.power, val=0.435 sun2000.0 2026-10-24 10:22:22.151 debug Fetched collected.chargeDischargePower, val=0.455 sun2000.0 2026-10-24 10:22:22.151 debug Fetched collected.houseConsumption, val=0.628 sun2000.0 2026-10-24 10:22:22.151 debug Try to read data from id/address 100/37498/medium/Power data sun2000.0 2026-10-24 10:22:22.151 debug Last read reg for 54015 ms - SDongle Device Search Status sun2000.0 2026-10-24 10:22:22.151 debug Update loop stopped sun2000.0 2026-10-24 10:22:22.151 warn Error while reading from 192.168.178.181 [Reg: 32000, Len: 11, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:22:22.151 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:22:22.150 debug Fetched collected.activePower, val=0.608 sun2000.0 2026-10-24 10:22:22.150 debug Fetched collected.inputPowerWithEfficiencyLoss, val=0.9684 sun2000.0 2026-10-24 10:22:22.149 debug Fetched collected.inputPower, val=1.076 sun2000.0 2026-10-24 10:22:22.149 debug Fetched inverter.0.derived.dailyActiveEnergy, val=2.2972070847 sun2000.0 2026-10-24 10:22:22.148 debug Fetched collected.sumDaily.feed-outPower, val=5.2010527708 sun2000.0 2026-10-24 10:22:22.148 debug Fetched collected.sumDaily.chargePower, val=0.7108348908 sun2000.0 2026-10-24 10:22:22.148 debug Fetched inverter.0.derived.dailySolarYield, val=1.0860871731 sun2000.0 2026-10-24 10:22:22.148 debug Fetched statistics.jsonToday, val={"consumption":{"value":7.899,"unit":"kWh","baseValue":7.899},"solarYield":{"value":1.467,"unit":"kWh"},"inputYield":{"value":1.123,"unit":"kWh"},"externalYield":{"value":0,"unit":"kWh"},"energyYield":{"value":2.87,"unit":"kWh"},"SOC":{"value":6,"unit":"%"},"chargeCapacity":{"value":0.63,"unit":"kWh"},"dischargeCapacity":{"value":2.11,"unit":"kWh"},"gridExport":{"value":0,"unit":"kWh"},"gridImport":{"value":5.21,"unit":"kWh"},"selfSufficiency":{"value":34,"unit":"%"},"selfConsumption":{"value":100,"unit":"%"},"updatedAt":"2026-10-24T10:22:22.000+02:00"} sun2000.0 2026-10-24 10:22:22.147 debug Fetched collected.sumDaily.inputPower, val=1.6121400325 sun2000.0 2026-10-24 10:22:22.147 debug Fetched inverter.0.derived.dailyInputYield, val=0.7329827181 sun2000.0 2026-10-24 10:22:22.147 debug Fetched collected.sumDaily.activePower, val=2.6840488628 sun2000.0 2026-10-24 10:22:22.147 debug Fetched collected.sumDaily.houseConsumption, val=7.8695903261 sun2000.0 2026-10-24 10:22:22.146 debug Fetched inverter.1.inputPower, val=0.291 sun2000.0 2026-10-24 10:22:22.146 debug Try to read data from id/address 2/32000/low/inverter status sun2000.0 2026-10-24 10:22:22.146 debug Update loop stopped sun2000.0 2026-10-24 10:22:22.146 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:22:22.146 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:22:22.141 debug Fetched inverter.1.activePower, val=0.278 sun2000.0 2026-10-24 10:22:22.139 debug Try to read data from id/address 1/47075/low/additional battery information sun2000.0 2026-10-24 10:22:22.139 debug Last read reg for 53915 ms - battery information sun2000.0 2026-10-24 10:22:22.139 debug Last read reg for 53920 ms - battery information sun2000.0 2026-10-24 10:22:22.139 debug Last read reg for 53925 ms - battery Pack max/min Temperature of unit 1 sun2000.0 2026-10-24 10:22:22.139 debug statistics: jsonToday updated sun2000.0 2026-10-24 10:22:22.139 debug ### Caculate usableSurplus power 0.435 bufferOn false soc 6 minSoc 0 bufferSoc 0 threshold 0 sun2000.0 2026-10-24 10:22:22.139 debug activePower 0.278 !== inputPower 0.291-chargePower 0 sun2000.0 2026-10-24 10:22:22.130 debug Try to read data from id/address 2/32064/high/Input Power sun2000.0 2026-10-24 10:22:22.109 debug Fetched inverter.0.battery.chargeDischargePower, val=0.455 sun2000.0 2026-10-24 10:22:22.109 debug Fetched inverter.0.derived.inputPowerWithEfficiencyLoss, val=0.7065 sun2000.0 2026-10-24 10:22:22.108 debug Fetched inverter.0.inputPower, val=0.785 sun2000.0 2026-10-24 10:22:22.107 debug Fetched inverter.0.activePower, val=0.33 sun2000.0 2026-10-24 10:22:22.106 debug Try to read data from id/address 2/32080/high/Inverter Activ Power sun2000.0 2026-10-24 10:22:22.106 debug Update loop stopped sun2000.0 2026-10-24 10:22:22.106 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:22:22.106 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:22:22.101 debug Try to read data from id/address 1/37000/high/battery Unit1 information sun2000.0 2026-10-24 10:22:22.096 debug Try to read data from id/address 1/32064/high/Input Power sun2000.0 2026-10-24 10:22:22.089 debug Try to read data from id/address 1/37765/high/Battery Charge And Discharge Power sun2000.0 2026-10-24 10:22:22.086 debug Fetched collected.consumptionToday, val=7.8988908131 sun2000.0 2026-10-24 10:22:22.086 debug Fetched collected.dailySolarYield, val=1.4672000377 sun2000.0 2026-10-24 10:22:22.045 debug Fetched collected.dailyInputYield, val=1.1233186919 sun2000.0 2026-10-24 10:22:22.044 debug Fetched inverter.1.derived.dailyActiveEnergy, val=0.393708095 sun2000.0 2026-10-24 10:22:22.044 debug Fetched inverter.1.derived.dailySolarYield, val=0.3854470458 sun2000.0 2026-10-24 10:22:22.044 debug Fetched inverter.1.derived.dailyInputYield, val=0.392358095 sun2000.0 2026-10-24 10:22:22.043 debug Try to read data from id/address 1/32080/high/Inverter Activ Power sun2000.0 2026-10-24 10:22:22.043 debug Interval 22.043 sec sun2000.0 2026-10-24 10:22:22.043 debug ### DataPolling START 22 sec ### sun2000.0 2026-10-24 10:22:22.042 debug ### DataPolling STOP ### sun2000.0 2026-10-24 10:22:22.042 debug Last read reg for 29940 ms - Power data sun2000.0 2026-10-24 10:22:22.042 debug Last read reg for 53906 ms - SDongle Device Search Status sun2000.0 2026-10-24 10:22:22.042 debug Update loop stopped sun2000.0 2026-10-24 10:22:22.042 warn Error while reading from 192.168.178.181 [Reg: 32000, Len: 11, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:22:22.042 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:22:22.034 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:22:20.033 debug Fetched inverter.0.derived.dailyActiveEnergy, val=2.2951827181 sun2000.0 2026-10-24 10:22:20.033 debug Fetched inverter.0.derived.dailySolarYield, val=1.0817529919 sun2000.0 2026-10-24 10:22:20.032 debug Fetched inverter.0.derived.dailyInputYield, val=0.7309605969 sun2000.0 2026-10-24 10:22:20.031 info Open Connection... sun2000.0 2026-10-24 10:22:20.031 debug Try to read data from id/address 2/32000/low/inverter status sun2000.0 2026-10-24 10:22:20.031 debug ### Duration: 3 used time: 10.001 sun2000.0 2026-10-24 10:22:20.031 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Timed out sun2000.0 2026-10-24 10:22:20.031 debug Modbus error: {"name":"TransactionTimedOutError","message":"Timed out","errno":"ETIMEDOUT"} sun2000.0 2026-10-24 10:22:10.078 debug Fetched collected.surplus.usablePower, val=0.381 sun2000.0 2026-10-24 10:22:10.078 debug Fetched collected.surplus.power, val=0.381 sun2000.0 2026-10-24 10:22:10.077 debug Fetched collected.chargeDischargePower, val=0.401 sun2000.0 2026-10-24 10:22:10.076 debug Fetched collected.houseConsumption, val=0.654 sun2000.0 2026-10-24 10:22:10.076 debug Fetched collected.activePower, val=0.634 sun2000.0 2026-10-24 10:22:10.075 debug Fetched collected.inputPowerWithEfficiencyLoss, val=0.9567 sun2000.0 2026-10-24 10:22:10.075 debug Fetched collected.inputPower, val=1.063 sun2000.0 2026-10-24 10:22:10.074 debug Fetched collected.sumDaily.feed-outPower, val=5.2009854986 sun2000.0 2026-10-24 10:22:10.074 debug Fetched collected.sumDaily.chargePower, val=0.7093044478 sun2000.0 2026-10-24 10:22:10.073 debug Fetched statistics.jsonToday, val={"consumption":{"value":7.896,"unit":"kWh","baseValue":7.896},"solarYield":{"value":1.462,"unit":"kWh"},"inputYield":{"value":1.12,"unit":"kWh"},"externalYield":{"value":0,"unit":"kWh"},"energyYield":{"value":2.87,"unit":"kWh"},"SOC":{"value":6,"unit":"%"},"chargeCapacity":{"value":0.63,"unit":"kWh"},"dischargeCapacity":{"value":2.11,"unit":"kWh"},"gridExport":{"value":0,"unit":"kWh"},"gridImport":{"value":5.21,"unit":"kWh"},"selfSufficiency":{"value":34,"unit":"%"},"selfConsumption":{"value":100,"unit":"%"},"updatedAt":"2026-10-24T10:22:10.000+02:00"} sun2000.0 2026-10-24 10:22:10.073 debug Fetched collected.sumDaily.inputPower, val=1.6085207869 sun2000.0 2026-10-24 10:22:10.073 debug Fetched collected.sumDaily.activePower, val=2.6820037872 sun2000.0 2026-10-24 10:22:10.072 debug Fetched collected.sumDaily.houseConsumption, val=7.8674779783 sun2000.0 2026-10-24 10:22:10.032 debug Fetched inverter.1.derived.inputPowerWithEfficiencyLoss, val=0.2619 sun2000.0 2026-10-24 10:22:10.031 debug Fetched inverter.1.inputPower, val=0.291 sun2000.0 2026-10-24 10:22:10.031 debug Try to read data from id/address 1/47075/low/additional battery information sun2000.0 2026-10-24 10:22:10.031 debug Last read reg for 41806 ms - battery information sun2000.0 2026-10-24 10:22:10.031 debug Last read reg for 41811 ms - battery information sun2000.0 2026-10-24 10:22:10.031 debug Last read reg for 41816 ms - battery Pack max/min Temperature of unit 1 sun2000.0 2026-10-24 10:22:10.030 debug statistics: jsonToday updated sun2000.0 2026-10-24 10:22:10.030 debug ### Caculate usableSurplus power 0.381 bufferOn false soc 6 minSoc 0 bufferSoc 0 threshold 0 sun2000.0 2026-10-24 10:22:10.030 debug activePower 0.27 !== inputPower 0.291-chargePower 0 sun2000.0 2026-10-24 10:22:10.027 debug Fetched inverter.0.battery.unit.1.chargeDischargePower, val=457 sun2000.0 2026-10-24 10:22:10.027 debug Fetched inverter.0.battery.chargeDischargePower, val=0.401 sun2000.0 2026-10-24 10:22:10.026 debug Fetched inverter.1.activePower, val=0.27 sun2000.0 2026-10-24 10:22:10.026 debug Fetched meter.derived.feed-inPower, val=-0.02 sun2000.0 2026-10-24 10:22:10.026 debug Fetched meter.activePowerL2, val=59 sun2000.0 2026-10-24 10:22:10.025 debug Try to read data from id/address 2/32064/high/Input Power sun2000.0 2026-10-24 10:22:10.025 debug Fetched meter.activePowerL1, val=-51 sun2000.0 2026-10-24 10:22:10.025 debug Fetched meter.voltageL3-L1, val=411.3 sun2000.0 2026-10-24 10:22:10.024 debug Fetched meter.voltageL2-L3, val=410.2 sun2000.0 2026-10-24 10:22:10.024 debug Fetched meter.voltageL1-L2, val=412.2 sun2000.0 2026-10-24 10:22:10.024 debug Fetched meter.powerFactor, val=-0.07 sun2000.0 2026-10-24 10:22:10.023 debug Fetched meter.activePower, val=-0.02 sun2000.0 2026-10-24 10:22:10.023 debug Fetched meter.currentL3, val=0.8 sun2000.0 2026-10-24 10:22:10.023 debug Fetched meter.currentL2, val=0.65 sun2000.0 2026-10-24 10:22:10.022 debug Fetched meter.voltageL3, val=236.3 sun2000.0 2026-10-24 10:22:10.022 debug Fetched meter.voltageL2, val=237.3 sun2000.0 2026-10-24 10:22:10.022 debug Fetched inverter.0.inputPower, val=0.772 sun2000.0 2026-10-24 10:22:10.021 debug Fetched inverter.0.activePower, val=0.364 sun2000.0 2026-10-24 10:22:10.020 debug Try to read data from id/address 2/32080/high/Inverter Activ Power sun2000.0 2026-10-24 10:22:10.020 debug activePower 0.364 !== inputPower 0.772-chargePower 0.401 sun2000.0 2026-10-24 10:22:10.017 debug Try to read data from id/address 1/37100/high/meter info sun2000.0 2026-10-24 10:22:00.016 debug Try to read data from id/address 1/37000/high/battery Unit1 information sun2000.0 2026-10-24 10:22:00.010 debug Try to read data from id/address 1/32064/high/Input Power sun2000.0 2026-10-24 10:22:00.005 debug Try to read data from id/address 1/37765/high/Battery Charge And Discharge Power sun2000.0 2026-10-24 10:22:00.000 debug Try to read data from id/address 1/32080/high/Inverter Activ Power sun2000.0 2026-10-24 10:22:00.000 debug ### DataPolling START 20 sec ### sun2000.0 2026-10-24 10:21:52.149 debug Fetched collected.consumptionToday, val=7.8955186919 sun2000.0 2026-10-24 10:21:52.149 debug Fetched sdongle.totalActivePower, val=0.602 sun2000.0 2026-10-24 10:21:52.105 debug Fetched collected.dailySolarYield, val=1.4620301517 sun2000.0 2026-10-24 10:21:52.105 debug Fetched sdongle.totalBatteryPower, val=0.423 sun2000.0 2026-10-24 10:21:52.104 debug Fetched sdongle.gridPower, val=0.03 sun2000.0 2026-10-24 10:21:52.104 debug Fetched collected.dailyInputYield, val=1.1203328716 sun2000.0 2026-10-24 10:21:52.104 debug Fetched sdongle.loadPower, val=0.632 sun2000.0 2026-10-24 10:21:52.103 debug Fetched sdongle.totalInputPower, val=1.032 sun2000.0 2026-10-24 10:21:52.103 debug Fetched inverter.1.string.PV1Power, val=304 sun2000.0 2026-10-24 10:21:52.102 debug ### DataPolling STOP ### sun2000.0 2026-10-24 10:21:52.082 debug Fetched inverter.1.string.PV1Current, val=1.53 sun2000.0 2026-10-24 10:21:52.082 debug Fetched inverter.1.string.PV1Voltage, val=198.5 sun2000.0 2026-10-24 10:21:52.082 debug Fetched inverter.1.derived.dailyActiveEnergy, val=0.392358095 sun2000.0 2026-10-24 10:21:52.081 debug Fetched inverter.1.derived.dailySolarYield, val=0.3841375458 sun2000.0 2026-10-24 10:21:52.081 debug Fetched inverter.1.derived.dailyInputYield, val=0.3906046047 sun2000.0 2026-10-24 10:21:52.080 debug Fetched collected.surplus.usablePower, val=0.403 sun2000.0 2026-10-24 10:21:52.080 debug Try to read data from id/address 100/37498/medium/Power data sun2000.0 2026-10-24 10:21:52.080 debug Last read reg for 23944 ms - SDongle Device Search Status sun2000.0 2026-10-24 10:21:52.080 debug Update loop stopped sun2000.0 2026-10-24 10:21:52.080 warn Error while reading from 192.168.178.181 [Reg: 32066, Len: 50, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:21:52.080 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:21:52.077 debug Try to read data from id/address 2/32066/low/inverter status sun2000.0 2026-10-24 10:21:52.077 debug Last read reg for 25910 ms - inverter deviceStatus sun2000.0 2026-10-24 10:21:52.042 debug Fetched collected.surplus.power, val=0.403 sun2000.0 2026-10-24 10:21:52.041 debug Fetched collected.chargeDischargePower, val=0.392 sun2000.0 2026-10-24 10:21:52.040 debug Fetched collected.houseConsumption, val=0.628 sun2000.0 2026-10-24 10:21:52.040 debug Fetched collected.activePower, val=0.639 sun2000.0 2026-10-24 10:21:52.039 debug Fetched collected.inputPowerWithEfficiencyLoss, val=0.9477 sun2000.0 2026-10-24 10:21:52.039 debug Fetched collected.inputPower, val=1.053 sun2000.0 2026-10-24 10:21:52.038 debug Fetched inverter.0.derived.dailyActiveEnergy, val=2.2931605969 sun2000.0 2026-10-24 10:21:52.038 debug Fetched collected.sumDaily.feed-inPower, val=0.0185113075 sun2000.0 2026-10-24 10:21:52.038 debug Fetched collected.sumDaily.chargePower, val=0.7072994478 sun2000.0 2026-10-24 10:21:52.037 debug Fetched inverter.0.derived.dailySolarYield, val=1.0778926059 sun2000.0 2026-10-24 10:21:52.037 debug Fetched statistics.jsonToday, val={"consumption":{"value":7.893,"unit":"kWh","baseValue":7.893},"solarYield":{"value":1.458,"unit":"kWh"},"inputYield":{"value":1.116,"unit":"kWh"},"externalYield":{"value":0,"unit":"kWh"},"energyYield":{"value":2.87,"unit":"kWh"},"SOC":{"value":6,"unit":"%"},"chargeCapacity":{"value":0.63,"unit":"kWh"},"dischargeCapacity":{"value":2.11,"unit":"kWh"},"gridExport":{"value":0,"unit":"kWh"},"gridImport":{"value":5.21,"unit":"kWh"},"selfSufficiency":{"value":34,"unit":"%"},"selfConsumption":{"value":100,"unit":"%"},"updatedAt":"2026-10-24T10:21:52.000+02:00"} sun2000.0 2026-10-24 10:21:52.037 debug Fetched collected.sumDaily.inputPower, val=1.6032057869 sun2000.0 2026-10-24 10:21:52.037 debug Fetched inverter.0.derived.dailyInputYield, val=0.7297282669 sun2000.0 2026-10-24 10:21:52.036 debug Fetched collected.sumDaily.activePower, val=2.6788337872 sun2000.0 2026-10-24 10:21:52.036 debug Fetched collected.sumDaily.houseConsumption, val=7.8642079783 sun2000.0 2026-10-24 10:21:52.035 debug Fetched inverter.1.derived.inputPowerWithEfficiencyLoss, val=0.2529 sun2000.0 2026-10-24 10:21:52.035 debug Try to read data from id/address 2/32016/medium/inverter PV strings sun2000.0 2026-10-24 10:21:52.035 debug Last read reg for 53039 ms - inverter status sun2000.0 2026-10-24 10:21:52.035 debug Update loop stopped sun2000.0 2026-10-24 10:21:52.035 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:21:52.035 debug Modbus error: {"modbusCode":6} sun2000.0 2026-10-24 10:21:52.031 debug Fetched inverter.1.inputPower, val=0.281 sun2000.0 2026-10-24 10:21:52.030 debug Try to read data from id/address 1/47075/low/additional battery information sun2000.0 2026-10-24 10:21:52.030 debug Last read reg for 23806 ms - battery information sun2000.0 2026-10-24 10:21:52.030 debug Last read reg for 23811 ms - battery information sun2000.0 2026-10-24 10:21:52.030 debug Last read reg for 23816 ms - battery Pack max/min Temperature of unit 1 sun2000.0 2026-10-24 10:21:52.030 debug statistics: jsonToday updated sun2000.0 2026-10-24 10:21:52.030 debug ### Caculate usableSurplus power 0.403 bufferOn false soc 6 minSoc 0 bufferSoc 0 threshold 0 sun2000.0 2026-10-24 10:21:52.030 debug activePower 0.265 !== inputPower 0.281-chargePower 0 sun2000.0 2026-10-24 10:21:52.027 debug Fetched inverter.0.battery.chargeDischargePower, val=0.392 sun2000.0 2026-10-24 10:21:52.026 debug Fetched inverter.1.activePower, val=0.265 sun2000.0 2026-10-24 10:21:52.026 debug Fetched meter.derived.feed-inPower, val=0.011 sun2000.0 2026-10-24 10:21:52.026 debug Fetched meter.activePowerL3, val=-27 sun2000.0 2026-10-24 10:21:52.026 debug Fetched meter.activePowerL2, val=88 sun2000.0 2026-10-24 10:21:52.025 debug Fetched meter.activePowerL1, val=-49 sun2000.0 2026-10-24 10:21:52.025 debug Try to read data from id/address 2/32064/high/Input Power sun2000.0 2026-10-24 10:21:52.025 debug Fetched meter.voltageL3-L1, val=411 sun2000.0 2026-10-24 10:21:52.024 debug Fetched meter.voltageL2-L3, val=409.6 sun2000.0 2026-10-24 10:21:52.024 debug Fetched meter.voltageL1-L2, val=412 sun2000.0 2026-10-24 10:21:52.023 debug Fetched meter.powerFactor, val=-0.063 sun2000.0 2026-10-24 10:21:52.023 debug Fetched meter.reactivePower, val=190 sun2000.0 2026-10-24 10:21:52.023 debug Fetched meter.activePower, val=0.011 sun2000.0 2026-10-24 10:21:52.022 debug Fetched meter.currentL2, val=0.69 sun2000.0 2026-10-24 10:21:52.022 debug Fetched meter.currentL1, val=-0.84 sun2000.0 2026-10-24 10:21:52.022 debug Fetched meter.voltageL2, val=237.1 sun2000.0 2026-10-24 10:21:52.021 debug Fetched meter.voltageL1, val=238.6 sun2000.0 2026-10-24 10:21:52.021 debug Fetched inverter.0.inputPower, val=0.772 sun2000.0 2026-10-24 10:21:52.021 debug Fetched inverter.0.activePower, val=0.374 sun2000.0 2026-10-24 10:21:52.020 debug Try to read data from id/address 2/32080/high/Inverter Activ Power sun2000.0 2026-10-24 10:21:52.020 debug activePower 0.374 !== inputPower 0.772-chargePower 0.392 sun2000.0 2026-10-24 10:21:52.015 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:21:50.014 info Open Connection... sun2000.0 2026-10-24 10:21:50.014 debug Try to read data from id/address 1/37100/high/meter info sun2000.0 2026-10-24 10:21:50.014 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 10:21:50.014 debug Modbus error: {"name":"TransactionTimedOutError","message":"Timed out","errno":"ETIMEDOUT"} sun2000.0 2026-10-24 10:21:49.631 debug {"timeout":10000,"delay":0,"connectDelay":2000,"modbusAdjust":false,"min":0,"max":6000,"maxDelay":200,"stat":{"successSumCounter":192,"errorSumCounter":100,"errorRate":34,"ETIMEDOUT":10},"adjust":{"successLevel":0,"successCounter":2,"errorCounter":0,"lastLength":2,"SuccessDelay":0,"ErrorDelay":0}} sun2000.0 2026-10-24 10:16:32.044 warn Error while reading from 192.168.178.181 [Reg: 38242, Len: 10, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:16:32.039 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:16:32.019 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:16:30.019 info Open Connection... sun2000.0 2026-10-24 10:16:30.018 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 10:16:12.154 warn Error while reading from 192.168.178.181 [Reg: 38242, Len: 10, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:16:12.108 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:16:12.105 info inverter 0 control: Service queue initialized sun2000.0 2026-10-24 10:16:12.019 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:16:10.018 info Open Connection... sun2000.0 2026-10-24 10:16:10.017 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 10:15:52.724 warn Error while reading from 192.168.178.181 [Reg: 38242, Len: 10, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:15:52.716 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:15:50.715 info Open Connection... sun2000.0 2026-10-24 10:15:50.715 info inverter 1 control: Service queue initialized sun2000.0 2026-10-24 10:15:50.655 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Timed out sun2000.0 2026-10-24 10:15:10.996 info Identified a Huawei SUN2000-5K-MAP0 model 1001 for modbus ID 2 sun2000.0 2026-10-24 10:15:05.400 info Identified a Huawei SUN2000-10KTL-M1 model 429 for modbus ID 1 sun2000.0 2026-10-24 10:14:51.734 warn Error while reading from 192.168.178.181 [Reg: 30000, Len: 71, modbusID: 2] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:14:51.734 error Can not connect to Huawei inverter for modbus ID 2! sun2000.0 2026-10-24 10:14:51.689 warn Error while reading from 192.168.178.181 [Reg: 30000, Len: 71, modbusID: 1] with: Modbus exception 6: Slave device busy (retry request again later) sun2000.0 2026-10-24 10:14:51.689 error Can not connect to Huawei inverter for modbus ID 1! sun2000.0 2026-10-24 10:14:51.679 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:14:49.678 info Open Connection... sun2000.0 2026-10-24 10:14:49.595 info starting. Version 2.7.3 in /opt/iobroker/node_modules/iobroker.sun2000, node: v22.23.3, js-controller: 7.2.5 sun2000.0 2026-10-24 10:14:45.749 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason sun2000.0 2026-10-24 10:14:45.749 info terminating sun2000.0 2026-10-24 10:14:45.749 info cleaned everything up... sun2000.0 2026-10-24 10:14:45.748 info Got terminate signal TERMINATE_YOURSELF sun2000.0 2026-10-24 10:14:45.702 info New modbus settings are stored. sun2000.0 2026-10-24 10:14:45.701 info Adjustment: It was completed successfully with delay value 0 ms sun2000.0 2026-10-24 10:14:29.730 info inverter 1 control: Service queue initialized sun2000.0 2026-10-24 10:14:29.667 info Adjustment: It has reached the step 9 with delay value 0 ms sun2000.0 2026-10-24 10:14:24.517 info inverter 0 control: Service queue initialized sun2000.0 2026-10-24 10:14:24.422 info Adjustment: It has reached the step 8 with delay value 0 ms sun2000.0 2026-10-24 10:14:16.730 info Adjustment: It has reached the step 7 with delay value 0 ms sun2000.0 2026-10-24 10:14:00.053 info Adjustment: It has reached the step 6 with delay value 0 ms sun2000.0 2026-10-24 10:14:00.028 info Adjustment: It has reached the step 5 with delay value 0 ms sun2000.0 2026-10-24 10:14:00.003 info Adjustment: It has reached the step 4 with delay value 0 ms sun2000.0 2026-10-24 10:13:46.268 info Adjustment: It has reached the step 3 with delay value 0 ms sun2000.0 2026-10-24 10:13:39.858 info Adjustment: It has reached the step 2 with delay value 0 ms sun2000.0 2026-10-24 10:13:39.748 info Adjustment: It has reached the step 1 with delay value 0 ms sun2000.0 2026-10-24 10:13:39.678 info Identified a Huawei SUN2000-5K-MAP0 model 1001 for modbus ID 2 sun2000.0 2026-10-24 10:13:32.035 info Identified a Huawei SUN2000-10KTL-M1 model 429 for modbus ID 1 sun2000.0 2026-10-24 10:13:23.676 info Connected Modbus TCP to 192.168.178.181:502 sun2000.0 2026-10-24 10:13:18.674 info Open Connection... sun2000.0 2026-10-24 10:13:18.617 info Adjustment: It starts for the Modbus connection... sun2000.0 2026-10-24 10:13:18.591 info starting. Version 2.7.3 in /opt/iobroker/node_modules/iobroker.sun2000, node: v22.23.3, js-controller: 7.2.5@Christian-Kohlöffel der zeitliche Ablauf und die Häufigkeit der Fehler (exception 6) deuten auf erhebliche Kommunikationsprobleme hin.
Überprüfe die Verkabelung der RS485-Kaskade
Die Verbindung zwischen Master (Pin 1/3 oder 2/4 je nach Modell) und Slave muss absolut stabil sein. Wenn hier Pakete verloren gehen, wartet der Dongle auf den Slave, was zu Timeouts führt.
Prüfe bitte, ob ein geschirmtes, verdrilltes Kabel (Cat6/Cat7) für die RS485-Verbindung genutzt wurde und der Abschlusswiderstand korrekt gesetzt ist (falls die Kabellänge lang ist). Der Dongle steckt zwingend im Master-Wechselrichter (Modbus-ID 1), der Slave hat meist die ID 2.Könnte aber auch auf ein konkurrierenden modbus Zugriff hinweisen. Also bitte auch alles Abschalten was gleichzeitig auf den modbus zugreift! (evcc, HA, Apps, modbus Adapter, weitere sun2000 Instanzen...)
-
@Christian-Kohlöffel der zeitliche Ablauf und die Häufigkeit der Fehler (exception 6) deuten auf erhebliche Kommunikationsprobleme hin.
Überprüfe die Verkabelung der RS485-Kaskade
Die Verbindung zwischen Master (Pin 1/3 oder 2/4 je nach Modell) und Slave muss absolut stabil sein. Wenn hier Pakete verloren gehen, wartet der Dongle auf den Slave, was zu Timeouts führt.
Prüfe bitte, ob ein geschirmtes, verdrilltes Kabel (Cat6/Cat7) für die RS485-Verbindung genutzt wurde und der Abschlusswiderstand korrekt gesetzt ist (falls die Kabellänge lang ist). Der Dongle steckt zwingend im Master-Wechselrichter (Modbus-ID 1), der Slave hat meist die ID 2.Könnte aber auch auf ein konkurrierenden modbus Zugriff hinweisen. Also bitte auch alles Abschalten was gleichzeitig auf den modbus zugreift! (evcc, HA, Apps, modbus Adapter, weitere sun2000 Instanzen...)
Hat eine Weile gedauert, ich habe alle COM Kabel geprüft, sind korrekt und gut verbunden und auch geschirmt verdrillt. Die Kabellänge ist ca. 1m. Der Master hat den Dongle drin stecken und der Dongle ist per Kabel LAN am 2m entfernten Router gut verbunden.
Alle andere Modbus Kommunikation sind ausgeschaltet. Alles neu gestartet und Einstellungen im Master Wechselrichter geprüft. Ich hab auch die Delay und Warte Zeiten im Adapter selbst ziemlich hoch gesetzt.
Nun gibt es eigentlich keine sporadischen Fehler mehr, sondern nur noch 2 relevante Fehler, die beide irgendwas mit der Batterie zu tun haben:
sun2000.0 2026-10-24 13:34:36.704 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:34:19.401 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:34:10.436 warn Not all data can be read! sun2000.0 2026-10-24 13:33:56.698 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:33:39.659 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:33:22.099 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:33:04.536 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:32:46.776 warn Error while reading from 192.168.178.181 [Reg: 32000, Len: 11, modbusID: 2] with: Timed out sun2000.0 2026-10-24 13:32:10.436 warn Not all data can be read! sun2000.0 2026-10-24 13:30:10.435 warn Not all data can be read! sun2000.0 2026-10-24 13:28:31.723 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:28:11.937 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:28:10.433 warn Not all data can be read! sun2000.0 2026-10-24 13:27:51.707 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:27:31.943 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:24:10.430 warn Not all data can be read! sun2000.0 2026-10-24 13:22:51.944 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:22:31.939 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:20:10.428 warn Not all data can be read! sun2000.0 2026-10-24 13:19:59.476 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Timed out -
Hat eine Weile gedauert, ich habe alle COM Kabel geprüft, sind korrekt und gut verbunden und auch geschirmt verdrillt. Die Kabellänge ist ca. 1m. Der Master hat den Dongle drin stecken und der Dongle ist per Kabel LAN am 2m entfernten Router gut verbunden.
Alle andere Modbus Kommunikation sind ausgeschaltet. Alles neu gestartet und Einstellungen im Master Wechselrichter geprüft. Ich hab auch die Delay und Warte Zeiten im Adapter selbst ziemlich hoch gesetzt.
Nun gibt es eigentlich keine sporadischen Fehler mehr, sondern nur noch 2 relevante Fehler, die beide irgendwas mit der Batterie zu tun haben:
sun2000.0 2026-10-24 13:34:36.704 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:34:19.401 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:34:10.436 warn Not all data can be read! sun2000.0 2026-10-24 13:33:56.698 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:33:39.659 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:33:22.099 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:33:04.536 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:32:46.776 warn Error while reading from 192.168.178.181 [Reg: 32000, Len: 11, modbusID: 2] with: Timed out sun2000.0 2026-10-24 13:32:10.436 warn Not all data can be read! sun2000.0 2026-10-24 13:30:10.435 warn Not all data can be read! sun2000.0 2026-10-24 13:28:31.723 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:28:11.937 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:28:10.433 warn Not all data can be read! sun2000.0 2026-10-24 13:27:51.707 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:27:31.943 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:24:10.430 warn Not all data can be read! sun2000.0 2026-10-24 13:22:51.944 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:22:31.939 warn Error while reading from 192.168.178.181 [Reg: 37000, Len: 23, modbusID: 1] with: Timed out sun2000.0 2026-10-24 13:20:10.428 warn Not all data can be read! sun2000.0 2026-10-24 13:19:59.476 warn Error while reading from 192.168.178.181 [Reg: 47075, Len: 14, modbusID: 1] with: Timed out
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
521
Online33.1k
Benutzer84.2k
Themen1.4m
Beiträge