FoxEss H3 Wechselrichter per Modbus in ioBroker
-
Ich bräuchte Hilfe um die FoxESS H3 Smart Werte im iobroker anzuzeigen.
Dies ist mein Konverter https://www.waveshare.com/wiki/RS485_TO_ETH_(C):
und seine Einstellungen aus dem WebUI:
oder per VirCom:
Der Wechselrichter hat die Default-ID 247.
Anschlussbild (I):
Kabelbelegung 1&2:
Im modbus Adapter:
Wie hier im Threat geschrieben, habe ich ein Register eingetragen:
Log vom Start:
2026-02-21 15:41:40.794 - info: modbus.0 (121590) starting. Version 8.0.3 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-02-21 15:41:40.823 - error: modbus.0 (121590) Invalid holdingRegisters address: -10001 2026-02-21 15:41:40.823 - debug: modbus.0 (121590) Initialize Objects for disInputs: [] 2026-02-21 15:41:40.823 - debug: modbus.0 (121590) Initialize Objects for coils: [] 2026-02-21 15:41:40.823 - debug: modbus.0 (121590) Initialize Objects for inputRegs: [] 2026-02-21 15:41:40.823 - debug: modbus.0 (121590) Initialize Objects for holdingRegs: [{"_address":"30000","address":-10001,"name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","type":"int16be","len":1,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":247}] 2026-02-21 15:41:40.823 - error: modbus.0 (121590) Invalid data holdingRegisters/0: {"_address":"30000","address":-10001,"name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","type":"int16be","len":1,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":247,"fullId":"modbus.0.0"} 2026-02-21 15:41:40.823 - error: modbus.0 (121590) Invalid object: {"type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"number","read":true,"write":true,"def":0,"unit":""},"native":{"regType":"holdingRegs","address":-10001,"deviceId":247,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}} 2026-02-21 15:41:40.823 - debug: modbus.0 (121590) Add undefined: {"type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"number","read":true,"write":true,"def":0,"unit":""},"native":{"regType":"holdingRegs","address":-10001,"deviceId":247,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}} 2026-02-21 15:41:40.871 - info: modbus.0 (121590) Can not execute task add for ID undefined: Parameter "id" needs to be of type "string" but type "undefined" has been passed 2026-02-21 15:41:40.888 - info: modbus.0 (121590) Connected to slave 192.168.178.80 2026-02-21 15:41:40.888 - debug: modbus.0 (121590) [DevID_247] Poll start --------------------- 2026-02-21 15:41:41.041 - debug: modbus.0 (121590) No current request. 2026-02-21 15:41:41.391 - debug: modbus.0 (121590) No current request. 2026-02-21 15:41:41.741 - debug: modbus.0 (121590) No current request.danach als String definiert:
2026-02-21 16:10:34.566 - info: modbus.0 (124436) starting. Version 8.0.3 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-02-21 16:10:34.596 - error: modbus.0 (124436) Invalid holdingRegisters address: -10001 2026-02-21 16:10:34.596 - debug: modbus.0 (124436) Initialize Objects for disInputs: [] 2026-02-21 16:10:34.596 - debug: modbus.0 (124436) Initialize Objects for coils: [] 2026-02-21 16:10:34.596 - debug: modbus.0 (124436) Initialize Objects for inputRegs: [] 2026-02-21 16:10:34.596 - debug: modbus.0 (124436) Initialize Objects for holdingRegs: [{"_address":"30000","address":-10001,"name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","type":"string16","len":2,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":247}] 2026-02-21 16:10:34.596 - error: modbus.0 (124436) Invalid data holdingRegisters/0: {"_address":"30000","address":-10001,"name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","type":"string16","len":2,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":247,"fullId":"modbus.0.0"} 2026-02-21 16:10:34.596 - error: modbus.0 (124436) Invalid object: {"type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"string","read":true,"write":true,"def":"","unit":""},"native":{"regType":"holdingRegs","address":-10001,"deviceId":247,"type":"string16","len":2,"offset":0,"factor":1,"poll":true}} 2026-02-21 16:10:34.596 - debug: modbus.0 (124436) Add undefined: {"type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"string","read":true,"write":true,"def":"","unit":""},"native":{"regType":"holdingRegs","address":-10001,"deviceId":247,"type":"string16","len":2,"offset":0,"factor":1,"poll":true}} 2026-02-21 16:10:34.641 - info: modbus.0 (124436) Can not execute task add for ID undefined: Parameter "id" needs to be of type "string" but type "undefined" has been passed 2026-02-21 16:10:34.657 - info: modbus.0 (124436) Connected to slave 192.168.178.80 2026-02-21 16:10:34.658 - debug: modbus.0 (124436) [DevID_247] Poll start --------------------- 2026-02-21 16:10:34.966 - debug: modbus.0 (124436) No current request. 2026-02-21 16:10:35.315 - debug: modbus.0 (124436) No current request. 2026-02-21 16:10:35.666 - debug: modbus.0 (124436) No current request.Jemand eine Idee was ich falsch gemacht habe?
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
danach als String definiert:
was?
dem log nach
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
task add for ID undefined:
geht es anscheinend um die ID!
Lösch diese nochmal,ggf. zwischenspeichern, und erneut eintragen.
Ansonsten mal ein downgrade des Adapters. die 8.0.3 dürfte nicht stable sein. wo hast du due her?
kein Support per PN! - Fragen im Forum stellen -
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton im Header. Danke!
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash - -
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
danach als String definiert:
was?
dem log nach
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
task add for ID undefined:
geht es anscheinend um die ID!
Lösch diese nochmal,ggf. zwischenspeichern, und erneut eintragen.
Ansonsten mal ein downgrade des Adapters. die 8.0.3 dürfte nicht stable sein. wo hast du due her?
geht es anscheinend um die ID
Probier mal mit einem Modbus-Tester, ob die ID 247 überhaupt erreichbar ist - z.B.
Raspberry PI5 mit Linux Debian 13, IoBroker v7.7.22, VIS-2, MariaDB (MySQL)
Shellies: 1G4, 1MiniG3, PlusI4DC, PlusPlugS, Pro0110PM, ProSmoke. Modbus: Waveshare Relay 8 Channels, Waveshare RS485-TO-ETH.
PV: 10 kWp Module, 2 x Deye WR SUN-10K, 3 x 10 kWh MeritSun LiFe Speicher, KEBA P30 Wallbox, Fronius Wattpilot home 11 -
geht es anscheinend um die ID
Probier mal mit einem Modbus-Tester, ob die ID 247 überhaupt erreichbar ist - z.B.
@fuzzy1955 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
ob die ID 247 überhaupt erreichbar ist
das sollte hier nicht das Problem srin, die Meldung meckert den Wertetyp an:
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
Parameter "id" needs to be of type "string" but type "undefined" has been passed
-
geht es anscheinend um die ID
Probier mal mit einem Modbus-Tester, ob die ID 247 überhaupt erreichbar ist - z.B.
@fuzzy1955
192.168.178.80 ist die Adresse des Waveshare RS4852ETH.
192.168.178.99 die Adresse des Wechselrichters.
-
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
danach als String definiert:
was?
dem log nach
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
task add for ID undefined:
geht es anscheinend um die ID!
Lösch diese nochmal,ggf. zwischenspeichern, und erneut eintragen.
Ansonsten mal ein downgrade des Adapters. die 8.0.3 dürfte nicht stable sein. wo hast du due her?
@Homoran
Ok, ich hatte die Model number als ID verstanden, da im Kommentar steht Model number of the inverter (8 chars, space padded). Daher im 2. Versuch die Model Number als String definiert."Ansonsten mal ein downgrade des Adapters. die 8.0.3 dürfte nicht stable sein. wo hast du due her?"
Ich folge dem Beta-Repo.
Habe jetzt die aus dem Stable Repo installiert.
Versuch mit Waveshare (.80):2026-02-21 22:04:43.371 - info: modbus.0 (157715) starting. Version 5.0.11 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-02-21 22:04:43.412 - error: modbus.0 (157715) Invalid holdingRegisters address: -10001 2026-02-21 22:04:43.412 - debug: modbus.0 (157715) Initialize Objects for disInputs: [] 2026-02-21 22:04:43.412 - debug: modbus.0 (157715) Initialize Objects for coils: [] 2026-02-21 22:04:43.413 - debug: modbus.0 (157715) Initialize Objects for inputRegs: [] 2026-02-21 22:04:43.413 - debug: modbus.0 (157715) Initialize Objects for holdingRegs: [{"_address":"30000","name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","unit":"","type":"int16be","len":1,"factor":1,"offset":0,"formula":"","role":"","room":"","poll":true,"wp":"","cw":"","isScale":"","address":-10001,"deviceId":247}] 2026-02-21 22:04:43.413 - error: modbus.0 (157715) Invalid data holdingRegisters/0: {"_address":"30000","name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","unit":"","type":"int16be","len":1,"factor":1,"offset":0,"formula":"","role":"","room":"","poll":true,"wp":"","cw":"","isScale":"","address":-10001,"deviceId":247,"fullId":"modbus.0.0"} 2026-02-21 22:04:43.413 - error: modbus.0 (157715) Invalid object: {"type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"number","read":true,"write":true,"def":0,"unit":""},"native":{"regType":"holdingRegs","address":-10001,"deviceId":247,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}} 2026-02-21 22:04:43.413 - debug: modbus.0 (157715) Add undefined: {"type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"number","read":true,"write":true,"def":0,"unit":""},"native":{"regType":"holdingRegs","address":-10001,"deviceId":247,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}} 2026-02-21 22:04:43.458 - info: modbus.0 (157715) Can not execute task add for ID undefined: Parameter "id" needs to be of type "string" but type "undefined" has been passed 2026-02-21 22:04:43.493 - info: modbus.0 (157715) Connected to slave 192.168.178.80 2026-02-21 22:04:43.493 - debug: modbus.0 (157715) [DevID_247] Poll start --------------------- 2026-02-21 22:04:43.667 - debug: modbus.0 (157715) No current request. 2026-02-21 22:04:44.017 - debug: modbus.0 (157715) No current request. 2026-02-21 22:04:44.367 - debug: modbus.0 (157715) No current request.Versuch mit H3 (IP .99):
2026-02-22 16:25:39.657 - info: modbus.0 (260646) starting. Version 5.0.11 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-02-22 16:25:39.700 - error: modbus.0 (260646) Invalid holdingRegisters address: -10001 2026-02-22 16:25:39.700 - debug: modbus.0 (260646) Initialize Objects for disInputs: [] 2026-02-22 16:25:39.700 - debug: modbus.0 (260646) Initialize Objects for coils: [] 2026-02-22 16:25:39.700 - debug: modbus.0 (260646) Initialize Objects for inputRegs: [] 2026-02-22 16:25:39.700 - debug: modbus.0 (260646) Initialize Objects for holdingRegs: [{"_address":"30000","name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","unit":"","type":"int16be","len":1,"factor":1,"offset":0,"formula":"","role":"","room":"","poll":true,"wp":"","cw":"","isScale":"","address":-10001,"deviceId":247}] 2026-02-22 16:25:39.700 - error: modbus.0 (260646) Invalid data holdingRegisters/0: {"_address":"30000","name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","unit":"","type":"int16be","len":1,"factor":1,"offset":0,"formula":"","role":"","room":"","poll":true,"wp":"","cw":"","isScale":"","address":-10001,"deviceId":247,"fullId":"modbus.0.0"} 2026-02-22 16:25:39.700 - error: modbus.0 (260646) Invalid object: {"type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"number","read":true,"write":true,"def":0,"unit":""},"native":{"regType":"holdingRegs","address":-10001,"deviceId":247,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}} 2026-02-22 16:25:39.700 - debug: modbus.0 (260646) Add undefined: {"type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"number","read":true,"write":true,"def":0,"unit":""},"native":{"regType":"holdingRegs","address":-10001,"deviceId":247,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}} 2026-02-22 16:25:39.746 - info: modbus.0 (260646) Can not execute task add for ID undefined: Parameter "id" needs to be of type "string" but type "undefined" has been passed 2026-02-22 16:25:39.782 - info: modbus.0 (260646) Connected to slave 192.168.178.99 2026-02-22 16:25:39.782 - debug: modbus.0 (260646) [DevID_247] Poll start --------------------- 2026-02-22 16:25:40.833 - debug: modbus.0 (260646) [DevID_247] Poll start --------------------- -
Also ich bin ein Stück weitergekommen.
Invalid holdingRegisters address: -10001
Hier ist mir aufgefallen, dass sich die Adresse ändert, wenn man das Holding Register verändert. Trägt man da 40001 ein, so kommt der Fehler nicht mehr und auch die ID-Fehlermeldung kommt nicht mehr.2026-02-22 16:42:41.507 - info: modbus.0 (262572) starting. Version 5.0.11 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for disInputs: [] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for coils: [] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for inputRegs: [] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for holdingRegs: [{"_address":"40001","name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","unit":"","type":"int16be","len":1,"factor":1,"offset":0,"formula":"","role":"","room":"","poll":true,"wp":"","cw":"","isScale":"","address":0,"deviceId":247,"id":"holdingRegisters.40001_Inverter_Model"}] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Add holdingRegisters.40001_Inverter_Model: {"_id":"holdingRegisters.40001_Inverter_Model","type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"number","read":true,"write":true,"def":0,"unit":""},"native":{"regType":"holdingRegs","address":0,"deviceId":247,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}} 2026-02-22 16:42:41.633 - info: modbus.0 (262572) Connected to slave 192.168.178.99 2026-02-22 16:42:41.633 - debug: modbus.0 (262572) [DevID_247] Poll start --------------------- 2026-02-22 16:42:41.633 - debug: modbus.0 (262572) Initialization of scale factors done! 2026-02-22 16:42:41.633 - debug: modbus.0 (262572) [DevID_247/holdingRegs] Poll address 0 - 1 registers 2026-02-22 16:42:46.634 - warn: modbus.0 (262572) Error: undefined 2026-02-22 16:42:46.634 - error: modbus.0 (262572) Request timed out. 2026-02-22 16:42:46.634 - error: modbus.0 (262572) Client in error state. 2026-02-22 16:42:46.634 - warn: modbus.0 (262572) Poll error count: 1 code: {"err":"timeout","timeout":5000}Gleicher Ablauf mit der Adresse des Wavshares.
-
Also ich bin ein Stück weitergekommen.
Invalid holdingRegisters address: -10001
Hier ist mir aufgefallen, dass sich die Adresse ändert, wenn man das Holding Register verändert. Trägt man da 40001 ein, so kommt der Fehler nicht mehr und auch die ID-Fehlermeldung kommt nicht mehr.2026-02-22 16:42:41.507 - info: modbus.0 (262572) starting. Version 5.0.11 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for disInputs: [] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for coils: [] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for inputRegs: [] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for holdingRegs: [{"_address":"40001","name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","unit":"","type":"int16be","len":1,"factor":1,"offset":0,"formula":"","role":"","room":"","poll":true,"wp":"","cw":"","isScale":"","address":0,"deviceId":247,"id":"holdingRegisters.40001_Inverter_Model"}] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Add holdingRegisters.40001_Inverter_Model: {"_id":"holdingRegisters.40001_Inverter_Model","type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"number","read":true,"write":true,"def":0,"unit":""},"native":{"regType":"holdingRegs","address":0,"deviceId":247,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}} 2026-02-22 16:42:41.633 - info: modbus.0 (262572) Connected to slave 192.168.178.99 2026-02-22 16:42:41.633 - debug: modbus.0 (262572) [DevID_247] Poll start --------------------- 2026-02-22 16:42:41.633 - debug: modbus.0 (262572) Initialization of scale factors done! 2026-02-22 16:42:41.633 - debug: modbus.0 (262572) [DevID_247/holdingRegs] Poll address 0 - 1 registers 2026-02-22 16:42:46.634 - warn: modbus.0 (262572) Error: undefined 2026-02-22 16:42:46.634 - error: modbus.0 (262572) Request timed out. 2026-02-22 16:42:46.634 - error: modbus.0 (262572) Client in error state. 2026-02-22 16:42:46.634 - warn: modbus.0 (262572) Poll error count: 1 code: {"err":"timeout","timeout":5000}Gleicher Ablauf mit der Adresse des Wavshares.
-
Also ich bin ein Stück weitergekommen.
Invalid holdingRegisters address: -10001
Hier ist mir aufgefallen, dass sich die Adresse ändert, wenn man das Holding Register verändert. Trägt man da 40001 ein, so kommt der Fehler nicht mehr und auch die ID-Fehlermeldung kommt nicht mehr.2026-02-22 16:42:41.507 - info: modbus.0 (262572) starting. Version 5.0.11 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for disInputs: [] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for coils: [] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for inputRegs: [] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Initialize Objects for holdingRegs: [{"_address":"40001","name":"Inverter Model","description":"Model number of the inverter (8 chars, space padded)","unit":"","type":"int16be","len":1,"factor":1,"offset":0,"formula":"","role":"","room":"","poll":true,"wp":"","cw":"","isScale":"","address":0,"deviceId":247,"id":"holdingRegisters.40001_Inverter_Model"}] 2026-02-22 16:42:41.550 - debug: modbus.0 (262572) Add holdingRegisters.40001_Inverter_Model: {"_id":"holdingRegisters.40001_Inverter_Model","type":"state","common":{"name":"Model number of the inverter (8 chars, space padded)","role":"","type":"number","read":true,"write":true,"def":0,"unit":""},"native":{"regType":"holdingRegs","address":0,"deviceId":247,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}} 2026-02-22 16:42:41.633 - info: modbus.0 (262572) Connected to slave 192.168.178.99 2026-02-22 16:42:41.633 - debug: modbus.0 (262572) [DevID_247] Poll start --------------------- 2026-02-22 16:42:41.633 - debug: modbus.0 (262572) Initialization of scale factors done! 2026-02-22 16:42:41.633 - debug: modbus.0 (262572) [DevID_247/holdingRegs] Poll address 0 - 1 registers 2026-02-22 16:42:46.634 - warn: modbus.0 (262572) Error: undefined 2026-02-22 16:42:46.634 - error: modbus.0 (262572) Request timed out. 2026-02-22 16:42:46.634 - error: modbus.0 (262572) Client in error state. 2026-02-22 16:42:46.634 - warn: modbus.0 (262572) Poll error count: 1 code: {"err":"timeout","timeout":5000}Gleicher Ablauf mit der Adresse des Wavshares.
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
Invalid holdingRegisters address: -10001
das klingt nach falschen Grundeinstellungen!
Alias verwenden aktiviert?
-
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
Invalid holdingRegisters address: -10001
das klingt nach falschen Grundeinstellungen!
Alias verwenden aktiviert?
@Homoran
Ja, die Selektion ist Standard. Jetzt deaktiviert.
Die ersten beiden Register laut Doku sind Model und SN:
die habe ich jetzt eingetragen:
Ergebnis:
Hier die Ausgabe vom GModbus:
Also scheint die FW des H3 Modbus über TCP (LAN-Kabel) zu unterstützen und das RS4852ETH ist überflüssig.
Hatte hier gelesen, dass nach dem Eintrag von ein paar Register, die restlichen automatische gelesen wurden. Stimmt das?
-
@Homoran
Ja, die Selektion ist Standard. Jetzt deaktiviert.
Die ersten beiden Register laut Doku sind Model und SN:
die habe ich jetzt eingetragen:
Ergebnis:
Hier die Ausgabe vom GModbus:
Also scheint die FW des H3 Modbus über TCP (LAN-Kabel) zu unterstützen und das RS4852ETH ist überflüssig.
Hatte hier gelesen, dass nach dem Eintrag von ein paar Register, die restlichen automatische gelesen wurden. Stimmt das?
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
Hatte hier gelesen, dass nach dem Eintrag von ein paar Register, die restlichen automatische gelesen wurden. Stimmt das?
im Modbus Adapter? nein!
in deinem Tool? möglich, aber kenn ich nicht -
Ich melde mich nochmal, weil ich hier gelesen habe, dass das Auslesen per TCP nicht empfohlen wird. Daher habe ich mir Waveshare RS485 TO ETH Converter
installiert. Hier bekam ich aber keine Verbindung zu H3 Smart. Der Wechselrichter geht in einen Fehlerstatus, wenn man in den Einstellungen "Meter 1" oder "2" aktiviert und trennt die PV-Seite sofort.
Dann habe ich den beim WR mitgelieferten Chint-DTSU666 mit einer Phase und dem Modbus-Kabel (ID 147) verbunden.
Am WR habe ich den COM-Port genommen.
Die ID 247 im WR unverändert gelassen.
Alles zusammengebaut und "Meter 1" wieder aktiviert. Aber auch hier zeigt der WR sofort den obigen Fehler an.
Um zu sehen, ob er überhaupt ansprechbar ist, habe ich mir das Interface USB2Modbus von Waveshare gekauft. Aber auch damit habe ich keine Daten auslesen können bzw. auch damit zeigt der WR den Fehler.D:\>modpoll -b 9600 -p none -m rtu -a 247 -r 30000 -c 32 COM9 modpoll 3.16 - FieldTalk(tm) Modbus(R) Master Simulator Copyright (c) 2002-2025 proconX Pty Ltd Visit https://www.modbusdriver.com for Modbus libraries and tools. Protocol configuration: Modbus RTU, FC3 Slave configuration...: address = 247, start reference = 30000, count = 32 Communication.........: COM9, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms Data type.............: 16-bit register, holding register table -- Polling slave... (Ctrl-C to stop) Reply time-out!Der Smartmeter (147) antwortet mir darüber.
Weiß jemand, was ich vergessen habe zu konfigurieren bzw. welchen Fehler ich gemacht habe?
Im Menübaum sehe ich keine weiteren Einstellungen zu diesem Thema.
-
Ich melde mich nochmal, weil ich hier gelesen habe, dass das Auslesen per TCP nicht empfohlen wird. Daher habe ich mir Waveshare RS485 TO ETH Converter
installiert. Hier bekam ich aber keine Verbindung zu H3 Smart. Der Wechselrichter geht in einen Fehlerstatus, wenn man in den Einstellungen "Meter 1" oder "2" aktiviert und trennt die PV-Seite sofort.
Dann habe ich den beim WR mitgelieferten Chint-DTSU666 mit einer Phase und dem Modbus-Kabel (ID 147) verbunden.
Am WR habe ich den COM-Port genommen.
Die ID 247 im WR unverändert gelassen.
Alles zusammengebaut und "Meter 1" wieder aktiviert. Aber auch hier zeigt der WR sofort den obigen Fehler an.
Um zu sehen, ob er überhaupt ansprechbar ist, habe ich mir das Interface USB2Modbus von Waveshare gekauft. Aber auch damit habe ich keine Daten auslesen können bzw. auch damit zeigt der WR den Fehler.D:\>modpoll -b 9600 -p none -m rtu -a 247 -r 30000 -c 32 COM9 modpoll 3.16 - FieldTalk(tm) Modbus(R) Master Simulator Copyright (c) 2002-2025 proconX Pty Ltd Visit https://www.modbusdriver.com for Modbus libraries and tools. Protocol configuration: Modbus RTU, FC3 Slave configuration...: address = 247, start reference = 30000, count = 32 Communication.........: COM9, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms Data type.............: 16-bit register, holding register table -- Polling slave... (Ctrl-C to stop) Reply time-out!Der Smartmeter (147) antwortet mir darüber.
Weiß jemand, was ich vergessen habe zu konfigurieren bzw. welchen Fehler ich gemacht habe?
Im Menübaum sehe ich keine weiteren Einstellungen zu diesem Thema.
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
Waveshare RS485 TO ETH
Hi,
wenn du den Waveshare RS485 TO ETH nimmst, was hast du da genau eingestellt - ist es das?
Und wie schauen die Einstellungen im IOBroker Modbus-Adapter genau aus? Bitte Screenshots.
[EDIT] Bevor beim Waveshare RS485 TO ETH die grüne LED nicht leuchtet, steckt der Fehler höchstwahrscheinlich zwischen IOB-Adapter und Waveshare.
-
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
Waveshare RS485 TO ETH
Hi,
wenn du den Waveshare RS485 TO ETH nimmst, was hast du da genau eingestellt - ist es das?
Und wie schauen die Einstellungen im IOBroker Modbus-Adapter genau aus? Bitte Screenshots.
[EDIT] Bevor beim Waveshare RS485 TO ETH die grüne LED nicht leuchtet, steckt der Fehler höchstwahrscheinlich zwischen IOB-Adapter und Waveshare.
@fuzzy1955
Ja, so sieht die akt. Konfig aus.
"Destination IP" ist die des iobrokers.
In "Einstellungen" nichts geändert.
Nur das eingetragen:
Wenn ich mit GModbus das Waveshare anspreche, leuchtet der Link:
Nur es kommt nicht das erwartet zurück:
iobroker meldet:
2026-03-03 22:03:45.230 - info: modbus.0 (589822) starting. Version 8.0.3 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-03-03 22:03:45.263 - debug: modbus.0 (589822) Initialize Objects for disInputs: [] 2026-03-03 22:03:45.263 - debug: modbus.0 (589822) Initialize Objects for coils: [] 2026-03-03 22:03:45.263 - debug: modbus.0 (589822) Initialize Objects for inputRegs: [] 2026-03-03 22:03:45.264 - debug: modbus.0 (589822) Initialize Objects for holdingRegs: [{"_address":30000,"address":30000,"name":"Model Name","description":"","type":"string","len":16,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":247,"id":"holdingRegisters.30000_Model_Name"},{"_address":30016,"address":30016,"name":"Serial Number","description":"","type":"string","len":16,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":247,"id":"holdingRegisters.30016_Serial_Number"}] 2026-03-03 22:03:45.264 - debug: modbus.0 (589822) Add holdingRegisters.30000_Model_Name: {"_id":"holdingRegisters.30000_Model_Name","type":"state","common":{"name":"","role":"","type":"string","read":true,"write":true,"def":"","unit":""},"native":{"regType":"holdingRegs","address":30000,"deviceId":247,"type":"string","len":16,"offset":0,"factor":1,"poll":true}} 2026-03-03 22:03:45.264 - debug: modbus.0 (589822) Add holdingRegisters.30016_Serial_Number: {"_id":"holdingRegisters.30016_Serial_Number","type":"state","common":{"name":"","role":"","type":"string","read":true,"write":true,"def":"","unit":""},"native":{"regType":"holdingRegs","address":30016,"deviceId":247,"type":"string","len":16,"offset":0,"factor":1,"poll":true}} 2026-03-03 22:03:45.331 - info: modbus.0 (589822) Connected to slave 192.168.178.80 2026-03-03 22:03:45.331 - debug: modbus.0 (589822) [DevID_247] Poll start --------------------- 2026-03-03 22:03:45.332 - debug: modbus.0 (589822) Initialization of scale factors done! 2026-03-03 22:03:45.332 - debug: modbus.0 (589822) [DevID_247/holdingRegs] Poll address 30000 - 32 registers 2026-03-03 22:03:45.404 - warn: modbus.0 (589822) Error in handler for FC3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 2026-03-03 22:03:45.753 - warn: modbus.0 (589822) Error in handler for FC3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 2026-03-03 22:03:46.104 - warn: modbus.0 (589822) Error in handler for FC3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4Das Debug-Log wenn ich über TCP abfrage:
2026-03-04 07:11:47.418 - info: modbus.0 (647850) starting. Version 8.0.3 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Initialize Objects for disInputs: [] 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Initialize Objects for coils: [] 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Initialize Objects for inputRegs: [] 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Initialize Objects for holdingRegs: [{"_address":30000,"address":30000,"name":"Model Name","description":"","type":"string","len":16,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":246,"id":"holdingRegisters.30000_Model_Name"},{"_address":30016,"address":30016,"name":"Serial Number","description":"","type":"string","len":16,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":246,"id":"holdingRegisters.30016_Serial_Number"}] 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Add holdingRegisters.30000_Model_Name: {"_id":"holdingRegisters.30000_Model_Name","type":"state","common":{"name":"","role":"","type":"string","read":true,"write":true,"def":"","unit":""},"native":{"regType":"holdingRegs","address":30000,"deviceId":246,"type":"string","len":16,"offset":0,"factor":1,"poll":true}} 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Add holdingRegisters.30016_Serial_Number: {"_id":"holdingRegisters.30016_Serial_Number","type":"state","common":{"name":"","role":"","type":"string","read":true,"write":true,"def":"","unit":""},"native":{"regType":"holdingRegs","address":30016,"deviceId":246,"type":"string","len":16,"offset":0,"factor":1,"poll":true}} 2026-03-04 07:11:47.511 - info: modbus.0 (647850) Connected to slave 192.168.178.99 2026-03-04 07:11:47.511 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:47.512 - debug: modbus.0 (647850) Initialization of scale factors done! 2026-03-04 07:11:47.512 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:47.520 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:48.571 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:48.571 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:48.577 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:49.628 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:49.628 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:49.634 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:50.465 - info: host.iobroker instance system.adapter.weatherunderground.0 having pid 647839 terminated with code 0 (NO_ERROR) 2026-03-04 07:11:50.684 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:50.684 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:50.690 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:51.741 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:51.741 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:51.747 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:52.798 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:52.799 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:52.804 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:53.855 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:53.855 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:53.861 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE
-
@fuzzy1955
Ja, so sieht die akt. Konfig aus.
"Destination IP" ist die des iobrokers.
In "Einstellungen" nichts geändert.
Nur das eingetragen:
Wenn ich mit GModbus das Waveshare anspreche, leuchtet der Link:
Nur es kommt nicht das erwartet zurück:
iobroker meldet:
2026-03-03 22:03:45.230 - info: modbus.0 (589822) starting. Version 8.0.3 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-03-03 22:03:45.263 - debug: modbus.0 (589822) Initialize Objects for disInputs: [] 2026-03-03 22:03:45.263 - debug: modbus.0 (589822) Initialize Objects for coils: [] 2026-03-03 22:03:45.263 - debug: modbus.0 (589822) Initialize Objects for inputRegs: [] 2026-03-03 22:03:45.264 - debug: modbus.0 (589822) Initialize Objects for holdingRegs: [{"_address":30000,"address":30000,"name":"Model Name","description":"","type":"string","len":16,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":247,"id":"holdingRegisters.30000_Model_Name"},{"_address":30016,"address":30016,"name":"Serial Number","description":"","type":"string","len":16,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":247,"id":"holdingRegisters.30016_Serial_Number"}] 2026-03-03 22:03:45.264 - debug: modbus.0 (589822) Add holdingRegisters.30000_Model_Name: {"_id":"holdingRegisters.30000_Model_Name","type":"state","common":{"name":"","role":"","type":"string","read":true,"write":true,"def":"","unit":""},"native":{"regType":"holdingRegs","address":30000,"deviceId":247,"type":"string","len":16,"offset":0,"factor":1,"poll":true}} 2026-03-03 22:03:45.264 - debug: modbus.0 (589822) Add holdingRegisters.30016_Serial_Number: {"_id":"holdingRegisters.30016_Serial_Number","type":"state","common":{"name":"","role":"","type":"string","read":true,"write":true,"def":"","unit":""},"native":{"regType":"holdingRegs","address":30016,"deviceId":247,"type":"string","len":16,"offset":0,"factor":1,"poll":true}} 2026-03-03 22:03:45.331 - info: modbus.0 (589822) Connected to slave 192.168.178.80 2026-03-03 22:03:45.331 - debug: modbus.0 (589822) [DevID_247] Poll start --------------------- 2026-03-03 22:03:45.332 - debug: modbus.0 (589822) Initialization of scale factors done! 2026-03-03 22:03:45.332 - debug: modbus.0 (589822) [DevID_247/holdingRegs] Poll address 30000 - 32 registers 2026-03-03 22:03:45.404 - warn: modbus.0 (589822) Error in handler for FC3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 2026-03-03 22:03:45.753 - warn: modbus.0 (589822) Error in handler for FC3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 2026-03-03 22:03:46.104 - warn: modbus.0 (589822) Error in handler for FC3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4Das Debug-Log wenn ich über TCP abfrage:
2026-03-04 07:11:47.418 - info: modbus.0 (647850) starting. Version 8.0.3 in /opt/iobroker/node_modules/iobroker.modbus, node: v22.22.0, js-controller: 7.1.0 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Initialize Objects for disInputs: [] 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Initialize Objects for coils: [] 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Initialize Objects for inputRegs: [] 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Initialize Objects for holdingRegs: [{"_address":30000,"address":30000,"name":"Model Name","description":"","type":"string","len":16,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":246,"id":"holdingRegisters.30000_Model_Name"},{"_address":30016,"address":30016,"name":"Serial Number","description":"","type":"string","len":16,"factor":1,"offset":0,"formula":"","role":"","unit":"","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":246,"id":"holdingRegisters.30016_Serial_Number"}] 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Add holdingRegisters.30000_Model_Name: {"_id":"holdingRegisters.30000_Model_Name","type":"state","common":{"name":"","role":"","type":"string","read":true,"write":true,"def":"","unit":""},"native":{"regType":"holdingRegs","address":30000,"deviceId":246,"type":"string","len":16,"offset":0,"factor":1,"poll":true}} 2026-03-04 07:11:47.445 - debug: modbus.0 (647850) Add holdingRegisters.30016_Serial_Number: {"_id":"holdingRegisters.30016_Serial_Number","type":"state","common":{"name":"","role":"","type":"string","read":true,"write":true,"def":"","unit":""},"native":{"regType":"holdingRegs","address":30016,"deviceId":246,"type":"string","len":16,"offset":0,"factor":1,"poll":true}} 2026-03-04 07:11:47.511 - info: modbus.0 (647850) Connected to slave 192.168.178.99 2026-03-04 07:11:47.511 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:47.512 - debug: modbus.0 (647850) Initialization of scale factors done! 2026-03-04 07:11:47.512 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:47.520 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:48.571 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:48.571 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:48.577 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:49.628 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:49.628 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:49.634 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:50.465 - info: host.iobroker instance system.adapter.weatherunderground.0 having pid 647839 terminated with code 0 (NO_ERROR) 2026-03-04 07:11:50.684 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:50.684 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:50.690 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:51.741 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:51.741 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:51.747 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:52.798 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:52.799 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:52.804 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE 2026-03-04 07:11:53.855 - debug: modbus.0 (647850) [DevID_246] Poll start --------------------- 2026-03-04 07:11:53.855 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 - 32 registers 2026-03-04 07:11:53.861 - debug: modbus.0 (647850) [DevID_246/holdingRegs] Poll address 30000 DONE@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
2026-03-03 22:03:45.404 - warn: modbus.0 (589822) Error in handler for FC3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range.
Offenbar passt das Offset nicht. Was ist da bei dir eingetragen? Meines schaut so aus:
-
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
2026-03-03 22:03:45.404 - warn: modbus.0 (589822) Error in handler for FC3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range.
Offenbar passt das Offset nicht. Was ist da bei dir eingetragen? Meines schaut so aus:
@fuzzy1955
Das das Offset nicht passt, scheint mir unwahrscheinlich, da es
a) so in der FoxESS Doku drin steht
b) wie gezeigt per LAN auch funktioniert.
Denke nicht, dass sich die Holding Register Adressen ändern, nur weil man statt LAN oder RS485 abfragt.
Du nutzt auch TCP?
Kannst du mal prüfen, ob du die Versionsnummern von Master, Slave und Manager auch abfragst und die bei dir 36001-36003 sind?
Version: Manager (H3_10_Smart) 1.12 Version: Master (H3_10_Smart) 1.39 Version: Slave (H3_10_Smart) 1.00 -
@fuzzy1955
Das das Offset nicht passt, scheint mir unwahrscheinlich, da es
a) so in der FoxESS Doku drin steht
b) wie gezeigt per LAN auch funktioniert.
Denke nicht, dass sich die Holding Register Adressen ändern, nur weil man statt LAN oder RS485 abfragt.
Du nutzt auch TCP?
Kannst du mal prüfen, ob du die Versionsnummern von Master, Slave und Manager auch abfragst und die bei dir 36001-36003 sind?
Version: Manager (H3_10_Smart) 1.12 Version: Master (H3_10_Smart) 1.39 Version: Slave (H3_10_Smart) 1.00@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
Du nutzt auch TCP
Ja. Meine Einstellungen im Modbus-Adapter sind:
Kannst du mal prüfen, ob du die Versionsnummern von Master, Slave und Manager auch abfragst
Geht leider nicht. Ich habe Deye SUN10k Wechselrichter.
-
@Int17 sagte in FoxEss H3 Wechselrichter per Modbus in ioBroker:
Du nutzt auch TCP
Ja. Meine Einstellungen im Modbus-Adapter sind:
Kannst du mal prüfen, ob du die Versionsnummern von Master, Slave und Manager auch abfragst
Geht leider nicht. Ich habe Deye SUN10k Wechselrichter.
@fuzzy1955
Ok, dann passen natürlich auch unsere Registernummern nicht.
Bei FoxESS:
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
553
Online32.7k
Benutzer82.6k
Themen1.3m
Beiträge