Then please show me a correct trace with the trigger “t_si_1”. Otherwise, I don’t know how to help you.
Shouldn’t it be possible to implement this using the force function? Or do you mean something similar to shading the sun - only in reverse?
We’ve already had a discussion about this somewhere. I can’t find it at the moment.
Nothing like this is currently planned.
But you could submit it as a pull request on GitHub.
Okay, let’s try this again and start over 
I’m sorry if i have not been able to answer to your questions and/or provide you with the requested information. My sincere apologies.
I’m fairly new to the Automations in Home Assistant as i used Node-red till now. So please provide me with some additional guidance to get you the information you need to help diagnose the problem.
In the mean time i’ve done some troubleshooting to further diagnose my shading not working and i have narrowed it down to the following:
- If the value “elevation” goes over the minimum limit the first time, the automation works and the screens close.
- if the value “elevation” changes within the limits of “minimum and maximum elevation” it does not trigger the automation.
Working example:
- “Shading Elevation Minimum Value” is set to 14
- “Shading Elevation Maximum Value” is set to 90
- sun elevation changes from 13.8 to 14.1
- the automation works
Non-working example:
- “Shading Elevation Minimum Value” is set to 14
- “Shading Elevation Maximum Value” is set to 90
- sun elevation changes from 14.2 to 14.5
- the automation does not work
My current yaml config:
alias: SCREEN SHADING TEST
description: ""
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
shading_forecast_sensor: weather.runningstraat_12
blind: cover.woonkamer_klein
auto_options:
- auto_shading_enabled
shading_position: 1
shading_azimuth_start: 65
shading_azimuth_end: 220
shading_weather_conditions:
- sunny
- partlycloudy
- cloudy
- clear
- rainy
- pouring
shading_waitingtime_start: 10
shading_elevation_min: 14
shading_forecast_temp: 1
individual_config:
- allow_shading_multiple_times
check_config: true
Thanks again for your patience and support
That’s just how Home Assistant works. Each automation only executes the trigger if the value is exceeded. But only then. Changes above a numerical range, for example, do not lead to a new trigger.
For this reason, I also mentioned that you have to perform a real status change via the developer toolbar when testing:
Okay, thank you for clarifying that. Much appreciated.
OK, that’s really good to know. That means that shading works like this?!
Threshold 22000 for start and 12000 for stop
if 22000 is exceeded for maybe 2 seconds, the timer will be start for beginning and only stop, if it will be under 12000? Is that right?
Or will the timer stop after the 2 seconds?
Thank your
Had here and there the issue, that closing of this shutter is not working. As usual, I am still not advanced to check properly the root cause. I can just say that the setting is the same to 3x other shutters in the room - but those have a different orientation and therefore a different setting for azimuth. Its again a shelly device that is triggered here.
Various Traces for this evening:
Configuration:
id: '1710705833036'
alias: CCA-2-Beschattung_Seite Zimmermann_Schlafzimmer
description: erstellt 22.02.24
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
shading_forecast_sensor: weather.openweathermap
blind: cover.s25_og_schlazi1_z_16
auto_options:
- auto_shading_enabled
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
time_control: time_control_input
cover_status_options: cover_helper_enabled
drive_time: 60
time_up_early: '08:00:00'
time_up_early_non_workday: '10:00:00'
time_up_late: '08:30:00'
time_up_late_non_workday: '10:00:00'
close_position: 0
time_down_late: '23:00:00'
time_down_late_non_workday: '23:00:00'
workday_sensor: binary_sensor.workday_sensor
position_tolerance: 10
shading_position: 20
shading_azimuth_start: 230
shading_azimuth_end: 365
shading_temperatur_sensor1: sensor.openweathermap_temperature
shading_min_temperatur1: 18
shading_weather_conditions:
- sunny
- partlycloudy
- clear
check_config: true
auto_global_condition: []
shading_elevation_min: 0
shading_forecast_temp: 21
sun_elevation_up: -1.6
sun_elevation_down: -2.5
cover_status_helper: input_text.rolladen_status_inputhelper_seite_zimmermann_schlafzimmer
individual_config:
- prevent_shading_end_if_closed
- allow_shading_multiple_times
- prevent_higher_position_closing
ignore_after_manual_config:
- ignore_opening_after_manual
As a reference another shutter in the same room, that seems to work flawless:
id: '1710705573880'
alias: CCA-2-Beschattung_Seite VDB_Schlafzimmer
description: erstellt 22.02.24
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
shading_forecast_sensor: weather.openweathermap
blind: cover.s25_og_schlazi4_vdb_19
auto_options:
- auto_shading_enabled
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
time_control: time_control_input
cover_status_options: cover_helper_enabled
drive_time: 60
time_up_early: '08:00:00'
time_up_early_non_workday: '10:00:00'
time_up_late: '08:30:00'
time_up_late_non_workday: '10:00:00'
close_position: 0
time_down_late: '23:00:00'
time_down_late_non_workday: '23:00:00'
workday_sensor: binary_sensor.workday_sensor
position_tolerance: 1
shading_position: 15
shading_azimuth_start: 50
shading_azimuth_end: 230
shading_temperatur_sensor1: sensor.openweathermap_temperature
shading_min_temperatur1: 14
shading_weather_conditions:
- sunny
- partlycloudy
- clear
- cloudy
check_config: true
auto_global_condition: []
shading_elevation_min: 0
shading_forecast_temp: 19
sun_elevation_up: -1.5
sun_elevation_down: -2.6
cover_status_helper: input_text.rolladen_status_inputhelper_vdb_schlafzimmer
individual_config:
- allow_shading_multiple_times
- prevent_shading_end_if_closed
- prevent_higher_position_closing
ignore_after_manual_config:
- ignore_opening_after_manual
@Herr.Vorragend Is it possible to keep the shutters in the shading position after the first shading movement? Which option do I have to set for this?
Hi,
how can I set the config so that the blinds open in the morning even though the window is tilted or open?
Had the surprise today, that a shutter in the children room was opened automatically although I think it was setup quit restrictive to not have any surprises / unwanted openings. Hope documention below is good enough to enable @Herr.Vorragend for checking, if he has time.
Configuration:
Configuration:
id: '1710705647112'
alias: CCA-2-Beschattung_Seite VDB_Kind
description: erstellt 22.02.24
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
shading_forecast_sensor: weather.openweathermap
blind: cover.s25_og_kind2_vdb_15
auto_options:
- auto_shading_enabled
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
time_control: time_control_input
cover_status_options: cover_helper_enabled
drive_time: 60
time_up_early: '09:00:00'
time_up_early_non_workday: '09:30:00'
time_up_late: '10:00:00'
time_up_late_non_workday: '10:00:00'
close_position: 0
time_down_late: '23:00:00'
time_down_late_non_workday: '23:00:00'
workday_sensor: binary_sensor.workday_sensor
position_tolerance: 1
shading_position: 17
shading_azimuth_start: 50
shading_azimuth_end: 230
shading_temperatur_sensor1: sensor.openweathermap_temperature
shading_min_temperatur1: 15
shading_weather_conditions:
- sunny
- partlycloudy
- clear
- cloudy
check_config: true
auto_global_condition:
- condition: state
entity_id: input_boolean.automatisierung_rollade_standard_automodus
state: 'on'
shading_elevation_min: 0
shading_forecast_temp: 21
sun_elevation_up: -1.5
sun_elevation_down: -2.6
ignore_after_manual_config:
- ignore_opening_after_manual
- ignore_shading_after_manual
individual_config:
- prevent_shading_end_if_closed
- prevent_higher_position_shading_end
- prevent_higher_position_closing
- allow_shading_multiple_times
cover_status_helper: input_text.rolladen_status_inputhelper_vdb_kind
Trace:
Value Input Helper:
{"open":{"a":true,"t":1714326056},"close":{"a":false,"t":1714300356},"ventilate":{"a":false,"t":0},"shading":{"a":false,"t":0},"locked":{"a":false,"t":0},"manual":{"a":false,"t":1714313269},"p":0,"v":4,"t":1714326056}
The traces are great. Thank you very much. It’s been a few days and you probably can’t follow it directly. But in the file ‘trace automation.cca_2_beschattung_seite_zimmermann_schlafzimmer 2024-04-25T19_01_44.798536+00_00.json’ I went through the entries line by line and the command to close the blind was executed in line 954.
The trace that immediately follows (file: ‘trace automation.cca_2_beschattung_seite_zimmermann_schlafzimmer 2024-04-25T19_03_02.114357+00_00.json’) is incomplete. Almost everything is missing here. But I can see from the trigger that a position change has been detected. So the roller blind has also reacted.
The traces are truncated here:
‘friendly_name’: ‘S25-OG-SCHLAZI1-Z_
Do you have any strange characters in the friendly name?
1 Like
Hi, what do you mean by that? So you don’t want to end the shading? Just like me? 
Then you could, for example, set the ‘Shading Brightness End Value’ to a very small value. And if you like, also increase the ‘Waiting Time For Shading End’.
Or you could set ‘Additional Condition For Disabling Sun Shading’ with any condition to true.
Is the roller blind then also in the ventilation position?
For example, triggered by the ventilation mode via a contact? Then it should already work like this.
The roller blind also opens in the morning when the roller blind is in the ventilation position.
I would need your configuration for more details.
Somehow I see several problems here.
First of all: I have also found a bug in the blueprint, which has already been fixed locally and will be published with the next update. It seems that ignoring after manual roller blind movements is not being honoured correctly. And you seem to be the first to have activated and tested this feature.
But then I don’t understand a few points about you.
- open_position = 100
- close_position = 0
- is_cover_open = true (The helper says that the roller blind is open).
- BUT: Your current_position is 0.
Why does your cover status helper have the wrong content?
The variable is_cover_manual is set to the value true. And has the same timestamp ( Sunday, 28 April 2024 16:07:49 GMT+02:00 DST) as is_cover_open (also set to true).
This means that manual roller blind movements are generally recognised
The timestamp in the Cover Status Helper for the close status is: Sunday, 28 April 2024 12:32:36 GMT+02:00 DST
I assume that the roller blind was closed again after Sunday, 28 April 2024 16:07:49 GMT+02:00 DST. And this status change was not recognised. But why?
Can you show me the history of the roller blind device?
And maybe even the history of the Helper?
If you like, you can also write to me via chat.
1 Like
Yes, I would not like to stop shading. I use a sun temperature for shading and do not want to stop shading if the temperature falls below this value again. Is it possible to install a lower threshold value for shading by temperature (as with brightness)?
I can’t introduce a lower threshold. It will be so complex if I have to take everything into account.
Do it via the additional conditions. If necessary, a template condition with the content “false”. (Untested)
auto_shading_end_condition:
- condition: template
value_template: "false"
In the meanwhile this shutter was not highlighting any issues anymore as most of the other shutters (ca 22x) in the house (thanks to your automatiion) quite well ! Yesterday and today just another shutter is affected, in the bathroom. Maybe there is some rare scenario / little bug impacting from time to time, but I cannot find a pattern. And I do not like to waste your time on searching for little issues. As said, 99% of the time all runs fine.
But anyhow, just for documentation my latest case:
Closing happens
Trace #1 - 20:53 [last trace before expected closing 15 Min later]: WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
Trace #2 - 21:08 [the closing by sun-elevation]: WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
Configuration:
id: '1710705621225'
alias: CCA-2-Beschattung_Seite VDB_Bad
description: erstellt 22.02.24
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
shading_forecast_sensor: weather.openweathermap
blind: cover.s25_og_bad_20
auto_options:
- auto_shading_enabled
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
time_control: time_control_input
cover_status_options: cover_helper_enabled
drive_time: 60
time_up_early: '07:00:00'
time_up_early_non_workday: '07:30:00'
time_up_late: '08:30:00'
time_up_late_non_workday: '08:30:00'
close_position: 10
time_down_late: '23:00:00'
time_down_late_non_workday: '23:00:00'
workday_sensor: binary_sensor.workday_sensor
position_tolerance: 1
shading_position: 25
shading_azimuth_start: 50
shading_azimuth_end: 230
shading_temperatur_sensor1: sensor.openweathermap_temperature
shading_min_temperatur1: 14
shading_weather_conditions:
- sunny
- partlycloudy
- clear
- cloudy
check_config: true
auto_global_condition:
- condition: state
entity_id: input_boolean.automatisierung_rollade_standard_automodus
state: 'on'
shading_elevation_min: 0
shading_forecast_temp: 19
sun_elevation_up: -1.5
sun_elevation_down: -2.6
cover_status_helper: input_text.rolladen_status_inputhelper_vdb_bad
individual_config:
- allow_shading_multiple_times
- prevent_shading_end_if_closed
A random other shutter was closed with lowered sun-elevation at around 21:08:
While the shutter in the bathroom has not received the closing trigger acc to the Home assistant log:
Here just snippets from April, 28nd. To mention - different then usually in my case, this shutter is closed manually in the evening before the others as its the sleeping room of my child. Happened at 18:08 at this day and at 19:40 it was opened by automation.
I dont have any clue, but I could assume that on the shading something impacted here. It was not a warm day and shading isnt here really active at these low temparatures during April - just fyi.
The input helper changes during this day:
The log on this shutter during the day:
