Skip to content
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

House Consumption and 2nd Battery #300

Open
raa-hasel opened this issue Jul 30, 2024 · 19 comments
Open

House Consumption and 2nd Battery #300

raa-hasel opened this issue Jul 30, 2024 · 19 comments

Comments

@raa-hasel
Copy link

raa-hasel commented Jul 30, 2024

Now i have a 2nd Battery Lynx connected to my inverter GW25K-ET. For Battery 1 there is a sensor for "Battery Power" but not for the 2nd Battery. What i see now is, that the power of charge or discharge of battery 2 are counted/added to the House Consumption.
This should be not the right way, or?
May be there is a Modbus-Register for "Battery 2 Power" ?

Version 0.9.9.27

@garv3
Copy link

garv3 commented Oct 13, 2024

It is exactly the same for me! Still no "Battery 2 Power". This makes the stats completely useless.

@garv3
Copy link

garv3 commented Oct 14, 2024

@mletenay No commits since 3.5 months now. Is the project still being maintained?

@mletenay
Copy link
Owner

Yes, it is. There just wasn't anything urgent to do recently, it just mostly works.
Regarding this 2nd battery, the situation is unchanged - we do not know where or whether that register exists.

@raa-hasel
Copy link
Author

Thanks for your update
Is house consumption not the calcution of the known power registers?
What is with the register 35264 (Battery2-Power)?

@garv3
Copy link

garv3 commented Oct 16, 2024

Yes, it is. There just wasn't anything urgent to do recently, it just mostly works. Regarding this 2nd battery, the situation is unchanged - we do not know where or whether that register exists.

https://forum.iobroker.net/assets/uploads/files/1703579717824-arm.745.esg2.et30.modbus.protocol.map.20221231..v1.pdf
Well, this document says 47924 is BMS Battery2 Voltage and 47925 is BMS Battery2 Current. Shouldn't this allow calculating Battery2 Power?

Thanks for your update Is house consumption not the calcution of the known power registers? What is with the register 35264 (Battery2-Power)?

Where did you find 35264 Battery2-Power?

@raa-hasel
Copy link
Author

I found it on Github :-)
May be not offical, but it works for me
https://github.com/marcelblijleven/goodwe/blob/master/goodwe/et.py

@garv3
Copy link

garv3 commented Oct 16, 2024

Yes, I just found it as well. Can this be implemented into the project? I have still not found where exactly the registers are defined in the project. Otherwise I would try to create a change request.

@garv3
Copy link

garv3 commented Oct 16, 2024

Okay, so now I understand what's going on. This repo uses the package goodwe 0.4.8 from PyPI. In the et.py of this package some lines are commented out which include the battery 2 power.

        # Power4S("pbattery2", 35264, "Battery2 Power", Kind.BAT),
        # Integer("battery2_mode", 35266, "Battery2 Mode code", "", Kind.BAT),
        # Enum2("battery2_mode_label", 35184, BATTERY_MODES, "Battery2 Mode", Kind.BAT),

I will try to uncomment this line and check if the power is read correctly.

@raa-hasel
Copy link
Author

FYI:
I'm using the register via modbus (Waveshare) directly

@garv3
Copy link

garv3 commented Oct 16, 2024

The script runs without errors but pbattery2 reports 0 W which is not correct:
pbattery2: Battery2 Power = 0 W

@raa-hasel You wrote it works for you? Which inverter and ARM firmware are you using?
I have a GW25K-ET on ARM 08.401 (newer versions were buggy so we downgraded).

@raa-hasel
Copy link
Author

raa-hasel commented Oct 16, 2024

GW25K-ET / 2 x Lynx F 16,4 H / DSP 07.7068 / ARM 08.401 / BMS 6
See my last post (modbus)
grafik

@garv3
Copy link

garv3 commented Oct 16, 2024

I am not sure how the PyPI goodwe package reads the data. I would have to dig into this.
But Maybe it is because my second BMS FW is 00 and won't show me an update. BMS1 FW is 07.
DSP and ARM are the same for our system. Hardware seems to be nearly identical too. With the difference that I am using 2x Lynx Home F Plus+ 13.1 batteries.

@raa-hasel
Copy link
Author

I do not have any problems with BMS 6, therefore ask Goodwe Support for theses Updates in advance.
SolarGoApp support only the update for BAT1 and till yet not for BAT2.

@garv3
Copy link

garv3 commented Oct 16, 2024

SolarGoApp support only the update for BAT1 and till yet not for BAT2.

This is a joke! WTH?
I will ask them to update the BMS. And report back if it did the trick. Thanks.

BTW: The PyPI package currently uses UDP because I currently have the old WiFi/LAN dongle installed. I will switch bach to the new 2.0 version soon and can test TCP then.

@raa-hasel
Copy link
Author

raa-hasel commented Oct 16, 2024

Be careful with 2.0 see German Forum if you can.
https://www.photovoltaikforum.com/thread/221719-goodwe-modbus-tcp-nur-%C3%BCber-wifi-lan-kit-2-0/

My opinion is if BAT1-Power readable via UDP, BAT2-Power should it be too.

@garv3
Copy link

garv3 commented Oct 16, 2024

Don't have the time to read the whole thread there right now. Can you give me a TLDR? I have used 2.0 over TCP before and everything seemed to work fine.

My opinion is if BAT1-Power readable via UDP, BAT2-Power should it be too.

Yes, but maybe it is due to BMS FW 00... We will see as soon as the FW has been updated.

@raa-hasel
Copy link
Author

Sorry TLDR is ?

@garv3
Copy link

garv3 commented Oct 16, 2024

"Too long, didn't read" - a summary. I am German, but reading the whole thread is just too time consuming for me now. So if you know what the conclusion of it is, I would appreciate a short summary why WiFi/LAN 2.0 should be avoided.

@vikicv
Copy link

vikicv commented Oct 28, 2024

Hello, thanks for supporting the goodwe community!
In my configuration of GW25k-ET and 2x Pylontech batteries connected I am also missing variables related to 2nd battery.
Not bringing any news, just recap.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants