Hi everyone,
I have a FoxESS KH10 hybrid inverter installed in July 2026 with a KH-WL Wi-Fi logger.
I'm trying to connect a Waveshare RS485-to-Ethernet (PoE) gateway for Home Assistant using the foxess_modbus integration.
The published KH10 installation manual shows a removable Meter/CT/RS485 connector with RS485 A/B terminals, but my inverter hardware is different. That connector is not present, the CT wiring goes directly to the PCB using JST-style connectors, and I cannot locate any labelled RS485, COM, A/B, Meter or Data terminals.
Has anyone with a 2025/2026 KH10 successfully connected to the inverter using RS485?
Specifically:
Where are the physical RS485 A/B terminals?
Has FoxESS changed the communications hardware on newer KH10 units?
Is there an updated service manual or wiring diagram showing the current hardware?
Any photos or guidance would be greatly appreciated.
Site Admin
With a WL version you don't need to wire anything as the modbus server is built into the inverter. You would simply select Direct LAN when setting up the plugin in Home assistant targetting the inverters IP address.
You might need to submit a bug report to the git project to get the WL Version supported if its not already supported.
You might need to submit a bug report to the git project to get the WL Version supported if its not already supported.
Community Admin / FoxESS Elite Professional
Did I help you? Feel free to leave me a tip
Book a zoom meeting for remote consultancy or help
Switch to Octopus and earn £50
Subscribe to my YouTube channel
3 x KH Hybird Inverters (Parallel Mode)
1 x H1 Gen1 (Solar Mode)
1 x H1 Gen2 WL (Testing, Modbus and API development)
24 x HV2600 (62.4kWh), 2 x EP12, 2 x ECS2900
32 x 490w across 4 arrays
2 x EV's (Tesla & Mercedes) Fox ESS EV Charger & Hypervolt Chargers
Heatpump & Low Carbon Housebuild
Did I help you? Feel free to leave me a tip Book a zoom meeting for remote consultancy or help Switch to Octopus and earn £50 Subscribe to my YouTube channel3 x KH Hybird Inverters (Parallel Mode)
1 x H1 Gen1 (Solar Mode)
1 x H1 Gen2 WL (Testing, Modbus and API development)
24 x HV2600 (62.4kWh), 2 x EP12, 2 x ECS2900
32 x 490w across 4 arrays
2 x EV's (Tesla & Mercedes) Fox ESS EV Charger & Hypervolt Chargers
Heatpump & Low Carbon Housebuild
Hi Will thank you for that, that's really helpful.
My KH10 was installed in July 2026 and has the KH-WL logger.
I originally planned to use a Waveshare RS485-to-Ethernet (PoE) gateway because I couldn't find the RS485 A/B terminals shown in the published KH10 installation manual. After inspecting the hardware, it appears the newer inverter revision no longer has the same accessible RS485 connection.
My inverter is connected to my home network via Ethernet (not Wi-Fi) using the KH-WL logger, and I can access the logger's local web interface without any problems. The inverter has a fixed IP address on my LAN and is fully reachable over the network.
However, when I configure foxess_modbus using Direct LAN and target the inverter's IP address, it cannot establish a Modbus connection. I also scanned the device from another machine on the same LAN and only HTTPS (port 443) appears to be open—Modbus TCP on port 502 does not appear to be listening.
Could you clarify:
Is Modbus TCP on port 502 expected to be available on current KH-WL firmware when connected via Ethernet?
Does the KH-WL expose Modbus through the Ethernet interface, or only under certain firmware versions/configurations?
Has the communication method changed on the newer 2026 hardware revisions?
If the hardware supports Direct LAN, is this a limitation of the current foxess_modbus integration rather than the inverter itself?
I'm happy to provide my KH-WL firmware versions and help test if that would be useful.
My KH10 was installed in July 2026 and has the KH-WL logger.
I originally planned to use a Waveshare RS485-to-Ethernet (PoE) gateway because I couldn't find the RS485 A/B terminals shown in the published KH10 installation manual. After inspecting the hardware, it appears the newer inverter revision no longer has the same accessible RS485 connection.
My inverter is connected to my home network via Ethernet (not Wi-Fi) using the KH-WL logger, and I can access the logger's local web interface without any problems. The inverter has a fixed IP address on my LAN and is fully reachable over the network.
However, when I configure foxess_modbus using Direct LAN and target the inverter's IP address, it cannot establish a Modbus connection. I also scanned the device from another machine on the same LAN and only HTTPS (port 443) appears to be open—Modbus TCP on port 502 does not appear to be listening.
Could you clarify:
Is Modbus TCP on port 502 expected to be available on current KH-WL firmware when connected via Ethernet?
Does the KH-WL expose Modbus through the Ethernet interface, or only under certain firmware versions/configurations?
Has the communication method changed on the newer 2026 hardware revisions?
If the hardware supports Direct LAN, is this a limitation of the current foxess_modbus integration rather than the inverter itself?
I'm happy to provide my KH-WL firmware versions and help test if that would be useful.
Did you make any progress on this? I'm getting a KH10 installed next month and I assume it will have the KH-WL logger as well (although need to confirm this with my installer). I was planning to get a modbus adapter to wire in but if this isn't feasible or necessary then I need to rethink.
Hi Asleep
Yes, I've made quite a bit of progress since starting this thread.
My KH10 (installed July 2026) also has the KH-WL logger. I initially went down the same route as you and bought a Waveshare RS485-to-Ethernet (PoE) gateway because Direct LAN wasn't working for me.
Following Will's advice, I spent a long time trying to get Direct LAN working. The inverter was connected to my home network via Ethernet with a fixed IP address, and I could access the KH-WL local web interface without any problems. However, foxess_modbus could never establish a Direct LAN connection. Port scans only showed HTTPS (443) and there was nothing listening on port 502, so Modbus TCP was never available on my unit.
That said, Fox Cloud works perfectly, so if you don't need local control or local polling, you'll still be able to monitor your system via the FoxESS app and the Home Assistant Fox Cloud integration. My goal, however, was a completely local connection with no cloud dependency.
In the end I decided to use a physical RS485 connection instead.
The good news is that this does work. I'm now connected locally to Home Assistant using foxess_modbus over RS485 and have full access to the inverter data and controls (PV, battery, grid import/export, SoC, charging/discharging, inverter settings, etc.). It's fast, reliable and doesn't depend on the cloud.
For anyone planning to do the same:
- The RS485 connection uses the same communication connector as the CT clamp.
- On my inverter, the CT clamp is connected to pins 7 and 8, while the RS485 pair is connected to pins 3 and 4.
- At the Ethernet gateway end, the RS485 pair connects to the A (D+) and B (D-) terminals on the Waveshare RS485-to-Ethernet gateway. Mine is configured for Modbus TCP to RTU, 9600 baud, 8 data bits, no parity, 1 stop bit (9600 8N1).
So my conclusions at the moment are:
- Direct LAN may work on some KH-WL units or firmware versions, but it did not on mine despite extensive testing.
- Physical RS485 definitely works on the current KH10 hardware once connected correctly.
- Fox Cloud remains available regardless, so you aren't left without monitoring while investigating local Modbus.
- If you're having your system installed soon, I'd ask your installer to leave access to the communications connector, or even better, install an RS485 cable while they're on site. It's only a few extra minutes during installation but could save a lot of work later if Direct LAN doesn't work on your unit.
I'm still interested in hearing from FoxESS whether newer KH-WL firmware is supposed to expose Modbus TCP over Ethernet, or whether there are differences between hardware or firmware revisions. If anyone from FoxESS can clarify that, it would be really useful.
Hopefully that helps with your planning.
Yes, I've made quite a bit of progress since starting this thread.
My KH10 (installed July 2026) also has the KH-WL logger. I initially went down the same route as you and bought a Waveshare RS485-to-Ethernet (PoE) gateway because Direct LAN wasn't working for me.
Following Will's advice, I spent a long time trying to get Direct LAN working. The inverter was connected to my home network via Ethernet with a fixed IP address, and I could access the KH-WL local web interface without any problems. However, foxess_modbus could never establish a Direct LAN connection. Port scans only showed HTTPS (443) and there was nothing listening on port 502, so Modbus TCP was never available on my unit.
That said, Fox Cloud works perfectly, so if you don't need local control or local polling, you'll still be able to monitor your system via the FoxESS app and the Home Assistant Fox Cloud integration. My goal, however, was a completely local connection with no cloud dependency.
In the end I decided to use a physical RS485 connection instead.
The good news is that this does work. I'm now connected locally to Home Assistant using foxess_modbus over RS485 and have full access to the inverter data and controls (PV, battery, grid import/export, SoC, charging/discharging, inverter settings, etc.). It's fast, reliable and doesn't depend on the cloud.
For anyone planning to do the same:
- The RS485 connection uses the same communication connector as the CT clamp.
- On my inverter, the CT clamp is connected to pins 7 and 8, while the RS485 pair is connected to pins 3 and 4.
- At the Ethernet gateway end, the RS485 pair connects to the A (D+) and B (D-) terminals on the Waveshare RS485-to-Ethernet gateway. Mine is configured for Modbus TCP to RTU, 9600 baud, 8 data bits, no parity, 1 stop bit (9600 8N1).
So my conclusions at the moment are:
- Direct LAN may work on some KH-WL units or firmware versions, but it did not on mine despite extensive testing.
- Physical RS485 definitely works on the current KH10 hardware once connected correctly.
- Fox Cloud remains available regardless, so you aren't left without monitoring while investigating local Modbus.
- If you're having your system installed soon, I'd ask your installer to leave access to the communications connector, or even better, install an RS485 cable while they're on site. It's only a few extra minutes during installation but could save a lot of work later if Direct LAN doesn't work on your unit.
I'm still interested in hearing from FoxESS whether newer KH-WL firmware is supposed to expose Modbus TCP over Ethernet, or whether there are differences between hardware or firmware revisions. If anyone from FoxESS can clarify that, it would be really useful.
Hopefully that helps with your planning.
Thank you, super helpful to hear how you got it working. Looks like it makes sense to go ahead with the RS485 physical connection and gateway. I'll pick this up and see if I can get the installer to connect to the inverter when they do the install.