Supported Features - nathanmarlor/foxess_modbus GitHub Wiki
Note: This page is linked to from the integration. Do not remove or rename!
We support different sets of features for different inverters, depending on how you are connected to your inverter.
In some cases, these are due to restrictions on the inverter itself: the H1 exposes far fewer registers over a direct LAN connection than it does over RS485, for instance. In other cases, this may be because we haven't identified the correct registers yet.
| Feature | H1/AC1/AIO Direct LAN | H1/AC1/AIO RS485 | H3/AIO | KH/KA |
|---|---|---|---|---|
| Read basic values | ✔️ | ✔️ | ✔️ | ✔️ |
| Read BMS values | ❌ | ✔️ | ❌ | ❌ |
| Read energy totals | ❌ | ✔️ | ✔️ | ✔️ |
| Read fault codes | ❌ | ✔️ | ✔️ | ✔️ |
| Read/write work mode, min/max SoC | ❌ | ✔️ | ✔️3 | ✔️ |
| Read/write charge periods | ❌ | ✔️ | ❌ | ❌ |
| Force Charge / Discharge | ✔️1,2 | ✔️ | ✔️2,3 | ✔️2 |
1 Force Charge / Discharge on the H1 LAN has the following restrictions:
- Work Mode is not available, so this is exposed as a "Force Charge Mode" combobox.
- Max SoC is not available. There is a separate "Force Charge Max SoC" sensor, and force charge will disable when the SoC reaches this value.
- Min SoC is respected by the inverter, but cannot be set over modbus.
- Since Work Mode is not available, when the Max Soc is reached, force charge will be disabled and the inverter will revert to its previous work mode (which may discharge the batteries).
2 If you Force Charge during the day, the inverter will prioritise energy drawn from the grid over PV energy, which means your PV generation will probably drop to 0. This is the same as FoxESS's "Force Charge" template, but different to standard Charge Periods.
3 Not supported by the AIO-H3 or Kuara H3.