NEWS
[Adapter] cloudfreie Auslesung von Deye-Invertern
-
@ilovegym said in [Adapter] cloudfreie Auslesung von Deye-Invertern:
ok, kann ich unter Admin 7.0.17 und js-controller 6.0.9 nicht nachvollziehen. Daher dachte ich, es liegt auch evt. daran..?
Wundert mich eigentlich. Der Fehler ist in der offiziellen (npm) Version definitiv drinnen. In der GH Version ist's schon korrigiert.. Der Fehler tritt nur auf, wenn du das Admin UI öffnest.
Aber im Kern kümmert sich Rene eh schon drum. Ist also alles im grünen Bereich. DANKE fürs mithelfen bzw fürs Fixen
-
Hi,
habe heute Version 0.0.15 installiert, leider hat die Probleme mit den Registern, habe 5 Instanzen, bei allen das gleiche, der Adapter startet, und wenn er Daten holen moechte, kommt das:2024-07-29 18:04:13.167 - error: deyeidc.1 (15766) TypeError: Cannot read properties of undefined (reading 'register') | TypeError: Cannot read properties of undefined (reading 'register') at Deyeidc.onData (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:166:11) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:152:10) at Socket.emit (node:events:520:28) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) at Readable.push (node:internal/streams/readable:390:5) at TCP.onStreamRead (node:internal/stream_base_commons:191:23) 2024-07-29 18:04:17.245 - info: host.iobroker "system.adapter.deyeidc.4" disabled 2024-07-29 18:04:17.245 - info: host.iobroker stopInstance system.adapter.deyeidc.4 (force=false, process=true) 2024-07-29 18:04:17.251 - info: host.iobroker stopInstance system.adapter.deyeidc.4 send kill signal 2024-07-29 18:04:17.251 - info: deyeidc.4 (15848) Got terminate signal TERMINATE_YOURSELF 2024-07-29 18:04:17.253 - info: deyeidc.4 (15848) terminating 2024-07-29 18:04:17.254 - info: deyeidc.4 (15848) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-07-29 18:04:17.755 - info: deyeidc.4 (15848) terminating 2024-07-29 18:04:17.807 - info: host.iobroker instance system.adapter.deyeidc.4 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
Zurueck auf 0.0.14 und alles ist gut...
System: Buanet Docker 10.0.0.1-Node22 - js-controller 6.0.9 - Admin 7.0.21
-
@ilovegym Danke für den Test. Ich hab den Adapter gestern abend mal frisch installiert - lief. Hab wohl nur eine Instanz, sollte aber nicht den Fehler ausmachen.
-
Das war vielleicht der unterschied, du hast frisch installiert und ich hab mit der bestehenden Config n Update gemacht..?
Da der Fehler bei den Registern liegt.. vielleicht hab ich da was falsches drin?
Oder er bekommt n Wert der nicht passt..?Hier die config
-
@ilovegym Das ist unwahrscheinlich, die hat es ja vorher auch getan. Strukturelle Änderungen gab es keine.
Hast du mal nur die eine Instanz [0] versucht? -
Ja, der Fehler tritt nach den 60sek auf..
-
@ilovegym Ich kann aus dem ersten Screenshot nicht wirklich was erkennen. Hast du mal die Logstufe auf debug gesetzt?
-
Ok, mach ich morgen Abend… vielleicht hat ja noch einer den Fehler..
-
Habe heute auch die 0.15 aufgespielt und danach diese Meldung erhalten. Die DP`s scheinen aber sonst wie gehabt zu funktionieren.
12844 2024-07-30 18:01:49.461 error TypeError: Cannot read properties of undefined (reading 'register') | TypeError: Cannot read properties of undefined (reading 'register') at Deyeidc.onData (C:\ioBroker\GLT\node_modules\iobroker.deyeidc\main.js:166:11) at Socket.<anonymous> (C:\ioBroker\GLT\node_modules\iobroker.deyeidc\main.js:152:10) at Socket.emit (node:events:519:28) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) at Readable.push (node:internal/streams/readable:390:5) at TCP.onStreamRead (node:internal/stream_base_commons:191:23) deyeidc.0
-
Hab nochmal geupdated, hier das komplette log:
2024-07-30 19:34:01.818 - info: deyeidc.0 (27892) Got terminate signal TERMINATE_YOURSELF 2024-07-30 19:34:01.821 - info: deyeidc.0 (27892) terminating 2024-07-30 19:34:01.822 - info: deyeidc.0 (27892) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-07-30 19:34:02.323 - info: deyeidc.0 (27892) terminating 2024-07-30 19:34:02.364 - info: host.iobroker instance system.adapter.deyeidc.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-07-30 19:34:03.616 - error: deyeidc.1 (27898) TypeError: Cannot read properties of undefined (reading 'register') | TypeError: Cannot read properties of undefined (reading 'register') at Deyeidc.onData (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:166:11) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:152:10) at Socket.emit (node:events:520:28) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) at Readable.push (node:internal/streams/readable:390:5) at TCP.onStreamRead (node:internal/stream_base_commons:191:23) 2024-07-30 19:34:05.743 - info: host.iobroker instance system.adapter.deyeidc.0 in version "0.0.15" started with pid 28018 2024-07-30 19:34:06.049 - info: tr-064.0 (14051) {"NewTotalNumberSyncGroups":"2","NewSyncGroupName":"sync_dsl","NewSyncGroupMode":"VDSL","Newmax_ds":"13258125","Newmax_us":"5185625","Newds_current_bps":"1601157,1750389,763912,1670101,1740643,1314488,1035425,1571816,1567295,1601588,1011045,1394843,1451758,1807280,531676,1771570,1705223,1298708,1044933,1522909","Newmc_current_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0","Newus_current_bps":"45351,53297,27920,41739,58945,27807,42143,39223,48087,54020,42618,33404,45628,58028,32142,51254,48672,22736,41801,43259","Newprio_realtime_bps":"4099,12227,2885,7778,18734,3522,1754,1541,7413,10505,4256,3176,5461,20468,3666,7773,7709,2165,601,4247","Newprio_high_bps":"39288,39646,19089,33012,39310,20130,38469,36282,33646,29000,37725,29695,39099,36477,25972,43064,40081,18365,40277,37998","Newprio_default_bps":"1964,1424,5946,949,901,4155,1920,1400,7028,14515,637,533,1068,1083,2504,417,882,2206,923,1014","Newprio_low_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0"} 2024-07-30 19:34:06.548 - debug: deyeidc.0 (28018) Redis Objects: Use Redis connection: 10.10.2.10:6379 2024-07-30 19:34:06.575 - debug: deyeidc.0 (28018) Objects client ready ... initialize now 2024-07-30 19:34:06.576 - debug: deyeidc.0 (28018) Objects create System PubSub Client 2024-07-30 19:34:06.578 - debug: deyeidc.0 (28018) Objects create User PubSub Client 2024-07-30 19:34:06.832 - debug: deyeidc.0 (28018) Objects client initialize lua scripts 2024-07-30 19:34:06.840 - debug: deyeidc.0 (28018) Objects connected to redis: 10.10.2.10:6379 2024-07-30 19:34:06.858 - debug: deyeidc.0 (28018) Redis States: Use Redis connection: 10.10.2.10:6379 2024-07-30 19:34:06.864 - debug: deyeidc.0 (28018) States create System PubSub Client 2024-07-30 19:34:06.865 - debug: deyeidc.0 (28018) States create User PubSub Client 2024-07-30 19:34:06.871 - debug: deyeidc.0 (28018) States connected to redis: 10.10.2.10:6379 2024-07-30 19:34:07.443 - info: deyeidc.0 (28018) starting. Version 0.0.15 in /opt/iobroker/node_modules/iobroker.deyeidc, node: v22.5.1, js-controller: 6.0.9 2024-07-30 19:34:07.469 - debug: deyeidc.0 (28018) IP address [10.1.1.100] seems to be valid. 2024-07-30 19:34:07.470 - info: deyeidc.0 (28018) Retrieving data from the inverter will be done every 60 seconds 2024-07-30 19:34:07.470 - debug: deyeidc.0 (28018) checkUserData is ready 2024-07-30 19:34:07.470 - debug: deyeidc.0 (28018) try to connect . . . 2024-07-30 19:34:07.477 - debug: deyeidc.0 (28018) Connected to server 2024-07-30 19:34:07.650 - debug: deyeidc.0 (28018) Response: {"register":1,"modbus":{"type":"Buffer","data":[1,3,44,0,4,1,0,2,1,50,50,48,50,50,52,49,52,56,56,0,1,0,0,18,12,7,0,0,0,1,18,2,7,0,0,11,184,0,0,1,1,0,75,0,0,0,60,59]}} 2024-07-30 19:34:08.243 - debug: deyeidc.0 (28018) Response: {"register":2,"modbus":{"type":"Buffer","data":[1,3,64,0,4,0,13,0,0,0,0,20,106,0,0,0,13,0,0,0,0,0,0,20,106,0,0,0,0,0,0,9,46,0,0,0,0,0,0,0,0,0,0,19,136,0,0,0,0,0,0,0,0,0,0,0,0,6,54,0,0,0,0,0,0,21,54,117]}} 2024-07-30 19:34:08.469 - debug: deyeidc.0 (28018) Response: {"register":3,"modbus":{"type":"Buffer","data":[1,3,8,1,97,0,45,0,0,0,0,136]}} 2024-07-30 19:34:08.564 - debug: deyeidc.0 (28018) Response: {"register":4,"modbus":{"type":"Buffer","data":[1,3,8,10,190,7,8,20,80,18,142,34]}} 2024-07-30 19:34:08.579 - debug: deyeidc.0 (28018) Data reception for 4 registersets completed 2024-07-30 19:34:08.580 - debug: deyeidc.0 (28018) [computeData] {"value1":"DV1","value2":"DC1","key":"DP1","name":"DC Power PV1","unit":"W","factor":0,"values":"DV1*DC1"} 2024-07-30 19:34:08.581 - debug: deyeidc.0 (28018) [computeData] {"value1":"DV2","value2":"DC2","key":"DP2","name":"DC Power PV2","unit":"W","factor":0,"values":"DV2*DC2"} 2024-07-30 19:34:08.581 - debug: deyeidc.0 (28018) [computeData] ResultJson: [{"key":"DP1","value":"158.85","unit":"W","name":"DC Power PV1"},{"key":"DP2","value":"0.00","unit":"W","name":"DC Power PV2"}] 2024-07-30 19:34:08.600 - debug: deyeidc.0 (28018) [watchStates] set to Power_Set 2024-07-30 19:34:09.059 - info: tuya.0 (10496) bf51aaad135aa1ced0dhmw: Error on Reconnect (5): connect EHOSTUNREACH 10.1.12.101:6668 2024-07-30 19:34:10.353 - info: influxdb.0 (7447) Store 1001 buffered influxDB history points 2024-07-30 19:34:12.050 - info: tr-064.0 (14051) {"NewTotalNumberSyncGroups":"2","NewSyncGroupName":"sync_dsl","NewSyncGroupMode":"VDSL","Newmax_ds":"13258125","Newmax_us":"5185625","Newds_current_bps":"1523785,1601157,1750389,763912,1670101,1740643,1314488,1035425,1571816,1567295,1601588,1011045,1394843,1451758,1807280,531676,1771570,1705223,1298708,1044933","Newmc_current_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0","Newus_current_bps":"49992,45351,53297,27920,41739,58945,27807,42143,39223,48087,54020,42618,33404,45628,58028,32142,51254,48672,22736,41801","Newprio_realtime_bps":"10254,4099,12227,2885,7778,18734,3522,1754,1541,7413,10505,4256,3176,5461,20468,3666,7773,7709,2165,601","Newprio_high_bps":"38753,39288,39646,19089,33012,39310,20130,38469,36282,33646,29000,37725,29695,39099,36477,25972,43064,40081,18365,40277","Newprio_default_bps":"985,1964,1424,5946,949,901,4155,1920,1400,7028,14515,637,533,1068,1083,2504,417,882,2206,923","Newprio_low_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0"} 2024-07-30 19:34:18.052 - info: tr-064.0 (14051) {"NewTotalNumberSyncGroups":"2","NewSyncGroupName":"sync_dsl","NewSyncGroupMode":"VDSL","Newmax_ds":"13258125","Newmax_us":"5185625","Newds_current_bps":"921663,1523785,1601157,1750389,763912,1670101,1740643,1314488,1035425,1571816,1567295,1601588,1011045,1394843,1451758,1807280,531676,1771570,1705223,1298708","Newmc_current_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0","Newus_current_bps":"27837,49992,45351,53297,27920,41739,58945,27807,42143,39223,48087,54020,42618,33404,45628,58028,32142,51254,48672,22736","Newprio_realtime_bps":"3840,10254,4099,12227,2885,7778,18734,3522,1754,1541,7413,10505,4256,3176,5461,20468,3666,7773,7709,2165","Newprio_high_bps":"21802,38753,39288,39646,19089,33012,39310,20130,38469,36282,33646,29000,37725,29695,39099,36477,25972,43064,40081,18365","Newprio_default_bps":"2195,985,1964,1424,5946,949,901,4155,1920,1400,7028,14515,637,533,1068,1083,2504,417,882,2206","Newprio_low_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0"} 2024-07-30 19:34:19.827 - info: tuya.0 (10496) bf36cda59741f65a3evbfd: Error on Reconnect (7): connect EHOSTUNREACH 10.1.5.86:6668 2024-07-30 19:34:21.228 - info: linux-control.0 (2133) getting data from Influxdb (10.1.1.4:22) 2024-07-30 19:34:22.803 - info: tuya.0 (10496) bf36cda59741f65a3evbfd: Connect locally to device 2024-07-30 19:34:22.803 - info: tuya.0 (10496) bf36cda59741f65a3evbfd Init with IP=10.1.5.86, Key=Y''bS^'ldE@_g'}d, Version=3.3 2024-07-30 19:34:22.833 - info: tuya.0 (10496) bf36cda59741f65a3evbfd: Error on Reconnect (1): connect EHOSTUNREACH 10.1.5.86:6668 2024-07-30 19:34:24.017 - info: host.iobroker instance system.adapter.oilfox.0 in version "4.3.0" started with pid 28087 2024-07-30 19:34:24.432 - info: tr-064.0 (14051) {"NewTotalNumberSyncGroups":"2","NewSyncGroupName":"sync_dsl","NewSyncGroupMode":"VDSL","Newmax_ds":"13258125","Newmax_us":"5185625","Newds_current_bps":"1817837,921663,1523785,1601157,1750389,763912,1670101,1740643,1314488,1035425,1571816,1567295,1601588,1011045,1394843,1451758,1807280,531676,1771570,1705223","Newmc_current_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0","Newus_current_bps":"47909,27837,49992,45351,53297,27920,41739,58945,27807,42143,39223,48087,54020,42618,33404,45628,58028,32142,51254,48672","Newprio_realtime_bps":"1609,3840,10254,4099,12227,2885,7778,18734,3522,1754,1541,7413,10505,4256,3176,5461,20468,3666,7773,7709","Newprio_high_bps":"45132,21802,38753,39288,39646,19089,33012,39310,20130,38469,36282,33646,29000,37725,29695,39099,36477,25972,43064,40081","Newprio_default_bps":"1168,2195,985,1964,1424,5946,949,901,4155,1920,1400,7028,14515,637,533,1068,1083,2504,417,882","Newprio_low_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0"} 2024-07-30 19:34:25.255 - info: linux-control.0 (2133) successful received data from Influxdb (10.1.1.4:22) 2024-07-30 19:34:26.003 - info: oilfox.0 (28087) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.oilfox, node: v22.5.1, js-controller: 6.0.9 2024-07-30 19:34:27.653 - info: oilfox.0 (28087) Terminated (NO_ERROR): Without reason 2024-07-30 19:34:28.179 - info: host.iobroker instance system.adapter.oilfox.0 having pid 28087 terminated with code 0 (NO_ERROR) 2024-07-30 19:34:30.046 - info: tr-064.0 (14051) {"NewTotalNumberSyncGroups":"2","NewSyncGroupName":"sync_dsl","NewSyncGroupMode":"VDSL","Newmax_ds":"13258125","Newmax_us":"5185625","Newds_current_bps":"1492501,1817837,921663,1523785,1601157,1750389,763912,1670101,1740643,1314488,1035425,1571816,1567295,1601588,1011045,1394843,1451758,1807280,531676,1771570","Newmc_current_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0","Newus_current_bps":"52177,47909,27837,49992,45351,53297,27920,41739,58945,27807,42143,39223,48087,54020,42618,33404,45628,58028,32142,51254","Newprio_realtime_bps":"14472,1609,3840,10254,4099,12227,2885,7778,18734,3522,1754,1541,7413,10505,4256,3176,5461,20468,3666,7773","Newprio_high_bps":"36303,45132,21802,38753,39288,39646,19089,33012,39310,20130,38469,36282,33646,29000,37725,29695,39099,36477,25972,43064","Newprio_default_bps":"1402,1168,2195,985,1964,1424,5946,949,901,4155,1920,1400,7028,14515,637,533,1068,1083,2504,417","Newprio_low_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0"} 2024-07-30 19:34:33.132 - error: deyeidc.0 (28018) TypeError: Cannot read properties of undefined (reading 'register') | TypeError: Cannot read properties of undefined (reading 'register') at Deyeidc.onData (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:166:11) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:152:10) at Socket.emit (node:events:520:28) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) at Readable.push (node:internal/streams/readable:390:5) at TCP.onStreamRead (node:internal/stream_base_commons:191:23) ^C
Auch die Instanzen geloescht, dann nur eine neu angelegt, die Konfig importiert, aber gleicher Fehler...
Also wenn das Nachvollziehbar ist, dann sollte der Fehler doch zu finden sein.. ? -
@ilovegym Ich habe heute nochmal geforscht. Kannst du bitte mal den Adapter direkt von Github installieren?
-
Siehe da, kaum macht man's richtig... :). die Github Version geht ohne Fehler!
Danke!! -
@ilovegym Super. Ich hab ja auch dran gearbeitet.
Wenn keine Fehler mehr auftreten mache ich morgen die 0.0.16 -
Moin,
ich habe komischerweise jetzt die Adapterversion 0.1.0 drauf und diese Warnungen im Log :
-
@mpf Ist nicht komisch, 'is a feature'. Der Adapter prüft jetzt, ob der Datenpunkt - in dem Fall "DV1" auch vorhanden ist. Eventuell bei den Coils mal nachsehen oder bei den Berechnungen die Formel prüfen.
-
@rene55 und die Version 0.1.0 ist so korrekt ?
-
@mpf Ich denke ja.
-
@rene55 sagte in [Adapter] cloudfreie Auslesung von Deye-Invertern:
@mpf Ich denke ja.
ist ja aktueller als 0.0.16.....
einwandfrei
Berechnung so korrekt ?
Wo finde ich den DP "DV1" ?Oder einfach löschen, wenn ich den nicht benötige ?
-
@mpf Die Formel sieht doch gut aus. Der "DP1" wird bei der nächsten Datenabholung angelegt.
-
Hallo Rene, hallo Forum,
bei den Versuchen an gewisse Daten von meiner Solaranlage zu kommen, bin ich über diesen IOBroker Adapter gestolpert und habe ihn gleich installiert. Einrichten mit IP und Seriennummer war total einfach. Dafür also auf alle Fälle schonmal Danke Rene55.
Ich habe den SUN-5K-SG03LP1-EU und nachdem ich einige JSON Dateien von verschiedenen Geräten getestet habe, erhielt ich mit der SUN2000.json erste brauchbare Ergebnisse. Ich habe auch schon unnötige Datenpunkte aus dem Setting heraus gelöscht.
Jetzt stellt sich mir nur die Frage, wo finde ich Informationen welche Register welche (sinnvollen) Daten enthalten, damit ich evtl. das Setting erweitern kann?Ich danke Euch schon einmal für Eure Hilfe.