Hi,
I requested Fox ESS to set my Meter Compensation to -50 last Monday and have received a ticket number but so far no other action as far as I can tell. It occurs to me that I can check this via Home Assistant, Developer Tools, Actions, FoxESS - Modbus: Read Registers. In fact I can theoretically also set it myself but to do either of these I need to know the register address. Does anyone have this information? As far as I can tell the KH Series Modbus protocol information was last updated in 2023 so obviously does not have this new address.
Anyone?
Thanks, Hugh
Modbus Address for Meter Compensation
-
HughInDevon
- Posts: 67
- Joined: Wed Jul 31, 2024 4:50 pm
KH10 with 4 off ECS4800 batteries.
20 Jinko 435W panels in 2 strings. 10 on house, south facing, 10 on barn, east facing.
Solar installation active on 27/11/2024. Export MPAN active on 30.12/2024.
Zappi V2 charger and 2 EVs.
Currently on Octopus Intelligent Go tariff.
Home Assistant modbus integration (Now working - ish)
20 Jinko 435W panels in 2 strings. 10 on house, south facing, 10 on barn, east facing.
Solar installation active on 27/11/2024. Export MPAN active on 30.12/2024.
Zappi V2 charger and 2 EVs.
Currently on Octopus Intelligent Go tariff.
Home Assistant modbus integration (Now working - ish)
-
WyndStryke
- Posts: 60
- Joined: Mon Nov 18, 2024 9:16 pm
You need to check it via a separate CT clamp or (ideally) from the smart meter itself. The inverter's CT will appear to be unchanged, at +10W import or whatever, but the readings will be biased by the compensation figure in the direction of forcing export. So for example, the inverter's CT is telling modbus that it is +10W import, but the smart meter itself is showing a small export.
I got a reply to the ticket maybe a minute after the setting was changed.
It'll look like this:
viewtopic.php?p=7429#p7429
As far as I know, the meter compensation setting is not currently available via modbus.
I got a reply to the ticket maybe a minute after the setting was changed.
It'll look like this:
viewtopic.php?p=7429#p7429
As far as I know, the meter compensation setting is not currently available via modbus.
-
HughInDevon
- Posts: 67
- Joined: Wed Jul 31, 2024 4:50 pm
Hi Wyndstryke,
Can I ask you how long it took Fox to set your Meter Compensation after you made your request? I have been waiting 7 days (5 working days) whereas my previous contacts with them have been much quicker.
I am using the Octopus Energy app to see what my grid import is. If I get the meter compensation right, the peak rate consumption should drop to zero. At present it shows a small fraction of a kWh per hour during the periods when I am running on battery.
I have been looking through all the Fox ESS API document I can find, the most useful one is https://github.com/nathanmarlor/foxess_ ... -Documents, particularly the one called Energy.Storage.Inverter.Modbus.TCP.Communication.protocols.for.FOXESS-1.pdf. Sadly no reference to Meter Compensation but hours of nerdy fun reading all the register values. I haven't had the courage to try writing directly to a register yet but my fingers are getting twitchy!
Regards, Hugh
Can I ask you how long it took Fox to set your Meter Compensation after you made your request? I have been waiting 7 days (5 working days) whereas my previous contacts with them have been much quicker.
I am using the Octopus Energy app to see what my grid import is. If I get the meter compensation right, the peak rate consumption should drop to zero. At present it shows a small fraction of a kWh per hour during the periods when I am running on battery.
I have been looking through all the Fox ESS API document I can find, the most useful one is https://github.com/nathanmarlor/foxess_ ... -Documents, particularly the one called Energy.Storage.Inverter.Modbus.TCP.Communication.protocols.for.FOXESS-1.pdf. Sadly no reference to Meter Compensation but hours of nerdy fun reading all the register values. I haven't had the courage to try writing directly to a register yet but my fingers are getting twitchy!
Regards, Hugh
KH10 with 4 off ECS4800 batteries.
20 Jinko 435W panels in 2 strings. 10 on house, south facing, 10 on barn, east facing.
Solar installation active on 27/11/2024. Export MPAN active on 30.12/2024.
Zappi V2 charger and 2 EVs.
Currently on Octopus Intelligent Go tariff.
Home Assistant modbus integration (Now working - ish)
20 Jinko 435W panels in 2 strings. 10 on house, south facing, 10 on barn, east facing.
Solar installation active on 27/11/2024. Export MPAN active on 30.12/2024.
Zappi V2 charger and 2 EVs.
Currently on Octopus Intelligent Go tariff.
Home Assistant modbus integration (Now working - ish)
-
WyndStryke
- Posts: 60
- Joined: Mon Nov 18, 2024 9:16 pm
It was about 5 days I think, but it is going to vary depending on how many tickets that they have in the queue, and whether that is all working days or includes a weekend / holiday / etc.
Note that the peak rate consumption won't get to exactly zero, unless you set it to some absurd level like several kW of export all the time. The reason is that if you turn on something like a kettle, there will be a brief 3kW spike which will pull from the grid no-matter-what. The inverter takes a few seconds to respond to the demand. The worst case scenario is one of those thermostatically controlled heaters which will continually flicker the power draw on and off to stay at a level target temperature, because each time it does that, there is a spike drawn from the grid. You can however get near to zero.
Note that the peak rate consumption won't get to exactly zero, unless you set it to some absurd level like several kW of export all the time. The reason is that if you turn on something like a kettle, there will be a brief 3kW spike which will pull from the grid no-matter-what. The inverter takes a few seconds to respond to the demand. The worst case scenario is one of those thermostatically controlled heaters which will continually flicker the power draw on and off to stay at a level target temperature, because each time it does that, there is a spike drawn from the grid. You can however get near to zero.