s-allius / tsun-gen3-proxy Goto Github PK

The TSOL MS-600 software sends values from 4 inputs, and the proxy registers them all with the home assistant. However, the inverter has only 2 inputs, so unhelpful values appear on the Home Assistant dashboard.

Only existing inputs should be registered

Thank you for sharing your TSUN proxy with us.

In the log file I see the following error

ERROR | root | Infos.parse: data_type: 76 not supported

Is this the intended behavior or do I need to change some setting to get rid of this error?

In version 0.6.0 GEN3 Plus Inverters only works if solarman.enabledin the 'confidence-toml' file is set to 'true'

In addition to this proxy mode, island mode is also to be implemented so that the GEN3 Plus inverters can also be monitored via MQTT without an Internet connection to the TSUN Cloud

With Version 0.4.0

The new counter 'Inverter Connection Count' is not counted down after sunset. Presumably, the updated counter is no longer transmitted to the MQTT broker after the connection is terminated by the inverter and therefore remains incorrect until sunrise.

The collect data interval is set to 1 minute for TSUN inverters. The proxy reads the values incorrectly and displays 1 second for GEN3 inverters and 60 seconds for GEN3PLUS inverters.

Support for displaying the type and manufacturer of solar modules in Home Assistant

The values should be added to the config.toml file

The following exceptions occur with the current main branch:

'2023-12-24 11:03:15 ERROR | conn | Exception for ('logger.talent-monitoring.com', 5005):
Traceback (most recent call last):
  File "/home/tsun-proxy/async_stream.py", line 31, in loop
    await self.__async_read()
  File "/home/tsun-proxy/async_stream.py", line 72, in __async_read
    self.read()                # call read in parent class
    ^^^^^^^^^^^
  File "/home/tsun-proxy/messages.py", line 164, in read
    self.__dispatch_msg()
  File "/home/tsun-proxy/messages.py", line 271, in __dispatch_msg
