FoxESS Community - Owners & Installers Forum

Hi all,

I have an H3 Pro inverter and am trying to connect to it via modbus. The guides I have found (https://github.com/nathanmarlor/foxess_ ... ring-Guide) do not include the H3 Pro and all other inverters seem to have a RS485 interface next to the Meter485. The H3 Pro only seems to have "EMS 485B" and "Meter 485A" on that connector but two 485 interfaces on the parallel outputs on the COM connector. Does anyone know if I can use one of the "485"/ pin 5/6 or the "WIFI 485"/ pin 3/4 on the COM connector? If so, do I need to set one of the DIP switches on the connector or configure the inverter's parallel settings?
Thanks,

Daniel

Hi Daniel,

I would think it is the EMS RS485 A/B pins in the Meter/CT connector you should be using, I know the parallel bus carries all of the signals but it’s not normal to connect this way.

To be sure can I suggest you make a request over on this thread and @MattiasLindahl as he was the first to connect the H3 Pro https://github.com/nathanmarlor/foxess ... ssions/516

Hi Dave,

thanks for the link!
The guys over at Github were able to help. I'll post a short summary here once I have everything set up.

Hi Daniel,

Did you have any luck setting up your H3 Pro/Modbus integration? I'm finding that v1.12.0 lets me manage Work Mode and some other settings, but most sensors are 'Unavailable'. v1.12.1 just bombs out after a minute or so.

H3-Pro-20.0
Master: 1.53
Slave: 1.06
ARM: 1.22

Not yet, still waiting for the electrician to come by and hook it up. I was reading up on things to be sure to have the right cables etc. available. Maybe the guys at the Github thread can help you.

craftonstudfarm wrote: ↑Wed Sep 25, 2024 3:31 pm Hi Daniel,

Did you have any luck setting up your H3 Pro/Modbus integration? I'm finding that v1.12.0 lets me manage Work Mode and some other settings, but most sensors are 'Unavailable'. v1.12.1 just bombs out after a minute or so.

H3-Pro-20.0
Master: 1.53
Slave: 1.06
ARM: 1.22

Not sure if that was you, but in this thread (https://github.com/nathanmarlor/foxess_ ... ssions/685) the solution is to set Max Read to 50 in Settings -> Devices&Services -> Click the ">" on Foxess Modbus -> select 'CONFIGURE' -> choose the Advanced Settings -> set Max Read to 50

Works well for me with H3 Pro connected via USR-TCP-410s and https://github.com/nathanmarlor/foxess_modbus.

Yes, that appears to be the workaround at the moment. Have been up and running for a while without issue; good to hear you are too