FoxESS Community - Owners & Installers Forum

Hi all,

Just trying to get my new inverter connected to HA via a Waveshare RS485 adapter. Using the one suggested here: https://github.com/nathanmarlor/foxess_ ... TH-%28B%29. I'm hosting HA on a docker container via a Synology NAS.

Finally have it connecting back to my network and believe it's communicating OK. I can see rx and tx packets on the vircom app:


When adding to Home Assistant via the HACS community mod, it connects initially and adds the integration/entities but then shows the following error:


I ran the following command which i've seen suggested elsewhere in this forum to check communications between the inverter and network via modpoll. This is the output I get:


This is as far as I've managed to get in troubleshooting! I notice that the start address appears different in HA and the suggested modpoll command (36001 and 41001) is that something to do with it?

I'm completely at a loss where to go from here, any ideas greatfully received.

What inverter is it you are connecting (H1,KH,H3,H1-Gen 2) ?

Dave Foster wrote: Tue Jul 02, 2024 1:48 pm What inverter is it you are connecting (H1,KH,H3,H1-Gen 2) ?

It's an H1-5.0-E-G2

Version_Master 1.14
Version_Slave 1.02
Version_ARM 1.17

clusterfuffle wrote: Tue Jul 02, 2024 1:54 pm

Dave Foster wrote: Tue Jul 02, 2024 1:48 pm What inverter is it you are connecting (H1,KH,H3,H1-Gen 2) ?

It's an H1-5.0-E-G2

Version_Master 1.14
Version_Slave 1.02
Version_ARM 1.17

I believe the early firmware versions of H1- Gen2 had incorrectly mapped registers, and this had to be updated for it to work with the integration (which is what your error message suggests and also the fact that you can modpoll read yourself from the 41000 registers)

I've just checked the latest firmware versions which are Master 1.23, Slave 1.02, Manager(ARM) 1.38 so you are well behind.

Can you contact your installer or email Fox service with your inverter serial number and ask them to update you to the latest firmware - then your inverter should respond on the correct modbus registers.

Dave Foster wrote: Tue Jul 02, 2024 2:05 pm

clusterfuffle wrote: Tue Jul 02, 2024 1:54 pm

Dave Foster wrote: Tue Jul 02, 2024 1:48 pm What inverter is it you are connecting (H1,KH,H3,H1-Gen 2) ?

It's an H1-5.0-E-G2

Version_Master 1.14
Version_Slave 1.02
Version_ARM 1.17

I believe the early firmware versions of H1- Gen2 had incorrectly mapped registers, and this had to be updated for it to work with the integration (which is what your error message suggests and also the fact that you can modpoll read yourself from the 41000 registers)

I've just checked the latest firmware versions which are Master 1.23, Slave 1.02, Manager(ARM) 1.38 so you are well behind.

Can you contact your installer or email Fox service with your inverter serial number and ask them to update you to the latest firmware - then your inverter should respond on the correct modbus registers.

Ah thank you so much that's really helpful! Luckily i've already asked my installer to update the firmware as I noticed some functionality in the app was greyed out so fingers crossed that will get done shortly. I will update the post when it's been done. Thanks again.

For anyone who stumbles on this for their own troubleshooting - firmware update did indeed fix the issue and HA is now receiving sensor data properly. Thanks all.

I have the same issue with an H1-3.7-E-G2. I was trying to get Home Assistant Foxess-modbus integration working without success. I can read the date/time registers (40001 - 40005) with modpoll but get illegal address messages with things like "Today output energy" - 11086

My current firmware revisions are:
Master - 1.18
Slave - 1.02
ARM - 1.28

I've asked my installer to update it and if they can't I'll raise a call with Fox-ESS.

Firmware updated but still no joy with those registers.

peter1050st wrote: Thu Jul 18, 2024 12:10 pm Firmware updated but still no joy with those registers.

The Gen 2 registers are often different to the H1, for the total yield today register you have to access it via it's holding register on 32017

That did it. Thanks Dave.