missing values in three_phase_hv.py #305
Comments
|
Please share your config |
|
|
I also have an issue with missing/incorrect values read from my 50kW 3ph Deye inverter at my office. When I restart your sunsynk add-on, the log shows several "unknown sensors specified" (see below log). Secondly, the decimal placement for the power reading of PV1, to 4 is incorrect, for example it reads 220.5W instead of 2205W. Thirdly, my 50kW inverter features two battery inputs, and your add-on is only reading the data of battery 1. And lastly, the decimal placement for the battery voltage is also incorrect, for example it reads 58.775V instead of 587.75V [14:48:23] INFO: Service restart after closing |
You are using LV definition on HV inverter and this causes the decimal to be off. |
|
That makes sense, the UI configuration only had the two options single-phase and three-phase to select. Failed to save add-on configuration, value must be one of ['single-phase', 'three-phase']. |
|
I'm not using the HA addon, but I think HV is only present on edge(or something similar) version. |
It's present in the dev/edge Version of the Addon. I use it for my HV inverters, works fine with a few unknown values (inverter Version etc) showing up. |
|
#309 should address those unknown values |
#309 Talks about making the entities model-aware ... but the Model Codes back as unkown value, so that would have to be fixed first, I guess |
|
#309 addresses unknown sensors, not unknown values you have here |
|
@bsafh looking at your errors, these sensors have undocumented values. You can change them in HA once and then it doesn't complain anymore. If you don't know what they are for, I'd suggest to remove them from SENSORS. |
|
@kellerza should we add all "No work" values to all those bitmask sensors? For some we have one of the Noworks defined, for some we have only Enable and Disable. Inverters come from factory with Nowork values and this causes the "Unknown register value". Or add some flag to silence those Nowork values? |
|
Well, I do know the model: Should that not be included in the code? "Or add some flag to silence those Nowork values?" |
|
Device type is not part of my last messages, this is different issue. |
|
I think the documentation about register 0 is wrong. My SUN-20K-SG01HP3-EU-AM2 has value 6 too. Maybe we should drop the sensor at all. Users probably know what kind of inverter they have. |
Why drop it?
So type 6 is documented, just not translated to englisch.
I don't think so ... |
|
Its just wild guess, but maybe 0x0600 means 6, which means 3PH HV. 600 and 601 are wrong fore sure since your 10kW and my 20kW inverters have the same value. |
|
#310 fixes inverter type for 3ph inverters based on values seen on the field. |
|
After updating to the new version I now get |
|
See as well bc65f2a |
|
The full register list seems to be |
|
It doesn't help. I have it already. What was the last working version? |
|
The one from just before. |
|
If you look at the 3ph definition file on github, you can click on “blame” and see what lines were change in which commits you can also look at all commits with that number and see what comes just after |
|
There has been several updates to the three phase definitions, so going to close this one |
Existing sensor definitions can be found here
You Inverter
Deye SUN-10K-SG01HP3-EU-AM2
Describe the issue/bug and what you expect
the addon (dev branch) reports missing values for various variables
Any suggestions on proposed registers is welcome.
device_type: 6 - this is a SUN-10K-SG01HP3-EU-AM2 high voltage 3-phase hybrid inverter
for the others I can't find settings in the Solarman Business portal for this device, sorry.
Logs (if applicable)
The text was updated successfully, but these errors were encountered: