Hi,
I do get the same error as DieBreuers:
WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: ‘dict object’ has no attribute ‘id’ when rendering ‘{{ trigger.id | regex_match(’^(t_shading_start|t_open_1|t_open_3)‘) }}’
Thanks for the great work on this automation blueprint!
I’m trying to use it with a setup where I don’t have a single cover entity, but instead two separate entities – one for position (number.cover_position) and one for tilt/lamella angle (number.cover_tilt). Since the trigger in the blueprint expects a single cover entity, I’m not sure how to make this compatible with my configuration.
Do you have any recommendation for handling this type of setup?
Thanks for the quick analysis. I thought I can trigger the automation manually to check if it is working.
As far understood I really have to wait until the external triggers are triggered.
I was confused of the following text: Check Configuration
With this boolean, you can enable or disable the basic plausibility check for the configuration. The check only takes place if the automation is executed manually.
the automation was disabled in the winter and now nothing works.
I need only sun shading, so I read the thread and tried different setups. I think my current setup is very close to working but it isn’t.
Can someone take a look at the traces and the configuration?
Thanks!
Config:
Oh, I just realized that the configuration of your position values is not correct. As described in the blueprint, each position may only occur once. Ventilation is at 100% for you. And Open as well.
On the one hand, you have already received an answer. But you need a trigger for that.
So you want two different temperature triggers? My problem is that I can’t fulfill every individual wish. Then the blueprint will burst at some point. And I also have to be able to provide the support for it.
That’s why I’ve added the additional conditions and the force actions. And if the customer user triggers in HA can be used in blueprints at some point, then almost anything is possible.
If necessary, you would just have to fork the blueprint.
Hi, thanks for the answer.
My requirements are very simple. I just want the shading to start on a simple trigger like Sun Azimuth, sun elevation, Sun Lux and temperature.
For two Windows, which are doors, like “Terrasse” and “Küche”, I also need a lockout Protection, thats all.
What do I need to set to simply Achieve this? Maybe I have too much setup for my simple requirements.
Hi there. I’m completely lost. I have shades that I imported from KNX to HA, and I’m trying to move my automatic shading from KNX to HA. I’m quite novice, but in general not to bad with technical stuff.
This automation brought me to the brink of despair. The shades simply never do what I want. One day they darken in the morning, eventhough regarding azimuth they should not, after redoing everything and trying again they are not shading at all. Today, a day with 25°. Could anyone somehow help me?
Hi, for some time im trying to get the blue print to work, but they don’t get the blinds to move… Maybe I’ve missed something.
I’ve got Aquara blind motors, and trying to get one moving at the moment.
One thing I cannot find if they have decent position entity. But still I can move them properly in HA.
I also have the position helper installed. And only looking for the shading function to work with my light sensor which does trigger the automation.
All three traces have absolutely nothing to do with each other.
Can we perhaps tackle the problems individually and specifically?
Example:
What should happen in the morning? And what happens in reality?
The temperature has triggered. Trigger: t_shading_start_pending_4. But the sun was not yet in the correct azimuth. So everything is fine.
Trace 2 belongs to a manual position change. Trigger: t_manual_1. Either you controlled manually or it is a trace for an execution that took place shortly before by CCA. Then I need the trace before that.
This trace belongs to the trigger t_shading_end_pending_5 and wants to end a shading. It was aborted because no shading position was recognized. So quite normal.