Repository navigation
Replies: 8 comments 6 replies
low power mode should be entirely automatic so if you are not seeing that then it suggests an issue with predbat controlling the inverter charge rate. Best you log a separate issue on that and include the logfiles, debug.yaml and graphs of the inverter charge rate |
Setting reserve min should be sufficient. Predbat will use this when planning and instructing the inverter to discharge - the discharge instruction will set this reserve value. Even with this, it's possible that the inverter won't 100% honour this limit. My inverter reserve is 4% but I've seen it sometimes reporting that it is at 1%. Predbat doesn't command that, it's just that the inverter believes that this is what the current SoC is. Remember that SoC % is an approximation, the inverter can't measure it, all it can measure is voltage of the battery cells, and from that it derives the SOC % |
Ok thanks. So just to confirm that with those settings you wouldn't expect this to be the plan (attached). |
I'm not sure I follow what the question is. What I see in the plan is the battery being exported down to a limit of 11% before midnight, and at midnight the SoC is 11%, and the battery starts charging, with the plan to be at 100% by the end of the cheap period. This all looks fine. There is possibly the opportunity for predbat to do a partial discharge and recharge overnight in the cheap period depending on your inverter rate and battery capacity, and whether you have slow rate charge turned on and combine charge slots off. But as a basic plan it looks fine to me |
|
Sorry, my wording was incorrect on the last reply which confuses things
further.
My main aim is to spread the discharge later on in the day over a longer
time window so that the discharge rate is 3kw (ish) instead of the inverter
maximum as it currently plans (7kw).
With the settings I have switched on (low power mode and combine slots) is
this plan the expected output or should I post the logs etc? If this is
expected behaviour is there another workaround to achieve this?
Thanks
Alex
…On Tue, 8 Sept 2026, 22:52 Geoffrey Coan, ***@***.***> wrote:
So just to confirm that with those settings you wouldn't expect this to be
the plan (attached).
I'm not sure I follow what the question is.
What I see in the plan is the battery being exported down to a limit of
11% before midnight, and at midnight the SoC is 11%, and the battery starts
charging, with the plan to be at 100% by the end of the cheap period.
This all looks fine.
There is possibly the opportunity for predbat to do a partial discharge
and recharge overnight in the cheap period depending on your inverter rate
and battery capacity, and whether you have slow rate charge turned on and
combine charge slots off. But as a basic plan it looks fine to me
—
Reply to this email directly, view it on GitHub
<#4988?email_source=notifications&email_token=CNXRYQ23HTMKY4LZ7QS7S6T5OB5S3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGU3TGOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18357391>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CNXRYQ7DRE3HW7WW5DD2EUD5OB5S3AVCNFSNUABIKJSXA33TNF2G64TZHM3DGNBUHA2TCMZWHNCGS43DOVZXG2LPNY5TCMBXGY4DMMJZUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CNXRYQ57QF3AXGGDLONLHVT5OB5S3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGU3TGOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/CNXRYQ462ZDUCI23G76LMT35OB5S3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGU3TGOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
|
ah OK thanks for the clarification By default predbat will charge and discharge the batteries at full rate as you have found. There is a low power switch which controls charging (reduces the charge rate to spread charging over a long period but still meets the target SoC), but there isn't a similar discharge control. The way I would achieve this is to reduce the battery discharge rate and predbat will extend the discharge period to that new rate. Write an automation to set select.predbat_manual_api to the discharge rate you want, e.g. set it at 9:00pm and clear it at midnight. |
|
Doesn't this Config do low power discharging? switch.predbat_set_export_low_power |
|
I have a self imposed export limit of 4000W. But I slow down the export by setting the Apps value inverter_limit_export: 400 to 400W in my case. I use this low value specifically for the saving session slots just so I qualify for the free weekend hour. |
If it's not in the documentation, then that's why I couldn't find it! I'll get it added Yes this should do what you want |
|
Thanks. Yes I have the export low power mode enabled but it only ever seems to do 15 mins at a lower rate then back to full inverter discharge rate. I just want to increase the snail rate by more than 15-30 mins to say 1-2 hours to reduce the wear on the battery 
|
|
I have the export low power switch set to on but it doesn't seem to give me
a snail or any extension to the period of discharge.
I could set the apps yaml to a hard limit but I want it to remain able to
do 7kw when there's an axle event.
…On Wed, 9 Sept 2026, 14:13 Rob, ***@***.***> wrote:
I have a self imposed export limit of 4000W. But I slow down the export by
setting the Apps value *inverter_limit_export: 400* to 400W in my case. I
use this low value specifically for the saving session slots just so I
qualify for the free weekend hour.
—
Reply to this email directly, view it on GitHub
<#4988?email_source=notifications&email_token=CNXRYQZHNREUXDPUJS7RD3D5OFJOXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGY4DSNJSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18368952>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CNXRYQ5MO62TS6MM4OISO6L5OFJOXAVCNFSNUABIKJSXA33TNF2G64TZHM3DGNBUHA2TCMZWHNCGS43DOVZXG2LPNY5TCMBXGY4DMMJZUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CNXRYQZ6UG4BMUA3375PNKL5OFJOXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGY4DSNJSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/CNXRYQ5IZ222QEBKARMUNSD5OFJOXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGY4DSNJSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
|
Also interested in what the best approach is here. I have my sigenergy battery indoor and my understanding of reducing wear on the battery is where possible charge / discharge it slowly. The one place I can at least discharge slowly is at night between 11pm (when my import rate pretty much matches my export) and 2am when the cheap rate kicks in. Id imagine a slower discharge from 11pm would reduce the temp increase on the battery compared to a full speed export. I turned on the low export power setting but can't get the snail to show up during these nightly exports. I also tried combine slots for export but it didn't help. So interested to know whether ideally predbat should also add the snail here and reduce battery wear as part of its optimization logic. I'd hate to have to use automations in HA to get around it (mainly as I know if probably make a mess of things). |
|
Would be good to know if it could be considered as a new feature or to
change the logic. I've ended up putting a manual state of charge at 7pm of
70% and then it spreads the discharge rate slowly between around 6pm and
midnight.
Thanks,
Alex
…On Wed, 7 Oct 2026, 09:22 Mark Kennedy, ***@***.***> wrote:
Also interested in what the best approach is here. I have my sigenergy
battery indoor and my understanding of reducing wear on the battery is
where possible charge / discharge it slowly. The one place I can at least
discharge slowly is at night between 11pm (when my import rate pretty much
matches my export) and 2am when the cheap rate kicks in.
Id imagine a slower discharge from 11pm would reduce the temp increase on
the battery compared to a full speed export. I turned on the low export
power setting but can't get the snail to show up during these nightly
exports. I also tried combine slots for export but it didn't help.
So interested to know whether ideally predbat should also add the snail
here and reduce battery wear as part of its optimization logic. I'd hate to
have to use automations in HA to get around it (mainly as I know if
probably make a mess of things).
—
Reply to this email directly, view it on GitHub
<#4988?email_source=notifications&email_token=CNXRYQ6ASPFQDLXYH5YI26L5SVWDDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXHA2TINZTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18785473>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CNXRYQYIWP7QBBLM6T4EAEL5SVWDDAVCNFSNUABIKJSXA33TNF2G64TZHM3DGNBUHA2TCMZWHNCGS43DOVZXG2LPNY5TCMBXGY4DMMJZUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CNXRYQ6DDIFJPQMVDPMLGO35SVWDDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXHA2TINZTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/CNXRYQ67B6QT4IWHEEJL6FL5SVWDDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXHA2TINZTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
|
Do you mind sharing the way that you achieved that @uxbpncgw , I might do the same at 11pm, start discharging slowly. I just want to somehow override predbats export speed somehow at that time. What do you think on this one @gcoan , would it be a feature request, bug, or something we might not see in predbat at all? For me it would be one of the best possible features to have in predbat (given my battery is indoors, not in the coolest room in the house, so any chance i can get to stop my battery peaking at 45C the better). I have put a few fans on it and it helped but making best use of slower imports/exports where possible would really be the icing on the cake and probably make the battery last a lot longer i think. I guess it could become complex to implement in predbat if it really was trying to model things like battery wear. In this case I think the battery wear isn't just a static figure, it can be some function of cycling the battery but also including the temperatures the battery might reach due to the rate it imports/exports at. Unless its just exposed as a simple (slow mode where possible) type flag which I guess we have but maybe not fully using it in certain cases. |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I am currently a week or two into using predbat to manage my foxess setup via cloud (not modbus). I'm looking at the export slots at the end of the day and trying to reduce the long term wear on the battery. In our house we use negligible amounts of power between 10pm and midnight. The low power mode seems quite inconsistent and frequently does 20 mins at 5kw then 1 hour of 7kw (inverter max). Is there a way to spread out the discharge between 10pm and midnight every day?
Settings at present:
Combine export slots is ON
Low power export mode is ON
Also, I had an episode where my battery drained to 8% (Fox says lowest SOC is 10%) a few days ago. Could have just been bottom balancing but I'm keen to avoid predbat trying to get into that zone. I have set my minimum set reserve min to 11% - is that adequate or do I need to go into expert mode and specify a remaining kWh?
Thanks for all help/advice.
All reactions