my TSUN Proxy is now also as a Home Assistant Add-on available.
The TSUN Proxy enables a reliable connection between TSUN third generation
inverters and an MQTT broker. With the proxy, you can easily retrieve real-time values
such as power, current and daily energy and integrate the inverter into Home Assistant.
This works even without an internet connection.
The optional connection to the TSUN Cloud can be disabled!
Supported devices:
TSOL MS-600, MS-700, MS-800
TSOL MS-1600, MS-1800, MS-2000
TSOL MS-3000
TSOL DC-1000 (from version 0.13)
The serial number of supported devices start with R17, R47, Y17, Y47 or 410.
Add my repository URL to the Home Assistant add-on store
It brings support for the TSOL MX-450 inverter and a web UI that allows you to easily access the internal log files without any other add-on like SSH or a file editor. The web UI also has a page with important messages. All warnings and error entries from the log since the last proxy restart are displayed there.
I hope this helps to use the proxy and set up the network well.
I just want to report that whilst I got this working with the Tsun MS 2000, there are problems that I think are more down to the hardware than the proxy.
Firstly, it constantly drops out which gives the appearance of around 50% of the regular yield. I’m not sure if it is actually dropping out or not but HA reports constant spikes. I don’t have this with any of my other inverters.
Secondly, the only way I could get it to work was to route all of my traffic through AdGaurd, and that meant that you can’t use the official Tsun app as it blocks it. This has meant difficulty in communicating with Tsun about the spikes in data.
If anyone has any work arounds, I’d really appreciate it.
I wish I had chosen a different inverter for my set up but was certain the proxy would work based on the comments here and elsewhere, but the hardware is just unreliable for this kind of thing.
I hope it’s ok to post this here as it’s a comment more about the hardware integration with the proxy than the add-on (which is a great idea!)
Thank you for the comment. You should setup up your network, that HA (and the Proxy) uses a public DNS server and only your local devices like your inverters use the addGuard. Than the inverter are connected to the TSUN-Proxy and the Proxy can forward the packets to the TSUN cloud.
A secon approach is, to use the client mode. In this mode the TSUN-Proxy establish a connection to an inverter (TCP:8899) and you don’t need the above Man in The Middle approach. The client mode has one disadvantage, cause we only get infos from the inverter but nothing about the Communikation Module in the inverter (Wifi, etc). For newer inverter firmwares you must use the client mode, because of the TLS encryption of the data stream to the TSUN cloud.