Can you update mode scheduler so that when either the end time or the max/min SOC is hit during a force charge/discharge schedule that the schedule will revert back to the set default work mode?
At the moment I have a schedule set so that between 5:30-7:30pm I force discharge the battery to 40%, however if I hit the 40% prior to 7:30pm my house load is pulled from the grid during the peak.
apparently it worked liked that previously but one non so bright spark in the software team decided that there was a problem with this logic:
the inverter might frequently switch in and out of forced discharge. For example, once the battery reaches the cutoff SOC during forced discharge, it immediately exits forced discharge, but if there is excess PV generation, the battery will be charged again. After charging just a little, it starts forced discharge again. Therefore, the previous logic had some drawbacks.
Of course, we greatly appreciate your suggestion. We are currently considering adding a new option, allowing you to choose between the new logic or the old logic. This will cater to all needs, and we will develop it as soon as possible.
Meanwhile complaints galore:
viewtopic.php?t=2628
viewtopic.php?t=2662
viewtopic.php?p=10674
viewtopic.php?p=10150
viewtopic.php?p=11906
the inverter might frequently switch in and out of forced discharge. For example, once the battery reaches the cutoff SOC during forced discharge, it immediately exits forced discharge, but if there is excess PV generation, the battery will be charged again. After charging just a little, it starts forced discharge again. Therefore, the previous logic had some drawbacks.
Of course, we greatly appreciate your suggestion. We are currently considering adding a new option, allowing you to choose between the new logic or the old logic. This will cater to all needs, and we will develop it as soon as possible.
Meanwhile complaints galore:
viewtopic.php?t=2628
viewtopic.php?t=2662
viewtopic.php?p=10674
viewtopic.php?p=10150
viewtopic.php?p=11906
I thought it worked properly before the latest app update! Thanks for confirmingsuti wrote: ↑Tue Feb 10, 2026 3:32 am apparently it worked liked that previously but one non so bright spark in the software team decided that there was a problem with this logic:
the inverter might frequently switch in and out of forced discharge. For example, once the battery reaches the cutoff SOC during forced discharge, it immediately exits forced discharge, but if there is excess PV generation, the battery will be charged again. After charging just a little, it starts forced discharge again. Therefore, the previous logic had some drawbacks.
Of course, we greatly appreciate your suggestion. We are currently considering adding a new option, allowing you to choose between the new logic or the old logic. This will cater to all needs, and we will develop it as soon as possible.
Meanwhile complaints galore:
viewtopic.php?t=2628
viewtopic.php?t=2662
viewtopic.php?p=10674
viewtopic.php?p=10150
viewtopic.php?p=11906
There is talk that they are going to possibly introduce a toggle for those that want it to stick (like me!) or those that want it to swap back to Self-use for example.
They are doing a lot of work in Q1, with a lot of massive changes to the behavior, and bound to rock the boat for a bit. They will eventually listen to feedback and rollout changes for more control.
Look at the latest Fox Cloud 2.0 App, looks very polished, but also not as intuitive as the older version that people knew.
They are doing a lot of work in Q1, with a lot of massive changes to the behavior, and bound to rock the boat for a bit. They will eventually listen to feedback and rollout changes for more control.
Look at the latest Fox Cloud 2.0 App, looks very polished, but also not as intuitive as the older version that people knew.
I've now configured this automation in HA, works exactly as I expect it to.
