simatec / iobroker.solax

solax adapter for ioBroker

ioBroker.solax

---

If you like it, please consider a donation:

---

Solax Adapter for ioBroker

---

Deutsche Beschreibung

English Description

---

What is Sentry.io and what is reported to the servers of that company?

Sentry.io is a service for developers to get an overview about errors from their applications. And exactly this is implemented in this adapter.

When the adapter crashes or an other Code error happens, this error message that also appears in the ioBroker log is submitted to Sentry. When you allowed iobroker GmbH to collect diagnostic data then also your installation ID (this is just a unique ID without any additional infos about you, email, name or such) is included. This allows Sentry to group errors and show how many unique users are affected by such an error. All of this helps me to provide error free adapters that basically never crashs.

---

Changelog

WORK IN PROGRESS

• (simatec) Dependencies updated

0.9.6 (2024-02-05)

• (simatec) small Design Fix

0.9.5 (2024-02-04)

• (simatec) Dependencies updated
• (simatec) Fix Data for X1/X3-EVC Wallbox

0.9.4 (2024-01-22)

• (simatec) adapter-dev added
• (simatec) delete Gulp
• (Andre-0815-4711) Data for X1/X3-EVC Wallbox added

0.9.3 (2024-01-14)

• (simatec) Fix Data for X1/X3-EVC Wallbox
• (simatec) Fix Inverter data
• (simatec) Dependencies updated

0.9.2 (2024-01-13)

• (simatec) Fix Data for X1/X3-EVC Wallbox

0.9.1 (2024-01-02)

• (simatec) Fix Inverter data
• (simatec) Fix Data for X1/X3-EVC Wallbox
• (simatec) Update Docu

0.9.0 (2024-01-02)

• (simatec) Cloud URL Check added
• (simatec) X1/X3-EVC added
• (simatec) Inverter Data for X3-Hybrid-G4 updated
• (simatec) Fix Inverter Data for X1 Hybrid G4
• (simatec) Dependencies updated

0.8.0 (2023-10-23)

• (simatec) X1-Hybrid-G4 added

0.7.7 (2023-09-06)

• (simatec) Dependencies updated
• (simatec) small Bugfix

0.7.6 (2023-07-30)

• (simatec) X3-Hybrid-G4 data updated
• (simatec) Dependencies updated
• (simatec) small Bugfix
• (simatec) Ukrainian translation added

0.7.5 (2023-05-29)

• (simatec) X3-MIC/PRO-G2 added
• (simatec) small Fix
• (simatec) Dependencies updated

0.7.4 (2023-05-04)

• (simatec) connection state added
• (simatec) suncalc package added
• (simatec) change from dawn und dusk calc

0.7.3 (2023-05-03)

• (simatec) small Bugfix
• (simatec) X3-Hybrid data added
• (simatec) Dependencies updated

0.7.2 (2023-04-27)

• (simatec) small Bugfix

0.7.1 (2023-04-27)

• (simatec) small Bugfix

0.7.0 (2023-04-26)

• (simatec) Dependencies updated
• (simatec) Config for Firmware Version added
• (simatec) small Bugfix

0.6.0 (2023-03-04)

• (simatec) Dependencies updated
• (simatec) Fix URL
• (simatec) small Bugfix

0.5.7 (2022-11-01)

• (simatec) Dependencies updated

0.5.6 (2022-09-21)

• (simatec) local mode for X1 boost added

0.5.5 (2022-09-21)

• (simatec) small Bugfixes

0.5.4 (2022-09-20)

• (simatec) small Bugfixes

0.5.3 (2022-09-20)

• (simatec) Hybrid-G4 added
• (simatec) small Bugfixes
• (simatec) appveyor test removed
• (simatec) travis test removed

0.5.1 (2022-09-13)

• (simatec) feedin added

0.5.0 (2022-09-12)

• (simatec) Dependencies updated
• (simatec) small Bugfixes
• (clausmuus) Add support for firmware version 3.001

0.4.6 (2022-04-11)

• (simatec) Fix states

0.4.5 (2022-04-04)

• (simatec) Dependencies updated
• (simatec) small Bugfixes

0.4.4 (2022-03-14)

• (simatec) Dependencies updated
• (simatec) battery data for local request added
• (simatec) night mode turn on/off added

0.4.3 (2022-02-03)

• (simatec) refactoring Sourcecode
• (simatec) Dependencies updated
• (simatec) Fix API Request

0.4.2 (2022-01-27)

• (simatec) Fix json state

0.4.1 (2022-01-26)

• (simatec) Fix react Translatation

0.4.0 (2022-01-25)

• (simatec) local request for Wifi Pocket Stick added
• (simatec) Dependencies updated
• (simatec) test and release updated
• (simatec) Number of days of history data added
• (simatec) Expert-Mode added
• (simatec) Docu updated
• (simatec) Bugfixes

0.3.7 (2021-11-17)

• (simatec) Dependencies updated
• (simatec) test and release updated

0.3.6 (2021-08-04)

• (simatec) deps fixed

0.3.5 (31.07.2021)

• (simatec) await/async functions fixed

0.3.4 (30.07.2021)

• (simatec) code cleanig
• (simatec) await functions fixed

0.3.3 (29.07.2021)

• (simatec) Formatted objects
• (simatec) await functions fixed
• (simatec) query interval changed
• (simatec) Dependencies updated

0.3.2 (28.07.2021)

• (simatec) fix for latest repo

0.3.1 (11.06.2021)

• (simatec) fix for latest repo
• (simatec) API-Token encrypted

0.3.0 (09.06.2021)

• (simatec) state settings changed
• (simatec) sentry plugin added
• (simatec) readme added
• (simatec) sunposition added
• (simatec) nightmode added

0.2.0 (07.06.2021)

• (simatec) powerdc 1-4 added
• (simatec) battPower added
• (simatec) many small bugfixes

0.1.1 (02.06.2021)

• (simatec) small Bugfixes

0.1.0 (02.06.2021)

• (simatec) first beta

License

MIT License

Copyright (c) 2021 - 2024 simatec

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.solax's Issues

additional data for Solax X3 Hybrid G3, when using a second inverter and a second meter

hello,

i'm using a second inverter with a second DTSU-666-meter.
The solax-adapter in cloud-mode report the power of this inverter as feedinpowerM2 (see log)

solaxRequest: {"success":true,"exception":"Query success!","result":{"inverterSN":"xXxXxXxXxXxX","sn":"xXxXxXxXxXxX","yieldtoday":0.7,"yieldtotal":5160.7,"feedinpower":-564,"feedinenergy":5579.32,"consumeenergy":1942.26,"feedinpowerM2":-8,"soc":10,"inverterType":"5","inverterStatus":"109","uploadTime":"2023-12-23 21:27:52","batStatus":"0"},"code":0}

In local-mode, this data is at position 100 (value: -8, see log). The unit is "Watt".
(The value is negative, because this is the standby-power of the inverter at night.)

{"type":"X3-Hybiyd-G3","SN":"xXxXxXxXxXxX","ver":"2.033.20","Data":[0,0,0,0,0,0,0,0,0.7,5160.7,-571,0,0,0,0,0,23,0.9,0,1385,0,10,216,174,25,25,17,16,3.1,3,165,1,0,0,0,0,0,0,0,0,0,5579.32,1942.18,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,9,1,1,1,900,100,10,20,25,0,0,0,0,443.4,1818.2,5568.3,0,0,2,0,0,0,0,0,0,0,0,0,1,1,1,-8,1185.49,17.29,1,273,190.6,0,0],"Information":[6,5,"X3-Hybiyd-G3","xXxXxXxXxXxX",1,4.71,0,4.53,1.07],"battery":{"brand":"1","masterVer":"5.06","slaveNum":"4","slaveVer":[0,0,0,0,0,0,0,0],"slaveType":[0,0,0,0,0,0,0,0]}}

Is it possible, to integrate this value in a future version of the adapter?
Thank you
Frank

X3-EVC Wallbox Control?

Hi,

Small question: Is it possible to control the X3-EVC Wallbox loacaly. At the moment it is contolled via vendor app, but what happens, if the cloud conenction is not available any more or lost or if you want to control it via iobroker? (talking about the charging modes)
I believe, it is not include in this adapter?

Monats Ertrag

Ist es möglich den Jahres ,Monats ,Wochen Ertrag in den Adapter zu bekommen

Liebe Grüße

Update stable version in repo from 0.7.7 to 0.8.0

Think about update stable version to 0.8.0

Version: stable=0.7.7 (62 days old) => latest=0.8.0 (15 days old)
Installs: stable=363 (54.59%), latest=38 (5.71%), total=665

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Wallbox Werte nicht vorhanden / nicht aktualisiert.

Grüßt euch!

Leider sind bei der Wallbox abfrage noch ein paar Werte unstimmig:

acpower0: keine Übermittlung der Gesamtleistung
acpower3: Textfeld ohne Leistung
capacity: keine Übermittlung
chargeduration: evtl falsches Datenformat (Datum <> Sekunden)
totalcharged: Aktualisierung sporadisch, hab noch kein System erkannt

Die Temperaturwerte stimmen auch nicht, die habe ich im JSON String aber schon nicht gefunden.

Bin mir jetzt nicht sicher ob es an meiner Installation oder an dem Adapter liegt. Habe deshalb noch eine neue Instanz installiert und mit der Wallbox verbunden. Da werden die Werte mit Fehler (außer acpower3) dann gar nicht mehr erzeugt.

Debug message:

local request: {"SN":"SQWGQWHxxx","ver":"3.004.11","type":1,"Data":[2,2,23225,23196,23118,599,604,601,1390,1400,1388,4179,20,0,5243,0,47,47,65488,64940,65184,64888,63998,0,12,0,2,15,0,0,0,0,0,4992,4992,4994,2105,3852,6145,1,0,0,0,0,0,0,0,0,1,100,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1701,0,10256,3851,6145,0,1,1,1,0,0,120,607,100,64936,2],"Information":[11,1,"C31103J1xxxxx",1,1.08,1.01,0,0,0,1],"OCPPServer":"","OCPPChargerId":""}

Version 0.9.3

Grüße und Danke
Richard

Datapoint solax.0.data.batteryChargingCycles with whitespace at the end

The Datapoint for batteryChargingCycles has a trailing whitespace at the end: "solax.0.data.batteryChargingCycles " it should be "solax.0.data.batteryChargingCycles"

Please convert README.md to plain english

The main README.md should be written in pure english. Currently you have german and english docu within one file.
This can confuse automatic translation for ioBroker webseite.

Please move the german partt to a seperate file (and add a link to it into README.md)

Thank s a lot

Wrong JSON Type

State value to set for "solax.0.data.json" has to be type "number" but received type "string"

After new installation and connection with inverter

Raspi complete freshly set up

Falsche und fehlende Daten in den Objekten

Describe the bug
In den Objekten werden mir teilweise falsche und teilweise keine Daten angezeigt. Ich kann auch nicht über die locale IP auf den Dongle zugreifen. Das Problem tritt sowohl im Localen als auch im Cloud Modus auf. Wenn ich über den AP des Dongles zugreife wird mir die lokale IP angezeigt. Wenn ich in der Solax Cloud schaue passen die Daten.

Versions:

• Adapter version: V0.4.5
• JS-Controller version: Node.js v14.19.0
• Node version: <14.19.0>
• Operating system: Linux (Raspberry Pi)

Additional context
Add any other context about the problem here.

Solax X3 Hybrid - weitere Werte gefunden

Servus,

ich habe noch ein paar weitere Werte gefunden, die in den Adapter übernommen werden könnten:

Höchste und niedrigste Spannung der Zellen im Akku
Nr. 125 BatteryCellVoltage_max Units.V div100
Nr. 126 BatteryCellVoltage_min Units.V div100

Höchste und niedrigste Temperatur der Zellen im Akku
Nr. 112 BatteryCellTemperature_max Units.C div10
Nr. 113 BatteryCellTemperature_min Units.C div10

Version 0.9.0 - zusätzliche Werte

Hallo,

ich hab die neue Version ausprobiert, funktioniert einwandfrei.

Zwei Kleinigkeiten sind mir aufgefallen:

• bei "batteryCellVoltageMin" wird als Name "Battery Cell Voltage Max" angezeigt.
• bei den Spannungswerten werden 3x,xx Volt angezeigt, richtig wären 3,xxx Volt. Wenn möglich, diese Werte bitte mit 3 Nachkommastellen anzeigen lassen.

