evcc-io / evcc

Sonne tanken ☀️🚘
https://evcc.io
MIT License
3.47k stars 639 forks source link

Sungrow SH15T. Issues with reading home battery data #16704

Closed leonidnf closed 1 day ago

leonidnf commented 3 days ago

Describe the bug

Evcc cannot read home battery data while using "sungrow-hybrid" template. The inverter SH15T, communication device Winet-S2, and the Battery SBR128 are updated to the latest firmware.

The inverter is connected via the LAN port on the Winet-S2 dongle.

image

Still, the invertor data is shown on another dashboard and there the Battery data is shown:

image

Steps to reproduce

Restart the Evcc

Configuration details

interval: 30s # control cycle interval

log: debug
levels:
  cache: error

modbusproxy:
  port: 5021
  uri: 192.168.200.133:502

meters:
  - name: grid1
    type: template
    template: sungrow-hybrid
    usage: grid
    modbus: tcpip
    id: 1
    host: 192.168.200.133 # Hostname
    port: 502 # Port
    timeout: 30s # optional for modbus: tcpip?

  - name: pv2
    type: template
    template: sungrow-hybrid
    usage: pv
    modbus: tcpip
    id: 1
    host: 192.168.200.133 # Hostname
    port: 502 # Port
    timeout: 30s # optional for modbus: tcpip

  - name: battery3
    type: template
    template: sungrow-hybrid
    usage: battery
    modbus: tcpip
    id: 1
    host: 192.168.200.133 # Hostname
    port: 502 # Port
    capacity: 12.8 # Akkukapazität in kWh (optional)
    timeout: 30s # optional for modbus: tcpip

chargers:
  - type: template
    template: twc3
    host: 192.168.200.9
    name: teslaCharger

vehicles:
  - name: teslay
    type: template
    template: tesla
    title: Tesla Y
    icon: car
    vin: xxxxx
    capacity: 59
    phases: 3
    accessToken: xxxxx
    refreshToken: xxxxx
    commandProxy: xxxxx

loadpoints:
  - title: Garage
    charger: teslaCharger
    mode: pv
    #  resetOnDisconnect: true
    vehicle: teslay

site:
  title: HomeSweetHome
  meters:
    grid: grid1
    pv:
      - pv2
    battery:
      - battery3
  residualPower: 100
  maxGridSupplyWhileBatteryCharging: 50
#  batteryDischargeControl: true

tariffs:
  currency: EUR # (default EUR)
  grid:
    type: tibber
    token: xxxxx
    homeid: xxxxx

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.082 # [currency]/kWh
  co2:
    type: grünstromindex
    zip: xxxxx

Log details

