FoxESS Community - Owners & Installers Forum

Yup, last failure for me was 3 Jun 13:43:29 UTC, next attempt at 13:48:31 UTC succeeded. However, even after a reload the website https://www.foxesscloud.com/ is still showing empty/broken battery info on the Overview or Sites Detail pages, and no battery at all on the Inverter Detail page. So it ...

The problem with "operation timed out" (41203) is that as far as I can tell in response to the client request for data, their cloud service is failing to send the "read register" commands to the inverter to fetch said data at all, so you might expect rebooting the inverter to do nothing at all since ...

Is it known to be broke today? Since around 10:30 I've been getting 41203 errors trying to retrieve the battery SoC and charge from grid schedule, and https://www.foxesscloud.com/ shows a blank for battery status and no control button:

I didn't ask for individual strings. I asked for the cumulative total, which I already knew is there somewhere and sent to the cloud. The side-by-side equivalent to all the other cumulative values I mentioned.

How do you know that the inverter sends cumalative PV generation to the cloud? Because I can see the data in the protocol, being sent out from the inverter into the cloud within the 5 minutely data block, grouped right next to all the other cumulative energy values I mention, and its value ...

So, as well as the current instantaneous power values in W, the inverter maintains cumulative since-manufacture transfer values in units of 0.1kWh. Those are kept for: PV generation, battery charge, battery discharge, grid export, grid import, inverter output, inverter input and load. Charge ...

Ta.

Well, yes, but the integration the inverter is doing is on a much shorter timescale than the 5 minutes that it sends a snapshot to the cloud at. (If I try to integrate the grid power numbers from the 5 minute snapshots. then I get numbers which are even more wildly out, and are out in both ...

No, I'm talking about the total transfer (in Wh) counters, not the instantaneous power (in W) numbers. These are continuously updated inside the inverter and do not "miss the kettle".

Hmm. With the consumer unit under the stairs, and the power and CT cables running up the side of the house, into the loft, then across to the opposite side of the loft to the inverter, is it expected that the import values reported by the inverter are consistently around 3.5% lower (full range 2-5 ...

In case it helps, here is my daily PV generation over the last year. This system is 6x390W panels, 3 on the back facing ESE, 3 on the front facing WNW, all as a single string with 6 optimisers.

Dave Foster wrote: ↑Sun Dec 03, 2023 9:15 am The main thing against the cloud is reliability, it isn't 5 9's - possibly only 3 9's

Since we've lost two full weekends, and a few days in addition to that, we're now well under 2 9's.

After any kind of glitch or reconfiguration, I find it can take half an hour or more for the wifi dongle to re-connect to the foxess cloud. Of course there's neither feedback nor control over this process, you just have to wait and hope. (I can understand not wanting to spam the servers or the ...

Functionality appears to have been restored at 1AM last night.

Please see the latest update and statement from FoxESS, click on the image to enlarge I think this is important: they can claim that the API/protocol is internal all they like (though I think there really should be a public, documented, supported API), but each time this has happened their own ...

Another one here with the timeout error when trying to get into battery settings on the app :( Sounds like a server side issue. When I make a request to see the current time settings through their website, I currently don't see any corresponding request from their side to my inverter to fetch those ...

Well, the slight issue for me there is that the inverter is in an awkward far corner of the loft, the loft space is mostly not boarded for walking on, and my stepladder is too short to make it easy to get up there. And my optimizer tends to generate 4-6 separate charge periods per day, customised to ...

Yup, the last time I was able to access the charge times was 19:40 last night (the 5th), since then just constant 41203 "Operation timed out" errors. I hope I have enough charge to get through the Agile peak hours coming up (my optimizer was *trying* to set a top-up period for round about now, but ...

So, modbus -> WiFi bridge, and you're done, no? I'm not seeing how "build your own server infrastructure to spoof the inverter" is the easy option by comparison :shock: Well, I'd first have to buy a modbus/wifi bridge, which I don't have. I'd then have to wire it in to the inverter using a custom ...

Well, it looks like it's started working again some time around 01:15, so I get some of the plunge pricing. Currently forecasting an average unit rate of 4.5p up to 11pm tomorrow.

If you have the latest firmware that allows schedules/strategies, some people have reported that setting a force charge in a schedule is still working. No, I don't, still on quite an old version, pre-1.50. And given what others have said about the inverter's own power consumption yoyoing and ...

How have you automated? I know you can with HA but I can't be bothered to work out how to do it! I wrote my own. Mostly a bunch of python. One set to run each day to suck the tariff rate (available 4pm in advance) and consumption data (available 12pm in arrears) out of the Octopus API. Another ...

As usual they pick the worst time for this. I'm on Octopus Agile, so I can arrange battery charge times to hit the cheapest half-hours. (That is now fully automated and was working quite well... at least when their systems aren't broken.) So when their cloud systems break, that costs me money. Today ...