-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Showing non-existing batteries #68
Comments
Hey Addie, I can't reproduce with the latest version on a SE3500K. There are two registers that indicate the presence of batteries. If these are not "255" (the unset value) then the entire battery block is read. So, in your case these registers are something other than "255". Could you add |
Ok, so not wholly unexpected. I'd be curious to know what is around those registers. I use the following script to dump large ranges of registers, you could try that and see if there's anything interesting there.
The output I get is:
The following is a list of blocks as documented by SolarEdge:
|
Here's the output of that script: dump.txt |
Hey @nmakel, just a friendly nudge from my side. How to progress with this? |
Hi,
First of all: thanks for the library. It enabled me to create a nice Domoticz plugin to monitor my solar installation.
Recently I have added support for meters to my plugin and that is working fine.
I am now working on supporting batteries as well and run into some strange things.
When testing with my inverter (which has no batteries connected to it), I found that the library reports batteries...
When running the example.py, I get this output:
So, for some reason, it detects non-existing batteries and reports invalid information for them.
Hope you can help me out with this one.
The text was updated successfully, but these errors were encountered: