I have a Gen2 3.6 Hybrid inverter and when running on FW 913 and using the 'Pause Charge' function, the charge rate dropped to 28W (near enough to 0 that it doesn't matter), however having updated to FW 915 I find that it now charges at 174W which is quite a lot different, and not really a pause at all.
It's not causing big problems, I just wondered if anyone else had noticed this?
Gen 2 3.6HY here on D0.915-A0.915.
I pause my battery discharge from 11.30pm to 5.30am every night when charging batteries overnight. This is to prevent the EV draining the battery if plugged in (Zappi). Checking last nights data there was 0w discharge during the paused time period - graph below. So mine seems to be working as advertised. You may need to double check your settings in the portal just to make sure.
However, I am noticing that the batteries only charge to 90% or thereabouts - even when set to 100%. They do get up to 100% on solar though. Probably to prevent the overvoltage errors that were common with the previous firmware.
Phil_H is that 'pause charge' through the quick-settings button on the app. IIRC that's implemented by reducing max charging power to 0 and, on recent systems, as you say, that doesn't seem to actually get all the way down to 0. (On my gen-3 it's more like 250W.)
You can achieve a better pause (down to 28W) by configuring a timed pause through the remote control, assuming that's available on your model.
But your batteries are charging during that time period, so the discharge will always be 0. I have Pause Charge set when I have excess solar so that rather than it filling the battery it exports it.
DD I'm using HA local control, I have an automation to set the pause charge register (the same as the remote control timed pause) whenever my charge rate is set to 0 (using predbat), charge rate 0 used to end up with 290W for me, but this is something that I haven't changed across the FW versions, and used to work fine.
Well, I found the problem, turns out the inverter FW upgrade decided clearing out my timed pause times would be a good idea, so instead of having 00:00-23:59 (meaning whenever I set the pause it would work) it was back at 00:00 - 00:00 so it just does nothing.
I was almost certain I saw a stage of the upgrade which said 'saving settings' and 'reloading settings', clearly it didn't work!
Phil_H I'm surprised that you are having to create an automation to set pause charge alongside the battery charge rate with predbat
I've got a gen 1 with the latest firmware 191/193 and predbat sets pause charge at the same time as charge rate 0.
Are you on a reasonably recent version of predbat? If you are, it's worth raising a predbat github issue if it's not working for you
Phil_H I have an automation to set the pause charge register (the same as the remote control timed pause) whenever my charge rate is set to 0 (using predbat), charge rate 0 used to end up with 290W for me
I'm doing much the same, though with a custom modbus script rather than HA. If the script calculates that it wants charging power of 0, it implements it by setting it to paused instead,
I have the pause times configured to be something like 7am to 11pm - I don't want a bug in my script to leave it in a paused-charge state which might then interfere with overnight charge. (Or rather, it keeps the script simple to not have to worry about unpausing overnight, since the timer takes care that of that part - script can just leave it in a paused state.)
I had a recent firmware upgrade, and it did manage to remember the pause times.
geoffreycoan I'm on 7.19.7, maybe I don't need the automation any more but it certainly used to be required, I know there was discussion around which inverters the pasue would work on and therefore whether it would be added to predbat due to wanting to be consistent across inverters. Maybe I'll do a bit of testing and see what I get.
Phil_H I’m on 7.19.7 too. When I turned the ‘old firmware’ switch off in givtcp I automatically got the new pause sensors and predbat started to use them. I think there was some more intelligent use of the pause controls implemented by Trefor a few versions ago, partly to fix the issue with newer firmware that discharge/charge rate zero didn’t do what it was supposed to do
geoffreycoan well having just tested it, I definitely only get the rate to 0, predbat isn't setting the pause, not really a problem for me given my automation deals with it but interesting that you have it working.
