How to change between modes

[Eisbaeeer]

The isolar app allowes different modes lilke manual, surplus loading, time based loading, etc.

[Louisbertelsmann]

I think sungrow doesn‘t provide modbus registers for that. I will check later.

[pdressen]

I have the suspicion, that the "EMS" aka the inverter simply overwrites the modbus registers of the wallbox every few seconds, depending on the charging mode (see #16).

[SunnyCrockett]

I got some information from Sungrow via ticket regarding this issue. See here:

The wallbox can only be started/stopped charging via the address 21212, with the charging mode not being stored in the wallbox itself but in the inverter. The various charging modes are parameters of the inverter and need to be set from the inverter side. 0xA0 fast charging 0xA1 green power charging(surplus charging) 0xA2 preset charging 0xA3 customized charging

And also:

Please try 33541 charging mode. The wallbox can be started/stopped charging via the address 21212 itself.

I could read the register 33541 of the inverter yet, maybe some of you have more luck...?

[Eisbaeeer]

I got some information from Sungrow via ticket regarding this issue. See here:

The wallbox can only be started/stopped charging via the address 21212, with the charging mode not being stored in the wallbox itself but in the inverter. The various charging modes are parameters of the inverter and need to be set from the inverter side. 0xA0 fast charging 0xA1 green power charging(surplus charging) 0xA2 preset charging 0xA3 customized charging

And also:

Please try 33541 charging mode. The wallbox can be started/stopped charging via the address 21212 itself.

I could read the register 33541 of the inverter yet, maybe some of you have more luck...?

That´s it. You safed my day! You must use the holding register of the Inverter to control the wallbox. Im able to change the modes via modbus. Only the timestamp is not clear. It´s not unix timestamp. Division of 3600 is also wrong. Perhaps anybody has an idea? The register of modbus is attached. Wallbox_holding-hegister-SH10RT_sungrow.txt

[SunnyCrockett]

Thanks for the new registers! How did you get those information? Could you post a screenshot (or something else) of the values you get? Maybe the timestamps need a "swap: work"-option like some other values of the wallbox/charger?

[SunnyCrockett]

I have forked the mkaiser yaml for Sungrow inverters and added the registers from @Eisbaeeer. Some of the registers have values, some not. Ich will test a bit when I find time for it. If someone wants to help/test, feel free: https://github.com/SunnyCrockett/Sungrow-SHx-Inverter-Modbus-Home-Assistant/blob/main/modbus_sungrow.yaml

[btota]

just wrote input; automation & tested for changing charging_mode (holding reg adress 33540 ??), no effect ... changing charging_mode from ISC, changes correct and HA output shows up (160,161,162,163)

@Eisbaeeer could you give a feedback?

input_number:
  # Charger wb
  set_ac_wb_charging_mode:
    name: Charger wb charging mode
    options:
      - "fastCharge"
      - "pvSurplus"
      - "quantity&timeBased"
      - "userDefined"
    icon: mdi:ev-station

automation:
    #Charger wb
  - id: "automation_sungrow_charger_wb_charging_mode"
    alias: "sungrow charger wb charging mode"
    description: "Set charger wb charging mode"
    trigger:
      - platform: state
        entity_id:
          - input_select.set_ac_wb_charging_mode
    condition: []
    variables:
      fast_charging: 0xA0 #160 #fast charging
      surplus_charging: 0xA1 #161 #green power charging(surplus charging)
      preset_charging: 0xA2 #162 #preset charging
      customized_charging: 0xA3 #163 #customized charging
    action:
      - service: modbus.write_register
        data_template:
          hub: SungrowSHx
          slave: !secret sungrow_modbus_slave
          address: 33540 # reg 33541
          value: >
            {% if is_state('input_select.set_ac_wb_charging_mode', "fastCharge") %} 
              {{fast_charging}}
            {% if is_state('input_select.set_ac_wb_charging_mode', "pvSurplus") %} 
              {{surplus_charging}}
            {% if is_state('input_select.set_ac_wb_charging_mode', "quantity&timeBased") %} 
              {{preset_charging}}
            {% if is_state('input_select.set_ac_wb_charging_mode', "userDefined") %} 
              {{customized_charging}}
            {% else %}
              {{surplus_charging}}
            {% endif %}
    mode: single    

  - id: "automation_sungrow_charger_wb_charging_mode_input_select_update"
    alias: "sungrow charger wb_charging mode input select update"
    description: "Updates Sungrow charger wb charging mode input select"
    trigger:
      - platform: state
        entity_id:
          - sensor.charger_wb_charging_mode
    condition:
      - condition: template
        value_template: "{{ not is_state('sensor.charger_wb_charging_mode', 'unavailable') }}"
    action:
      - service: input_select.select_option
        target:
          entity_id: input_select.set_ac_wb_charging_mode
        data:
          option: "{{ states('sensor.charger_wb_charging_mode') }}"
    mode: single

[SunnyCrockett]

I added a surplus charging with/without grid input to my fork today and it seem to work (I guess I will add an update after write_register later). I will try to help to implement the charging mode next

[SunnyCrockett]

@btota I got the input for charging mode working for me. Is it working for you, too?

[btota]

@SunnyCrockett pretty good job, thx! A short test, beside feedback from ISC - switching between modes works fine (unfortunately my EV was fullcharged, when I saw your post). Charging mode tells me "Unknown charging mode!", because of no charging is started, I think. Looking forward for more testing till next weekend.

[SunnyCrockett]

Does anyone know how to use modbus.write_register for an uint32 with swap: word? I am trying to update the timestamps but get errors setting i.e. the value 1716764820:

ERROR (MainThread) [homeassistant.components.automation.set_sungrow_charger_wb_charging_duration] set sungrow charger wb charging duration: Error executing script. Unexpected error for call_service at pos 1: 'H' format requires 0 <= number <= 65535

[albertofralbe]

From the docs and the error you posted it seems like you would need to write to the two registers separately

[SunnyCrockett]

@albertofralbe thanks for the hint! It works for me now, but you have to switch to the charging mode in prior to changing any depenging values. For example, if you have selected surplus charging, changes of values for preset charging are not written into the inverter. I also added a template for system datetime and removed the registers which were already in the integration of mkaiser.

Has anyone guessed yet what the unknown (???) registers are for?

[btota]

@SunnyCrockett thx, looks pretty good. Can one read the "unknown" values with the "known" regs directly over ISC?

[SunnyCrockett]

I have removed the unknown registers because they were part of the uint32 values. I found two new ones, one can be used to start/stop charging via the inverter. The other one...I dont know?! I have uploaded the new versions and also my dashboard for now: https://github.com/SunnyCrockett/Sungrow-SHx-Inverter-Modbus-Home-Assistant/tree/main/dashboards/HACS_Charger

[Ccc-ccccc]

@SunnyCrockett Great Job!

I am currently trying to control the wallbox via evcc and modbus via the inverter's Winet-s. While hat works in principal, the inverter's built in EMS interferes with evcc making phase changing via evcc rather impossible. Did you come across any inverter registers that would allow to disable the inverter's EMS control of the wallbox? So, the inverter would just allow to access the wallbox via modbus...

[SunnyCrockett]

Thanks! I dont use evcc, so everything I can say is theoretical. Did you try to change the mode of the wallbox so it works independent from the inverter and then change the registers via the inverter dongle? Or maybe disconnect the wallbox from inverter and connect to the wallbox via WLAN directy? That way evcc could do all the work for you and the inverter doesnt know there is a wallbox.