Helper Length
Or you can delete the helper and create a new one. After all, you have nothing to lose.
Hello Herr.Vorragend,
Yesterday evening the blind was closed correctly as configured with the trigger ‘Sun Elevation < -5°’.
This morning there were 3 triggers to open the blind:
- Time up early workday at 6:10 am
- Sun Elevation < 1° at 6:38 am
- Time up late workday at 7:10 am
Unfortunately, it did not go up at any of them.
The blind should therefore have been raised at the sun elevation trigger.
Unfortunately, the trace is over 200.000 lines long and I can’t post it here. How can I make it accessible to you?
You have to use a file uploader. That’s how the others do it here in the thread.
Or you can create a ticket on GitHub. You can upload files there.
What does your config look like?
Maybe I can already see something?
The uploader does not accept .json or .zip files. Am I doing something wrong?
The helper setup is strange - I choose input_helper.text, and my setup then looks like that, no text length adjustable:
I can also see the log errors in the protocol:
Invalid value: {"open":{"a":0,"t":0},"close":{"a":0,"t":0},"shading":{"a":0,"t":0,"p":0,"q":0},"vpart":{"a":0,"t":0},"vfull":{"a":0,"t":0},"manual":{"a":0,"t":0},"v":5,"t":1744891721} (length range 0 - 100)
When I go to the settings of the helper, it looks like that:
Also here, no length adjustable
I have the feeling I am missing something silly…system is up to date on 2025.4.2
Please activate the advanced mode on your user profile. Then you will also see the option to change the text length.
1 Like
Unfortunately I can’t get it to work.
I only want the following:
sensor.gw1100a_solar_lux , should be higher than 50000 lux.
azimuth , should have a value above 56 but no more than 229.
the external venetian blinds should move to 0% (close completely) and then tilt to 35%.
they should go up if the wind is too strong:
input_boolean.virtual_switch_wind_speed_upper_stage_1 switches on
or when one of the other condition ends.
Have you corrected the position values?
As I said? Shading and close position must not be identical.
And if so, then show me a trace of a very specific problem.
I have opened an issue in Git and uploaded the traces here.
New Update
2025.04.18:
- Updated: Just to be more bulletproof, the tilt position control can now be specifically switched on or off. Please activate if necessary. #163
- Updated: There is no default value for "Sun Shading Forecast Temperature" here now. To not compare the forecast temperature, leave this field empty. #179
- Added: Allow entities of the switch domain as resident sensor or with the force entities #167
- Added: New additional actions: Commands can now be executed before opening, closing, shading and ventilation #166
- Fixed: Fixed problems resetting manual override #184
- Fixed: Make sure that the reset of the manual override is only executed once #178
- Fixed: Problems with lockout protection and partial ventilation solved #181
- Fixed: There was no latest time for closing the cover when the scheduler was used with sun/brightness #170
- Added: Added Sun elevation examples into the description #175
- Added: New feature 'Allow opening the cover when resident is still present' #192
- Breaking change: Please reconfigure "Allow sun protection when resident is still present" ('resident_shading_enabled' was renamed)
Please note the breaking change with ‚resident_shading_enabled‘.
Please activate the Cover Tilt function explicitly if you want to use it. Otherwise the function is inactive by default.
3 Likes
I would like to thank Herr.Vorragend for his help. In my case, the problem was the configured Resident sensor in the Resident Settings area. The sensor was always true when at least one person was present, the roller blind did not go up in the morning. That wasn’t really a fault, that’s how the sensor is intended at this point. I was misled by the point Allow sun protection when resident is still present. In the last update, Mr Vorragend also added a change (Allow opening the cover when resident is still present), which can be used to ensure that the roller blind still raises. In my case, I have not configured anything in this section and CCA now works the way I want it to. 
1 Like
Okay, let me try to describe it. So, opening and closing works so far. Ventilation works too. There are just problems with the shading.
I have nine windows facing three different directions.
Usually, there are two windows next to each other.
I’d like to shade them simultaneously.
I’d like to discuss it with two windows and then try to apply it to the others.
I’m sure I’m making a mistake, but I can’t seem to get any further because I don’t know how to narrow it down.
The bedroom and bathroom windows should shade at the same time.
Both windows have their own assistant. However, I used the light sensor and the temperature sensor for both together. Now this is happening: The bathroom window is shaded, but the bedroom window isn’t. And then vice versa. And so I’m at a loss, because I even copied the code for automating the second window.
Now you would have to explain to me how I can retrieve the trace.
Or could you show me an example so I can send you exactly what you need?
Sorry, I’ve been using HA for a year, but I’m still a bit clumsy with things like this.
I want these two windows to shade from morning until around 2 p.m., because after that the sun disappears 
The way I’ve set it up, this would then be connected to the sensor.sun_solar_azimuth entity.
But what exactly is the elevation? It never reaches 90 degrees for me, and that confuses me.
Thanks in advance.
Hey, sounds like you’re on the right track! 
To help you figure this out, it would be great if you could share a trace of your automation. Here’s how you can get it:
- Go to Settings → Automations & Scenes → Automations in Home Assistant.
- Click on the automation you want to check.
- At the top, click “Trace”.
- On the left, choose a recent run – preferably one that didn’t work as expected.
- At the top right, click “Export Trace” – it will download a YAML file.
You can post that file here (or copy the text inside), and we’ll take a look together. Just remove anything private if needed.
Also, just to understand better:
Are your light sensors placed inside the rooms or outside?
If they’re inside, that might cause problems – because once the shading is active, the room gets darker, and that could mess with your logic.
About the elevation: That means how high the sun is in the sky. 90° would be directly overhead – but that doesn’t happen in most places. You can use elevation to check if the sun is “high enough” to cause shading.
Okay, thanks for the offer.
I’ve decided to test it from a small window first before continuing with the other ones. So, as I see fit, I filled the blueprint with my data and checked the log using Check Config to see if there was anything there.
And lo and behold, I’ve already encountered my first error. But what does this mean exactly?
2025-04-23 14:25:08.317 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)‘) }}’
I gradually enabled more features in the options. And just as I got to shading, this exact message popped up. The weather isn’t the best here today, but I tried to figure it out anyway.
Of course, I also downloaded a trace. Do you have a particular preference for where I can/should upload it?
You can use whatever you want.
Example: https://pastebin.com/ or Google Drive
Okay… Ive uploaded in Google Drive.
https://drive.google.com/drive/folders/1PLfuO9yck6jMOLzkZtFFYT3phYXTeuXA?usp=share_link
The actual trigger is missing in this trace. Did you run the automation here manually?
I need a trace to the trigger where you expect the execution.
Add this to your automation in YAML editor to let HA save more traces (Symbol with three dots top right > “In Yaml bearbeiten”.
trace:
stored_traces: 100
When exporting traces, select the right trace with the left/right arrows.
Yes, today I started it manually because I wanted to get a closer look. Then I came across this error message in the log. I’ve added the extended trace storage to the YAML code for this particular roller shutter. As soon as it’s running, I’ll download the trace.
I have a quick question about the manual overrides.
It seems that it tracks if manual actions were taken by this:
########################################
# Trigger for manual cover controls
########################################
- platform: state
entity_id: !input blind
attribute: current_position
id: "t_manual_1"
for: "00:01:00"
this will account as a manual position change and can then prevent automations for overriding this manual change for a specific time.
Hovewer: doesn’t every automatic trigger that leads to the cover changing its position also activate this trigger, thus registering it as a manual intervention, thus preventing future automated changes?
I’m sure what I’m saying is wrong, I just really can’t follow…