�
)
  File "/home/tsun-proxy/messages.py", line 288, in msg_contact_info
    self.__process_contact_info()
  File "/home/tsun-proxy/messages.py", line 302, in __process_contact_info
    result = struct.unpack_from(f'!{name_len+1}pB', self._recv_buffer,
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
struct.error: unpack_from requires a buffer of at least 26 bytes for unpacking 3 bytes at offset 23 (actual buffer size is 24)
'
'2023-12-24 11:03:15 DEBUG | conn | in AsyncStream.close() l('172.28.1.32', 40620) | r('47.254.132.252', 5005)'

Aktuell funktioniert bei mir die Übertragung nicht mehr ordnungsgemäß.
Sowohl nach TSUN noch an Home Assistant.
Im MQTT sehe ich, dass die Config übertragen wird, jedoch die Werte werden nicht übermittelt.
Im Proxy Home Assistant Eintrag wird ein Internal SW Error hoch gezählt und die Verbundenen Controller zählen auf 300 und höher nach Oben.

It's unclear how the proxy can be looped into the connection between the inverter and the TSUN cloud.

Some examples would help

At startup there are some glitches, which aren't visible in the TSUN cloud.

Observed with all versions since version 0.5:

For some time now, the TSUN apps and the TSUN website have always shown the inverter as offline, although status data and measured values are displayed correctly.
This may be due to an interruption in the connection to the TSUN Cloud, especially if the connection to the inverter is maintained

Home Assistant supports configuration of devices to which the individual sensors are assigned. For devices that contain multiple logical units, sub devices are also supported.
For the TSUN inverters, this concept is suitable and the following devices should be created:

• Inverter
• Controller with Wifi/WWAN
• 1 to 4 inputs for solar modules

This means that not all sensors are assigned directly to the inverter and you can use the individual sub-devices on the dashboards as required.

The events and alarms of the inverter should be displayed in the log of Home Assistant

The container runs in non-root mode. It is important that the proxy has the correct UID. Otherwise, reading and writing files on the host volumes is not possible.

Needed:

1. better documentation
   Even better:
2. an automatic mode, so that images can run in any environment, without reconfiguring the UID.

A documentation about all MQTT topics and how to customize them

If the Home Assistant Service has restarted, the proxy should send his autoconfig MQTT topics again. This assures that both are in sync.

The measured values for daily energy production increase continuously and start from zero again with the new day. Since the proxy only sends values to the MQTT broker and the Home Assistant when it receives values from the inverter, the meters are only reset at the start of solar production and not at midnight.
We should send an MQTT update packet at least at midnight so that the meters are reset at the start of a new day. See the red arrow in the picture

The GEN3PLUS inverters sends after a connection setup or reestablishment, the missing data together with the realtime data. In the Power on Timegraph we will see glitches in that moment:

We want to handle this situation and send the non realtime data with a proper timestamp to home assistant, so that they will be inserted in the database at the proper place. Then we should see a permanent growing Power on Timegraph.

The temperature value looks as if it is displayed in Fahrenheit and not in degrees Celsius

Hi,

first, thank you for this amazing promising project!
I am looking forward to use this in my home setup...

Unfortunately I am not able to start the container as you described the startup process.
I build the image and tried to start the container by running:
docker run --dns '192.168.212.20' --env 'UID=1000' -p '5005:5005' -p '10000:10000' -v /srv/tsun-proxy/config:/home/tsun-proxy/config -v /srv/tsun-proxy/log:/home/tsun-proxy/log tsun-proxy

And I get the following:

######################################################
# prepare: 'tsun-proxy' Version:
# for running with UserID:1000, GroupID:1000
#
# create user
######################################################
#
'2024-04-08 20:20:23  INFO | root | Server "tsun-proxy - " will be started'
'2024-04-08 20:20:23  INFO | root | Initialize proxy statistics'
Traceback (most recent call last):
  File "/home/tsun-proxy/./server.py", line 83, in <module>
    Inverter.class_init()
  File "/home/tsun-proxy/inverter.py", line 21, in class_init
    cls.entity_prfx = ha['entity_prefix'] + '/'
                      ~~^^^^^^^^^^^^^^^^^
KeyError: 'entity_prefix'

Is this an error in the code or on my side?

Background:
I tried to use a lxc container and a debian vm under proxmox virtualization.

Btw: Do you have a donation option?

after an OTA update we see unknown messages with ID: 0x76, 0x77, 0x78

we also see incomplete message...

There is a new version of the iomqtt library out, which has some breaking changes.

With version 0.4.3:
Proxy counters do not work properly after restart.

1. After a proxy restart or update, the proxy counters are registered by establishing the first inverter connection. The expectation is that this happens directly at proxy start.

2. The counter values are in the status 'unknown' until the first sunset. here is the expectation, that the counter will be synchronized directly after the proxy start.

If the DNS name logger.talent-monitoring.com is resolved to itself by the proxy, then countless connections are established through this loop until the system crashes.
This is a misconfiguration of the DNS setup and should be recognized by the proxy and the outgoing connection should not be established. The proxy then runs and at least delivers the data to the MQTT broker.

For getting a better view on the proxy, we should add the proxy as a device to Home-Assistant:

possible data to show:

• Proxy version
• number of connection
• connection time
• events like connection errors, establishments, ...

also wishful:

• a switch to disable the connections to the internet

In forwarding mode, we wait for the responses from the TSUN cloud.

For GEN3 inverters we need the timestamp in the proper timezone. Since TSUN don't handle the summertime change correct and there is no time shift allowed between the inverter and the cloud, we want the proper timestamp from the cloud.
However, if there is a configuration problem or the cloud is unavailable, we will no longer receive a response with the correct timestamp from the cloud.

In this situation we want an error handling wich sends the local time to the inverter. Otherwise the logging on Home Assistant will also stop.