Would you like to transfer it to GitHub? Or do you not have an account? Then I’ll do it.
I’ve had similar thoughts myself. There might be something to it. Thank you.
Would you like to transfer it to GitHub? Or do you not have an account? Then I’ll do it.
I’ve had similar thoughts myself. There might be something to it. Thank you.
Thanks for the feedback. I guess it’s a bit of both, translation and not knowing why this works with 6 other shutters (I copied them and basically have the same settings there as I never touched them after copying) and only this one does drop me that message. I will check the posts again and see if I can make sense of it. Thanks a lot for taking the time to get back to me about this and sorry to have two messages, the second was to indicate that I changed something what I found different in the 7th shutter but that left me with the same result. ![]()
Since I run this automation with a rooftop window shutter, I intended to have the shading position equal to the fully closed position. Mostly to prevent any heating up if the sun directly hits the window. I have the same settings for a wintergarden shutter which is the confusing part: Shading the wintergarden to 0% open state works, the rooftop window shutter drops that message. ![]()
90 seconds is enough. My problem seems to be that manual control is not resetting for some reason. I don’t understand your first sentence, care to elaborate?
added a Ticket in Github - https://github.com/hvorragend/ha-blueprints/issues/280. Maybe easier.
@Herr.Vorragend do you may have the posibiliy to implement this fix for the Awning function?
I have created the issue on Github, I hope it is correct as I did it
Good that you were able to take a little break @Herr.Vorragend
Nevertheless we are happy to see you here again ![]()
Hi, I’ve been using the module for several months now and I’ve noticed something. I have 18 roller shutters and have configured them all individually. When the roller shutters are operated in the morning and evening according to twilight, they all operate simultaneously. During the day, when the temperature exceeds a certain value, for example, they should all move to the shading height. However, they never do this simultaneously. Instead, some of the roller shutters move first, followed by the others after a delay. The settings for shading are identical. Can anyone explain this? This behavior is unpleasant.
I’ve been using this blueprint for a while, and it’s great!
I have covers that are in front of windows opening vertically, and I’m wondering if there’s a way to prevent the cover from closing all the way, depending if the window is open or not.
I tried to do this via the ventilation option, but that only triggers if a window is opened. Am I missing a setting to do this or is this something I will manually have to setup?
Is anybody running this blueprint with the old Homematic device?
Is there anything to be aware of or are there any tips?
I’m switching my hole setup from Fhem to ha now, so I need to move a lot of device from the old system to the new system.
So I want to avoid bigger problem during the migration.
any advise is welcome.
Cheers Robert
I finished the Migration without any big Problem.
I automated also some roof shutters from the company velux.
Is there a way to block the cover when a special temperature is reached?
I don’t want to move the cover when they are blocked with ice or snow.
Cheers Robert
i think you can use the “additional conditions” for that!
Today none of my covers opened (except one).
I recently updated them all to not shadow if the temperature is not high enough, as we are entering winter here in my area.
This is the config of one of the automations that didn’t open the cover:
- id: '1729493001458'
alias: Persiana - Ventanal escaleras
description: ''
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.ventanal_escaleras
ventilate_tilt_position: 31
auto_options:
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
- auto_shading_enabled
time_up_late: 09:45:00
time_up_late_non_workday: '11:00:00'
sun_elevation_down: -5.5
time_up_early_non_workday: '10:30:00'
resident_sensor: input_boolean.dormir_largo
workday_sensor: binary_sensor.workday_sensor
time_up_early: 09:00:00
cover_status_helper: input_text.helper_cover_ventanal_escaleras
cover_status_options: cover_helper_enabled
shading_forecast_sensor: weather.casa
ignore_after_manual_config:
- ignore_opening_after_manual
reset_override_config: reset_time
check_config: true
check_config_debuglevel: debug
shading_position: 32
shading_elevation_min: 15
shading_forecast_type: hourly
shading_azimuth_start: 80
shading_azimuth_end: 180
shading_elevation_max: 70
shading_forecast_temp: 24
And this is the only one that opened:
alias: Persiana - dormitorio P1 ventana 1
description: ""
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
blind: cover.ventana_1_3
auto_options:
- auto_up_enabled
- auto_down_enabled
- auto_sun_enabled
- auto_shading_enabled
check_config: false
time_up_late_non_workday: "12:00:00"
time_up_early_non_workday: "11:00:00"
sun_time_duration: 309
sun_elevation_up: 0
sun_elevation_down: 0.9
time_up_late: "11:30:00"
workday_sensor: binary_sensor.workday_sensor
time_up_early: "09:00:00"
resident_sensor: input_boolean.invitados
cover_status_options: cover_helper_enabled
cover_status_helper: input_text.helper_cover_guest_room
ignore_after_manual_config:
- ignore_opening_after_manual
reset_override_config: reset_time
shading_min_temperatur1: 24
shading_forecast_sensor: weather.casa
shading_temperatur_sensor1: sensor.mj_dorm_temp
shading_position: 28
shading_forecast_type: hourly
Here is the trace of one of the failing ones: PrivateBin
Ok, someone accidentally activated the input boolean that makes the automation not open automatically. My bad
Something that I don’t understand what happens is that the covers get closed in the morning if I open them during night.
Sometimes I want my office to stay as cold as possible, so I open the windows during night, and I also open the covers.
For some reason, then about 7:30 am this automation closes it, and I have no idea of why. There is nothing set to that time, and I would prefer to keep them open.
Thanks for your tip.
But I’m new in home assistant.
I found these additional conditions but it isn’t as easy as I thought.
Did you have any advice for me how to deal with it?
Cheers Robert
the best would be to have an outdoor temperature sensor. than you can say, if the temp of the external sensor is below x degree stop the automation to move the shutter! If you have no no external sensor it would be possible to add a weather integration and use the temperature from there, but this could be inaccurate!
I allready for an Homematic Outdoor Temperaturen Sensor and also an Netatmo.
Netatmo isn’t working as good as it suppose to. From time to time the base is losing the Wi-Fi connection.
And also the direct HomeKit intergration is loosing the connectivity.
So I would prefer the Homematic temp sensor.
Would you be so kind to explain me how to setup the addional condition.
I all read tried into set it up. But it looks it was not working.
Cheers Robert
Edit:
Screenshot added
@Herr.Vorragend: could you please give feedback on this inquiry ![]()
BR
Philipp