Negative data values are not updated

At cloud mode negative data values seem to get not updated. For me feedinpower was not updated.
I have added following line to:
https://github.com/simatec/ioBroker.solax/blob/master/main.js
Line 274:
await adapter.setStateAsync('data.feedinpower', solaxRequest.data.result.feedinpower ? solaxRequest.data.result.feedinpower : 0, true);

Or remove the less equal zero check at line 315
state.val >= 0

Both fixes work for me, but I have no clue of any side affects or how this is intended to work, so hopefully you could find a proper solution.

cheers,
Thomas

Data for Inverter X1 Hybrid G4 are not correct

Please add the Inverter Solax X1 Hybrid G4 to the adapter. At the moment, when operating this inverter, the data is displayed at incorrect data points.

{"inverterSN":"xxxxxxxxxxxxxxx","sn":"xxxxxxxxxxxx","inverterType":"X1-Hybrid-G4","inverterStatus":"Wait Mode","uploadTime":"Thu Oct 19 2023 21:56:17 GMT+0200 (Mitteleuropäische Sommerzeit)","connectType":"local","online":true,"connection":true,"firmwareVersion":"3.006.04","totalSize":5,"acvoltage1":0,"acvoltage2":0,"acvoltage3":0,"accurrent1":0,"accurrent2":0,"accurrent3":0,"acpower1":0,"acpower2":0,"acpower3":0,"acpower":0,"dcvoltage1":0,"dcvoltage2":20.900000000000002,"dccurrent1":0,"dccurrent2":0.30000000000000004,"dcpower1":0,"dcpower2":0,"acfrequency1":0,"acfrequency2":0,"acfrequency3":0,"voltageeps1":0,"voltageeps2":10,"voltageeps3":0,"currenteps1":0,"currenteps2":4,"currenteps3":0,"powereps1":0,"powereps2":0,"powereps3":0,"feedinpower":512,"batteryVoltage":0,"batteryCurrent":0,"batteryPower":0,"cpuTemperature":0,"powerConsumer":0,"inverterTemperature":219,"yieldtotal":0,"yieldtoday":0,"totalBatteryInputFromGrid":0,"totalBatteryDischargeEnergy":300,"totalBatteryChargeEnergy":6253.6,"todaysBatteryDischargeEnergy":0,"todaysBatteryChargeEnergy":0,"totalpvenergy":0,"pvenergy":0,"totalFeed":0,"totalconsumption":0,"feedinenergy":0,"consumeenergy":0.2,"batteryCapacityRemainig":0,"batteryTemperature":0,"batteryRemainingEnergy":0,"batteryChargingCycles ":0}

