New Photovoltaik Setup

Energy
1

Hi,
I recently got a new PV system installed and now I’m looking for the best way to integrate my components into HA.
The following components were installed:
a Solinteg MHT-8K-25 inverter and a Solinteg Intg R Smart Meter
a Pylontech Force H3 battery (newest model with lan and wifi)
a Enjoyelec HEMS Controller Air 2 (rebranded from Flexenergie)

The Enjoyelec HEMS is connected to the inverter via serial Modbus.
All components besides the Smart Meter are connected to my lan, partly with internet connection allowed.
Right now I am using the HACS solax plugin the connected to the inverter via Modbus TCP which works, even though I am unsure if it relies on any cloud functionality from solinteg.
I tried solarman to connect to the battery but found out that it only works through the cloud connection which is disabled as of now.
I couldn’t find any way to connect to the Enjoyelec HEMS with Home Assistant which doesn’t supprise me.

Can anyone here recommend a best practice to connect to my devices through lan with HA and without reliance on the cloud?

Thanks a whole lot :slight_smile:

Nana

2

Really? A battery with LAN connection - are you sure?

The documentation suggests the Pylontech Force H3 has only the standard Modbus RTU and a CAN port connection only. Either of which are used to communicate with the inverter only.

My experience of Pylontech batteries is that you are not expected (indeed not allowed) to connect to the battery itself, unless you want to talk over the Console (RS232) port. Doing this is possible (if it has one) but quite tricky, and of questionable value.

Solarman is the company that build most of the dongles and run the cloud systems used by many inverter manufacturers to connect an inverter to the cloud. Hence any “solarman” integration is expecting to connect to a solarman dongle, and via that to talk to the inverter. You don’t appear to have a dongle.

If however you have an Enjoyelec HEMS in there, connected to (and controlling) the inverter (and battery), then you will probably not be able to connect to the inverter yourself anyway. Maybe connect to the HEMS and see what that offers?

Doesn’t surprise me either. This is an energy control system and the company that built it are not expecting (or allowing) you to try and do its job, or bypass the app that comes with it. What you need to get started is the “enjoyelec HEMS Open API (cloud to cloud)” documentation, which I can’t seem to find on the web [not that that surprises me at all, I think this is only available to “flexibility providers and utilities”, so no DIY use].

3

Yeah, it gets an IP and if I allow it access to the internet I can use the solarman integration to get data from the battery. The inverter gets another IP (which I use the solax integration with,which works). So I don’t know why the battery has a lan port that works with solarman but there it is.

I didn’t find any documentation either and it doesn’t suprise me that they keep their cards close to their chest, HA is, in their eyes, a competitor but I still don’t like it :wink:

4

Interesting. My assumption is that there is a dongle of some sort that connects to either the RS232 console port, or to the CAN port. To answer your question - how to connect the battery with Home Assistant, would require more detail on what is behind this and which battery port it is connected to, and what data it is returning.

5

OK, so a lot more digging and yes, the new Pylontech Force H3 has both a LAN port connection and a WiFi built in.

There is a manual that can be downloaded from the Pylontech website

“RESS-Installation Manual-Force H3 Wi-Fi Portal Introduction”

This shows that behind the port is probably a standard Solarman dongle (logger) with the usual serial number and connection back via the cloud to a standard Solarman cloud account and app.

The app shows not only the inverter information, but also the battery information, so my assumption is that the Solarman cloud somehow combines both the inverter (probably with its own logger) with the battery (with its own logger).

The battery information available appears to be quite limited, just pack voltage and current, unit count, and SOC, of of which can be obtained via the CAN link. There may be extra cell temperature information, and that only normally comes via the RS232 console port. There is also the RS485 port, which if not being used to connect to the inverter can provide information.

Since this is clearly a Solarman logger, you can always try getting into that using the DHCP generated IP address. The loggers usually offer a config web page on port 80. Older models allowed secondary servers and even direct access to the inverter (battery) Modbus connection, but more recent models appear to block any attempt at direct connection.

If you can’t get through or around the logger, then the other way for direct access is to connect to the standard RS232 port. Since this does not appear in the documentation for this unit, my assumption is that port is being used for the logger. Normally Solarman loggers use RS485 Modbus, so perhaps not, and the RS232 port is still there somewhere behind the covers.

The quad-connection port available includes the standard Pylontech link pair (link-in and link-out) as well as RS485 and CAN, normally used to talk to the inverter. The CAN link if used can be sniffed. The RS485 port can be used, but has a complicated proprietary protocol that is challenging to work with.

The direction most manufacturers appear to be taking over time is to move to Loggers with cloud connection only, and either not provide or actively prevent any direction connection, which makes connecting to HA without cloud difficult to impossible.

6

Yeah, I can access the, very limited, config page but the only thing, besides wifi config (without the ability to disable wifi), is another server (see screenshot)

Screenshot 2025-12-21 105202
Screenshot 2025-12-21 105202976×520 22.7 KB

7

Oh yes, that screenshot brings back memories.

I had two/three of these Loggers, for my Solis inverter. The original (oldest) one supplied by my installer had the facility in Server B to on-post to another remote server, as well as an open 8899 port for direct Modbus access to the inverter. I tested both using Node-RED and the standard http node.

I found these little devices most frustrating, and I eventually abandoned my logger(s) [actually I ending up fixing them with a large club hammer] and went with a direct Modbus connection, since this avoids the cloud and gives me 15 second updates rather than 15 minutes (with Solis Cloud). I now can’t remember exactly what little worked and what did not, but you may wish to experiment.

I had to search, but here is my post on the ‘Loggers’ from three years ago. I noted at that time that these loggers were gradually going WiFi - my open/working logger was a LAN only model - and that in the newer WiFi models any open access appeared to have been removed.

I guess, going back to your original question, your options are limited to using the Solarman-based integrations etc that work with the standard WiFi logger / cloud.

I am still curious as to which battery port this S-Logger is attached to, and how they stich together in the cloud the battery info with the inverter info. Your battery pack must connect to your inverter via either CAN or the RS485 port. If CAN, then the RS485 port is open for use. If there is also still, as I expect, the usual Pylontech RS232 port for console access, which is the port I use to extract battery information down to the cell level.