Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sungrow SG10RT - "unable to decode request"

See original GitHub issue

Just got a Sungrow SG10RT installed and my config.py looks like this:

inverter_ip = "192.168.1.120"
inverter_port = 502
slave = 0x01
model = "sungrow-sg10rt"
timeout = 3
scan_interval = 10
json_file = "telemetry.json"

Confirmed that port 502 is open on the inverter_ip. Log:

INFO:root:Loaded config sungrow-sg10rt
INFO:root:Creating SungrowModbusTcpClient
INFO:root:Connecting
INFO:root:Connected
INFO:root:No MQTT configuration detected
INFO:root:No InfluxDB configuration detected
INFO:root:No PVOutput configuration detected
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:Transaction failed. ([Errno 54] Connection reset by peer)
DEBUG:pymodbus.framer.socket_framer:Processing:
DEBUG:pymodbus.transaction:Getting transaction 1
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

I saw another issue that mentioned using pymodbus version 2.4.0. I’m already on that version as per requirements.txt

Any ideas?

Issue Analytics

State:
Created 2 years ago
Comments:17 (7 by maintainers)

Top GitHub Comments

3reactions

bohdan-scommented, Dec 16, 2021

I thought I would just update, I have forked (and rewritten) Solariot here: https://github.com/bohdan-s/SunGather The main difference is there is no more model files, it uses a shared registers file and detects your model to return the correct registers. It also resolves the PVOutput data issues above.

0reactions

gservatcommented, Dec 7, 2021

Come to think of it I don’t think that “energy used” column is very accurate either.

Top Results From Across the Web

Issues · meltaxa/solariot - GitHub

InfluxDBClientError: 400: {"error":"unable to parse 'Sungrow ... Sungrow SG10RT - "unable to decode request" ... Sungrow SG10RT inverter modbus.

Sungrow SH10.RT Modbus integration

Hi, I created a Modbus based integration for a Sungrow SH10. ... ModbusIOException: Modbus Error: [Input/Output] Unable to decode request

Sungrow modbus map - Solar PV discussion - Whirlpool Forums

Anyway, I've recently installed a Sungrow inverter with the wifi dongle. ... raise ModbusIOException("Unable to decode request")

The World's Most Bankable Inverter Brand | SUNGROW HOME

With more than 24 years of experience in the development and production of photovoltaic inverter technology, Sungrow is committed to providing clean power ......