mattervn / modbustcp2mqtt

Sungrow & SMA Solar Inverter addon for Home Assistant using mobusTCP

ModbusTCP2MQTT

My organization has renamed to MatterVN. All "TenySmart" repos will be redirected to "MatterVN". Please check and update your urls. Sungrow & SMA Solar Inverter addon for Home Assistant. This addon will connect directly to your Inverter using ModbusTCP/MobusWebTCP

Support models

The Inverter must be accessible on the network using TCP.

PV Grid-Connected String Inverters

SG30KTL, SG10KTL, SG12KTL, SG15KTL, SG20KTL, SG30KU, SG36KTL, SG36KU, SG40KTL, SG40KTL-M, SG50KTL-M, SG60KTL-M, SG60KU, SG30KTL-M, SG30KTL-M-V31, SG33KTL-M, SG36KTL-M, SG33K3J, SG49K5J, SG34KJ, LP_P34KSG, SG50KTL-M-20, SG60KTL, SG80KTL, SG80KTL-20, SG60KU-M, SG5KTL-MT, SG6KTL-MT, SG8KTL-M, SG10KTL-M, SG10KTL-MT, SG12KTL-M, SG15KTL-M, SG17KTL-M, SG20KTL-M, SG80KTL-M, SG111HV, SG125HV, SG125HV-20, SG30CX, SG33CX, SG36CX-US, SG40CX, SG50CX, SG60CX-US, SG110CX, SG250HX, SG250HX-US, SG100CX, SG100CX-JP, SG250HX-IN, SG25CX-SA, SG75CX, SG3.0RT, SG4.0RT, SG5.0RT, SG6.0RT, SG7.0RT, SG8.0RT, SG10RT, SG12RT, SG15RT, SG17RT, SG20RT

PV Grid-Connected String Inverters Gen 2

SG5K-D, SG8K-D

Residential Hybrid Inverters

SH5K-20, SH3K6, SH4K6, SH5K-V13, SH5K-30, SH3K6-30, SH4K6-30, SH5.0RS, SH3.6RS, SH4.6RS, SH6.0RS, SH10RT, SH8.0RT, SH6.0RT, SH5.0RT

Installation

1. Navigate in your Home Assistant frontend to Supervisor -> Add-on Store.
2. Click the 3-dots menu at upper right ... -> Repositories and add https://github.com/MatterVN/HassioAddon
3. Install ModbusTCP2MQTT Addon
4. Configure and Start it

smart_meter: True - (Only needed for SG* Models)

Set to true if you have a smart meter installed, this will return power usage at the meter box, without it you can not calculate house power usage. Hybrid inverters will provide this by default (load_power_hybrid)

Registers

