Sungrow SH6.0RS

[buleus]

Hello
I have a question about sungrow sh6.0.rs maybe someone can help me.I use a sungrow sh6.0.rs and a battery SBR064 and 2 easee chargers. I am not pushing back to the grid any surplus.My problem is that:
i have setup to prioritize vehicle charging when home battery is above 50%. The problem is that this function is not working to my setup or i do not know how to set it up....I will explain:
the car continue to charge from solar (i have enough power) but the battery is keep charging from the grid. After the battery is complet full everything works as should be.Is there any way to limit the battery charging from the grid and allow all the power to the charger? I will atach my config and if you need some logs too
thank you !

evcc.txt

[zachelnet]

Hello,
If you're using Min+Solar, this behaviour is possible, because you're using power from the grid. Have you tried switching the charger to solar?

[buleus]

thank you for your answer.....as i understand...and maybe i am wrong ...because i 'm not feeding back to the grid solar scenario is not available for me.....is this corect?

[zachelnet]

thank you for your answer.....as i understand...and maybe i am wrong ...because i 'm not feeding back to the grid solar scenario is not available for me.....is this corect?

The solar scenario should be possible. Can you post your configuration?

[buleus]

sure here it is:

open evcc at http://evcc.local:7070

network:
schema: http
host: evcc.local # .local suffix announces the hostname on MDNS
port: 7070

levels:
site: debug
lp-1: debug
lp-2: debug
cache: error
db: error

unique installation id

plant: 8a

interval: 30s # control cycle interval

sponsortoken: ey

sponsors can set telemetry: true to enable anonymous data aggregation

see #4554

telemetry: true

meters:

• name: grid
  type: template
  template: sungrow-hybrid
  usage: grid
  modbus: tcpip
  id: 1
  host: 127.0.0.1 # Hostname
  port: 5021 # Port
  timeout: 30s # optional

• name: pv
  type: template
  template: sungrow-hybrid
  usage: pv
  modbus: tcpip
  id: 1
  host: 127.0.0.1 # Hostname
  port: 5021 # Port
  timeout: 30s # optional

• type: custom
  name: battery
  power:
  source: go # handling old and new firmware
  script: |
  res := float64(-bp)
  if (brs&0x4 > 0 || bc < 0) && bp >= 0 {
  res = float64(bp)
  }
  res
  in:

  • name: brs
    type: int
    config:
    source: modbus
    id: 1
    uri: 127.0.0.1:5021
    register:
    type: input
    address: 13000 # Battery running state
    decode: uint16
  • name: bc
    type: int
    config:
    source: modbus
    id: 1
    uri: 127.0.0.1:5021
    register:
    type: input
    address: 13020 # Battery current
    decode: uint16
  • name: bp
    type: int
    config:
    source: modbus
    id: 1
    uri: 127.0.0.1:5021
    register:
    type: input
    address: 13021 # Battery power
    decode: int16
    energy:
    source: modbus
    id: 1
    uri: 127.0.0.1:5021
    register:
    address: 13026 # Total battery discharge energy, 0.1kWh
    type: input
    decode: uint32s
    scale: 0.1
    soc:
    source: modbus
    id: 1
    uri: 127.0.0.1:5021
    register:
    address: 13022 # Battery level
    type: input
    decode: int16
    scale: 0.1

chargers:

• name: Easee
  type: template
  template: easee
  user: b
  password: C
  charger: U
  timeout: 30s # optional
  authorize: true

• name: Easee1
  type: template
  template: easee
  user: b
  password: C
  charger: Z
  timeout: 30s # optional
  authorize: true

vehicles:

• name: Zoe
  type: template
  title: Zoe
  template: renault
  user: b
  password: L
  icon: car
  capacity: 40
  phases: 1
  mode: minpv
  minCurrent: 6
  maxCurrent: 16
  priority: 1
  cache: 15m
  alternativewakeup: false

loadpoint describes the charger, charge meter and connected vehicle

loadpoints:

• title: Poarta # display name for UI
  charger: Easee # charger
  mode: "off" # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available

  remaining settings are experts-only and best left at default values

  priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
  soc:

  polling defines usage of the vehicle APIs

  Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery

  or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.

  poll:
  # poll mode defines under which condition the vehicle API is called:
  # charging: update vehicle ONLY when charging (this is the recommended default)
  # connected: update vehicle when connected (not only charging), interval defines how often
  # always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
  mode: charging
  # poll interval defines how often the vehicle API may be polled if NOT charging
  interval: 60m
  estimate: true # set false to disable interpolating between api updates (not recommended)
  enable: # pv mode enable behavior
  delay: 1m # threshold must be exceeded for this long
  threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
  disable: # pv mode disable behavior
  delay: 3m # threshold must be exceeded for this long
  threshold: 0 # maximum import power (W)

• title: Curte # display name for UI
  charger: Easee1 # charger
  mode: "off" # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available

  remaining settings are experts-only and best left at default values

  priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
  soc:

  polling defines usage of the vehicle APIs

  Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery

  or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.

  poll:
  # poll mode defines under which condition the vehicle API is called:
  # charging: update vehicle ONLY when charging (this is the recommended default)
  # connected: update vehicle when connected (not only charging), interval defines how often
  # always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
  mode: charging
  # poll interval defines how often the vehicle API may be polled if NOT charging
  interval: 60m
  estimate: true # set false to disable interpolating between api updates (not recommended)
  enable: # pv mode enable behavior
  delay: 1m # threshold must be exceeded for this long
  threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
  disable: # pv mode disable behavior
  delay: 3m # threshold must be exceeded for this long
  threshold: 0 # maximum import power (W)

site:
title: M Residence
meters:
grid: grid
pv:
- pv
battery:
- battery
residualPower: 300

modbusproxy:

• port: 5021
  uri: 192.168.0.93:502

Message config using evcc go-text-template rendering, evcc variables and sprig-functions

messaging:
events:
start: # charge start event
title: Charge started
msg: Started charging in "${mode}" mode
stop: # charge stop event
title: Charge finished
msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
connect: # vehicle connect event
title: Car connected
msg: "Car connected at ${pvPower:%.1fk}kW PV"
disconnect: # vehicle connected event
title: Car disconnected
msg: Car disconnected after ${connectedDuration}
soc: # vehicle soc update event
title: Soc updated
msg: Battery charged to ${vehicleSoc:%.0f}%
guest: # vehicle could not be identified
title: Unknown vehicle
msg: Unknown vehicle, guest connected?
services:

• type: telegram
  token: ""
  chats:
  • ""

tariffs are the fixed or variable tariffs

tariffs:
currency: RON # three letter ISO-4217 currency code (default EUR)
grid:
type: fixed
price: 1.3 # optional, additional charges per kWh

[buleus]

Maybe it's your config about residualPower wrong. Did you try to set the value to 0?

I don't think you need this if you have a zero export configuration in the inverter.

in the documentation they said that the systems with battery should have a minimum residual power of 100/200….

[mfuchs1984]

In case of 0 export, it does not make sense to have positive residualPower, since there will never be export.

[buleus]

ok great! will
modify this and let you know guys how’s working! thank you again

[mfuchs1984]

I think you need to ask Sungrow why your battery is charging although there is not enough PV power.

[buleus]

:) yeah i have ask them some other stuff…they never respond…anyway is anyone here with sh series inverter to copy the settings? maybe my initial inverter setup was wrong….
seems like battery is charging first in any condition…there is a lot of setup in isolar cloud and i don’t know them