bohdan-s / SunGather

GNU General Public License v3.0
164 stars 68 forks source link

SG10RS - Configured to use total_active_power but not configured to scrape this register #185

Open jkerekes99 opened 5 months ago

jkerekes99 commented 5 months ago

Hi, apologies if this has been covered before, however, I haven't been able to find the answer searching.

My inverter is: SG10RS with WiNet-S Dongle

I am using the Home Assistant Addon via the repo. I am getting all the entities except for:

The log shows the following: 2024-06-04 12:22:38 INFO Loaded config: /share/SunGather/config.yaml 2024-06-04 12:22:39 INFO Loaded registers: registers-sungrow.yaml 2024-06-04 12:22:39 INFO Registers file version: 0.2.4 2024-06-04 12:22:42 ERROR MQTT: Configured to use total_active_power but not configured to scrape this register MQTT: Configured to use total_active_power but not configured to scrape this register

Not sure what I'm doing wrong, there is not much to configure in the addin and as I said the other entities are working well.

bohdan-s commented 5 months ago

Smart _meter needs true and level set to 2

jkerekes99 commented 5 months ago

Smart _meter needs true and level set to 2

Thanks for the quick reply. I have added "level", I still get that error in the log and those entities are missing: CleanShot 2024-06-04 at 17 46 17

I have a S100 smart meter.

jkerekes99 commented 5 months ago

Just tried level: 3 and I still get the error. Maybe it is ignoring level in the yaml file?

I noticed level is not exposed in the GUI config.

jkerekes99 commented 5 months ago

So I opened /share/SunGather/config.yaml and it is showing level: 1. So it is NOT taking the "level" changes made in the addon configuration tab.

I changed level in the config.yaml file directly and restarted the SunGather addon, same error again.

hadimiqbal commented 5 months ago

Any update on this , i have the same inverter but cannot get HA to show anything

jkerekes99 commented 5 months ago

It is working for me, just not:

CleanShot 2024-06-19 at 10 09 27

hadimiqbal commented 5 months ago

having said that, it just started when i moved the port back to 502 image

jkerekes99 commented 5 months ago

@hadimiqbal So you get entities I don't. But your Inverter is a different model to mine.

My inverter is a SG10RS Yours is a SG10RT.

hadimiqbal commented 5 months ago

Yeah its actually RS i was just trying different name if it made a difference

jkerekes99 commented 5 months ago

Yeah its actually RS i was just trying different name if it made a difference

Interesting, where did you change the model? You are getting "Active Power" where I am not.

hadimiqbal commented 5 months ago

i did it in the UI but the YAML looks like this for now image

hadimiqbal commented 5 months ago

its funny i am not seeing the ones you see, do you think it may take time ?

hadimiqbal commented 5 months ago

would you know how toi generate more than these 3 image

jkerekes99 commented 5 months ago

Not sure, I don't think so. My entities appeared immediately.

Are you running the latest firmware on your inverter? 06AF4468-2510-4AE8-8864-C9CD73BEF1A0_4_5005_c

A218789A-4454-4745-8B0B-E8C76F008D91_1_201_a

jkerekes99 commented 5 months ago

would you know how toi generate more than these 3

They just appeared after entering the IP address into the GUI config and hitting start.

jkerekes99 commented 5 months ago

Ok, so I managed to get all the supported entities working: CleanShot 2024-06-23 at 17 51 05

I had to however set: level:3 in the config.yaml (via terminal, not via HA adding).

Setting to 2 does not work.

However the issue I am getting now is the log file is filled with errors trying to scrape the other unsupported entities: Traceback (most recent call last): File "/venv/lib/python3.12/site-packages/pymodbus/transaction.py", line 208, in execute self.client.framer.processIncomingPacket(response, File "/venv/lib/python3.12/site-packages/pymodbus/framer/socket_framer.py", line 153, in processIncomingPacket self._process(callback) File "/venv/lib/python3.12/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 2024-06-23 17:47:56 WARNING Modbus connection failed Modbus connection failed 2024-06-23 17:47:58 ERROR index out of range index out of range 2024-06-23 17:47:58 ERROR Modbus Error: [Input/Output] Unable to decode request Traceback (most recent call last): File "/venv/lib/python3.12/site-packages/pymodbus/transaction.py", line 208, in execute self.client.framer.processIncomingPacket(response, File "/venv/lib/python3.12/site-packages/pymodbus/framer/socket_framer.py", line 153, in processIncomingPacket self._process(callback) File "/venv/lib/python3.12/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 Modbus Error: [Input/Output] Unable to decode request Traceback (most recent call last): File "/venv/lib/python3.12/site-packages/pymodbus/transaction.py", line 208, in execute self.client.framer.processIncomingPacket(response, File "/venv/lib/python3.12/site-packages/pymodbus/framer/socket_framer.py", line 153, in processIncomingPacket self._process(callback) File "/venv/lib/python3.12/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

Is there a way to be able to pick the entities/registers you want the addon to scrape? rather than just choosing a level? Ideally, I would love level 2 to work on the SG10RS inverters, however it doesn't.

mitch-1211 commented 4 months ago

Hi @jkerekes99, I am also using this add on with the SG10RS. I'm able to get the following sensors with level 3:

Sungrow SG10RS Active Export to Grid
sensor.sungrow_sg5rs_active_export_to_grid
MQTT
—
—

Sungrow SG10RS Active Generation
sensor.sungrow_sg5rs_active_generation
MQTT
—
—

Sungrow SG10RS Active Import from Grid
sensor.sungrow_sg5rs_active_import_from_grid
MQTT
—
—

Sungrow SG10RS Daily Export to Grid
sensor.sungrow_sg10rs_daily_export_to_grid
MQTT
—
—

Sungrow SG10RS Daily Generation
sensor.sungrow_sg10rs_daily_generation
MQTT
—
—

Sungrow SG10RS Daily Import from Grid
sensor.sungrow_sg10rs_daily_import_from_grid
MQTT
—
—

Sungrow SG10RS Last reset
sensor.sungrow_sg10rs_last_reset
MQTT
—
—

Sungrow SG10RS Load Power
sensor.sungrow_sg10rs_load_power
MQTT
—
—

Sungrow SG10RS Meter Power
sensor.sungrow_sg10rs_meter_power
MQTT
—
—

Sungrow SG10RS Power State
binary_sensor.sungrow_sg10rs_power_state
MQTT
—
—

Sungrow SG10RS Temperature
sensor.sungrow_sg10rs_temperature
MQTT
—
—

Sungrow SG10RS Total Export Energy
sensor.sungrow_sg5rs_total_export_energy
MQTT
—
—

Sungrow SG10RS Total Import Energy
sensor.sungrow_sg5rs_total_import_energy
MQTT
—
—

Sungrow SG10RS Total Power Yields
sensor.sungrow_sg5rs_total_power_yields
MQTT

No errors in log like you have. Can you share your config.yaml? (located under /share/SunGather/config.yaml)