This tool should be able to access most registers exposed. Some registers only exposed to MQTT, you must create sensor manually. (Sorry i don't have time):

level: 1 - This is the most useful data for day to day

Level: 2 - This should be everything your inverter supports

Level: 3 - This will try every register, you will get lots of 0/65535 responses for registers not supported.

Useful Registers:

This is just a brief list of registers I have found useful

daily_power_yields - Total Power in kWh generated today total_power_yields - Total Power in kWh generated since inverter install total_running_time - Total Hours inverter has been powered on since install internal_temperature - Internal temperature of the Inverter total_active_power - Current power being generated by the inverter in Watts meter_power - (SG* Models)Power usage at the meter box, needs a smart meter installed. +ve means consuming from the grid, -ve means exporting to the grid load_power - Power being consumed in total load_power_hybrid - (SH* Models only) Power being consumed in total export_to_grid - How much being currently exported to the grid. For SG* Models this is calculated from meter_power if -ve value, returned as a positive value. (For Hybrid models export_power_hybrid is used) import_from_grid - How much being currently imported from grid. This is calculated from meter_power if +ve value (_for hybrid models export_power_hybrid [will be negative when importing from grid] is used) timestamp - Last time data was collected, based on Inverters clock by default

Meta

This add-on is based on SunGather

modbustcp2mqtt's Issues

daily_energy_consumption incorrect data

the sensor "sensor.inverter_daily_energy_consumption" is giving a reading of 6,553.5kwh, the actual number should be 6.5535 kwh, how do i fix this? how to a divide the sensors value by 1000

Note: using sg5k-d

Support Smart Meter

at first thanks for your great work.
Is it possible to integrate new adresses for inverters with smart meter? See picture for inverter types and adress codes.

ERROR:pymodbus.factory:index out of range

I get the following issue when I try this addon.

INFO:root:Modbus connected
INFO:root:Configured MQTT Client
INFO:root:Publish Home Assistant Discovery message
DEBUG:pymodbus.transaction:Current transaction state - IDLE
DEBUG:pymodbus.transaction:Running transaction 1
DEBUG:pymodbus.transaction:SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0x88 0x0 0x64
DEBUG:pymodbus.client.sync:New Transaction state 'SENDING'
DEBUG:pymodbus.transaction:Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
DEBUG:pymodbus.transaction:Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
DEBUG:pymodbus.transaction:RECV: 0x0 0x1 0x0 0x0 0x0 0x2 0x1 0x84 0x2
DEBUG:pymodbus.framer.socket_framer:Processing: 0x0 0x1 0x0 0x0 0x0 0x2 0x1 0x84 0x2
DEBUG:pymodbus.factory:Factory Response[132]
ERROR:pymodbus.factory:index out of range
ERROR:pymodbus.transaction:Modbus Error: [Input/Output] Unable to decode request
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/pymodbus/transaction.py", line 190, in execute
    self.client.framer.processIncomingPacket(response,
  File "/usr/lib/python3.9/site-packages/pymodbus/framer/socket_framer.py", line 153, in processIncomingPacket
    self._process(callback)
  File "/usr/lib/python3.9/site-packages/pymodbus/framer/socket_framer.py", line 175, in _process
    raise ModbusIOException("Unable to decode request")
pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] Unable to decode request
WARNING:root:Modbus connection failed
WARNING:root:Failed to scrape inverter, sleeping until next scan
DEBUG:pymodbus.transaction:Current transaction state - TRANSACTION_COMPLETE
DEBUG:pymodbus.transaction:Running transaction 2
DEBUG:pymodbus.transaction:Clearing current Frame : - 0x0 0x1 0x0 0x0 0x0 0x2 0x1 0x84 0x2
DEBUG:pymodbus.transaction:SEND: 0x0 0x2 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0x88 0x0 0x64
DEBUG:pymodbus.client.sync:New Transaction state 'SENDING'
DEBUG:pymodbus.transaction:Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
DEBUG:pymodbus.transaction:Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
DEBUG:pymodbus.transaction:RECV: 0x0 0x2 0x0 0x0 0x0 0x2 0x1 0x84 0x2
DEBUG:pymodbus.framer.socket_framer:Processing: 0x0 0x2 0x0 0x0 0x0 0x2 0x1 0x84 0x2
DEBUG:pymodbus.factory:Factory Response[132]
ERROR:pymodbus.factory:index out of range
ERROR:pymodbus.transaction:Modbus Error: [Input/Output] Unable to decode request
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/pymodbus/transaction.py", line 190, in execute
    self.client.framer.processIncomingPacket(response,
  File "/usr/lib/python3.9/site-packages/pymodbus/framer/socket_framer.py", line 153, in processIncomingPacket
    self._process(callback)
  File "/usr/lib/python3.9/site-packages/pymodbus/framer/socket_framer.py", line 175, in _process
    raise ModbusIOException("Unable to decode request")
pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] Unable to decode request
WARNING:root:Modbus connection failed
WARNING:root:Failed to scrape inverter, sleeping until next scan

Any ideas on what is wrong.

It´s a Sungrow SG10RT connected via a sungrow WiNet-S wifi module.
Please let me know what additional information I should provide.
Addon version is 0.2

Unable to add Repositiory to Homeassistant

When trying to add the repo to HA an error will be thrown.
I try to Add: https://github.com/TenySmart/HassioAddon

Following error appears in the log:

Custom MQTT server?

Hello, I do not use the mqtt built in HA, is it possible to edit mqtt login details?

Support for SG15RT?

Is there a way of adding support for the SG15RT inverter?

Noob needs additional info

Hi what info does this integration provide? Even I have a Smartmeter function installed with my Sungrow SG5K inverter (which provides info on power used from the grid, power fed into the grid and the total solar production) I'm only getting these 3 sensors? Any chance to get more data?

Home Assistant OS installation of ModbusTCP2MQTT - s6-overlay-suexec: fatal: can only run as pid 1

I have issues all of a sudden communicating with the Sungrow SG5kd. I don't believe i have done anything to break it, but i have started getting the error;
s6-overlay-suexec: fatal: can only run as pid 1
This in the ModbusTCP2MQTT Log, and the overall home assistant system log is showing
Failed to to call /addons/4ee6ccd4_modbus_inverter/stats - Container addon_4ee6ccd4_modbus_inverter is not running

I am fairly new to home assistant and would love someone to point me in the right direction. I am running the HyperV image of home assistant OS - core-2022.5.2 (i was at 2022.5.4, but tried a restore an older backup of home assistant to 2022.5.2 to see if it was the update which broke it)

I assume i am getting the Container Addon not running error due to the fact that there is the S6 overlay error, but any further diagnosis is a little above my current level of expertise

s6-overlay-suexec: fatal: can only run as pid 1 (Recent changes do not fix closed issue)

As per previous issue: #33

Unfortunately the changes do not appear to have worked, and/or the add-on doesn't upgrade in HA.

Thanks for your ongoing efforts.

Code location of Entities

Where is the location in the code where you add the entities?
I do only see 3 entities for MQTT and want to look into the code to add some more and learn a bit:

Can you please give me a hint where I can find the location?

Working - but with error initially

Ive been adding sensors from attributes and noticed that everytime I restart HA the integration stops working.

To get it working I have to stop MQTT Broker and ModbusTCP2MQTT and then start MQTT Broker First, wait, then start ModbustTCP2MQTT

It then throws an error intitially, but then begins working.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:23:33] INFO: Configured'core-mosquitto' mqtt broker.
INFO:root:Create SungrowModbusTcpClient. Model: sungrow-sg8kd
INFO:root:Modbus connected
INFO:root:Configured MQTT Client
INFO:root:Publish Home Assistant Discovery message
WARNING:root:Modbus connection failed
WARNING:root:Failed to scrape inverter, sleeping until next scan
ERROR:pymodbus.factory:Unable to decode response Modbus Error: Unknown response 0
ERROR:pymodbus.transaction:Modbus Error: [Input/Output] Unable to decode request
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/pymodbus/transaction.py", line 190, in execute
    self.client.framer.processIncomingPacket(response,
  File "/usr/lib/python3.9/site-packages/pymodbus/framer/socket_framer.py", line 165, in processIncomingPacket
    self._process(callback, error=True)
  File "/usr/lib/python3.9/site-packages/pymodbus/framer/socket_framer.py", line 175, in _process
    raise ModbusIOException("Unable to decode request")
pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] Unable to decode request
WARNING:root:Modbus connection failed
WARNING:root:Failed to scrape inverter, sleeping until next scan
INFO:root:{'inverter_size': 8.0, 'daily_power_yield': 14000.0, 'total_power_yield': 86.66, 'inverter_power_on_hours': 5080, 'internal_temp': 60.0, 'pv1_voltage': 176.3, 'pv1_current': 7.2, 'pv2_voltage': 294.8, 'pv2_current': 14.1, 'total_pv_power': 5452, 'grid_voltage': 245.9, 'inverter_current': 21.3, 'total_active_power': 5316, 'grid_frequency': 50.1, 'export_power': -2504, 'export_power_indicator': 65535, 'power_meter': 2811, 'daily_export_energy': 9900.0, 'total_export_energy': 5930.6, 'daily_import_energy': 6100.0, 'total_import_energy': 4548.8, 'daily_energy_consumption': 4100.0, 'total_energy_consumption': 2735.7, 'timestamp': '2022-02-02T10:23:53'}

