Had randomly another issue where an error came up and shutter was not closed by sun elevation. Just report it here for the sake of bugfixing. The automation is just awesome!
I have this automation running, works fine for my shutters at my office, but my 14y and 17y old girls are not happy with it for the bedrooms. is there any change i can bypass the automation and set a time helper that opens the blinds on a given time, without the settings of CCA?
I was looking at this, but it has to be a binary sensor. I know how to make a input_boolean, but don’t know how to make a binary senor?
I made an input_boolean switch, but can not link this into the sensor entity.
At weekends and during vacations, the roller blind closes automatically but only opens manually. ← That’s how I implemented it.
You just need to have an integrated calendar including vacations.
Or
You use the resident mode. For example with a Zigbee switch or presence detector.
At weekends and during vacations, the roller blind closes automatically but only opens manually. ← That’s how I implemented it.
You just need to have an integrated calendar including vacations.
that is what i want to do. how did u do that? i make a calendar (helper schedule)? or put something in my google calendar?
The vacations are saved in my Google calendar, the calendar is linked to HA. As soon as the word “vacation” appears, I trigger a switch helper with this blueprint (📆 Calendar Notifications & Actions - #3 by Blacky).
I think that will be the solution to your problem. If your daughters also like to sleep in at the weekend, you could create a helper group with weekends and vacations. Just create a weekday sensor that only recognizes the weekends
Hi! I just started with the config, but came to a problem (for me). It is the “Contact Sensor Entity” wich won’t work for me, cause I am using Homematic three-state-sensors [open/closed/tilted] for the balkony-doors (and even some windows).
Could it be an option for an enhancement to define a “contact sensor” or alternativly a “three-state-sensor”?
At the moment, my own automation works like:
if night-mode=true (= helper) and sensor switched from * to tilted then tilt-position
if night-mode=true (= helper) ans sensor switched from * to open then then open-position
if night-mode=true (= helper) and sensor switched from * to closed then closed-position
In this case the helper is needed to avoid drive-up / drive-down during daytime. I could do it without helper (reading current LUX), but this idea came later and -you could know- sometimes I’m a little bit to lazy^^ or “never change a running system”^^
HI guys,
at first…amazing blueprint :)…i use it to close/open my covers in the evening/morning in winter with sun elevation and time. But now in spring and later in autum it could be usefull that the covers should not close, depending on the forcast temperature!
For shading its possible to set the forcast temperatur to close the covers, if temp is higher than the given temp. But thats usesless for me i think!
So is it possible to implement an option to close the cover if the temp forcast in the night is below a given value (for example 7°C) ? Or is it still implimented and i oversee that feature?
thx for helping
2024.04.05-01:
- Update: Forecast Temperature below 0 possible
- Delay lines minimally changed
- Added: Allow shading to activate multiple times a day #44
- Fixed: Ventilation is usually activated too often.
Hello. I keep getting an ‘entity does not support this service’ error on one of my shades. It opens them fine in the morning (all SmartWings via zigbee) and around 9AM one shade (out of 4) goes down to 25%. They do not close at night. Here’s an error and the trace. Love the automation, but it’s hard for me to find the error.
Hi, I have installed the latest version of the Blueprint. Unfortunately the shading function does not work, though all requirements are met. Here is the latest trace