It was quite a lot of searching, but it was worth it. With your error, you have found a fundamental flaw in the system. I am currently fixing this in all branches and will upload the fix for the master branch shortly.
1 Like
Another update:
2024.02.28-02:
- Fixed: Float values were incorrectly compared as integers. This fixed problems with sun-elevation and brightness.
2 Likes
You are my Hero! 
Btw: How am I able to Update the automations ? 
This is from actual Version 2024.02.28-02
config:
alias: Jalousie Büro Automation
description: “”
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.jalousien_buro_wz_esszimmer_kuche_jalousie_buro
auto_options:
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
drive_time: 56
open_position: 0
time_up_early: “06:30:00”
time_up_late_non_workday: “08:30:00”
auto_global_condition:
- condition: state
entity_id: binary_sensor.raspberrymatic_sv_alarmzone_1
state: “off”
close_tilt_position: 0
cover_status_options: cover_helper_enabled
time_down_late: “23:00:00”
time_down_late_non_workday: “23:00:00”
brightness_time_duration: 30
sun_elevation_down: -3.5
workday_sensor: binary_sensor.workday_sensor
shading_position: 0
shading_tilt_position: 0
shading_brightness_sensor: sensor.wetterstation_brightness
shading_sun_brightness_start: 210
shading_sun_brightness_end: 190
shading_azimuth_end: 150
shading_elevation_max: 40
shading_temperatur_sensor1: sensor.wetterstation_temperature
shading_min_temperatur1: 20
shading_forecast_temp: 18
drive_delay_random: 0
drive_delay_fix: 2
auto_down_condition:
time_down_early: “16:00:00”
time_down_early_non_workday: “16:00:00”
close_position: 0
cover_status_helper: input_text.jalousie_status_helfer_buro
auto_up_force: binary_sensor.raspberrymatic_sv_alarmzone_1
open_tilt_position: 50
trace:
open_position: 0
open_tilt_position: 0
close_position: 0
close_tilt_position: 0
You cannot use the same height in open and close position.
Got it. Will test further tomorrow.
Thanks a lot!
Hello, after installing and setting up the blueprint, the blinds when instructed will only make a small up and down movement but will not retract (pull out) completely. Does anyone know what the problem could be? It seems like it changed its mind and came back 
alias: CCA
description: ""
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.zaluzie_pracovna
open_position: 100
open_tilt_position: 50
time_up_late: "08:00:00"
auto_up_condition: []
auto_down_condition: []
close_tilt_position: 10
auto_down_force: input_boolean.vytahnuti_zaluzie
auto_options:
- auto_down_enabled
- auto_up_enabled
auto_down_action: []
close_position: 10
check_config_debuglevel: ""
sun_time_duration: 0
shading_weather_conditions: []
time_down_late: "17:23:00"
No closing this evening with actual version? General bug?
I am not aware of anything. Trace?
I can’t imagine that this behavior is caused by the blueprint. If you like, you can send me your trace.
Mine also not closed today with the actual version.
Opened this morning as it should.
Trace:
Config:
id: '1708945967351'
alias: Jalousie Büro Automation
description: ''
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.jalousien_buro_wz_esszimmer_kuche_jalousie_buro
auto_options:
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
drive_time: 56
open_position: 2
time_up_early: '06:30:00'
time_up_late_non_workday: '08:30:00'
auto_global_condition:
- condition: state
entity_id: binary_sensor.raspberrymatic_sv_alarmzone_1
state: 'off'
close_tilt_position: 0
cover_status_options: cover_helper_enabled
time_down_late: '23:00:00'
time_down_late_non_workday: '23:00:00'
brightness_time_duration: 30
sun_elevation_down: -3.5
workday_sensor: binary_sensor.workday_sensor
shading_position: 1
shading_tilt_position: 1
shading_brightness_sensor: sensor.wetterstation_brightness
shading_sun_brightness_start: 210
shading_sun_brightness_end: 190
shading_azimuth_end: 150
shading_elevation_max: 40
shading_temperatur_sensor1: sensor.wetterstation_temperature
shading_min_temperatur1: 20
shading_forecast_temp: 18
drive_delay_random: 0
drive_delay_fix: 2
auto_down_condition: []
time_down_early: '16:00:00'
time_down_early_non_workday: '16:00:00'
close_position: 0
cover_status_helper: input_text.jalousie_status_helfer_buro
auto_up_force: binary_sensor.raspberrymatic_sv_alarmzone_1
open_tilt_position: 50
time_up_late: '08:00:00'
ventilate_position: 1
ventilate_tilt_position: 30
@ Jack77777777:
What kind of device is it that the positions only differ by two values?
Are you only using the tilt of the blind?
"open_position": 2,
"close_position": 0,
I saw here straight away that your blind was already closed at 12:10. This means that there has already been a closing process today and no further drives will be made.
Just as an aside: It is possible to increase the number of traces by adding the following lines to the YAML code in the respective automation.
trace:
stored_traces: 20
That would be very kind of you 
Here’s the trace.
Now I realized something… I am using Tahoma Switch (Somfy) and the movement which is doing is same or very similar as command “Identify”
Mine (Shelly) were closed properly with yesterdays update. Many thanks!
I can’t do anything with the trace. There was no reaction to the change in position. You probably have to go back a little further.
That makes me happy. At least there’s a little light at the end of the tunnel. 
1 Like
In the second trace, your are forcing down with the following boolean:
"auto_down_force":
"input_boolean.vytahnuti_zaluzie",
But your config looks quite good. It should work with that.