Addon doenst intall on HA. WARNING: Running pip as the 'root' user can result in broken permissions...

Installation fails with error

end of Supervisor logs:

<....>

Collecting idna<4,>=2.5
  Downloading idna-3.4-py3-none-any.whl (61 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.5/61.5 kB 10.8 MB/s eta 0:00:00
Collecting websocket-client>=1.2.1
  Downloading websocket_client-1.4.1-py3-none-any.whl (55 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 55.0/55.0 kB 10.6 MB/s eta 0:00:00
Collecting PyYAML
  Downloading PyYAML-5.4.1.tar.gz (175 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 175.1/175.1 kB 13.5 MB/s eta 0:00:00
Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
  Preparing metadata (pyproject.toml): started
  Preparing metadata (pyproject.toml): finished with status 'done'
Collecting toml~=0.10.0
  Downloading toml-0.10.2-py2.py3-none-any.whl (16 kB)
Using legacy 'setup.py install' for pycryptodomex, since package 'wheel' is not installed.
Using legacy 'setup.py install' for paho-mqtt, since package 'wheel' is not installed.
Using legacy 'setup.py install' for SungrowModbusWebClient, since package 'wheel' is not installed.
Building wheels for collected packages: PyYAML
  Building wheel for PyYAML (pyproject.toml): started
  Building wheel for PyYAML (pyproject.toml): finished with status 'done'
  Created wheel for PyYAML: filename=PyYAML-5.4.1-cp310-cp310-linux_armv7l.whl size=45657 sha256=411219d9d46e192dd8eef6d00e67d5476725b2be1f9d04d57207c006229745f6
  Stored in directory: /tmp/pip-ephem-wheel-cache-bln7b5l8/wheels/c7/0d/22/696ee92245ad710f506eee79bb05c740d8abccd3ecdb778683
Successfully built PyYAML
Installing collected packages: pyserial, paho-mqtt, websocket-client, urllib3, toml, PyYAML, pymodbus, pycryptodomex, idna, charset-normalizer, certifi, SungrowModbusWebClient, SungrowModbusTcpClient, requests, readsettings
  Running setup.py install for paho-mqtt: started
  Running setup.py install for paho-mqtt: finished with status 'done'
  Running setup.py install for pycryptodomex: started
  Running setup.py install for pycryptodomex: still running...
  Running setup.py install for pycryptodomex: still running...
  Running setup.py install for pycryptodomex: finished with status 'done'
  Running setup.py install for SungrowModbusWebClient: started
  Running setup.py install for SungrowModbusWebClient: finished with status 'done'
Successfully installed PyYAML-5.4.1 SungrowModbusTcpClient-0.1.6 SungrowModbusWebClient-0.3.2 certifi-2022.9.24 charset-normalizer-2.1.1 idna-3.4 paho-mqtt-1.6.1 pycryptodomex-3.11.0 pymodbus-2.4.0 pyserial-3.5 readsettings-3.4.5 requests-2.28.1 toml-0.10.2 urllib3-1.26.12 websocket-client-1.4.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

Removing intermediate container fd315f040121
 ---> d283b20defd2
Step 9/23 : COPY SunGather/ /
 ---> 8c60c83c1846
Step 10/23 : COPY SunGather/exports/ /exports
 ---> 22ae017b0630
Step 11/23 : COPY run.sh /

Home Assistant 2022.10.5 Supervisor 2022.10.0 Operating System 9.3

Modbus client is not connected, attempting to reconnect

Hi! I cant get this to work, i get following message.

I have a SG20RT with the wifi dongle, Using port 8082 and http.

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[08:35:58] INFO: Configured'core-mosquitto' mqtt broker.
[08:35:58] INFO: Generated config file.
2022-12-21 08:35:59 INFO Starting SunGather 0.3.8
2022-12-21 08:35:59 INFO Loaded config: config.sg
2022-12-21 08:35:59 INFO Loaded registers: //registers-sungrow.yaml
2022-12-21 08:35:59 INFO Registers file version: 0.2.0
2022-12-21 08:35:59 INFO Logging to console set to: INFO
2022-12-21 08:35:59 INFO Modbus client is not connected, attempting to reconnect
2022-12-21 08:35:59 INFO Connection: SungrowModbusWebClient_0.3.2(192.168.1.:8082)
2022-12-21 08:36:12 WARNING No data returned for read, 4999:1
No data returned for read, 4999:1
2022-12-21 08:36:12 INFO Model detection failed, please set model in config.py
2022-12-21 08:36:12 INFO Loading Export: exports\mqtt
2022-12-21 08:36:12 ERROR Failed loading export: 'NoneType' object has no attribute 'replace'
Please make sure mqtt.py exists in the exports folder
Failed loading export: 'NoneType' object has no attribute 'replace'
Please make sure mqtt.py exists in the exports folder
2022-12-21 08:36:12 INFO Modbus, Connecting new session
2022-12-21 08:36:22 WARNING No data returned for read, 5000:100
No data returned for read, 5000:100
2022-12-21 08:36:27 WARNING No data returned for read, 5100:100
No data returned for read, 5100:100
2022-12-21 08:36:32 WARNING No data returned for hold, 4999:10
No data returned for hold, 4999:10
2022-12-21 08:36:37 WARNING No data returned for hold, 5009:10
No data returned for hold, 5009:10
2022-12-21 08:36:42 WARNING No data returned for hold, 5034:10
No data returned for hold, 5034:10
2022-12-21 08:36:42 INFO Disconnecting: SungrowModbusWebClient_0.3.2(192.168.1.:8082)
2022-12-21 08:36:42 INFO Disconnecting: None
2022-12-21 08:36:42 WARNING Data collection failed, skipped exporting data. Retying in 30 secs
Data collection failed, skipped exporting data. Retying in 30 secs
2022-12-21 08:36:42 WARNING SunGather is taking 30.02 to process, which is longer than interval 30, Please increase scan interval

`KeyError: '4ee6ccd4_modbus_inverter'` in logs when trying to install add-on

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 106, in wrapper
    return await self._method(*args, **kwargs)
  File "/usr/src/supervisor/supervisor/addons/__init__.py", line 181, in install
    await addon.instance.install(store.version, store.image, arch=addon.arch)
  File "/usr/src/supervisor/supervisor/utils/__init__.py", line 33, in wrap_api
    return await method(api, *args, **kwargs)
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/supervisor/supervisor/docker/addon.py", line 534, in _install
    self._build(version)
  File "/usr/src/supervisor/supervisor/docker/addon.py", line 560, in _build
    _LOGGER.error("Can't build %s:%s: %s", self.image, version, err)
  File "/usr/src/supervisor/supervisor/docker/addon.py", line 78, in image
    return self.addon.image
  File "/usr/src/supervisor/supervisor/addons/addon.py", line 391, in image
    return self.persist.get(ATTR_IMAGE)
  File "/usr/src/supervisor/supervisor/addons/addon.py", line 165, in persist
    return self.sys_addons.data.user[self.slug]
KeyError: '4ee6ccd4_modbus_inverter'

Only 9 sensors get auto-discovered

I just installed the add-on and connected to an SH6.0RT inverter with smart meter, scan_level is set to DETAIL . However, MQTT auto-discovered only 9 sensors:

The full MQTT message contains a lot more sensors though:

QoS: 0
Payload: device_type_code: SH6.0RT
run_state: 'ON'
protocol_number: 1094856704
protocol_version: 16781568
arm_software_version: 16722
dsp_software_version: 19780
nominal_active_power: 6
output_type: 3P4L
daily_power_yields: 30.9
total_power_yields: 24279
internal_temperature: 43.1
mppt_1_voltage: 247
mppt_1_current: 0
mppt_2_voltage: 509.4
mppt_2_current: 1.3
total_dc_power: 615
phase_a_voltage: 232.2
phase_b_voltage: 232.2
phase_c_voltage: 233.8
total_reactive_power: -5
power_factor: 1
grid_frequency: 49.9
active_power_regulation_setpoint: 0
meter_power: 0
load_power: 400
daily_running_time: 0
pv_power_of_today: 0
daily_pv_energy_yields: 24.9
monthly_pv_energy_yields: 0
yearly_pv_energy_yields: 0
direct_power_consumption_today_pv: 0
direct_power_consumption_pv: 4.5
direct_power_consumption_monthly_pv: 0
direct_power_consumption_yearly_pv: 0
export_power_from_pv_today: 0
export_power_from_pv: 15.4
export_power_from_pv_monthly: 0
export_power_from_pv_yearly: 0
battery_charge_power_from_pv_today: 0
battery_charge_power_from_pv: 5
battery_charge_power_from_pv_monthly: 0
battery_charge_power_from_pv_yearly: 0
system_state: Run
running_state: 11
power_generated_from_pv: 1
battery_charging: 1
battery_discharging: 0
load_active: 1
feed_into_grid: 0
import_from_grid: 0
power_generated_from_load: 0
daily_pv_generation: 35.5
total_pv_generation: 2557.9
daily_pv_export: 20.9
total_pv_export: 1824.4
load_power_hybrid: 396
export_power_hybrid: 4
daily_battery_charge_from_pv: 7
total_battery_charge_from_pv: 413.7
co2_reduction: 1790.5
daily_direct_energy_consumption: 7.6
total_direct_energy_consumption: 319.8
battery_voltage: 320.2
battery_current: 0.5
battery_power: 149
battery_level: 96.8
battery_state_of_healthy: 100
battery_temperature: 25
daily_battery_discharge_energy: 3.2
total_battery_discharge_energy: 367.5
self_consumption_of_day: 26.6
grid_state: 0
phase_a_current: 0.7
phase_b_current: 0.7
phase_c_current: 0.7
total_active_power: 400
daily_import_energy: 0
total_import_energy: 37.8
daily_charge_energy: 7
total_charge_energy: 412.2
drm_state: 255
daily_export_energy: 20.9
total_export_energy: 1834.4
start_stop: Start
power_limitation_switch: Enable
power_limitation_setting: 100
power_factor_setting: 0
reactive_power_adjustment_mode: 'Off'
reactive_power_percentage_setting: 0
power_limitation_adjustment: 0
reactive_power_adjustment: 0
export_to_grid: 0
timestamp: '2022-8-14 18:26:59'

Is there anywhere I can set which sensors are shown?

Unable to install v0.3 (Can only find 0.2.2.1)

Hello,

I seem to only be able to install v0.2.2.1 of the add-on via the repository in my Home Assistant instance.
The Changelog and documentation etc has all updated to reflect the most recent v0.3 version available but I just can't seem to install it.

https://i.imgur.com/PUeJzt8.png

I have gone as far as to completely start fresh with a new Home Assistant instance but I still seem to only be able to find v0.2.
Is there anything else I should be doing to try and get v0.3 to show up for install?

Cheers

How to set custom MQTT server

I don't want to use the built-in MQTT server from HA, where can I set my MQTT server IP? Thanks

WARNING MQTT: Server Error; Server not configured MQTT: Server Error; Server not configured

Addon from Home assistant is showing this fail

Expected data source not listed

I cannot get the data to appear in the dropdown to select the correct data source.

I've set the data collection to full.

SG6KTL-EC_001_001

is it possible to incl. SG6KTL-EC_001_001
i have used sungrow-sg10kt until the last update, and it was working fine, but now it wont work.

sungrow-sg8kd power consumption

Are you able to figure out the power consumption for the sungrow-sg8kd. Generation only seems to really only provide half the data required for anything meaningful

Support For SG10RS?

Thank you for your work here! Any-chance this would work for the SG10RS (G3) inverter?

Add-On using float without default value?

Hi,

First of all, thanks for a great Add-ON!

I am getting warnings in HA :
2021-12-17 19:30:24 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'float' got invalid input 'unknown' when rendering template '{{ states("sensor.sungrow20ktl_mtotalactivepower_kw") | float / 17 }}' but no default was specified. Currently 'float' will return '0', however this template will fail to render in Home Assistant core 2022.1

I am having a hard time finding the root of these warnings but they seem to correspond to when i restart the Add-On or Inverter is offline.

Thanks!

BR,

/Pontus

Cannot configure addon in home assistant

Hi,
I installed the addon in my home assistant (2022.9.1) but when i go to the configuration page of the addon I only see the line:
" This add-on does not expose configuration for you to mess with… "

So I cannot set the host etc.

Am I doing something wrong or is there another way to configure the addon?

Thank you for your help!

P.S. I am trying to connect the SGRT17

Energy Management Dashboard - Inverter Power Needs to be kWh as a unit of measurement

I've been able to implement my inverter within my HA instance and am getting data, however when trying to use the HA energy management dashboard I can only see the following:

• Inverter Daily Energy Consumption
• Inverter Daily Energy Import
• Inverter Energy Monthly
• Inverter Energy Today

I'm expecting to see a Inverter Power which I believe to be a live measurement of the power being produced by my solar inverter. I've been looking around and it appears as this sensor's unit of measurement is a "W" watt... it won't be picked up via the energy management dashboard.

Are you able to review the above and change the unit of measurement from W to kWh and device_class to energy I believe this should resolve the issue.

Happy to discuss further or test as a beta if needed.

Cheers

TypeError: fromRegisters() got an unexpected keyword argument 'endian'

I'm getting the following error.
File "/ModbusTCP.py", line 260, in load_sma_register message = BinaryPayloadDecoder.fromRegisters(received.registers, endian=Endian.Big)

and reading the pymodbus docs there is no mention for endian=
classmethodfromRegisters(registers, byteorder='<', wordorder='>')

Sleeping until next scan loop

I've been running into an issue (generally overnight) where the script fails to communicate with the inverter and displays the below message and then never seems to be able to reconnect. The only way I've been able to fix this is to restart the add-on

WARNING:root:Failed to scrape inverter, sleeping until next scan
DEBUG:pymodbus.transaction:Current transaction state - TRANSACTION_COMPLETE
DEBUG:pymodbus.transaction:Running transaction 1291
DEBUG:pymodbus.transaction:SEND: 0x5 0xb 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0x88 0x0 0x64
DEBUG:pymodbus.client.sync:New Transaction state 'SENDING'
DEBUG:pymodbus.transaction:Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
DEBUG:pymodbus.transaction:Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
DEBUG:pymodbus.transaction:RECV:
DEBUG:pymodbus.framer.socket_framer:Processing:
DEBUG:pymodbus.transaction:Getting transaction 1291
DEBUG:pymodbus.transaction:Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
WARNING:root:Modbus connection failed
WARNING:root:Failed to scrape inverter, sleeping until next scan

Failed to install Modbus

I am getting the error in HASSIO whenever I attempt to upgrade or unisntall and reinstall to version 3. The command '/bin/ash -o pipefail -c pip install --upgrade pycryptodomex==3.11.0 --no-cache-dir -r requirements.txt' returned a non-zero code: 1

Variable IP address in configuration?

My inverter regularly changes IP address (and MAC address, meaning I can't assign a static IP), so I have to manually update 'Inverter_host' in the config frequently so that the addon can find it again.

I can find the correct IP by pinging and can record this as an entity in HASS, but not sure if I can use this value in the addon configuration?

In short, is there a way that 'Inverter_host' in the config/yaml can point to a HASS entity with the current IP, rather than using just a manually-entered IP address?

Entities for "return to grid" and "grid consumption"

Hi,

I can't see entities for the items "return to grid" and "grid consumption" though it should be possible to configure, I think.
I have a sungrow sg10rt, also tried to choose model sg5kd, which makes no difference.

regards and thanks for your work

Georg

Add information about how to create the dashboard in readme

In the readme there is this gif:
https://github.com/TenySmart/ModbusTCP2MQTT/blob/main/images/diagram.gif
But no information on how to create it.
I successfully installed the add-on but am a bit puzzled now how to continue to see the data?

Incorrect sensor data?

The addon pulls through all the data which is great, however my SG8k with either the config for the 5kw or 8kw version reports no data to the sensors:

These are the entity attributes:

state_class: total_increasing inverter_size: 8
daily_power_yield: 100
total_power_yield: 0
inverter_power_on_hours: 2
internal_temp: 39.1
pv1_voltage: 0
pv1_current: 0
pv2_voltage: 0
pv2_current: 0
total_pv_power: 0
grid_voltage: 235.8
inverter_current: 0
total_active_power: 0
grid_frequency: 50.1
export_power: 493
export_power_indicator: 0
power_meter: 493
daily_export_energy: 0
total_export_energy: 0
daily_import_energy: 4200
total_import_energy: 4.2
daily_energy_consumption: 100
total_energy_consumption: 0.1
timestamp: 2022-03-17T19:41:14
unit_of_measurement: kWh
device_class: energy
icon: mdi:solar-power
friendly_name: Inverter Daily Energy Import

I can see the power generation in the app, anyone having the same issues? I can't select any other attributes for the HA energy component so it'd be good to get a fix for the addon

Is it possible to connect SG12RT?

Would me grateful!

Setup help

I'm trying to setup my sg5k-d in home assistant and it's connected. the logs in ModbusTCP2MQTT addons are saying

INFO:root:{'daily_power_yield': 42700.0, 'total_power_yield': 71.3, 'internal_temp': 39.9, 'pv1_voltage': 321.2, 'pv1_current': 0.6, 'pv2_voltage': 338.9, 'pv2_current': 0.4, 'total_pv_power': 359, 'grid_voltage': 238.4, 'inverter_current': 1.4, 'total_active_power': 346, 'grid_frequency': 50.1, 'export_power': 65535, 'export_power_indicator': 32767, 'power_meter': 65535, 'daily_purchased_energy': 6553.5, 'daily_energy_consumption': 6553500.0, 'total_energy_consumption': 6553.5, 'timestamp': '2022-02-11T18:18:27'}
INFO:root:Published to MQTT

so im assuming that works
so how do i get it to display the data on the dashboard?

Compatible with Sungrow SH6.0rt?

I tried to install and configure it, but seems to be not working with SH6.0rt. Whats so different to SH10rt?

No daily self consumption or daily grid consumption

After update to 0.3.3 I don't get any value for daily self consumption or daily grid consumption. It doesn't matter which inverter is selected or which scan level. I only get following data

Before update everything working well. My inverter is SG10KTL-M, before update SG8K-D was used. I use home assistant latest revision.

sensor.inverter_daily_energy_import off by a factor of 1000

sensor.inverter_daily_energy_import claims to be kWh unit_of_measurement, but comparing the values reported vs the values in the app it looks to be smaller by a factor of 1000.

Eg the app shows 4.9 kWh, while the addon is reporting 0.0049 kWh

Can multiple inverters be added?

I have 2x Sungrow SG5K-D inverters. This add-on appears to only pull data from the specified host. Can 2x hosts be specified? Thanks

Socket error on client ModbusTCP, disconnecting.

Hi,

I am having these errors on MQTT Mosquitto broker and not getting any sensor data. Not sure if I have messed up something in the configs? Any help is appreciated. This is my first MQTT intergration.

1642389840: New connection from 172.30.33.4 on port 1883.
1642389840: New client connected from 172.30.33.4 as ModbusTCP (p2, c1, k60, u'addons').
1642389862: Socket error on client ModbusTCP, disconnecting.

The logs from TCP2MQTT seem to show everything is okay on that end?

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[14:29:35] INFO: Configured'core-mosquitto' mqtt broker.
INFO:root:Create SungrowModbusTcpClient. Model: sungrow-sg5kd
INFO:root:Modbus connected
INFO:root:Configured MQTT Client
INFO:root:Publish Home Assistant Discovery message

Energy Distribution Options

New to Home Assistant and hoping there is something I have missed in the install/config. The energy distribution isn't displaying correctly (when compared to the native app iSolarCloud). As far as I can see I am missing an option for Grid Consumption in the Energy Configuration Section.

I have a SG8K but am using the SG5K as suggested here.

What I was comparing to at the time (iSolarCloud)

Addon disconnects and MQTT broker socket error - username 'addons'

I've been able to get the addon working however it disconnects at times and there is no real logic to why. After a review of the MQTT broker log I noticed the login below

1642395202: New client connected from 172.30.33.12 as ModbusTCP (p2, c1, k60, u'addons').

I've running the Mosquitto broker 6.0.1 and from all accounts appears you need to pass the correct auth otherwise you will get a socket error.

1642395266: Socket error on client ModbusTCP, disconnecting.

Which you can see resolves in a disconnection

Are we able to have options within the config to include

MQTT_USER
MQTT_PASS
MQTT_HOST
MQTT_PORT

I believe this will resolve this issue, I note I also had System Bridge installed with the wrong username and password which resulted in the same socket error and disconnection message. Fixing the U/P fixed the socket error and you can see the correct username.

Hopefully this is an easy fix

Integration effecting isolarcloud app data

Since updating, the app I use to view solar inverter data directly is behaving strangely.

It's either disconnected from the internet and not uploading the data. Constant grid draw is incorrect and incorrect PV and lpad.

Purchased Energy Spikes

I'm having occasional spikes in the value that is reported for purchased energy, which is throwing my Energy dashboards out - from memory the figure is reported through modbus strangely (65,000 odd minus energy from grid or something like that)

Is it possible to have some logic that if the figure is higher then a threshold its ignored?

Can and if so how to use with 2 Sungrow inverters

Hi!

I'm new to home assistant but this appears to only support one inverter, is that right ? Thanks to others I found the correct MQQT config and details for home assistant configuration.yaml and that is all working but just for one inverter.

I have a SG5K-D and a SH5K-30.

Thanks!

FATAL: No internal MQTT Broker found

Hi
Still getting this error on Current version: 0.3.3.1
curl: (7) Couldn't connect to server
[13:58:12] ERROR: Something went wrong contacting the API
[13:58:13] FATAL: No internal MQTT Broker found. Please install Mosquitto broker.

Add-on not update to Version 0.2.2

My HA add-on only installs for 0.2.1.1.1 and does not seem to update to 0.2.2 (have issue with Sungrow WFIF dongle not being read anymore). Any reference to force or get to update to 0.2.2 version?

Grid consumption and Return to grid for energy dashbord missing

Only Inverter Daily Generation can be selected in the dashboard confiration page.
Grid consumption and Return to grid are not listed in dashboard configuration.
Smart_meter is set to true

Sungrow SG10RT with WiNet-S_001_247
Do I need to configue something in addition to see the missing statitsics?

FATAL: No internal MQTT Broker found. Please install Mosquitto broker

Getting these errors with HS addon version 0.3.0
The Mosquitto broker is installed

curl: (7) Couldn't connect to server

[20:32:30] ERROR: Something went wrong contacting the API

[20:32:31] FATAL: No internal MQTT Broker found. Please install Mosquitto broker.

Sensors Available Through Add-on

Hi, thanks for creating this great integration - I'm still getting the hang of it. I've only gotten the following sensors which were created when I installed this addon:

How do I add ones for energy exported, energy imported from the grid, and energy consumed?

Modbus Error: [Input/Output] [Errno 104] Connection reset by peer

When the add-on is started it receives some data from the WiNet-S and the subsequent connections are reset by peer :
2022-08-23 17:24:21 DEBUG Running transaction 10
2022-08-23 17:24:21 DEBUG SEND: 0x0 0xa 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0x88 0x0 0x64
2022-08-23 17:24:21 DEBUG New Transaction state 'SENDING'
2022-08-23 17:24:21 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-08-23 17:24:21 DEBUG Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-08-23 17:24:21 DEBUG RECV: 0x0 0xa 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0x0 0x64 0x0 0x1 0x1 0x4 0x0 0x86 0x0 0x0 0x0 0x47 0x0 0x0 0x1 0x99 0x8 0xbf 0x0 0x0 0x10 0x96 0x0 0x35 0x6 0x43 0x0 0x0 0x0 0x0 0x0 0x0 0x8 0xca 0x0 0x0 0x8 0xf0 0x9 0x0 0x9 0x10 0x0 0x20 0x0 0x20 0x0 0x20 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x8 0xb9 0x0 0x0 0x0 0x0 0x0 0x0 0x3 0xe8 0x1 0xf3 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x32 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xc 0x60 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x27 0x10 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
2022-08-23 17:24:21 DEBUG Processing: 0x0 0xa 0x0 0x0 0x0 0xcb 0x1 0x4 0xc8 0x0 0x64 0x0 0x1 0x1 0x4 0x0 0x86 0x0 0x0 0x0 0x47 0x0 0x0 0x1 0x99 0x8 0xbf 0x0 0x0 0x10 0x96 0x0 0x35 0x6 0x43 0x0 0x0 0x0 0x0 0x0 0x0 0x8 0xca 0x0 0x0 0x8 0xf0 0x9 0x0 0x9 0x10 0x0 0x20 0x0 0x20 0x0 0x20 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x8 0xb9 0x0 0x0 0x0 0x0 0x0 0x0 0x3 0xe8 0x1 0xf3 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x32 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xc 0x60 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x27 0x10 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
2022-08-23 17:24:21 DEBUG Factory Response[ReadInputRegistersResponse: 4]
2022-08-23 17:24:21 DEBUG Adding transaction 10
2022-08-23 17:24:21 DEBUG Getting transaction 10
2022-08-23 17:24:21 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-08-23 17:24:21 DEBUG Scraping: read, 5100:100
2022-08-23 17:24:21 DEBUG load_registers: read, 5100:100
2022-08-23 17:24:21 DEBUG Current transaction state - TRANSACTION_COMPLETE
2022-08-23 17:24:21 DEBUG Running transaction 11
2022-08-23 17:24:21 DEBUG SEND: 0x0 0xb 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0xec 0x0 0x64
2022-08-23 17:24:21 DEBUG New Transaction state 'SENDING'
2022-08-23 17:24:21 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-08-23 17:24:21 DEBUG Transaction failed. ([Errno 104] Connection reset by peer)
2022-08-23 17:24:21 DEBUG Processing:
2022-08-23 17:24:21 DEBUG Getting transaction 11
2022-08-23 17:24:21 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-08-23 17:24:21 WARNING Modbus connection failed
Modbus connection failed
2022-08-23 17:24:21 DEBUG Modbus Error: [Input/Output] [Errno 104] Connection reset by peer
2022-08-23 17:24:21 DEBUG Scraping: hold, 4999:10
2022-08-23 17:24:21 DEBUG load_registers: hold, 4999:10
2022-08-23 17:24:21 DEBUG Current transaction state - TRANSACTION_COMPLETE
2022-08-23 17:24:21 DEBUG Running transaction 12
2022-08-23 17:24:21 DEBUG SEND: 0x0 0xc 0x0 0x0 0x0 0x6 0x1 0x3 0x13 0x87 0x0 0xa
2022-08-23 17:24:21 DEBUG New Transaction state 'SENDING'
2022-08-23 17:24:21 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-08-23 17:24:21 DEBUG Transaction failed. ([Errno 104] Connection reset by peer)
2022-08-23 17:24:21 DEBUG Processing:
2022-08-23 17:24:21 DEBUG Getting transaction 12
2022-08-23 17:24:21 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-08-23 17:24:21 WARNING Modbus connection failed
Modbus connection failed
2022-08-23 17:24:21 DEBUG Modbus Error: [Input/Output] [Errno 104] Connection reset by peer
2022-08-23 17:24:21 INFO Scraping: 2/3 registers failed to scrape
2022-08-23 17:24:21 INFO Inverter: Successfully scraped in 0.228663 secs
2022-08-23 17:24:21 DEBUG MQTT: Publishing: inverter/SG10RT/registers : {"device_type_code": "SG10RT", "run_state": "OFF", "daily_power_yields": 26.0, "total_power_yields": 134, "total_running_time": 71, "internal_temperature": 40.9, "total_apparent_power": 2239, "phase_a_voltage": 228.8, "total_active_power": 2233, "work_state_1": "Run", "meter_power": 0, "load_power": 2233, "export_to_grid": 0, "import_from_grid": 0}
2022-08-23 17:24:21 DEBUG MQTT: Message 21 Published
2022-08-23 17:24:21 INFO MQTT: Published
2022-08-23 17:24:21 INFO Closing Session: ModbusTcpClient(192.168.178.58:502)
2022-08-23 17:24:21 DEBUG Processing Time: 0.28 secs
2022-08-23 17:24:21 INFO Next scrape in 29 secs
2022-08-23 17:24:51 DEBUG Checking Modbus Connection
2022-08-23 17:24:51 INFO Modbus, Connecting new session
2022-08-23 17:24:51 DEBUG Scraping: read, 5000:100
2022-08-23 17:24:51 DEBUG load_registers: read, 5000:100
2022-08-23 17:24:51 DEBUG Current transaction state - TRANSACTION_COMPLETE
2022-08-23 17:24:51 DEBUG Running transaction 13
2022-08-23 17:24:51 DEBUG SEND: 0x0 0xd 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0x88 0x0 0x64
2022-08-23 17:24:51 DEBUG New Transaction state 'SENDING'
2022-08-23 17:24:51 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-08-23 17:24:51 DEBUG Transaction failed. ([Errno 104] Connection reset by peer)
2022-08-23 17:24:51 DEBUG Processing:
2022-08-23 17:24:51 DEBUG Getting transaction 13
2022-08-23 17:24:51 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-08-23 17:24:51 WARNING Modbus connection failed
Modbus connection failed
2022-08-23 17:24:51 DEBUG Modbus Error: [Input/Output] [Errno 104] Connection reset by peer
2022-08-23 17:24:51 DEBUG Scraping: read, 5100:100
2022-08-23 17:24:51 DEBUG load_registers: read, 5100:100
2022-08-23 17:24:51 DEBUG Current transaction state - TRANSACTION_COMPLETE
2022-08-23 17:24:51 DEBUG Running transaction 14
2022-08-23 17:24:51 DEBUG SEND: 0x0 0xe 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0xec 0x0 0x64
2022-08-23 17:24:51 DEBUG New Transaction state 'SENDING'
2022-08-23 17:24:51 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-08-23 17:24:51 DEBUG Transaction failed. ([Errno 104] Connection reset by peer)
2022-08-23 17:24:51 DEBUG Processing:
2022-08-23 17:24:51 DEBUG Getting transaction 14
2022-08-23 17:24:51 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-08-23 17:24:51 WARNING Modbus connection failed
Modbus connection failed
2022-08-23 17:24:51 DEBUG Modbus Error: [Input/Output] [Errno 104] Connection reset by peer
2022-08-23 17:24:51 DEBUG Scraping: hold, 4999:10
2022-08-23 17:24:51 DEBUG load_registers: hold, 4999:10
2022-08-23 17:24:51 DEBUG Current transaction state - TRANSACTION_COMPLETE
2022-08-23 17:24:51 DEBUG Running transaction 15
2022-08-23 17:24:51 DEBUG SEND: 0x0 0xf 0x0 0x0 0x0 0x6 0x1 0x3 0x13 0x87 0x0 0xa
2022-08-23 17:24:51 DEBUG New Transaction state 'SENDING'
2022-08-23 17:24:51 DEBUG Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-08-23 17:24:51 DEBUG Transaction failed. ([Errno 104] Connection reset by peer)
2022-08-23 17:24:51 DEBUG Processing:
2022-08-23 17:24:51 DEBUG Getting transaction 15
2022-08-23 17:24:51 DEBUG Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-08-23 17:24:51 WARNING Modbus connection failed
Modbus connection failed
2022-08-23 17:24:51 DEBUG Modbus Error: [Input/Output] [Errno 104] Connection reset by peer
2022-08-23 17:24:51 INFO Disconnecting: ModbusTcpClient(192.168.178.58:502)
2022-08-23 17:24:51 INFO Disconnecting: None
2022-08-23 17:24:51 WARNING Data collection failed, skipped exporting data. Retying in 30 secs
Data collection failed, skipped exporting data. Retying in 30 secs
2022-08-23 17:24:51 DEBUG Processing Time: 0.23 secs
2022-08-23 17:24:51 INFO Next scrape in 29 secs
2022-08-23 17:25:21 DEBUG Checking Modbus Connection
2022-08-23 17:25:21 INFO Modbus client is not connected, attempting to reconnect
2022-08-23 17:25:21 INFO Connection: ModbusTcpClient(192.168.178.58:502)