Search found 42 matches

Be aware that newer H1's have a USB port for the datalogger instead of an RS485 port. Make sure you get the right sort of datalogger!

Yep, I was replying to Dave.

There's an effort to get T series support without going the ESP32 route at https://github.com/LucasTor/FoxESS-T-series, but I'm not sure how far it got.

Note that the T3 does not use modbus, and the information at that link is not relevant to it.

No need to be snarky! That's right - there's a pv sum for all pv, but not for the individual strings.

It's just a Reimann sum integral, integrating pv power every poll.

How do you know that the inverter sends cumalative PV generation to the cloud? There's no modbus register for it. The consensus seems to be that the cumulative figure shown on foxcloud is calculated by the cloud, not by the inverter.

Does the smart meter show 0 even when the foxess app says you're drawing from the grid (and not just when you're supplying the house load from batteries)?

Yep I have the same inverter. There's no ethernet port, you'll need to use a RS485 adapter

Is it a hybrid inverter without any batteries attached? That's normal at dawn / dusk.

The only time I see you pulling from the grid is in your first screenshot around 6am, and that's presumably because you depleted the battery: suddenly the discharge power drops and you switch to the grid, and remain on the grid until solar picks up.

Add the battery soc to the graphs, and you'll see ...

Are you doing your own install?

It's not possible to do with with HA. You can extend the wires (for some loss of accuracy but it's not the end of the world - there are stories of people doing it on the Facebook group). Alternatively, then inverter supports installing an RS485-capable electricity ...

It's probably a problem with your browser. Try chrome?

Set a time, do not enable the toggle, as described above. Then it won't charge from the grid, and won't discharge.

I'm still on old versions - 1.48/1.02/1.45.

Looking at soc and kwh remaining, I'm losing almost exactly as much charge as I'd expect.

I suspect you might be right on the two issues point.

I'm seeing the same thing - a constant discharge of ~120W when it shouldn't be discharging at all.

Interestingly 120W is my base load (with the fridge compressor off).

Here, the no-discharge period is from 2am to 5am.

It's responding with exception code 02, Illegal Data Address. (as you're requesting 1000 not 10000)

Looks like Dakboard has native support for home assistant

What sized inverter do you have?

It looks like the inverter is supplying as much as it can, and the grid is picking up the rest

See

https://www.facebook.com/groups/foxessownersgroup/permalink/1862360824146091/



Both times set to midnight: Charge period disabled
Times set but "Enable charge from grid" disabled: battery won't discharge but won't charge from grid. The same as checking "Enable force charge" previously ...

I have the same: an H1 without a lan port.

The modbus route really isn't hard, and gives you much more information as well as the ability to control the inverter.

Just don't buy the W610: go for one of the other ones listed on the sidebar here: https://github.com/nathanmarlor/foxess_modbus/wiki

Sounds like a genuine fault with your inverter. I'd start by talking to your installer

Do bear in mind that you might not find it straightforward to export 12kW

Foxcloud goes down regularly. Just be patient.

It's written on the back of the foxess clamp. Mine's inside the fuse box so I can't photo it, but there are pics and similar discussion on the Facebook group.

https://m.facebook.com/groups/foxessownersgroup/permalink/1723788324670009/

https://m.facebook.com/groups/foxessownersgroup/permalink ...

Your ct clamp needs to match the spec of the foxess one, which iirc is 100A/33.33mA. The datasheet for the clamp should give its spec, or it might even be written on the clamp. (The output from a ct clamp should be linear, but the gradient can differ between models).

Load is calculated from ...