Replies: 1 comment 1 reply
-
This is expected behavior, see my response in your previous discussion: #440 (reply in thread) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I wrote this script which does a forced charge for 4 hours but limited by Max SOC to the level of cloud cover expected. It worked (with max SOC set to 80%) but looking at isolarcloud (see screenshot) it shows an odd pattern where SOC rises to 100% and then drops down to 80% at 4am when the script completed. Actual grid draw/battery charge KW data suggests it only charged to 80% and didn't discharge etc. Any ideas what is going on ? Potentially just a isolarcloud data gathering issue ?
alias: Forced Charge with SOC set
sequence:
entity_id: script.sg_set_forced_charge_battery_mode
action: script.turn_on
data: {}
entity_id: input_number.set_sg_max_soc
data:
value: "{{ states('sensor.home_cloud_cover_day_1') | replace('%', '') | float }}"
action: input_number.set_value
entity_id: input_number.set_sg_max_soc
data:
value: 100
action: input_number.set_value
entity_id: script.sg_set_self_consumption_mode
action: script.turn_on
data: {}
description: ""
Beta Was this translation helpful? Give feedback.
All reactions