raschy / iobroker.deyeidc Goto Github PK
View Code? Open in Web Editor NEWReading out the inverter without cloud
License: MIT License
Reading out the inverter without cloud
License: MIT License
Describe the bug
Adapter liest im IObroker keine Werte aus
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Der Adapter liest nach "Objekte" alle Werte vom Deye aus
Screenshots & Logfiles
Fehler bei Protokolle Adapter deyeidc:
Error: Frame CheckSum faulty! 8a|2a | Error: Frame CheckSum faulty! 8a|2a at idcCore.checkDataFrame (/opt/iobroker/node_modules/iobroker.deyeidc/lib/idc-core.js:70:10) at Deyeidc.onData (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:170:24) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:158:10) at Socket.emit (node:events:517:28) at addChunk (node:internal/streams/readable:368:12) at readableAddChunk (node:internal/streams/readable:341:9) at Readable.push (node:internal/streams/readable:278:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
Versions:
Describe the bug
deyeidc has an invalid jsonConfig: [{"instancePath":"/items/_coils/items/coils/items/1","schemaPath":"#/items/allOf/17/then/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"trim"},"message":"must NOT have additional properties"},{"instancePath":"/items/_coils/items/coils","schemaPath":"#/patternProperties/%5E.%2B/allOf/25/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match "then" schema"},{"instancePath":"/items/_coils","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match "then" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match "then" schema"}]
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error message
Versions:
Additional context
Error is caused by
{
"type": "number",
"trim": false,
"attr": "rules",
"width": "15%",
"title": "rule",
"default": ""
}
Error seems to be fixed at github already but fix did not yet make its way into a release.
See https://forum.iobroker.net/topic/63899/adapter-cloudfreie-auslesung-von-deye-invertern/931
Describe the bug
Ich nutze die aktuellste Version und erhalte den folgenden Eintrag im ioBroker Log:
RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 10. Received 13
Ich nutze einen Deye SUN10K.
To Reproduce
Expected behavior
Keine Meldung im Log.
Screenshots & Logfiles
Kann ich nachliefern, wenn dieser benötigt wird.
Versions:
Additional context
Nichts.
Describe the bug
Looks like there is no documentation how to use the setPower function to write percentages to register 40
Versions:
Additional context
I'd like to use blockly scripts to dynamically set register 40 to stay below 600W power out of the house
deyeidc.MI600.json funktioniert auch für deye Sun800 das ist die gute Nachricht.
In der json ist aber ein fehler: DP1 = DC1*DV1 !!!
Node 8.16.1
NPM: 9.5.1
Bekomme beim installieren diese Fehlermeldung:
`$ iobroker url https://github.com/raschy/ioBroker.deyeidc --host rockpro64 --debug
Installing raschy/ioBroker.deyeidc#1c042ce4617e44dfb6fcb2a5bf37ab2dc37e2906... (System call)
npm WARN skipping integrity check for git dependency ssh://[email protected]/raschy/ioBroker.deyeidc.git
npm ERR! code 1
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | linux | arm64npm ERR! gyp info find Python using Python version 3.8.10 found at "/usr/bin/python3"npm ERR! (node:17150) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.npm ERR! (Use node --trace-deprecation ...
to show where the warning was created)npm ERR! gyp info spawn /usr/bin/python3npm ERR! gyp info spawn args [npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',npm ERR! gyp info spawn args 'binding.gyp',npm ERR! gyp info spawn args '-f',npm ERR! gyp info spawn args 'make',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/bufferutil/build/config.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/addon.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/18.16.1/include/node/common.gypi',npm ERR! gyp info spawn args '-Dlibrary=shared_library',npm ERR! gyp info spawn args '-Dvisibility=default',npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.16.1',npm ERR! gyp info spawn args '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.16.1/<(target_arch)/node.lib',npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/bufferutil',npm ERR! gyp info spawn args '-Dnode_engine=v8',npm ERR! gyp info spawn args '--depth=.',npm ERR! gyp info spawn args '--no-parallel',npm ERR! gyp info spawn args '--generator-output',npm ERR! gyp info spawn args 'build',npm ERR! gyp info spawn args '-Goutput_dir=.'npm ERR! gyp info spawn args ]npm ERR! gyp info spawn makenpm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]npm ERR! make: cc: Command not foundnpm ERR! make: *** [bufferutil.target.mk:111: Release/obj.target/bufferutil/src/bufferutil.o] Error 127npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: make
failed with exit code: 2npm ERR! gyp ERR! stack at ChildProcess.onExit (/opt/iobroker/node_modules/node-gyp/lib/build.js:194:23)npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28)npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:291:12)npm ERR! gyp ERR! System Linux 5.15.93-rockchip64npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/bufferutilnpm ERR! gyp ERR! node -v v18.16.1npm ERR! gyp ERR! node-gyp -v v7.1.2npm ERR! gyp ERR! not oknpm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2023-06-23T07_01_45_324Z-debug-0.log
npm WARN skipping integrity check for git dependency ssh://[email protected]/raschy/ioBroker.deyeidc.git npm ERR! code 1npm ERR! path /opt/iobroker/node_modules/bufferutilnpm ERR! command failednpm ERR! command sh -c node-gyp-buildnpm ERR! make: Entering directory '/opt/iobroker/node_modules/bufferutil/build'npm ERR! CC(target) Release/obj.target/bufferutil/src/bufferutil.onpm ERR! make: Leaving directory '/opt/iobroker/node_modules/bufferutil/build'npm ERR! gyp info it worked if it ends with oknpm ERR! gyp info using [email protected] ERR! gyp info using [email protected] | linux | arm64npm ERR! gyp info find Python using Python version 3.8.10 found at "/usr/bin/python3"npm ERR! (node:17150) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.npm ERR! (Use node --trace-deprecation ...
to show where the warning was created)npm ERR! gyp info spawn /usr/bin/python3npm ERR! gyp info spawn args [npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',npm ERR! gyp info spawn args 'binding.gyp',npm ERR! gyp info spawn args '-f',npm ERR! gyp info spawn args 'make',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/bufferutil/build/config.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/addon.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/18.16.1/include/node/common.gypi',npm ERR! gyp info spawn args '-Dlibrary=shared_library',npm ERR! gyp info spawn args '-Dvisibility=default',npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.16.1',npm ERR! gyp info spawn args '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.16.1/<(target_arch)/node.lib',npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/bufferutil',npm ERR! gyp info spawn args '-Dnode_engine=v8',npm ERR! gyp info spawn args '--depth=.',npm ERR! gyp info spawn args '--no-parallel',npm ERR! gyp info spawn args '--generator-output',npm ERR! gyp info spawn args 'build',npm ERR! gyp info spawn args '-Goutput_dir=.'npm ERR! gyp info spawn args ]npm ERR! gyp info spawn makenpm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]npm ERR! make: cc: Command not foundnpm ERR! make: *** [bufferutil.target.mk:111: Release/obj.target/bufferutil/src/bufferutil.o] Error 127npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: make
failed with exit code: 2npm ERR! gyp ERR! stack at ChildProcess.onExit (/opt/iobroker/node_modules/node-gyp/lib/build.js:194:23)npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28)npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:291:12)npm ERR! gyp ERR! System Linux 5.15.93-rockchip64npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/bufferutilnpm ERR! gyp ERR! node -v v18.16.1npm ERR! gyp ERR! node-gyp -v v7.1.2npm ERR! gyp ERR! not oknpm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2023-06-23T07_01_45_324Z-debug-0.log
host.rockpro64 Cannot install raschy/ioBroker.deyeidc#1c042ce4617e44dfb6fcb2a5bf37ab2dc37e2906: 1
ERROR: Process exited with code 25`
I have two deye inverters up and running with v0.0.14 in iobroker.
I now got a new one (M80G4) that has a serial number including a character at the end - this one is not accepted by the deyeidc adapter
other than that, the inverter looks the same compared to the other two
can this be adapted / will that one work?
thanks for your work and support!
Hi,
it is not possible to use dyndns?
IP address [#####.ddns.net] is not valid !
it is possible to add this support?
Thx.
Thomas
Describe the bug
When updating from 0.0.4 to 0.0.9 the adapter does not work anymore
Screenshots & Logfiles
deyeidc.0 | 2023-08-09 10:46:09.716 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason |
---|---|---|---|
deyeidc.0 | 2023-08-09 10:46:09.715 | info | terminating |
deyeidc.0 | 2023-08-09 10:46:09.710 | error | Cannot read properties of undefined (reading 'indexOf') |
deyeidc.0 | 2023-08-09 10:46:09.709 | error | TypeError: Cannot read properties of undefined (reading 'indexOf') at mathOperation (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:347:30) at Deyeidc.readComputeAndWatch (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:316:22) at Deyeidc.onData (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:170:16) |
deyeidc.0 | 2023-08-09 10:46:09.708 | error | unhandled promise rejection: Cannot read properties of undefined (reading 'indexOf') |
deyeidc.0 | 2023-08-09 10:46:09.707 | error | Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). |
deyeidc.0 | 2023-08-09 10:45:09.276 | info | starting. Version 0.0.9 (non-npm: raschy/ioBroker.deyeidc) in /opt/iobroker/node_modules/iobroker.deyeidc, node: v18.7.0, js-controller: 4.0.24 |
Versions:
Hi raschy,
ich habe einen DEYE SUN 12K-SG04LP3-EU. Den WR lese ich momentan über den Modbus-Adapter aus. Funktioniert auch soweit.
Jetzt bin ich auf deinen Adapter gestossen und probiere diesen zum laufen zu bringen.
Die Verbindung wird aufgebaut, doch kann ich keine Daten auslesen. Es kommt immer die untenstehende Fehlermeldnung.
Ich habe den Register Range von 500-520 festgelegt und die folgenden Daten eingeben. Die Daten habe ich deiner Definintion vom SUN10K entnommen. Diese entsprechen auch dem SUN12K.
"register": 514,
"rules": 1,
"key": "Battery_Today_Charge",
"name": "Battery_Today_Charge",
"name": "Battery Today Charge",
"unit": "kWh",
"factor": 1,
"nullable": false
"register": 515,
"rules": 1,
"key": "Battery_Today_Discharge",
"name": "Battery_Today_Discharge",
"name": "Battery Today Discharge",
"unit": "kWh",
"factor": 1,
"nullable": false
[requestData] error: RangeError [ERR_OUT_OF_RANGE]: The value of "value" is out of range. It must be >= 0 and <= 4294967295. Received 27_964_892_196 stack: RangeError [ERR_OUT_OF_RANGE]: The value of "value" is out of range. It must be >= 0 and <= 4294967295. Received 27_964_892_196 at new NodeError (node:internal/errors:405:5) at checkInt (node:internal/buffer:74:11) at writeU_Int32LE (node:internal/buffer:694:3) at Buffer.writeUInt32LE (node:internal/buffer:707:10) at idcCore.requestFrame (/opt/iobroker/node_modules/iobroker.deyeidc/lib/idc-core.js:275:10) at Deyeidc.requestData (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:225:29) at async /opt/iobroker/node_modules/iobroker.deyeidc/main.js:92:5
Wo mache ich einen Fehler?
Gruß
Ralph
I have with the new Version wrong values from Total AC Output Power (Active)
On Webinterface of the Logger i have 15W
Data in IOBroker is 1310720 W
WR is DEYE 1600
Number of Register 86 Rule 3 Key Apo_t1 Name Total AC Output Power (Active) "Einheit W" Faktor 1
Version: stable=0.0.11 (70 days old) => latest=0.0.14 (15 days old)
Installs: stable=593 (70.34%), latest=93 (11.03%), total=843
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!
I installed yesterday the 0.0.9 and everything is working fine.
This morning i recieve warnings:
ControlCode faulty!: Data may be corrupt, therefore discarded
I have set the start register to 0 and end to 90.
The adapter is still green and on debug but no further message but it seems to work fine. How to get rid of this warnings? Here an example of the whole logs.
`
deyeidc.0 | 2023-08-22 11:11:49.951 | debug | connection closed/destroyed |
---|---|---|---|
deyeidc.0 | 2023-08-22 11:11:29.951 | debug | Response: {"register":1,"modbus":{"type":"Buffer","data":[1,3,182,0,4,1,0,2,1,50,51,48,50,50,55,56,56,51,57,0,1,0,0,18,12,7,0,1,1,1,22,18,24,0,0,31,64,0,0,2,1,0,75,0,0,0,60,23,8,22,11,6,40,0,0,0,0,10,190,7,8,20,80,18,142,0,0,0,0,0,0,19,156,0,44,0,0,0,0,0,0,0,0,0,100,0,0,0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,1,255,245,0,0,0,10,0,2,0,0,0,0,0,0,0,0,0,0,0,4,0,0,0,0,0,0,0,36,0,0,0,0,0,0,0,0,0,0,0,17,0,0,0,17,0,0,9,66,0,0,0,0,0,2,0,0,0,0,19,136,0,0,0,0,0,0,0,0,0,0,0,0,2,198,0,0,0,0,0,0,14,116,118]}} |
deyeidc.0 | 2023-08-22 11:11:29.641 | debug | Response: {"register":0,"modbus":{"type":"Buffer","data":[1,3,2,22,11,247]}} |
deyeidc.0 | 2023-08-22 11:11:29.579 | debug | connected |
deyeidc.0 | 2023-08-22 11:11:29.542 | debug | try to connect . . . |
deyeidc.0 | 2023-08-22 11:06:20.888 | debug | connection closed/destroyed |
deyeidc.0 | 2023-08-22 11:06:00.888 | debug | Response: {"register":1,"modbus":{"type":"Buffer","data":[1,3,182,0,4,1,0,2,1,50,51,48,50,50,55,56,56,51,57,0,1,0,0,18,12,7,0,1,1,1,22,18,24,0,0,31,64,0,0,2,1,0,75,0,0,0,60,23,8,22,11,1,32,0,0,0,0,10,190,7,8,20,80,18,142,0,0,0,0,0,0,19,156,0,44,0,0,0,0,0,0,0,0,0,100,0,0,0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,1,255,245,0,0,0,10,0,2,0,0,0,0,0,0,0,0,0,0,0,4,0,0,0,0,0,0,0,36,0,0,0,0,0,0,0,0,0,0,0,17,0,0,0,17,0,0,9,56,0,0,0,0,0,2,0,0,0,0,19,136,0,0,0,0,0,0,0,0,0,0,0,0,2,28,0,0,0,0,0,0,13,212,48]}} |
deyeidc.0 | 2023-08-22 11:06:00.629 | debug | Response: {"register":0,"modbus":{"type":"Buffer","data":[1,3,2,22,11,247]}} |
deyeidc.0 | 2023-08-22 11:06:00.565 | debug | connected |
deyeidc.0 | 2023-08-22 11:05:59.542 | debug | try to connect . . . |
deyeidc.0 | 2023-08-22 11:01:07.268 | debug | connection closed/destroyed |
deyeidc.0 | 2023-08-22 11:00:47.268 | warn | ControlCode faulty!: Data may be corrupt, therefore discarded |
deyeidc.0 | 2023-08-22 11:00:30.052 | debug | [watchStates] set to Power_Set |
deyeidc.0 | 2023-08-22 11:00:29.989 | debug | Response: {"register":1,"modbus":{"type":"Buffer","data":[1,3,182,0,4,1,0,2,1,50,51,48,50,50,55,56,56,51,57,0,1,0,0,18,12,7,0,1,1,1,22,18,24,0,0,31,64,0,0,2,1,0,75,0,0,0,60,23,8,22,10,56,28,0,0,0,0,10,190,7,8,20,80,18,142,0,0,0,0,0,0,19,156,0,44,0,0,0,0,0,0,0,0,0,100,0,0,0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,1,255,245,0,0,0,10,0,2,0,0,0,0,0,0,0,0,0,0,0,4,0,0,0,0,0,0,0,36,0,0,0,0,0,0,0,0,0,0,0,17,0,0,0,17,0,0,9,46,0,0,0,0,0,2,0,0,0,0,19,146,0,0,0,0,0,0,0,0,0,0,0,0,2,68,0,0,0,0,0,0,13,242,209]}} |
deyeidc.0 | 2023-08-22 11:00:29.680 | debug | Response: {"register":0,"modbus":{"type":"Buffer","data":[1,3,2,22,10,54]}} |
deyeidc.0 | 2023-08-22 11:00:29.617 | debug | connected |
deyeidc.0 | 2023-08-22 11:00:29.543 | debug | try to connect . . . |
Die installation von deyeidc endet mit dem Fehlercode 25. Anderer Adapter lassen sich ohne Probleme installieren.
jscontroller 5.0.19
$ iobroker add deyeidc auto --host DietPi --debug Installing [email protected]... (System call) npm ERR! code 1 npm ERR! path /opt/iobroker/node_modules/bufferutil npm ERR! command failednpm ERR! command sh -c node-gyp-buildnpm ERR! gyp info it worked if it ends with oknpm ERR! gyp info using [email protected] ERR! gyp info using [email protected] | linux | arm64npm ERR! gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3"npm ERR! (node:3748) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only. npm ERR! (Use
node --trace-deprecation ...to show where the warning was created)npm ERR! gyp info spawn /usr/bin/python3npm ERR! gyp info spawn args [npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',npm ERR! gyp info spawn args 'binding.gyp',npm ERR! gyp info spawn args '-f',npm ERR! gyp info spawn args 'make',npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/opt/iobroker/node_modules/bufferutil/build/config.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/addon.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/18.19.1/include/node/common.gypi',npm ERR! gyp info spawn args '-Dlibrary=shared_library',npm ERR! gyp info spawn args '-Dvisibility=default',npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.19.1',npm ERR! gyp info spawn args '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.19.1/<(target_arch)/node.lib',npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/bufferutil',npm ERR! gyp info spawn args '-Dnode_engine=v8',npm ERR! gyp info spawn args '--depth=.',npm ERR! gyp info spawn args '--no-parallel',npm ERR! gyp info spawn args '--generator-output',npm ERR! gyp info spawn args 'build',npm ERR! gyp info spawn args '-Goutput_dir=.'npm ERR! gyp info spawn args ]npm ERR! Traceback (most recent call last):npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py", line 51, in <module>npm ERR! sys.exit(gyp.script_main())npm ERR! ^^^^^^^^^^^^^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 670, in script_mainnpm ERR! return main(sys.argv[1:])npm ERR! ^^^^^^^^^^^^^^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 662, in mainnpm ERR! return gyp_main(args)npm ERR! ^^^^^^^^^^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 629, in gyp_mainnpm ERR! [generator, flat_list, targets, data] = Load(npm ERR! ^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 150, in Loadnpm ERR! result = gyp.input.Load(npm ERR! ^^^^^^^^^^^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 3021, in Loadnpm ERR! LoadTargetBuildFile(npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 411, in LoadTargetBuildFilenpm ERR! build_file_data = LoadOneBuildFile(npm ERR! ^^^^^^^^^^^^^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 239, in LoadOneBuildFilenpm ERR! build_file_contents = open(build_file_path, "rU").read()npm ERR! ^^^^^^^^^^^^^^^^^^^^^^^^^^^npm ERR! ValueError: invalid mode: 'rU' while trying to load binding.gypnpm ERR! gyp ERR! configure error npm ERR! gyp ERR! stack Error:
gypfailed with exit code: 1npm ERR! gyp ERR! stack at ChildProcess.onCpExit (/opt/iobroker/node_modules/node-gyp/lib/configure.js:351:16)npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:517:28)npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:292:12)npm ERR! gyp ERR! System Linux 6.1.21-v8+npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/bufferutilnpm ERR! gyp ERR! node -v v18.19.1npm ERR! gyp ERR! node-gyp -v v7.1.2npm ERR! gyp ERR! not ok npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-02-17T06_56_31_890Z-debug-0.log npm ERR! code 1npm ERR! path /opt/iobroker/node_modules/bufferutilnpm ERR! command failednpm ERR! command sh -c node-gyp-buildnpm ERR! gyp info it worked if it ends with oknpm ERR! gyp info using [email protected] ERR! gyp info using [email protected] | linux | arm64npm ERR! gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3"npm ERR! (node:3748) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.npm ERR! (Use
node --trace-deprecation ...to show where the warning was created)npm ERR! gyp info spawn /usr/bin/python3npm ERR! gyp info spawn args [npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',npm ERR! gyp info spawn args 'binding.gyp',npm ERR! gyp info spawn args '-f',npm ERR! gyp info spawn args 'make',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/bufferutil/build/config.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/addon.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/18.19.1/include/node/common.gypi',npm ERR! gyp info spawn args '-Dlibrary=shared_library',npm ERR! gyp info spawn args '-Dvisibility=default',npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.19.1',npm ERR! gyp info spawn args '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.19.1/<(target_arch)/node.lib',npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/bufferutil',npm ERR! gyp info spawn args '-Dnode_engine=v8',npm ERR! gyp info spawn args '--depth=.',npm ERR! gyp info spawn args '--no-parallel',npm ERR! gyp info spawn args '--generator-output',npm ERR! gyp info spawn args 'build',npm ERR! gyp info spawn args '-Goutput_dir=.'npm ERR! gyp info spawn args ]npm ERR! Traceback (most recent call last):npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py", line 51, in <module>npm ERR! sys.exit(gyp.script_main())npm ERR! ^^^^^^^^^^^^^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 670, in script_mainnpm ERR! return main(sys.argv[1:])npm ERR! ^^^^^^^^^^^^^^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 662, in mainnpm ERR! return gyp_main(args)npm ERR! ^^^^^^^^^^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 629, in gyp_mainnpm ERR! [generator, flat_list, targets, data] = Load(npm ERR! ^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 150, in Loadnpm ERR! result = gyp.input.Load(npm ERR! ^^^^^^^^^^^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 3021, in Loadnpm ERR! LoadTargetBuildFile(npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 411, in LoadTargetBuildFilenpm ERR! build_file_data = LoadOneBuildFile(npm ERR! ^^^^^^^^^^^^^^^^^npm ERR! File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 239, in LoadOneBuildFilenpm ERR! build_file_contents = open(build_file_path, "rU").read()npm ERR! ^^^^^^^^^^^^^^^^^^^^^^^^^^^npm ERR! ValueError: invalid mode: 'rU' while trying to load binding.gypnpm ERR! gyp ERR! configure error npm ERR! gyp ERR! stack Error:
gyp failed with exit code: 1npm ERR! gyp ERR! stack at ChildProcess.onCpExit (/opt/iobroker/node_modules/node-gyp/lib/configure.js:351:16)npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:517:28)npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:292:12)npm ERR! gyp ERR! System Linux 6.1.21-v8+npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/bufferutilnpm ERR! gyp ERR! node -v v18.19.1npm ERR! gyp ERR! node-gyp -v v7.1.2npm ERR! gyp ERR! not oknpm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-02-17T06_56_31_890Z-debug-0.log host.DietPi Cannot install [email protected]: 1 ERROR: Process exited with code 25
Node wurde komplett neu installiert.
aarch64
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
/usr/bin/npx
/usr/bin/corepack
v18.19.1
v18.19.1
10.2.4
10.2.4
0.22.0
5.0.12
root
root```
Hallo Raschy,
ich lese mit deinem Adapter erfolgreich zwei Deye Sun 600 Mikrowechselrichter aus. Funktioniert super.
Da meine WR über keine Modbus Schnittstelle verfügen würde ich auch gerne das Register: 40 Active Power Regulation damit beschreiben um eine Nulleinspeisung zu erreichen.
Leider speichert er den Wert nicht. Ich vermute ich beschreibe damit nur den Logger und der holt sich den Wert immer wieder neu vom Wechselrichter.
Gibt es da irgendeine Möglichkeit das mit deinem Adapter zu machen? Oder mit Modbus Adapter im iOBroker.
Die Lösung von: https://github.com/kbialek/deye-inverter-mqtt?tab=readme-ov-file#readme ist mir zu kompliziert.
Bitte um Antwort.
Gruß Manuel
Hallo,
habe heute festgestellt, das ich seit dem 03.05 das Problem habe, das der Adapter nicht mehr startet, also ich bekomme immer nur diese Fehlermeldung im Log angezeigt:
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: <<<<<<< HEAD
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: ^^
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: SyntaxError: Unexpected token '<<'
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: at internalCompileFunction (node:internal/vm:76:18)
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: at wrapSafe (node:internal/modules/cjs/loader:1283:20)
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1328:27)
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1203:32)
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1019:12)
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1231:19)
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: at require (node:internal/modules/helpers:177:18)
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:12:17)
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1364:14)
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi Caught by controller[1]: Node.js v18.20.2
2024-05-08 10:53:21.725 - error: host.iobroker-ESXi instance system.adapter.deyeidc.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
Habe bis jetzt leider noch keine Lösung gefunden.
Habe auch ein komplettes Backup vom Server wiederhergestellt, die vor dem 03.05 lag, jedoch habe ich auch mit den Backups (Komplettes Backup von Virtueller Maschine) die Fehler.
Kann mir eventuell helfen ?
Version: stable=0.0.0 (0 days old) => latest=0.0.9 (42 days old)
Installs: stable=0 (0%), latest=142 (27.15%), total=523
Click to edit
Describe the bug
Chrashes after installation of 0.0.11
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots & Logfiles
deyeidc.0 | 2023-09-04 09:30:57.957 | debug | checkUserData is ready
-- | -- | -- | --
deyeidc.0 | 2023-09-04 09:30:57.957 | debug | Sync time set to 60000 ms
deyeidc.0 | 2023-09-04 09:30:57.956 | debug | IP address [192.168.200.106] seems to be valid.
deyeidc.0 | 2023-09-04 09:30:57.943 | info | starting. Version 0.0.11 in /opt/iobroker/node_modules/iobroker.deyeidc, node: v18.17.1, js-controller: 4.0.24
deyeidc.0 | 2023-09-04 09:30:26.816 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason
deyeidc.0 | 2023-09-04 09:30:26.816 | info | terminating
deyeidc.0 | 2023-09-04 09:30:26.815 | debug | [onUnload] cleaned everything up...
deyeidc.0 | 2023-09-04 09:30:26.813 | error | Cannot read properties of undefined (reading 'indexOf')
deyeidc.0 | 2023-09-04 09:30:26.813 | error | TypeError: Cannot read properties of undefined (reading 'indexOf') at mathOperation (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:347:30) at Deyeidc.readComputeAndWatch (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:316:22) at Deyeidc.onData (/opt/iobroker/node_modules/iobroker.deyeidc/main.js:170:16)
deyeidc.0 | 2023-09-04 09:30:26.813 | error | unhandled promise rejection: Cannot read properties of undefined (reading 'indexOf')
deyeidc.0 | 2023-09-04 09:30:26.812 | error | Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
deyeidc.0 | 2023-09-04 09:30:26.806 | debug | Response: {"register":1,"modbus":{"type":"Buffer","data":[1,3,64,0,4,0,0,0,0,0,0,12,105,0,0,0,0,0,0,0,0,0,0,7,74,0,0,4,181,0,0,9,6,0,0,0,0,0,0,0,0,0,0,19,146,0,0,0,0,0,0,0,0,0,0,0,0,0,180,0,0,0,0,0,0,8,252,83]}}
deyeidc.0 | 2023-09-04 09:30:26.665 | debug | Response: {"register":0,"modbus":{"type":"Buffer","data":[1,3,2,4,9,122]}}
deyeidc.0 | 2023-09-04 09:30:26.603 | debug | connected
deyeidc.0 | 2023-09-04 09:30:26.593 | debug | try to connect . . .
deyeidc.0 | 2023-09-04 09:29:26.592 | debug | checkUserData is ready
deyeidc.0 | 2023-09-04 09:29:26.592 | debug | Sync time set to 60000 ms
deyeidc.0 | 2023-09-04 09:29:26.592 | debug | IP address [192.168.200.106] seems to be valid.
deyeidc.0 | 2023-09-04 09:29:26.579 | info | starting. Version 0.0.11 in /opt/iobroker/node_modules/iobroker.deyeidc, node: v18.17.1, js-controller: 4.0.24
deyeidc.0 | 2023-09-04 09:29:26.521 | debug | States connected to redis: 127.0.0.1:9000
deyeidc.0 | 2023-09-04 09:29:26.472 | debug | States create User PubSub Client
deyeidc.0 | 2023-09-04 09:29:26.472 | debug | States create System PubSub Client
deyeidc.0 | 2023-09-04 09:29:26.469 | debug | Redis States: Use Redis connection: 127.0.0.1:9000
deyeidc.0 | 2023-09-04 09:29:26.461 | debug | Objects connected to redis: 127.0.0.1:9001
deyeidc.0 | 2023-09-04 09:29:26.458 | debug | Objects client initialize lua scripts
deyeidc.0 | 2023-09-04 09:29:26.450 | debug | Objects create User PubSub Client
deyeidc.0 | 2023-09-04 09:29:26.450 | debug | Objects create System PubSub Client
deyeidc.0 | 2023-09-04 09:29:26.449 | debug | Objects client ready ... initialize now
deyeidc.0 | 2023-09-04 09:29:26.437 | debug | Redis Objects: Use Redis connection: 127.0.0.1:9001
Versions:
Additional context
Before I updated I think I had v0.0.4 installed and it didn't have any problems. The Deye SUN600 is running and is reachable. It has firmware version 1.57
Hallo Rasch,
ich habe den Deye Sun600 und versuche diesen über IOBroker auszulesen.
Die Installation habe ich nun schon mehrfach auf meine Raspi 3B+ durchgeführt, ohne Erfolg.
Ich hatte die GitHub Version als auch die freigebene Version probiert, ich kriege keine Daten vom Inverter.
Hier der letzte Log:
2024-03-02 15:53:50.662 - info: admin.0 (1329) ==> Connected system.user.admin from ::ffff:192.168.179.2
2024-03-02 15:55:57.703 - warn: admin.0 (1329) deyeidc has an invalid jsonConfig: [{"instancePath":"/items/_coils/items/coils/items/1","schemaPath":"#/items/allOf/17/then/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"trim"},"message":"must NOT have additional properties"},{"instancePath":"/items/_coils/items/coils","schemaPath":"#/patternProperties/%5E.%2B/allOf/23/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match "then" schema"},{"instancePath":"/items/_coils","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match "then" schema"}]
2024-03-02 15:57:00.085 - info: host.raspiBDW "system.adapter.deyeidc.0" enabled
2024-03-02 15:57:00.176 - info: host.raspiBDW instance system.adapter.deyeidc.0 started with pid 1717
2024-03-02 15:57:03.558 - info: deyeidc.0 (1717) starting. Version 0.0.14 in /opt/iobroker/node_modules/iobroker.deyeidc, node: v19.9.0, js-controller: 5.0.19
2024-03-02 15:57:03.619 - info: deyeidc.0 (1717) Retrieving data from the inverter will be done every 60 seconds
Was mach ich falsch??
Grüße
Hans
Kann mir jemand erklären wie ich das weg bekomme?
`$ iobroker url https://github.com/raschy/ioBroker.deyeidc --host rockpro64 --debug
install raschy/ioBroker.deyeidc#c8e6ee63f93e3bc8f6bef811e9dc77a6061b1dcb
NPM version: 10.5.0
Installing raschy/ioBroker.deyeidc#c8e6ee63f93e3bc8f6bef811e9dc77a6061b1dcb... (System call)
npm WARN skipping integrity check for git dependency ssh://[email protected]/raschy/ioBroker.deyeidc.git
npm ERR! code 1
npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/addon.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/18.20.2/include/node/common.gypi',npm ERR! gyp info spawn args '-Dlibrary=shared_library',npm ERR! gyp info spawn args '-Dvisibility=default',npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.20.2',npm ERR! gyp info spawn args '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.20.2/<(target_arch)/node.lib',npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/utf-8-validate',npm ERR! gyp info spawn args '-Dnode_engine=v8',npm ERR! gyp info spawn args '--depth=.',npm ERR! gyp info spawn args '--no-parallel',npm ERR! gyp info spawn args '--generator-output',npm ERR! gyp info spawn args 'build',npm ERR! gyp info spawn args '-Goutput_dir=.'npm ERR! gyp info spawn args ]npm ERR! gyp info spawn makenpm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]npm ERR! make: cc: No such file or directorynpm ERR! make: *** [validation.target.mk:111: Release/obj.target/validation/src/validation.o] Error 127npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: make
failed with exit code: 2npm ERR! gyp ERR! stack at ChildProcess. (/opt/iobroker/node_modules/node-gyp/lib/build.js:209:23)npm ERR! gyp ERR! System Linux 5.15.93-rockchip64npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/node-gyp/bin/node-gyp.js" "rebuild"npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/utf-8-validatenpm ERR! gyp ERR! node -v v18.20.2npm ERR! gyp ERR! node-gyp -v v10.1.0npm ERR! gyp ERR! not oknpm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-05-06T11_41_19_591Z-debug-0.log
npm WARN skipping integrity check for git dependency ssh://[email protected]/raschy/ioBroker.deyeidc.git npm ERR! code 1npm ERR! path /opt/iobroker/node_modules/utf-8-validatenpm ERR! command failednpm ERR! command sh -c node-gyp-buildnpm ERR! make: Entering directory '/opt/iobroker/node_modules/utf-8-validate/build'npm ERR! CC(target) Release/obj.target/validation/src/validation.onpm ERR! make: Leaving directory '/opt/iobroker/node_modules/utf-8-validate/build'npm ERR! gyp info it worked if it ends with oknpm ERR! gyp info using [email protected] ERR! gyp info using [email protected] | linux | arm64npm ERR! gyp info find Python using Python version 3.10.12 found at "/usr/bin/python3"npm ERR! gyp info spawn /usr/bin/python3npm ERR! gyp info spawn args [npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',npm ERR! gyp info spawn args 'binding.gyp',npm ERR! gyp info spawn args '-f',npm ERR! gyp info spawn args 'make',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/utf-8-validate/build/config.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/addon.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/18.20.2/include/node/common.gypi',npm ERR! gyp info spawn args '-Dlibrary=shared_library',npm ERR! gyp info spawn args '-Dvisibility=default',npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.20.2',npm ERR! gyp info spawn args '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.20.2/<(target_arch)/node.lib',npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/utf-8-validate',npm ERR! gyp info spawn args '-Dnode_engine=v8',npm ERR! gyp info spawn args '--depth=.',npm ERR! gyp info spawn args '--no-parallel',npm ERR! gyp info spawn args '--generator-output',npm ERR! gyp info spawn args 'build',npm ERR! gyp info spawn args '-Goutput_dir=.'npm ERR! gyp info spawn args ]npm ERR! gyp info spawn makenpm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]npm ERR! make: cc: No such file or directorynpm ERR! make: *** [validation.target.mk:111: Release/obj.target/validation/src/validation.o] Error 127npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: make
failed with exit code: 2npm ERR! gyp ERR! stack at ChildProcess. (/opt/iobroker/node_modules/node-gyp/lib/build.js:209:23)npm ERR! gyp ERR! System Linux 5.15.93-rockchip64npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/node-gyp/bin/node-gyp.js" "rebuild"npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/utf-8-validatenpm ERR! gyp ERR! node -v v18.20.2npm ERR! gyp ERR! node-gyp -v v10.1.0npm ERR! gyp ERR! not oknpm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-05-06T11_41_19_591Z-debug-0.log
host.rockpro64 Cannot install raschy/ioBroker.deyeidc#c8e6ee63f93e3bc8f6bef811e9dc77a6061b1dcb: 1
ERROR: Process exited with code 25`
Ich musste den Adapter neu installieren da das Updfate von 0.0.4 auf 0.0.9 nicht geklappt hat.
Ich habe vorher die Settings per JSON exportiert.
Nach dem Reimport waren alle Werte wieder da bis auf die "Werte (Formeln)" für die 2 Berechnung von DP1 bzw DP2 bei mir (Key, Name, Einheit und Faktor waren korrekt importiert)
Auch hat er nun für die brechneten Werte einen Faktor 2 gehabt, welche den Wert ja um 100 verkleinert? Das war vorher auch anders, aber gut möglich dass das bei Version 0.0.4 noch anders war
Hello,
the only hint i found in the repo respective the readme.md is
npm install iobroker.deyeidc
My try:
http://192.168.188.46:8081/#tab-adapters --> searched for Deye. Does not appear.
How can i attach my 12kW Deye to ioBroker?
Thanks
Hi,
ich habe gestern ein Update des WRs auf 2.06 gewagt. An sich tut alles soweit. Auch die Daten werden vom Adapter ausgelesen.
Jedoch erscheint minütlich die Meldung "Error: Frame CheckSum faulty! d"
WR: Bosswerk BW-MI600 (ohne Zusatzrelais)
FW: MW3_16U_5406_2.06
Der Debug zeigt folgendes:
`
023-09-08 08:40:10.309 - debug: deyeidc.0 (1188) Sync time set to 60000 ms
2023-09-08 08:40:10.310 - debug: deyeidc.0 (1188) checkUserData is ready
2023-09-08 08:41:10.312 - debug: deyeidc.0 (1188) try to connect . . .
2023-09-08 08:41:10.321 - debug: deyeidc.0 (1188) connected
2023-09-08 08:41:10.331 - error: deyeidc.0 (1188) Error: Frame CheckSum faulty! d
2023-09-08 08:41:10.386 - debug: deyeidc.0 (1188) Response: {"register":0,"modbus":{"type":"Buffer","data":[1,3,2,8,6,63]}}
2023-09-08 08:41:10.515 - debug: deyeidc.0 (1188) Response: {"register":2,"modbus":{"type":"Buffer","data":[1,3,64,0,4,0,0,0,0,0,0,26,34,0,0,0,0,0,0,0,0,0,0,13,121,0,0,11,202,0,0,9,76,0,0,0,0,0,0,0,0,0,0,19,136,0,0,0,0,0,0,0,0,0,0,0,0,3,72,0,0,0,0,0,0,11,154,179]}}
2023-09-08 08:41:10.688 - debug: deyeidc.0 (1188) Response: {"register":1,"modbus":{"type":"Buffer","data":[1,3,82,0,4,1,0,2,1,50,50,48,52,48,57,48,55,56,50,0,1,0,0,18,12,7,0,0,0,1,18,2,7,0,0,23,112,0,0,2,1,0,75,0,0,0,60,23,9,8,6,54,24,0,0,0,0,10,190,7,8,20,80,18,142,0,0,0,0,0,0,19,156,0,44,0,0,0,0,0,0,0,0,0,120,248]}}
2023-09-08 08:41:10.866 - debug: deyeidc.0 (1188) Response: {"register":2,"modbus":{"type":"Buffer","data":[1,3,64,0,4,0,0,0,0,0,0,26,34,0,0,0,0,0,0,0,0,0,0,13,121,0,0,11,202,0,0,9,76,0,0,0,0,0,0,0,0,0,0,19,136,0,0,0,0,0,0,0,0,0,0,0,0,3,72,0,0,0,0,0,0,11,154,179]}}
2023-09-08 08:41:10.948 - debug: deyeidc.0 (1188) Response: {"register":3,"modbus":{"type":"Buffer","data":[1,3,8,1,75,0,22,1,32,0,3,166]}}
2023-09-08 08:41:11.004 - debug: deyeidc.0 (1188) [watchStates] set to Power_Set
2023-09-08 08:41:11.005 - debug: deyeidc.0 (1188) [watchStates] set to DV1
2023-09-08 08:41:11.005 - debug: deyeidc.0 (1188) [watchStates] set to DC1
2023-09-08 08:41:11.005 - debug: deyeidc.0 (1188) [watchStates] set to DV2
2023-09-08 08:41:11.006 - debug: deyeidc.0 (1188) [watchStates] set to DC2
2023-09-08 08:41:11.058 - debug: deyeidc.0 (1188) Response: {"register":4,"modbus":{"type":"Buffer","data":[1,3,8,10,190,7,8,20,80,18,142,34]}}
2023-09-08 08:41:31.059 - debug: deyeidc.0 (1188) connection closed/destroyed
2023-09-08 08:42:10.311 - debug: deyeidc.0 (1188) try to connect . . .
2023-09-08 08:42:10.317 - debug: deyeidc.0 (1188) connected
2023-09-08 08:42:10.323 - error: deyeidc.0 (1188) Error: Frame CheckSum faulty! d
2023-09-08 08:42:13.047 - debug: deyeidc.0 (1188) Response: {"register":0,"modbus":{"type":"Buffer","data":[1,3,2,8,6,63]}}
2023-09-08 08:42:13.282 - debug: deyeidc.0 (1188) Response: {"register":1,"modbus":{"type":"Buffer","data":[1,3,82,0,4,1,0,2,1,50,50,48,52,48,57,48,55,56,50,0,1,0,0,18,12,7,0,0,0,1,18,2,7,0,0,23,112,0,0,2,1,0,75,0,0,0,60,23,9,8,6,54,24,0,0,0,0,10,190,7,8,20,80,18,142,0,0,0,0,0,0,19,156,0,44,0,0,0,0,0,0,0,0,0,120,248]}}
2023-09-08 08:42:16.628 - debug: deyeidc.0 (1188) Response: {"register":2,"modbus":{"type":"Buffer","data":[1,3,64,0,4,0,0,0,0,0,0,26,34,0,0,0,0,0,0,0,0,0,0,13,121,0,0,11,202,0,0,9,76,0,0,0,0,0,0,0,0,0,0,19,136,0,0,0,0,0,0,0,0,0,0,0,0,4,206,0,0,0,0,0,0,11,184,200]}}
2023-09-08 08:42:19.893 - debug: deyeidc.0 (1188) Response: {"register":3,"modbus":{"type":"Buffer","data":[1,3,8,1,78,0,33,1,48,0,3,7]}}
2023-09-08 08:42:21.192 - debug: deyeidc.0 (1188) Response: {"register":4,"modbus":{"type":"Buffer","data":[1,3,8,10,190,7,8,20,80,18,142,34]}}
2023-09-08 08:42:41.192 - debug: deyeidc.0 (1188) connection closed/destroyed
Hi,
ich bin ziemlicher Neuling mit diesem Adapter.
Ich habe einen oben genannten WR finde aber keine Konfig Vorlage.
Ich habe hier : Deye300G3-EU wohl die Modbus Daten gefunden.
Kann mir jemand helfen die hier zu konfigurieren?
Danke sehr und LG.
Hi raschy,
erstmal vielen Dank für den Adapter - habe eben meinen MI600 konfiguriert. Sobald die Sonne aufgeht sollten da Werte reinkommen.
Ich habe noch nen SUN-3.6K-SG03LP1-EU welchen ich momentan über RS485 via Modbus-Adapter auslese und beschreibe - das funktioniert auch.
Würde aber gerne auf den TCP Server vom Logger gehen statt des RS485 Adapters.
Auslesen funktioniert erstmal - aber können über den deyeidc-Adapter auch Register geschrieben werden?
Falls du auch Erfahrung hast, wie ich mit dem Modbus-Adapter auf den Logger connecten kann, wäre ich dir auch sehr dankbar.
VG
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.