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.

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

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

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.

Hi ....

Please review as I'm new to this and just giving it a crack, in an ideal world all the attributes would become sensors... and I needed to provide auth for my MQTT host and your options don't provide this.

Thought I would give it a shot?

Let me know your thoughts.

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?

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)

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

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

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?

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:

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?

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

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?

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.

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.