FoxESS Community - Owners & Installers Forum

Last night, my batteries started charging on schedule (01:30-04:40) then stopped after about an hour, and the charge schedules are gone, all set to 00:00. The car was charging too so that then flattened the battery!

Never seen this before, any thoughts? Makes me really want to pull the wifi data logger and just have local control as can only presume something from the cloud wiped it?

Last night my battery started force charging at 2.30 (possibly around the same time as your issue occurred) until it was full. I'm using the HomeAssistant foxess_em integration which is supposed to control the battery charging based on the predicted solar for the next day. In this case it appears that it disabled the charging at 12.30 so no charging should have happened at all. This is very annoying as now I'm exporting my PV energy to the grid at a lower price than I paid for it last night.

I wonder if something happened on the FoxESS Cloud side that caused our inverters to revert to a previous setting.

danelphick wrote: ↑Wed Mar 06, 2024 1:26 pm
I wonder if something happened on the FoxESS Cloud side that caused our inverters to revert to a previous setting.

Yep that’s what we think happened last night, because of all the problems with their cloud, we think that Foxess moved their servers from being self-hosted to Alibaba cloud, and it seems quite a few users had disrupted or reset charge periods.

Obviously not good short term pain, but hopefully the benefits of it having those extra resources will be worth it, their api’s have been performing reasonably well this morning, so lets see how it now performs.

Glad I see others with similar issues, I would have been most happy with a full charge as cloudy almost all day here in mid Cornwall, luckily managed to have a low power use day so far, but about to be tea time!

Can you all please double check your schedules are doing what you expect, i’ve heard a few people have seen previous days schedules running which has led to force discharging when they weren’t expecting it.

And also check your normal charge periods are still doing what you expect them to.

We've lost the overnight charge as well, this coincided with us switching to Foxess2.0 so we thought it was that. Trouble is any attempt to reset on Foxess(my phone) or Foxess2.0 (my wife's phone) just says unsupported function code 44096 - I believe this is Chinese for "we've already got your money so if it doesn't work you can go and F*** yourself", but if anyone out there's able to tell me what's happening or how to get aound it I'd be grateful.
Cheers, Mick.

Mick Heayes wrote: ↑Thu Mar 07, 2024 3:46 am We've lost the overnight charge as well, this coincided with us switching to Foxess2.0 so we thought it was that. Trouble is any attempt to reset on Foxess(my phone) or Foxess2.0 (my wife's phone) just says unsupported function code 44096 - I believe this is Chinese for "we've already got your money so if it doesn't work you can go and F*** yourself", but if anyone out there's able to tell me what's happening or how to get aound it I'd be grateful.
Cheers, Mick.

It should work this morning Mick, it appeared to have limited access from around 11pm last night - i’ve been told they made some changes last night to improve performance and fix some data issues.

Still getting the error message whenI submit the times to force charge - last night it didn't take on anything at all.
When I go back to look (I'm on FosESS2.0 now) it has reverted to Start time 00 00 End time 00 00, not enabled.

Cheers, Mick.

My charge worked fine last night, I use the Inverter built in timer rather than the new schedules

grrrr what I have just noticed today though, that hasn't happened in a very long time, the SoC just jumped from 66% to 98% in around 10 minutes.

I had this long standing issue with this happening a lot, ended up being a faulty lead between 2 batteries! Frustrating to see this occur again and hope it is not something more ominous.

Mick Heayes wrote: ↑Thu Mar 07, 2024 11:49 am Still getting the error message whenI submit the times to force charge - last night it didn't take on anything at all.
When I go back to look (I'm on FosESS2.0 now) it has reverted to Start time 00 00 End time 00 00, not enabled.

Cheers, Mick.

If you’ve got the Fox v1.0 app try with that, a couple of users found the v1 app worked whereas v2 didn’t.