Page 1 of 1
What's broken here?
Posted: Fri Jun 13, 2025 9:33 am
by MarkRS
The attached picture shows (I hope) the situation. One "graph" shows the inverter in a state that the other graph appears to contradict.
I have Home Assistant running and have a trigger that responds to Octopus initiating a charging session by setting the inverter (H1-5.0-E - AUX) to force charge mode using Nathan Marlor's modbus integration. The trigger has been successfully initiating but I haven't been convinced that it's been switching the mode.
I plugged in the EV yesterday and got a charge schedule (from Octopus) starting at 10pm.
I looked at the mode last night after 10pm and it showed the inverter being in force charge mode.
The attached picture shows that the integration thinks it was in force charge mode at that point.
The battery charge state (in the picture) suggests it wasn't in that state until the usual cheap rate time of 11:30.
Any idea what's going on here? Is there something needing fixing?
Re: What's broken here?
Posted: Fri Jun 13, 2025 10:11 am
by Dave Foster
There’s another sensor with Force Charge that sets the charge power (number.force_charge_power) check that has been set to a reasonable value for charging i.e. 3kW - i’ve seen it get reset to a smaller value.
Re: What's broken here?
Posted: Fri Jun 13, 2025 10:24 am
by MarkRS
Thanks for that @Dave.
The modbus integration shows the value for that sensor as 5kW
Re: What's broken here?
Posted: Fri Jun 13, 2025 1:29 pm
by Dave Foster
Are you using any Fox cloud schedules ?, the schedules use the same active power register as modbus uses to force charge and so they would override the force charge instruction.
Re: What's broken here?
Posted: Fri Jun 13, 2025 2:05 pm
by MarkRS
Yes, I've got the main Octopus 11:30pm - 5:30 am set as force charge on the Fox website. The HA trigger is for when Octopus schedules EV charging outside those times.
I'd thought the HA thing would be an extra. Will the Fox cloud schedule overriding everything else always? Should I just turn it off and do everything from HA?
If this is the case I'm still a bit surprised that HA would report the mode as force charge if in fact the Fox schedule has overridden it to self use.
Re: What's broken here?
Posted: Fri Jun 13, 2025 2:29 pm
by Dave Foster
Yes you can't use scheduler at the same time as force charge/discharge (in fact any work modes) or minsoc - best to do everything by home assistant.
Scheduler runs in the inverter manager and will always win, so you set the work mode to force charge (which sets a few registers including the active power register) and scheduler will immediately set the power back the way it wants - it'll sit there fighting like that all night.
Ironically you can set the old charge periods i.e. you could have the charge period set 11:30 - 05:30 they have no effect on home assistant work modes.
Re: What's broken here?
Posted: Fri Jun 13, 2025 2:35 pm
by MarkRS
Are we talking about the same thing here.
I was not very precise. What I'm using on the website is the work model templates to set the 23:30-05:30 period.
Re: What's broken here?
Posted: Fri Jun 13, 2025 3:36 pm
by Dave Foster
MarkRS wrote: ↑Fri Jun 13, 2025 2:35 pm
Are we talking about the same thing here.
I was not very precise. What I'm using on the website is the work model templates to set the 23:30-05:30 period.
Yes those are the schedules (called scheduler in the V2 app).
If on that same screen you click the small red icon to the right of the words ‘Battery Status >’, those are the ‘charge periods’ - you can use those with home assistant but again not with the scheduler (aka ‘work model templates’)
Re: What's broken here?
Posted: Fri Jun 13, 2025 3:45 pm
by MarkRS
OK got it.
Thank you very much for your help.