I am finding a big difference in behaviour if I use mobile app or browser.
I think the latest app version has played havoc. That's the version where they added all the sliders (who needs that!!)
Whenever I use the mobile app now it screws all my settings. For example, when I have a work schedule set, it always uses grid. Even when I program in Self-Use.
I now only using browser v2 and the php code to do settings.
Before I used my script i was using the app. I deleted the work schedules completely then ran the script to create them. Perhaps its conflicting data between the various places you can enter the info?
Exactly what I did last night for my latest test!!
Thanks for staying in touch. I really appreciate it. This issue is giving me the *****. And paying for grid power is very annoying.
Thanks for staying in touch. I really appreciate it. This issue is giving me the *****. And paying for grid power is very annoying.
Also considering rebooting my entire system. But I don't really know how. And not sure it would make any difference anyway, since it surely has a battery backup of previous settings.
If you do reboot system, here is a previous post (picture 2 posts down also)mikeincairns wrote: ↑Wed May 27, 2026 4:28 am Also considering rebooting my entire system. But I don't really know how. And not sure it would make any difference anyway, since it surely has a battery backup of previous settings.
viewtopic.php?p=15192#p15192
Having tested this further, I don't think it was ever fixed. I did find out that PV output is not being forced to 0 when the Force Charging takes the battery to the SOC limit, it just being capped at whatever is going to the battery so none is exported.diarmidr wrote: ↑Mon May 25, 2026 12:58 pm My app updated at some point over the last few days and I think this issue has been resolved. Not when the battery hits the target SOC during "Force Charge" it reverts to a behaviour similar to "Self-use" where it only charges from the available surplus PV.