[site  ] DEBUG 2024/10/17 20:17:53 ----
[twc3  ] TRACE 2024/10/17 20:17:53 GET http://192.168.200.9/api/1/vitals
[twc3  ] TRACE 2024/10/17 20:17:53 {"contactor_closed":false,"vehicle_connected":true,"session_s":10085,"grid_v":236.8,"grid_hz":49.782,"vehicle_current_a":0.4,"currentA_a":0.2,"currentB_a":0.4,"currentC_a":0.0,"currentN_a":0.2,"voltageA_v":0.0,"voltageB_v":0.0,"voltageC_v":1.1,"relay_coil_v":11.8,"pcba_temp_c":21.3,"handle_temp_c":17.9,"mcu_temp_c":28.1,"uptime_s":152263,"input_thermopile_uv":-259,"prox_v":0.0,"pilot_high_v":8.7,"pilot_low_v":-11.7,"session_energy_wh":262.800,"config_status":5,"evse_state":4,"current_alerts":[],"evse_not_ready_reasons":[1]}
[lp-1  ] DEBUG 2024/10/17 20:17:53 charge power: 0W
[lp-1  ] DEBUG 2024/10/17 20:17:53 charge currents: [0.2 0.4 0]A
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: send 38 af 00 00 00 06 01 04 32 d1 00 02
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: recv 38 af 00 00 00 07 01 04 04 00 00 00 00
[site  ] DEBUG 2024/10/17 20:17:53 grid power: -0W
[pv2   ] TRACE 2024/10/17 20:17:53 modbus: send 38 b0 00 00 00 06 01 04 13 98 00 02
[pv2   ] TRACE 2024/10/17 20:17:53 modbus: recv 38 b0 00 00 00 07 01 04 04 00 00 00 00
[pv2   ] TRACE 2024/10/17 20:17:53 modbus: send 38 b1 00 00 00 06 01 04 32 ca 00 02
[pv2   ] TRACE 2024/10/17 20:17:53 modbus: recv 38 b1 00 00 00 07 01 04 04 10 de 00 00
[site  ] DEBUG 2024/10/17 20:17:53 pv power: 0W
[battery3] TRACE 2024/10/17 20:17:53 modbus: send 38 b2 00 00 00 06 01 04 32 dd 00 01
[battery3] TRACE 2024/10/17 20:17:53 modbus: recv 38 b2 00 00 00 05 01 04 02 05 1c
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: send 38 b3 00 00 00 06 01 04 15 e2 00 02
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: recv 38 b3 00 00 00 07 01 04 04 fe b8 ff ff
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: send 38 b4 00 00 00 06 01 04 13 9a 00 01
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: recv 38 b4 00 00 00 05 01 04 02 09 61
[battery3] TRACE 2024/10/17 20:17:53 modbus: send 38 b5 00 00 00 06 01 04 32 c8 00 01
[battery3] TRACE 2024/10/17 20:17:53 modbus: recv 38 b5 00 00 00 05 01 04 02 00 00
[battery3] TRACE 2024/10/17 20:17:53 modbus: send 38 b6 00 00 00 06 01 04 32 c8 00 01
[battery3] TRACE 2024/10/17 20:17:53 modbus: recv 38 b6 00 00 00 05 01 04 02 00 00
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: send 38 b7 00 00 00 06 01 04 15 e4 00 02
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: recv 38 b7 00 00 00 07 01 04 04 02 2e 00 00
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: send 38 b8 00 00 00 06 01 04 13 9b 00 01
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: recv 38 b8 00 00 00 05 01 04 02 09 4d
[battery3] TRACE 2024/10/17 20:17:53 modbus: send 38 b9 00 00 00 06 01 04 32 e2 00 02
[battery3] TRACE 2024/10/17 20:17:53 modbus: recv 38 b9 00 00 00 07 01 04 04 01 23 00 00
[battery3] TRACE 2024/10/17 20:17:53 modbus: send 38 ba 00 00 00 06 01 04 32 de 00 01
[battery3] TRACE 2024/10/17 20:17:53 modbus: recv 38 ba 00 00 00 05 01 04 02 02 f3
[site  ] DEBUG 2024/10/17 20:17:53 battery soc: 76%
[site  ] DEBUG 2024/10/17 20:17:53 battery power: 0W
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: send 38 bb 00 00 00 06 01 04 15 e6 00 02
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: recv 38 bb 00 00 00 07 01 04 04 ff 29 ff ff
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: send 38 bc 00 00 00 06 01 04 13 9c 00 01
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: recv 38 bc 00 00 00 05 01 04 02 09 47
[site  ] DEBUG 2024/10/17 20:17:53 grid currents: [-1.37 2.34 -0.905]A
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: send 38 bd 00 00 00 06 01 04 32 ec 00 02
[grid1 ] TRACE 2024/10/17 20:17:53 modbus: recv 38 bd 00 00 00 07 01 04 04 14 49 00 00
[site  ] DEBUG 2024/10/17 20:17:53 site power: 100W
[lp-1  ] DEBUG 2024/10/17 20:17:53 charge voltages: [0 0 1.1]V
[lp-1  ] DEBUG 2024/10/17 20:17:53 charger status: B
[tesla ] TRACE 2024/10/17 20:17:53 GET https://fleet-api.prd.eu.vn.cloud.tesla.com/api/1/vehicles/LRWYGCFSXPC742839/vehicle_data
[tesla ] TRACE 2024/10/17 20:17:54 {"response":null,"error":"vehicle unavailable: vehicle is offline or asleep","error_description":"","txid":"8cd7c097efa03cafbc6d94e18cf5a0a1"}
[lp-1  ] DEBUG 2024/10/17 20:17:54 pv charge current: 0A = 0A + -0.145A (100W @ 3p)
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5007 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 01d2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5010 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 00dc
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5011 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 0000
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5012 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 01f5
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5013 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 0000
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5016 qty 2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 00000000
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5018 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 0961
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5019 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 094d
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5020 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 093b
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5032 qty 2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 00000000
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5034 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 03e7
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5241 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: modbus: exception '0' (unknown), function '4'
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5600 qty 2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 000e0000
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5602 qty 2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: feb8ffff
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5604 qty 2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 022e0000
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5606 qty 2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: ff29ffff
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5725 qty 2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 00000000
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5722 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: fffe
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5723 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 0005
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5724 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: ffff
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5740 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: modbus: exception '0' (unknown), function '4'
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5741 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: modbus: exception '0' (unknown), function '4'
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5742 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: modbus: exception '0' (unknown), function '4'
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5743 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: modbus: exception '0' (unknown), function '4'
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5744 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: modbus: exception '0' (unknown), function '4'
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 5745 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: modbus: exception '0' (unknown), function '4'
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 12999 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 8200
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 13000 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 0000
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 13007 qty 2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 04de0000
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 13009 qty 2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: ffe6ffff
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 13019 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 0a56
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 13020 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 0030
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 13021 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 051c
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 13030 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 0015
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 13031 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 0015
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 13032 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 0015
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: id 1 addr 13033 qty 2
[proxy-5021] TRACE 2024/10/17 20:17:54 read input: 04c40000
[proxy-5021] TRACE 2024/10/17 20:17:54 read holdings: id 1 addr 12999 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read holding: 00cf
[proxy-5021] TRACE 2024/10/17 20:17:54 read holdings: id 1 addr 13049 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:54 read holding: 0000
[proxy-5021] TRACE 2024/10/17 20:17:54 read holdings: id 1 addr 13050 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:55 read holding: 00cc
[proxy-5021] TRACE 2024/10/17 20:17:55 read holdings: id 1 addr 13051 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:55 read holding: 0000
[proxy-5021] TRACE 2024/10/17 20:17:55 read holdings: id 1 addr 13057 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:55 read holding: 03e8
[proxy-5021] TRACE 2024/10/17 20:17:55 read holdings: id 1 addr 13058 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:56 read holding: 0064
[proxy-5021] TRACE 2024/10/17 20:17:56 read holdings: id 1 addr 13073 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:56 read holding: 024e
[proxy-5021] TRACE 2024/10/17 20:17:56 read holdings: id 1 addr 13086 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:56 read holding: 00aa
[proxy-5021] TRACE 2024/10/17 20:17:56 read holdings: id 1 addr 13099 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:56 read holding: 0005
[proxy-5021] TRACE 2024/10/17 20:17:56 read holdings: id 1 addr 33046 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:57 read holding: 02bc
[proxy-5021] TRACE 2024/10/17 20:17:57 read holdings: id 1 addr 33047 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:57 read holding: 02bc
[proxy-5021] TRACE 2024/10/17 20:17:57 read holdings: id 1 addr 33148 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:57 read holding: ffff
[proxy-5021] TRACE 2024/10/17 20:17:57 read holdings: id 1 addr 33149 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:57 read holding: ffff
[proxy-5021] TRACE 2024/10/17 20:17:57 read holdings: id 1 addr 30229 qty 1
[proxy-5021] TRACE 2024/10/17 20:17:57 read holding: 0055
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5007 qty 1
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 01d2
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5010 qty 1
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 00dc
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5011 qty 1
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 0000
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5012 qty 1
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 01f5
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5013 qty 1
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 0000
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5016 qty 2
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 00000000
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5018 qty 1
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 0965
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5019 qty 1
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 0949
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5020 qty 1
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 0940
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5032 qty 2
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 00000000
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5034 qty 1
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: 03e7
[proxy-5021] TRACE 2024/10/17 20:18:04 read input: id 1 addr 5241 qty 1

