Closed andynash closed 9 months ago
cdpuk
commented
1 year ago What happens if you use the GivEnergy app to set the max discharge power to a problematic value?
If that works, it's useful to pull the raw values from the GE web portal to try and spot the differences.
What model of inverter and battery are being used?
reidjr
commented
1 year ago This is a Gen2 inverter issue, certainly for PV charge, present in firmware up to 909 (latest). For me the minimum PV charge value reported is 292,. You can' set 0, and the register shows that, but inverter behaviour is to continue to charge till the sun goes down or battery is full. Same on givtcp, the phone app, the web portal. I didn't notice it was the same for discharge.🙄.
andynash
commented
1 year ago Yes, I tested this morning and it is a GivEnergy issue, possibly Gen2 only, I couldn't say.
I hadn't seen an issue on charging (I don't have a use for limiting charge speed so don't use that), but on discharge it is present when set through the app too - sorry I should have checked that before posting here.
I've upgraded today to 909 to see if that fixes it, and haven't had a chance to test it again yet, but will do so...
reidjr
commented
1 year ago Sorry to say, 909 doesn't fix it. However there are new commands now being added to givtcp (sorry) and to the givenergy web portal to apply selective battery pause. Works on 909 at least, and can set either off/charge paused/discharge paused/charge+discharge paused. This command does not change the max charge register, its another control.
andynash
commented
1 year ago Weird, the amount it decides to discharge at (for my one and only test) is now exactly 300W, so that has changed slightly. But no, I concur, 909 doesn't fix.
I'm sure those new controls will be added to this integration in due course, as they do sound simpler/more direct than modifying the power limits (if you are just wanting to pause completely). Maybe as a select?
@reidjr Do you know if there's a bug/community issue somewhere already for following the power limit issue?
@cdpuk I guess you can close this, or mark 'pending upstream' or whatever suits? Thanks!
reidjr
commented
1 year ago Not as such. Givenergy know the Gen2 does that, its been discussed in the community forums, but never seen a definitive " it will be fixed" comment. As you have probably founfd on the community forum, theres no FAQ, no stickies and no real way to find out whats going on without reading 3000 post threads..... I digress :-)
andynash
commented
1 year ago I have indeed noticed that 😂 thanks for the update though 👍
I don't pay much attention to the forums, but will try and poke my nose in more often...
andynash
commented
9 months ago Sorry to say, 909 doesn't fix it. However there are new commands now being added to givtcp (sorry) and to the givenergy web portal to apply selective battery pause. Works on 909 at least, and can set either off/charge paused/discharge paused/charge+discharge paused. This command does not change the max charge register, its another control.
@cdpuk Is it going to be possible to add this battery pause feature to the integration? (I'm on 909 and can't see it there yet unless Im missing something)
With Intelligent Octopus now supporting Outgoing Fixed/Agile, there's a good reason to want to prevent solar charging during the day (so that solar is exported instead), so I'm sure it would be useful to many.
Thanks for this excellent and integration by the way, I could try GivTCP which has this feature, but yours seems a simpler and more robust solution so I'd prefer to stick with it if at all possible.
cdpuk
commented
9 months ago GivTCP has gone the route of forking the givenergy_modbus library internally. This means new things can be added, but it's engineered in a way that makes it difficult to cleanly import in to projects like this.
Unless we can get updates pushed back to the main givenergy_modbus codebase, the quickest approach is probably to do the same as GivTCP, but then we've got 3 completely separate codebases trying to achieve the same thing.
Also, I'm the owner of a Gen1 inverter, so I have no way to test any of these changes (or benefit from them!). In this particular case I'd argue the workaround of changing the charge/discharge rates is pretty good.
I'm going to close this issue, but feel free to raise specific ideas like the pause feature this as something new - it might just take a while to get around to.
Version of the custom_component
1.8.0
Configuration
Add your logs here.
Added below, seems there are two log sections in this template?
Describe the bug
When setting the discharge limit number entity to 0 using the relevant service, the number entity is correctly updated to 0 (ditto when setting to any other value). However, for any value less than 370-382 W, the battery continues to discharge (at a rate of between 370 and 382 W), as seen by sensor.battery_power and the GivEnergy mobile app.
Higher discharge values appear to work as expected.
N.b. This occurs regardless of actual consumption. If consumption is higher than 370-382 W, the battery continues discharging at that rate, and grid power increases to fill the gap. I've not been able to observe consumption at less than this, as our baseload is usually higher.
This has been observed while there has been no solar generation. When there is solar generation that reduces or eliminates the unwanted discharge, but obviously that is just obscuring the problem.
It is as though any value for discharge power limit that is less than 370-382 W = 370-382 W.
Logs don't appear to show anything particularly informative I'm afraid. Happy to dig further if you can guide me - I've set givenergy_local to debug and filtered for givenergy using grep, while changing from a value of 3600 to 0 and back to 3600.
Debug log