Take a look here.
And this is also available for Close and Ventilate.
My shutters (shelly) were not closed during todays sunset. This happens since the latest update.
#1 WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
#2 WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
I can’t do anything with the traces. The trigger is missing in one of them. Nothing recognizable. And in the other, only the detection of the drice is processed.
Question in passing:
Is this correct?
"sun_elevation_up": -1.5,
"sun_elevation_down": -2.6,
And recommendation:
Do not use such a large group.
1 Like
Will consider your recommendation. For shading i established one per shutter, but just for simple opening / closing i was going for a group, which is a bit easier to maintain sometimes and was also working fine so far.
Elevation setting is correct and slightly offseted vs sunset / sunrise.
I adressed this issue some weeks before in my setup and you needed to adjust some integer-issue. Not sore if this came up with your last bigger rework.
First of all, thank you for the blueprint. I’m not sure whether my plan will work with this blueprint.
I use the height of the sun, the brightness, the sensor and the times.
Until now, I had solved it in such a way that the shutters are only opened when a person enters a certain room and the brightness is right. If I have seen this correctly in the blueprint, the automation only triggers as soon as brightness, sun height and time apply.
Is there also a way to store an entity here and only when this is on are all conditions checked again to open the shutters?
Couldn’t this be implemented using the additional conditions? However, the problem is that you then have to wait for another trigger or use the force function. Because conditions cannot trigger in HA.
On the one hand, I think your construct with the different groups and automations is quite clever.
But on the other hand, I don’t know whether this always works with CCA. I have never considered this. But I also ask myself whether I want that at all.
To find out, you could use one automation for a roller blind with all your features for testing.
btw: Float values are now possible everywhere.
1 Like
Thx for reply!!
Ok maybes with the resident mode?
If this Boolean is true the covers will open but only if the state of the Sun and the brightness is true.
Force mode ignores all …
Is that right?
Greetz …
My shutter has no position attribute, it is a fibaro module and don’t see this. Alhough it shows the real position but not as an attribute. So this isn’t working for me… how can I adapt?
You must perform the calibration run in ZwaveJS once.
Calibration is done in the homecenter of Fibaro… these are not directly integrated into HA.
Then you need to find out more about this.
I know that all Fibaro actuators (FGRM-222 and FGR-223) normally send the position data. As a Fibaro command and also as a Zwave command.
However, it is very important that you execute a calibration beforehand.
Unfortunately, I can’t answer why the Homecenter can’t or doesn’t do this.
1 Like
Stupid question: Have you ever looked at the attributes? Not that there’s anything there after all.
Wow, great work. Easy setup and it just works.
Allthough I would like it for shading in the wintertime as well. If I use the wether forecast the temperature seems to be considered which I do not need. To set it to a low level It needs to accept values below 0°C. May I ask for an option to set the Forecast Temperatur Value below 0?
1 Like
Hi, I can also allow negative values. That’s not a problem. I will add it.
But regardless of that, you can also just delete the forecast sensor. This comparison is optional.
1 Like
How should I update the blueprint, if there is a newer version available?
For me not explainable / randomly two out of 20 Covers were opened some minutes ago. Not eure what triggered them.
Trace: WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
Automation as Yaml:
alias: CCA-2-Beschattung_Garten_Schiessscharte links
description: erstellt 22.02.24
use_blueprint:
path: hvorragend/cover_control_automation.yaml
input:
shading_forecast_sensor: weather.openweathermap
blind: cover.s25_eg_schiesssch2_li_garten_2024
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: 15
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: 30
shading_azimuth_end: 140
shading_temperatur_sensor1: sensor.openweathermap_temperature
shading_min_temperatur1: 12
shading_weather_conditions:
- sunny
- partlycloudy
- clear
check_config: true
shading_forecast_temp: 21
auto_global_condition:
- condition: state
entity_id: input_boolean.automatisierung_rollade_sonnenschutz
state: "on"
shading_elevation_min: 0
brightness_down: 0
sun_elevation_up: -1.5
sun_elevation_down: -2.6
cover_status_helper: input_text.rolladen_status_inputhelper_garten_schiessscharte_links
Do you see the problem?
"close_position": 15,
"shading_position": 20,
"position_tolerance": 10,
I haven’t looked any deeper. But that should be enough.
Due to the tolerance value, both position specifications are almost identical. And the end of the shading has been triggered.
1 Like
Thank you @Herr.Vorragend Have fixed the configuration. Was thinking its tolerance in percentage but it is the number ?
The shutters were fully opened. Not yet understand, what lead to this, but simply have fixed the tolerance and lets see what will happen.
Many thanks! Still astonished by this tool 