What type of operating system are you running?

HomeAssistant Add-on

Nightly build

Version

v0.130.13

andig commented 2 days ago

Evcc cannot read home battery data while using "sungrow-hybrid" template.

Issue unclear.

leonidnf commented 2 days ago

Hi @andig , thank you for your fast response!

The first screenshot shows that the Battery SOC is 73% (which is correct), but the battery discharging is 0.0 w (which is not correct). In the second screenshot, it can be seen that the battery discharging 1.05 kW. In the EVCC logs can be seen that

[site ] DEBUG 2024/10/17 20:17:53 battery power: 0W

I assume that the EVCC sungrow-hybrid template can not properly calculate the charging/discharging power of the battery. Please let me know if additional info is needed.

andig commented 2 days ago

Was sagt

evcc meter --log trace,db:error

Welche Werte stimmen nicht?

leonidnf commented 2 days ago

Hi @andig , I'm running the EVCC as a HomeAssistant Add-on and I can not run evcc meter command inside of the docker container (it can not find the evcc.yaml config file there). But from the Log dashboard, I can see that the following value is not correct: DEBUG 2024/10/18 14:50:21 battery power: 0W At the moment battery power should be around 1000W.

I'm using EVCC as a Modbus proxy and an entire dashboard is based on the values provided by this proxy. On that dashboard I can see the battery power

andig commented 2 days ago

Lets see evcc meter please.

leonidnf commented 2 days ago

@andig I have installed the Evcc on standalone linux server just for debugging and was able to pull the evcc meter logs

battery3
--------
[battery3] TRACE 2024/10/18 15:15:24 modbus: send 00 0b 00 00 00 06 01 04 32 dd 00 01
[battery3] TRACE 2024/10/18 15:15:24 modbus: recv 00 0b 00 00 00 05 01 04 02 00 91
[battery3] TRACE 2024/10/18 15:15:24 modbus: send 00 0c 00 00 00 06 01 04 32 c8 00 01
[battery3] TRACE 2024/10/18 15:15:24 modbus: recv 00 0c 00 00 00 05 01 04 02 00 00
[battery3] TRACE 2024/10/18 15:15:24 modbus: send 00 0d 00 00 00 06 01 04 32 c8 00 01
[battery3] TRACE 2024/10/18 15:15:24 modbus: recv 00 0d 00 00 00 05 01 04 02 00 00
[battery3] TRACE 2024/10/18 15:15:24 modbus: send 00 0e 00 00 00 06 01 04 32 e2 00 02
[battery3] TRACE 2024/10/18 15:15:24 modbus: recv 00 0e 00 00 00 07 01 04 04 01 6c 00 00
[battery3] TRACE 2024/10/18 15:15:24 modbus: send 00 0f 00 00 00 06 01 04 32 de 00 01
[battery3] TRACE 2024/10/18 15:15:24 modbus: recv 00 0f 00 00 00 05 01 04 02 00 f6
Power:        0W
Energy:       36.4kWh
Soc:          25%
Controllable: true

Battery 3 power is shown as 0, but it should be 129W

andig commented 2 days ago

Battery power is the odd one:

  power:
    source: calc
    mul:
    - source: modbus
      {{- include "modbus" . | indent 4 }}
      register:
        address: 13021 # Battery power 32DD -> 00 91
        type: input
        decode: int16
    - source: calc
      add:
      - source: modbus
        {{- include "modbus" . | indent 6 }}
        register:
          type: input
          address: 13000 # Battery running state 32C8 -> 00 00
          decode: bool16
          bitmask: 2 # Charging
        scale: -1
      - source: modbus
        {{- include "modbus" . | indent 6 }}
        register:
          type: input
          address: 13000 # Battery running state 32C8 -> 00 00
          decode: bool16
          bitmask: 4 # Discharging

According to the bitmask your battery is neither charging nor discharging. Whatever that means.

andig commented 1 day ago

That doesn't tell me anything. Check the docs for Register 13000 Running State. Afaik our implementation is correct (based on https://forum.iobroker.net/topic/50564/bedeutung-codes-running-states-sungrow-wechselrichter). If new docs say differently we'd need them to double-check.

Closing until new documentation available.

leonidnf commented 10 hours ago

@andig Thank you! Will check the docs and maybe some other open source materials. I see that evcc users have a similar issue: https://github.com/evcc-io/evcc/issues/15915