2023-10-19 11:43:16.664 - �[34mdebug�[39m: solax.3 (10170) local request: {"sn":"xxxxxxxxxxxx","ver":"3.006.04","type":15,"Data":[2310,10,191,5000,2217,0,8,0,192,0,2,208,0,2,0,0,0,0,0,0,0,0,0,0,100,0,17,3598,0,0,0,0,0,0,512,0,20,0,191,28,0,0,0,0,0,0,0,0,0,0,0,1,1,0,217,0,65345,65535,65386,65535,0,0,0,0,0,0,0,0,0,0,0,0,0,0,3000,0,62536,65535,0,0,0,0,0,0,0,2,0,0,0,0,0,0,20,0,0,0,0,0,0,11008,4875,5898,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"Information":[5,15,"Hxxxxxxxxxxxxxx",8,1.29,0,1.28,1.04,0,1]}

Many thanks

Default value is wrong

This is the log of adapter start:

solax.0 | 2022-04-03 08:51:38.893 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.893 | warn | Object solax.0.info.success is invalid: Default value has to be type "boolean" but received type "string"
solax.0 | 2022-04-03 08:51:38.887 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.886 | warn | Object solax.0.history.yield_7_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.883 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.883 | warn | Object solax.0.history.yield_6_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.866 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.866 | warn | Object solax.0.history.yield_5_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.863 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.862 | warn | Object solax.0.history.yield_4_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.858 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.858 | warn | Object solax.0.history.yield_3_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.853 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.853 | warn | Object solax.0.history.yield_2_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.846 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.846 | warn | Object solax.0.history.yield_1_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.837 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.837 | warn | Object solax.0.suninfo.Azimut is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:38.829 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:38.828 | warn | Object solax.0.suninfo.Altitude is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:34.791 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
solax.0 | 2022-04-03 08:51:34.790 | info | terminating
solax.0 | 2022-04-03 08:51:34.790 | info | Got terminate signal TERMINATE_YOURSELF
solax.0 | 2022-04-03 08:51:11.684 | warn | system settings cannot be called up. Please check configuration!
solax.0 | 2022-04-03 08:51:11.630 | info | starting. Version 0.3.7 in /opt/iobroker/node_modules/iobroker.solax, node: v14.19.1, js-controller: 4.0.21
solax.0 | 2022-04-03 08:51:11.608 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.608 | warn | Object solax.0.info.success is invalid: Default value has to be type "boolean" but received type "string"
solax.0 | 2022-04-03 08:51:11.587 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.587 | warn | Object solax.0.history.yield_7_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.583 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.583 | warn | Object solax.0.history.yield_6_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.578 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.578 | warn | Object solax.0.history.yield_5_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.574 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.574 | warn | Object solax.0.history.yield_4_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.569 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.569 | warn | Object solax.0.history.yield_3_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.566 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.566 | warn | Object solax.0.history.yield_2_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.562 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.562 | warn | Object solax.0.history.yield_1_days_ago is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.559 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.559 | warn | Object solax.0.suninfo.Azimut is invalid: Default value has to be type "number" but received type "string"
solax.0 | 2022-04-03 08:51:11.536 | warn | This object will not be created in future versions. Please report this to the developer.
solax.0 | 2022-04-03 08:51:11.535 | warn | Object solax.0.suninfo.Altitude is invalid: Default value has to be type "number" but received type "string"
host.iobroker | 2022-04-03 08:51:06.833 | error | iobroker  host.iobroker Object solax.0.info.success is invalid: Default value has  to be type "boolean" but received type "string"host.iobroker This  object will not be created in future versions. Please report this to the  developer.
host.iobroker | 2022-04-03 08:51:06.823 | error | iobroker  host.iobroker Object solax.0.history.yield_7_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.817 | error | iobroker  host.iobroker Object solax.0.history.yield_6_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.810 | error | iobroker  host.iobroker Object solax.0.history.yield_5_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.804 | error | iobroker  host.iobroker Object solax.0.history.yield_4_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.798 | error | iobroker  host.iobroker Object solax.0.history.yield_3_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.791 | error | iobroker  host.iobroker Object solax.0.history.yield_2_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.785 | error | iobroker  host.iobroker Object solax.0.history.yield_1_days_ago is invalid:  Default value has to be type "number" but received type  "string"host.iobroker This object will not be created in future  versions. Please report this to the developer.
host.iobroker | 2022-04-03 08:51:06.778 | error | iobroker  host.iobroker Object solax.0.suninfo.Azimut is invalid: Default value  has to be type "number" but received type "string"host.iobroker This  object will not be created in future versions. Please report this to the  developer.
host.iobroker | 2022-04-03 08:51:06.765 | error | iobroker  host.iobroker Object solax.0.suninfo.Altitude is invalid: Default value  has to be type "number" but received type "string"host.iobroker This  object will not be created in future versions. Please report this to the  developer.```


 - Adapter version: 0.3.7
 - JS-Controller version: 4.0.21
 - Node version: 14.19.1
 - Operating system: Debian 11

Objekt "acpower" wird nicht aktualisiert

Hallo,
ich habe leider das Problem, dass nach einer unbestimmten Zeit das Objekt "acpower" nicht mehr aktualisiert wird. Alle anderen Objekte werden weiterhin problemlos aktualisiert.
Ich hatte das Problem jetzt bereits zum 2. Mal. Der Datenpunkt wird ca. 1 Woche lange aktualisiert, dann nicht mehr. Wenn ich den Adapter stoppe, den Datenpunkt lösche und den Adapter wieder starte, wird er sofort wieder neu angelegt, korrekt abgerufen und auch wieder aktualisiert.

Please fix issues reported by adapter checker

Please fix issues reported by adapter checker

ioBroker/ioBroker.repositories#2373 (comment)

Update stable version in repo from 0.3.7 to 0.4.6

Think about update stable version to 0.4.6

Version: stable=0.3.7 (160 days old) => latest=0.4.6 (15 days old)
Installs: stable=110 (71.43%), latest=22 (14.29%), total=154
Click to edit

negative Werte

negative Werte werden mit z.B. 65148 A angezeigt

hinzufügen von "maxValue: 32768" zu den entsprechenden Datenpunkten in der main.js

Status Icon

Das Status Icon in der Ansicht Instanzen bleibt immer grün (Aktiv und Lebenszeichen) auch wenn keine Verbindung zum Solax WIFI Adapter besteht (Adapter wurde auch schon ausgesteckt)
Hier wäre eine genauere farbliche Statusanzeige hilfreich

Solax adapter not refreshing data

The adapter connects to the pocket Wifi and collects the data only once after a restart of the adapter.

After the restart of the adapter, the adapter is not refreshing/polling the solax wifi pocket.

Admin version used: 6.0.7
Solax adapter version: 0.4.6

Bekomme keine LOKALEN Daten mehr vom WIFI Stick

Ich betreibe den Adapter im LOCAL (expert) Mode
Der Adapter hat 5 Monate perfekt funktioniert. Seit einer Woche bekomme ich aber, im LOCAL Expoert Mode, keine Daten mehr vom WIFI Stick
Mir einem "curl -d "optType=ReadRealTimeData&pwd=xxxxxxxxx" -X POST http://192.168.12.xxx" in der Komandozeile auf einem PC bekomme ich die Daten
Nach Installation einer neuen 2. Instanz bekomme ich Daten aus der Solax Cloud, allso funktioniert der Stick offensichtlich. - leider werden die Daten aus der Cloud nur im 5 Minuten Takt aktualisiert.
Ich kann nicht mehr nachvollziehen ob und was sich geändert haben soll.

Ich habe schon alles probiert, restore über den Backup Adapter,
Neuinstallation mit "iobroker/iobroker 7.2.0 Docker" Image auf meiner QNAP
Alle Solax Objekte gelöscht , Alles upgedated ...
Ich habe nun keine Idee mehr, da auch das Log trotz "Silly" Log Level keine Informationen liefert

Was kann ich noch tun ?

Das ist alles was ich nach einem Neustart im Log sehe:

solax.0	29152	2023-03-16 21:55:57.496	info	starting. Version 0.6.0 (non-npm: simatec/ioBroker.solax#1e2f5bcbe778bbbb9f881ed1f4a094d9fb2e29f8) in /opt/iobroker/node_modules/iobroker.solax, node: v16.19.1, js-controller: 4.0.24
solax.0	28103	2023-03-16 21:55:52.803	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
solax.0	28103	2023-03-16 21:55:52.801	info	terminating
solax.0	28103	2023-03-16 21:55:52.799	info	Got terminate signal TERMINATE_YOURSELF

Versions:
Solax Adapter 0.5.7 und 0.6.0
Wifi Adapter Version 3.0.0.21 (Config Seiten sind im lokalen Netz erreichbar)

Plattform: docker
Betriebssystem: linux
Architektur: x64
CPUs: 4
Geschwindigkeit: 3112 MHz
Modell: AMD Embedded R-Series RX-421ND
RAM: 19.51 GB
System-Betriebszeit: 16 T. 19:56:08
Node.js: v16.19.1
time: 1678562707284
timeOffset: -60
Anzahl der Adapter: 470
NPM: 8.19.3
Datenträgergröße: 580.33 GB
freier Festplattenspeicher: 119.01 GB
Betriebszeit: 00:40:43
Aktive Instanzen: 20
Weg: /opt/iobroker/
Hostname: iobroker-2
js-Controller: 4.0.24

Request interval

Hallo,

bei mir funktioniert der request interval nicht, obwohl auf 6 Minuten eingestellt.
Bei einem Neustart des Adapters werden die Daten Richtig abgerufen. Nach 6 Minuten kommen keine neuen Daten. Im Log erscheint folgendes:

solax.0 | 2021-08-29 11:27:50.703 | debug | is Night: true
solax.0 | 2021-08-29 11:27:50.686 | debug | Sun Azimut: NaN°
solax.0 | 2021-08-29 11:27:50.686 | debug | Sun Altitude: NaN°
solax.0 | 2021-08-29 11:27:50.686 | debug | calculate astrodata ...
solax.0 | 2021-08-29 11:27:50.685 | debug | current local Time: 11:27
solax.0 | 2021-08-29 11:27:50.685 | debug | nauticalDawn: aN:aN
solax.0 | 2021-08-29 11:27:50.684 | debug | nauticalDusk: aN:aN
solax.0 | 2021-08-29 11:27:50.683 | debug | nightCalc started ...

Kann es daran liegen, dass hier eine Variable "Night" auf true steht, obwohl das nicht stimmt und somit keine Daten abgerufen werden? Oder wo liegt der bug.

Wallbox Werte

Moin,

bei den Daten der Wallbox stimmen einige Werte nicht.

1. Chagring-Mode Green und Eco sind vertauscht
2. acpower1 hat sich ein Komma eingeschlichen, hier wird 13,23 W anstatt 1323 W ausgegeben.

AC Power for 3phases is not correctly accumulated

The power of all three phases is not correctly accumulated.
Solax X3 mic 6k G2 with USB Dongle v3 (expert mode) with local data. (not cloud)
release 0.7.4 installed

X3 G4 Overflow Values

Hi simatec,

thanks for adding the Overflow Values for the X3 G4 Model.

Could you change the Value from kw to "Count" or "Number" for these Values. There should also be no multiplier.
Perhaps you could also add an "l" to "Overfow" at 77/87/93 to have "Overflow".

69: { name: 'data.yieldtotalOverflow', description: 'Inverter AC-Energy out total Overflow', type: 'number', multiplier: 0.1, unit: 'kWh', role: 'value.power.consumption' }, // 'Total Energy': (19, 'kWh'),
75: { name: 'data.totalBatteryDischargeEnergyOverflow', description: 'Total Battery Discharge Energy Overflow', type: 'number', multiplier: 0.1, unit: 'kWh', role: 'value.power.consumption' }, // Total Battery Discharge Energy
77: { name: 'data.totalBatteryChargeEnergyOverfow', description: 'Total Battery Charge Energy Overflow', type: 'number', multiplier: 0.1, unit: 'kWh', role: 'value.power.consumption' }, // Total Battery Charge Energy
81: { name: 'data.totalpvenergyOverflow', description: 'Total PV Energy Overflow', type: 'number', multiplier: 0.1, unit: 'kWh', role: 'value.power.consumption' }, // 'Total Consumption': (42, 'kWh'),
87: { name: 'data.totalFeedOverfow', description: 'Total Feed-in Energy Overfow', type: 'number', multiplier: 0.01, unit: 'kWh', role: 'value.power.consumption' }, // 'Total Feed-in Energy': (41, 'kWh'),
91: { name: 'data.feedinenergyOverflow', description: 'Feed in Energy Overflow', type: 'number', multiplier: 0.01, unit: 'kWh', role: 'value.power' }, // Feed in Energy: (12.2,'kWh'),
93: { name: 'data.consumeenergyOverfow', description: 'Consume Energy Overfow', type: 'number', multiplier: 0.01, unit: 'kWh', role: 'value.power' }, // Consume Energy: (7.8,'kWh'),

The "Line" 88 + 89 are the same except the number. There should be the "Overflow" additive in Line 89, but without the multiplier and Count or Number as unit.

Perhaps you can also add line 72 as "totalBatteryInputFromGridOverflow".

Thanks for your effort!

Wallbox Integration

Moin,

anbei ein paar Werte die ich schon von der Wallbox identifizieren konnte.
{ /****************************************** X1/X3-EVC *****************************************/ isOnline: { name: 'info.online', description: 'Charger Online', type: 'boolean', role: 'switch' }, 2: { name: 'data.acvoltage1', description: 'Grid Voltage 1', type: 'number', multiplier: 0.1, unit: 'V', role: 'value.power' }, // 'AC Voltage 1': (0, 'V'), 3: { name: 'data.acvoltage2', description: 'Grid Voltage 2', type: 'number', multiplier: 0.1, unit: 'V', role: 'value.power' }, // 'AC Voltage 2': (1, 'V'), 4: { name: 'data.acvoltage3', description: 'Grid Voltage 3', type: 'number', multiplier: 0.1, unit: 'V', role: 'value.power' }, // 'AC Voltage 3': (2, 'V'), 13: { name: 'data.accurrent1', description: 'Charge Current 1', type: 'number', maxValue: 32768, multiplier: 0.1, unit: 'A', role: 'value.power' }, // 'Output Current 1': (3, 'A'), 14: { name: 'data.accurrent2', description: 'Charge Current 2', type: 'number', maxValue: 32768, multiplier: 0.1, unit: 'A', role: 'value.power' }, // 'Output Current 2': (4, 'A'), 15: { name: 'data.accurrent3', description: 'Charge Current 3', type: 'number', maxValue: 32768, multiplier: 0.1, unit: 'A', role: 'value.power' }, // 'Output Current 3': (5, 'A'), 16: { name: 'data.accurrent1', description: 'Grid Current 1', type: 'number', maxValue: 32768, multiplier: 0.1, unit: 'A', role: 'value.power' }, // 'Grid Current 1': (3, 'A'), 17: { name: 'data.accurrent2', description: 'Grid Current 2', type: 'number', maxValue: 32768, multiplier: 0.1, unit: 'A', role: 'value.power' }, // 'Grid Current 2': (4, 'A'), 18: { name: 'data.accurrent3', description: 'Grid Current 3', type: 'number', maxValue: 32768, multiplier: 0.1, unit: 'A', role: 'value.power' }, // 'Grid Current 3': (5, 'A'), 23: { name: 'data.plugTemperature', description: 'Plug temperature', type: 'number', unit: '°C', role: 'value.temperature' }, // 'Ladepistolen Temperature, 24: { name: 'data.boardTemperature', description: 'Mainboard temperature', type: 'number', unit: '°C', role: 'value.temperature' }, // 'Mainboard Temperature, }
information_dataPoints:
{ /***************************************** X1/X3-EVC ***************************************/ 0: { name: 'info.totalSize', description: 'Total Size of Power', type: 'number', unit: 'kW', role: 'value.power' }, 2: { name: 'info.chargerSN', description: 'Unique identifier of charger (Serial No.)', type: 'string', role: 'text' }, 4: { name: 'info.version', description: 'Version', type: 'string', role: 'text' },

Hier noch einmal der komplette Datensatz:
{"SN":"SQKASDFGHJ","ver":"3.004.11","type":1,"Data":[0,0,23226,23502,23810,0,0,0,0,0,0,0,0,0,0,0,73,65494,65485,0,0,0,0,0,20,0,0,15,0,0,0,0,0,4994,5002,5000,4916,7690,5898,1,0,0,0,0,0,0,0,0,1,100,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,1,0,0,119,1204,1000,64876,1],"Information":[11,1,"C3110123456789",1,1.08,1.01,0,0,0,1],"OCPPServer":"","OCPPChargerId":""}

Wenn mein Auto da ist gibt es ein update der Werte.

History Daten werden zu spät kopiert

Describe the bug
Die History Daten werden exakt 2 Stunde zu spät ausgelesen und geschrieben.

Expected behavior
Die Daten sollten um 23:59:50 gelesen werden

Das sieht nach einem Zeitzonenproblem aus. Wie und wo kann man das beeinflussen? Einstellung am Adapter selber habe ich keine gefunden.

add Data from DTSU666-D (Smartmeter Solax) (LOCAL)

Daten von Netz/Smartmeter werden nicht mit in den Adapter übertragen,
diese wären sehr wichtig um eine vernünftige Nulleinspeisung zu realisieren.

Im Cloud request sind diese Daten enthalten:

In der Solax-App können diese Daten ebenfalls bei der Lokalen Verbindung abgerufen werden:

Sowie auf der Website:

Da ich eine hohe Autarkie anstrebe und die Täglichen Überschüsse möglichst effizient nutzen möchte wäre ich euch unglaublich dankbar das ihr diese Daten in die json integriert.

Da ich leider nicht weiß wie ihr an die Daten rankommt und ein curl bei mir negativ ausfällt bin ich auf euch angewiesen.
Ich bin leider "nur" Hardware-Entwickler und nicht so tief in der Materie wir ihr, aber falls ich euch irgendwie behilflich sein kann meldet euch einfach und ich schau was ich tun kann.

LG Philipp

Issue + Solution for ioBroker (showing the wrong value for batpower)

The probleme that I was facing is that the solax adapter reads out the wrong value for "batpower". When the value is actually =0.0 it does not write it in the batpower datapoint. Instead it just remains on the previous value which for my specific need is an issue because as I am doing a full visualisation, it shows the wrong value and with that beeing the case it also triggers the wrong animation in my vis.

I fixed it by writting a Blokly script in the ioBroker that triggers every 10 seconds and if the soc (state of charge) of the Battery is =100 it just changes the value of the datapoint to 0 (You also need to allow "Writable" for batpower to work).

Not really sure why this happens maybe it is because I am using it with a Qcells system instead of a Solax one but the rest just works perfectly. BTW Solax and Qcells kind of belong together so the adapter is cross compatible to qcells in case you didnt know.

Adapter blockiert Pocket WiFi 3

Describe the bug :

Ausgangslage:
Adapter: v0.6.0
Pocket Wifi 3 Firmware Version: 3.001.02
Betriebsart: Local IP Wifi Pocket Stick

Der Adapter arbeitet einwandfrei und liefert die Daten während ca. 5 bis 10 Minuten.
Danach blockiert der Adapter die Kommunikation mit dem Pocket Wifi d.h. das Pocket Wifi kann mit der lokalen IP-Adresse via Browser nicht mehr angesprochen werden - es gibt keine Rückmeldung via Browser.

Sobald der Adapter gestoppt wird, kann das Pocket Wifi via Browser wieder korrekt angesprochen werden.

Die Abfrage mittels curl funktioniert ohne Probleme.

Update stable version in repo from 0.6.0 to 0.7.4

Think about update stable version to 0.7.4

Version: stable=0.6.0 (76 days old) => latest=0.7.4 (15 days old)
Installs: stable=319 (57.89%), latest=36 (6.53%), total=551
Click to edit

Wallbox integration error: "Cannot read properties of undefined (reading 'name')"

Describe the bug
Hallo!

Vielen Dank für die Wallbox Integration, leider schlägt nach dem Update der Instanzstart fehl. Folgende Logs werden geschrieben:

solax.1 | 2024-01-02 10:26:29.394 | error | Cannot read properties of undefined (reading 'name') solax.1 | 2024-01-02 10:26:29.393 | error | TypeError: Cannot read properties of undefined (reading 'name') at /opt/iobroker/node_modules/iobroker.solax/main.js:608:71 solax.1 | 2024-01-02 10:26:29.387 | error | unhandled promise rejection: Cannot read properties of undefined (reading 'name') solax.1 | 2024-01-02 10:26:29.386 | 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().

Die Verbindung zu Wechselrichter bleibt bestehen und fragt auch weiterhin die Werte ab.

Screenshots:
Version 0.9.0:

Log:

Nach downgrade auf Version 0.8.0:

Systeminfo:
CPU: 8,2 %
RAM: 70 %
Betriebszeit: 6h
Verfügbar: 5.0.17
Installiert: 5.0.17
Plattform: linux
Betriebssystem: linux
Architektur: x64
CPUs: 4
Geschwindigkeit: 872 MHz
Modell: Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz
RAM: 3.7 GB
System-Betriebszeit: 05:47:33
Node.js: v18.19.0
NPM: 10.2.3
Adapter-Anzahl: 615
Datenträgergröße: 50.1 GB
Freier Festplattenspeicher: 32.9 GB
Aktive Instanzen: 22

Exported Power Value

It seems to be that the "Exported Power" value is not translated correctly.
I have a 3 phase solax meter SMD630 installed directly at house connection, from wicht the solax inverter might get the value.

In the "solax.0.data.exportedpower" object I permannently get a value near 65535 W (hex FFFF) even in the late afternoon when there is very less harvesting and less power consumation.
When I switch on a 1000 W devices, the values decreases ! down to about 64500 W
However I expect the correct value for imported/exported power including localy consumed power
It seems to me that here is just somethink incorrect with the sining for that value

The Solax Web Interface is showing all corret values

I have a X1-Boost/Air/Mini with the latest Adpater Version 0.5.7 an a most current ioBroker environment.
I have configured local access via WIFI 3.003.02 Stick, witch was working pretty well so far

I am happy to test an update or provide more information

Thanks

Solax Pocket Wifi 2 mit Firmware 3.x.x.x

Hallo, ich möchte meinen Solax X3 Hybrid G2 über eine lokale Verbindung mit iobroker verbinden und habe dazu einen Pocket Wifi V2 (grau).
Als Firmware ist hier v3.001.02 installiert. In der Beschreibung taucht diese HW/SW-Kombination nicht auf, ein Downgrade auf v2.x schlägt fehl.
Die Verbindung iobroker - solax wifi wird hergestellt, aber die Inverterwerte sind allesamt 0.
Ist dieses Verhalten schon einmal vorgekommen?

Danke & Grüße
Frank

Nachtrag:
Über den LAN-Port des WR wird eine Cloudverbindung hergestellt, das funktioniert.

Adapter verliert Cloud Verbindung

Heute morgen gegen 3:30 hat der Adapter die Verbindung zur SolaX Cloud verloren.
Der direkte Aufruf der API URL, so wie sie in der SolaX Cloud beschrieben wir funktioniert einwandfrei.

Eine Umstelelung des Loglevel auf debug zeigte folgendes:

Versions:

• Adapter version: 0.7.7
• JS-Controller version: 5.0.12
• Node version: v16.20.2
• Operating system: linux

Temperatur Wechselrichter

Servus,

ich nutze den Adapter 0.7.5 seit einiger Zeit, echt Klasse!
Hab im Issue #168 gelesen, dass noch die Temperaturdaten zum Wechselrichter fehlen.

Ich habe einen von Q-Cells gelabelten X-3 Hybrid G4 ohne aktive Kühlung und mir eine Kühlung gebastelt, da der WR doch recht warm wird.

Habe heute die Temperatur an den rückseitigen Kühlrippen mit laufender Kühlung gemessen, dann die Kühlung deaktiviert und anschließend wieder aktiviert.

Aufgrund der gemessenen Werte gehe ich davon aus, dass die Temperatur des WR im Wert #54 in °C ausgegeben wird.

Update stable version in repo from 0.5.7 to 0.6.0

Think about update stable version to 0.6.0

Version: stable=0.5.7 (138 days old) => latest=0.6.0 (15 days old)
Installs: stable=374 (79.24%), latest=41 (8.69%), total=472
Click to edit

Überlauf der Summenwerte

Ich habe einen SolaX X3 Hybridwechselrichter 15.0 G4.2 im lokalen modus mit dem Adapter 0.7.5

Ich habe ein Überlaufen der Summenwerte beobachtet:

Der Wert für
Total PV Energy / data.totalpvenergy (Zeile 80)
ist bei mir 1x "Übergelaufen", daher ist jetzt in Zeile 81 eine 1
Der Überlauf ist bei 6554 in Zeile 80 passiert, lt. Grafana.
Total Feed-in Energ / data.totalFeed (Zeile 86)
ist bei mit 7 mal "Übergelaufen" daher ist jetzt in Zeile 87 eine 7
Der Überlauf ist bei 655 in Zeile 87 passiert, lt. Grafana.

Anbei mein aktuelles Ergebnis des curl:
{"sn":"XXXXXX","ver":"3.008.10","type":14,"Data":[2358,2408,2365,163,156,155,3844,3762,3667,11273,4891,6235,134,84,6556,5271,5002,5002,5001,2,0,0,0,0,0,0,0,0,0,0,0,0,0,1,10816,0,0,0,0,47910,0,0,4779,0,0,1,53,457,256,4612,2829,5894,100,0,60,0,0,0,0,0,0,0,0,0,0,0,0,0,64966,0,469,116,0,0,9876,0,9763,0,29,43,3056,1,506,0,0,0,17523,7,41830,0,4010,0,0,0,0,0,0,0,0,0,0,0,1,76,1,29,133,256,5256,3600,0,350,215,193,33,33,43,2139,258,9766,9252,9252,8995,0,0,3338,3301,26234,30,21302,14389,18757,12609,16692,12611,14384,21302,14389,18757,12609,16692,12611,14384,21302,14389,18754,12345,16694,12867,14131,21302,14389,18754,12345,16694,12355,13872,21302,14389,18754,12849,16688,12867,12848,1281,1799,514,769,0,47910,0,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"Information":[15.000,14,"XXXXXXX",8,1.30,0.00,1.28,1.09,0.00,1]}

Ich vermute das
Total Consumption / data.totalconsumption (Zeile 88)
und
Inverter AC-Energy out total / data.yieldtotal (Zeile 68)
beide jeweils in den Zeilen darauf (89 und 69) Überlaufcounter haben. Da die Werte bei mir noch keinen "Überlauf" erreicht haben, also noch bei 0 stehen, kann ich das noch nicht bestätigen.

Ich weiß jetzt nicht was besser ist. Ich würde eine "fertige" Aufmultiplizierung der "Total" Werte bevorzugen. Evtl. zusätzlich die Ausgabe der Überlaufcounter und ggf. die "Rohdaten" für die Nutzer, die sich bereits selbst etwas gebaut haben?

Nebenbei ist mir aufgefallen dass die Werte:
23 EPS 1 Voltage data.voltageeps1
24 EPS 2 Voltage data.voltageeps2
25 EPS 3 Voltage data.voltageeps3
26 EPS 1 Current data.currenteps1
27 EPS 2 Current data.currenteps2
28 EPS 3 Current data.currenteps3
alle W als Maßeinheit haben, dass müsste V bzw. A sein.

Vielen Dank für die viele Arbeit, die Du in dieses Projekt investierst!

JSON aus lokaler Anbindung nicht stimmig

Hallo,

hier das JSON aus der lokalen Anbindung

{"inverterSN":8,
"sn":"xxxxxxxxx",
"inverterType":14,
"inverterStatus":"Wait Mode",
"uploadTime":"Sun Sep 11 2022 08:07:27 GMT+0200 (Mitteleuropäische Sommerzeit)",
"connectType":"local",
"online":true,
"firmwareVersion":"3.003.02",
"totalSize":15,
"currentdc1":0,
"currentdc2":0,
"voltagedc1":0,
"voltagedc2":0,
"outputcurrent":0,
"acvoltage":0,
"acpower":0,
"inverterTemp":0,
"yieldtoday":0,
"yieldtotal":0,
"exportedPower":5971,
"powerdc1":3739,
"powerdc2":0,
"batteryVoltage":1,
"batteryCurrent":0,
"batteryPower":42,
"batteryTemperature":0,
"batteryCapacityRemainig":18,
"totalFeed":0,
"totalconsumption":4250,
"powernow":0,
"gridfrequency":2824}

hier das fast zeitgleiche JSON aus der API

{"success":true,"exception":"Query success!","result":{
"inverterSN":"xxxxxxxxx",
"sn":"xxxxxxx",
"acpower":0.0,
"yieldtoday":0.0,
"yieldtotal":0.0,
"feedinpower":0.0,
"feedinenergy":0.0,
"consumeenergy":0.0,
"feedinpowerM2":0.0,
"soc":98.0,
"peps1":0.0,
"peps2":0.0,
"peps3":0.0,
"inverterType":"14",
"inverterStatus":"107",
"uploadTime":"2022-09-11 08:05:40",
"batPower":0.0,
"powerdc1":0.0,
"powerdc2":46.0,
"powerdc3":null,
"powerdc4":null,
"batStatus":"0"}}

Die Werte passen leider überhaupt nicht. Der WR ist zur Zeit nur im EPS Modus da es morgen final an angeschlossen wird. sprich nur Akku und Solar.

Werde erstmal wieder cloud wechseln. Hast du dazu eine Idee woran es liegen kann?

VG und Danke für die tolle Arbeit

Andreas

Erweiterung für Q.HOME+ ESS

Hallo,

wie realistisch wäre eine Erweiterung um die Q.HOME Cloud für die Qcells Hyb G3? Ist identisch zu Solax nur gebrandet und andere Web Adressen.

Ich werde gerne auch unterstützen soweit ich kann, bin allerdings kein Softwareentwickler.

Was ich bisher gesehen hab ist alles 1:1 identisch.

Kann gerne weitere Infos beisteuern um Klarheit zu schaffen.

Grüße fanatikz

keine Wallbox Daten mehr

Seit dem letzten Update kommen kein Wallbox Daten mehr.
Die Werte werden nicht mehr aktualisiert.
Es scheint, als ob der Adapter den Geräte-Typ nicht mehr zuordnen kann. Nach einer neu Anlage der Instanz werden die Datenpunkte gar nicht erstellt.

Adapter verliert Verbindung zur Solaranlage nach Wechsel des Clients im Heimnetz von Router auf Repeater

Sobald der Client (welcher die Daten abfragt) im Heimnetz seine Verbindung vom Router auf z.B einen Repeater wechselt verliert der Adapter seine Verbindung zur Anlage. Der Adapter muss dann wieder neu gestartet werden um wieder eine Verbindung herzustellen und Daten zu liefern. Die Abfrage der Daten erfolgt lokal.

I can't downgrade

Describe the bug
I tried to downgrade my pocket WiFi V2 versión 3.001.002 but It failed

To Reproduce

Expected behavior

Screenshots & Logfiles

Versions:

Additional context
Add any other context about the problem here.

Bekomme den Pocket Wifi V3 nicht ans Laufen

Hallo, erst mal Vielen dank für die Arbeit mit dem Adapter !
Leider bekomme ich den Pocket Wifi V3 nicht ans Laufen.
Ich habe allerdings auch keine Seriennummer des Kommunikationsmoduls gefunden.
Der Pocket Wifi hat nur eine Registrierungsnummer.

Die Fehlermeldung ist entweder
solaxRequest: {"success":false,"exception":"Query success!","result":"no auth!"}
-- wenn ich die Seriennummer des X1 verwende
oder
solaxRequest: {"success":false,"exception":"Query success!","result":"this sn did not access!"}
-- wenn ich die Registrierungsnummer des Pocket Mini verwende

Mach ich hier was falsch, oder geht der Pocket Mini V3 nicht (noch nicht ;) ) ?

Update stable version in repo from 0.3.7 to 0.4.3

Think about update stable version to 0.4.3

Version: stable=0.3.7 (93 days old) => latest=0.4.3 (15 days old)
Installs: stable=80 (82.47%), latest=13 (13.4%), total=97
Click to edit

API call fails

Describe the bug
I use your ioBroker adapter since one year for my two Solax inverters. One Hybrid one from 2019 and the other is a X1 3,6-T.
Since yesterday 2 pm I don't receive any updates from the solax cloud.
There are no error messages seen in ioBroker log.

If I go manually to solax cloud or look into my solax app I see the latest values how many power is available. Only ioBroker adapter is affected.

I restarted my inverters already and restartet the iobroker Adapter multiple times. I also installed another instance of the solax adapter and entered again my credentials.

Versions:

• Adapter version: 0.5.7
• JS-Controller version: 4.0.24
• Node version: 16.16.0
• Operating system: linux / docker

Wifi 3.0 dongle

I am using a "blue" usb 3.0 Wifi dongle. The firmware version is 3.001.04. Th wifi accesspoint is Wifi_SRxxxxxxx and the ip-addres is 192.168.10.10.

The Solax adapter doesn't return the inverter-data or any info values

no data on version 0.7.4

Ich nutze aktuell die Version 0.6.0 und Wifi Stick´s mit der Version 2 und 3.
Stick V2.0 = 2.033.20 und Stick V3.0 = 3.003.02
Wenn ich jetzt auf die Version 0.7.4 aktualisiere bekomme ich keine Daten mehr von den Stick´s V3.0.

Update stable version in repo from 0.6.0 to 0.7.5

Think about update stable version to 0.7.5

Version: stable=0.6.0 (101 days old) => latest=0.7.5 (15 days old)
Installs: stable=369 (63.18%), latest=38 (6.51%), total=584
Click to edit