mkaiser / Sungrow-SHx-Inverter-Modbus-Home-Assistant

Sungrow SH Integration for Home Assistant for SH3K6, SH4K6, SH5K-20, SH5K-V13, SH3K6-30, SH4K6-30, SH5K-30, SH3.RS, SH3.6RS, SH4.0RS, SH5.0RS, SH6.0RS, SH5.0RT, SH6.0RT, SH8.0RT, SH10RT, SH5.0RT-20, SH6.0RT-20, SH8.0RT-20, SH10RT-20, SH5.0RT-V112, SH6.0RT-V112, SH8.0RT-V112, SH10RT-V112, SH5.0RT-V122, SH6.0RT-V122, SH8.0RT-V122, SH10RT-V122, SH4.6R

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Force charge and all other modbus write registers don't work

MIRR23 opened this issue · comments

Describe the bug:

All of the modbus write register commands don't work. Doesn't matter how long I wait nothing updates.
I probably know why, but unsure what I have to write in the YAML-code.

The standard code is the following:
action: - service: modbus.write_register - data_template: hub: SungrowSHx slave: !secret sungrow_modbus_slave address: 13051 # reg 13052 value: "{{ states('input_number.set_sg_forced_charge_discharge_power') | int}}"

hub: SungrowSHx seems to be wrong.
Can you tell me what else to write there?

Screenshot of the automation trace:
image

Your Sungrow inverter:

  • Model: SH-10.RT

  • The inverter is connected via (mark one)

    • LAN (internal port)
    • [] WiNet-S (LAN)
    • [] WiNet-S (WLAN)
  • Are you using a Modbus Proxy (mark one)

    • [] yes
    • no
    • [] I don't know what that is

Home Assistant version:

  • Version: 2024.2.2

modbus_sungrow.yaml:

  • Version/ time stamp : 2023-12-31
  • I ensured to use the most recent version

** Inverter Firmware Status:**

  • I made sure that the newest firmware is installed via the installers account

Never mind... I just forgot, that I changed the modbus name because of two inverters...

** Issue closed **