Please create an issue. Just copy&paste your posts to Issues · hvorragend/ha-blueprints · GitHub. Thank you.
New update
2024.02.01-01:
* Minor Layout changes
* Removed commented out code
* Fixed closing-condition
* Fixed cover status helper initialisation and still make the first cover drive possible
I have done that for you: Individual opening and closing times · Issue #6 · hvorragend/ha-blueprints · GitHub
Please take a look in the issue: Adaptive Cover? · Issue #3 · hvorragend/ha-blueprints · GitHub
But I am not sure if I really will do this.
Sorry, I haven’t read your reply before I added a new issue #9.
Maybe you can close #6 as a duplicate?
New update:
BREAKING CHANGE:
Please reconfigure/rename the variables close_position and shading_position in your blueprint config.
2024.02.02-01:
- BREAKING CHANGE: Please reconfigure/rename the variables close_position and shading_position in your blueprint config
Old: closed_position - New: close_position
Old: shading_cover_position - New: shading_position
- Added tilt positions for open, close and ventilation
Hi,
I was wondering if there might be an option for a „drive down up late on non-workdays“
Example: kids have to get up latest 7am on workdays but on weekend 8:30 is ok.
Maybe I’m thinking wrong and should adjust sun elevation instead!?
Hi, automation with external helper seems to function not as intended.
I’ve set up an helper and moved a cover manually (manual: on in text_input). This evening the cover didn’t close automatically.
Which version are you using?
Could you please show me the history of the helper?
Version: 2024.02.03-01
id: '1706541385621'
alias: 'CCA: Büro'
description: ''
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.beschattung_buro_empfanger
auto_options:
- auto_up_enabled
- auto_down_enabled
- auto_brightness_enabled
- auto_ventilate_enabled
- auto_shading_enabled
time_up_early: '07:30:00'
time_up_early_non_workday: '08:00:00'
time_up_late: '08:30:00'
default_brightness_sensor: sensor.illumination_average
brightness_up: 80
brightness_down: 20
brightness_time_duration: 60
workday_sensor: binary_sensor.workday_sensor
contact_cover_place: door
contact_sensor: binary_sensor.fenstergriff_buro_offen
ventilate_position: 89
drive_delay_random: 5
position_tolerance: 1
shading_temperatur_sensor1: sensor.temperatursensor_temperatur
shading_min_temperatur1: 24
shading_temperatur_sensor2: sensor.hue_motion_buro_temperature
shading_min_temperatur2: 24
shading_forecast_temp: 24
sun_time_duration: 60
shading_azimuth_start: 185
shading_azimuth_end: 315
shading_elevation_min: 7
shading_sun_brightness_start: 10000
shading_sun_brightness_end: 5000
drive_delay_fix: 0
check_config: false
check_config_debuglevel: ''
auto_shading_end_condition:
- condition: state
entity_id: input_boolean.automatik_beschattung_nach_sonnenstand
state: 'on'
auto_shading_start_condition:
- condition: state
entity_id: input_boolean.automatik_beschattung_nach_sonnenstand
state: 'on'
close_position: 0
shading_position: 45
cover_status_options: cover_helper_enabled
cover_status_helper: input_text.cover_status_helper_buro
Good morning, i have got the same probleme like @crandler . Last night I opened a blind to 20% (after all blindes were closed) to find out if I had the same problem and this morning the blind didn’t open. The Logbook says, it opened, but it won’t open.
Using the Version 2024.02.03-01
Isn’t that exactly how it should be?
The status is not known, so it is not driven. It is only opened if the status is “closed”. And vice versa.
But I don’t think that’s good either. Let’s see if we can change that in the future.
I just don’t understand how the logbook should say anything else. Then I need to know whether the automation has started the blinds or not.
You shut down manually at 17:40, didn’t you?
in a different shutter-automation-solution it was implemented like this:
shutter status unknown (manual interaction) > automatic shading stops, but auto-down and auto-up keeps working (and then you have a known state again)
for me this bahaviour made sense…
yes, bc it didn’t close as per definition:
If you want to be able to intervene manually and the automation should execute the next movement as usual, a helper is required.
Maybe I misunderstood something again. I thought that if I use a helper, I can put the blind in any position and by using the helper the blind will still open or close
How about following idea:
Helper variable keeps last state and timestamp of CCA and timestamp of manual movement.
You add a field for “ignore for time x after manual movement”. One can enter e.g. 3 hours to temporarily ignore CCA movements. After this period, last state of CCA is restored or next step is calculated to prevent first up, then down.
If too complicated, a selectable force up/force down with unknown state would be helpful.
Please create an issue.
1 Like
To be honest, I don’t like it at all when the blinds are suddenly moved after x hours. I didn’t like that in the FHEM module AutoShuttersControl (ASC) either. I always had the problem that I wondered about spontaneous movements. 
But I have an idea. I’m working on something. I also want the roller blinds to be operated only once. I’ll check it in at a GitHub branch first.
Originally, the behavior was planned differently. That was also the reason why I didn’t go Eimeel’s way and introduced the helpers for this purpose.
A few days ago, I adapted the behavior of the helpers to the other procedure. Otherwise manual overrides would have been overwritten again and again.
1 Like
I just want to control my blinds via sunrise and sunset but it doesn’t work. I use sun.sun and it also says 7:52h. But they go up at 8 o’clock sharp. what could be the reason? 
Couldn’t someone here who understands everything make a tutorial video about it?