Files
tsun-gen3-proxy/ha_addons/ha_addon/DOCS.md
Stefan Allius 036dd6d1dc S allius/issue281 (#282)
* accept DCU serial number starting with '410'

* determine sensor-list by serial number

* adapt unit test for DCU support

* send first batterie measurements to home assistant

* add test case for sensor-list==3036

* add more registers for batteries

* improve error logging (Monitoring SN)

* update the add-on repro only for one stage

* add configuration for energie storages

* add License and Readme file to the add-on

* addon: add date and time to dev and debug docker container tag

* disable duplicate code check for config.py

* cleanup unit test, remove trailing whitespaces

* update changelog

* fix example config for batteries

* cleanup config.jinja template

* fix comments

* improve help texts
2025-02-24 22:39:34 +01:00

6.9 KiB

Home Assistant Add-on: TSUN Proxy

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!

Pre-requisites

  1. This Add-on requires an MQTT broker to work. For a typical installation, we recommend the Mosquitto add-on running on your Home Assistant.

  2. You need to loop the proxy into the connection between the inverter and the TSUN Cloud, you must adapt the DNS record within the network that your inverter uses. You need a mapping from logger.talent-monitoring.com and/or iot.talent-monitoring.com to the IP address of your Home Assistant. This can be done, for example, by adding a local DNS record to AdGuard Home Add-on (navigate to filters on the AdGuard panel and add an entry under custom filtering rules).

Installation

The installation of this add-on is pretty straightforward and not different in comparison to installing any other Home Assistant add-on.

  1. Add the repository URL to the Home Assistant add-on store Add repository on my Home Assistant
  2. Reload the add-on store page
  3. Click the "Install" button to install the add-on.
  4. Add your inverter configuration to the add-on configuration
  5. Start the "TSUN-Proxy" add-on
  6. Check the logs of the "TSUN-Proxy" add-on to see if everything went well.

Please note, the add-on is pre-configured to connect with Home Assistants default MQTT Broker. There is no need to configure any MQTT parameters if you're running an MOSQUITTO add-on. Home Assistant communication and TSUN Cloud URL and Ports are also pre-configured.

This automatic handling of the TSUN Cloud and MQTT Broker conflicts with the TSUN Proxy official documentation. The official documentation will state mqtt.host, mqtt.port, mqtt.user, mqtt.passwd solarman.host, solarman.port tsun.host, tsun.port and Home Assistant options are required. For the add-on, however, this isn't needed.

Configuration

Note: Remember to restart the add-on when the configuration is changed.

Example add-on configuration after installation:

inverters:
  - serial: R17E760702080400
    node_id: PV-Garage
    suggested_area: Garage
    modbus_polling: false
    pv1.manufacturer: Shinefar
    pv1.type: SF-M18/144550
    pv2.manufacturer: Shinefar
    pv2.type: SF-M18/144550

Note: This is just an example, you need to replace the values with your own!

Example add-on configuration for GEN3PLUS inverters:

inverters:
  - serial: Y17000000000000
    monitor_sn: 2000000000
    node_id: inv_1
    suggested_area: Roof
    modbus_polling: true
    client_mode.host: 192.168.x.x
    client_mode.port: 8899
    client_mode.forward: true
    pv1.manufacturer: Shinefar
    pv1.type: SF-M18/144550
    pv2.manufacturer: Shinefar
    pv2.type: SF-M18/144550
    pv3.manufacturer: Shinefar
    pv3.type: SF-M18/144550
    pv4.manufacturer: Shinefar
    pv4.type: SF-M18/144550

Example add-on configuration for GEN3PLUS energie storages:

batteries:
  - serial: 4100000000000000
    monitor_sn: 2300000000
    node_id: bat_1
    suggested_area: Garage
    modbus_polling: false
    pv1.manufacturer: Shinefar
    pv1.type: SF-M18/144550
    pv2.manufacturer: Shinefar
    pv2.type: SF-M18/144550

Note: This is just an example, you need to replace the values with your own!

more information about the configuration can be found in the configuration details page.

MQTT settings

By default, this add-on requires no mqtt config from the user. This is not an error!

However, you are free to set them if you want to override, however, in general usage, that should not be needed and is not recommended for this add-on.

Changelog & Releases

This repository keeps a change log using GitHub's releases functionality.

Releases are based on Semantic Versioning, and use the format of MAJOR.MINOR.PATCH. In a nutshell, the version will be incremented based on the following:

  • MAJOR: Incompatible or major changes.
  • MINOR: Backwards-compatible new features and enhancements.
  • PATCH: Backwards-compatible bugfixes and package updates.

Support

Got questions?

You have several options to get them answered:

You could also open an issue here GitHub.

Authors & contributors

The original setup of this repository is by Stefan Allius.

We're very happy to receive contributions to this project! You can get started by reading CONTRIBUTING.md.

License

This project is licensed under the BSD 3-clause License.

Note the aiomqtt library used is based on the paho-mqtt library, which has a dual license. One of the licenses is the so-called Eclipse Distribution License v1.0. It is almost word-for-word identical to the BSD 3-clause License. The only differences are:

  • One use of "COPYRIGHT OWNER" (EDL) instead of "COPYRIGHT HOLDER" (BSD)
  • One use of "Eclipse Foundation, Inc." (EDL) instead of "copyright holder" (BSD)

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.