Everyone is free to create a configuration video. I don’t do that. I also don’t know whether it’s really necessary.
If you need specific help, then you need to help me with troubleshooting. I can’t help you with just your sentences.
What have you already tried? A config check?
What does your configuration look like?
Help me and I’ll try to help you. 
Hallo @Herr.Vorragend , guten Tag,
can you please advise what the maximum acceptable numerical value is for the position tolerance? I have entered 100% but it appears with a red underline.
Memo: I have one roller controller, which reports a wrong value after some time, I.e. open instead of closed, which causes the automation not to run in the morning to open the rollers.
If I understood all the functions of the blueprint, I would have been happy to do it. However, I don’t understand how the individual building blocks in the blueprint relate to each other.
Apparently I’m just too stupid.
Just now, the blinds suddenly all went down at 5:26pm.
I don’t understand it. I didn’t change anything yesterday.
Strangely enough, it worked this evening. How can I set an offset to sunset and sunrise? For example, they should go down half an hour after sunset.
@Herr.Vorragend Is it possible that the values for the sun azimuth only have to be integer values?
I tried -2.5° yesterday and it didn’t work (no cover moved). This morning I set it to -2° - this worked this evening.
New updates:
2024.02.03-01:
- Strict separation of the two brightness sensors. The previous problem was that the shading sensor used the same values to open or close the blinds as the normal sensor. Depending on the sensor (different edge, slope, median, filter, etc.), incorrect triggers occur.
Important: If required, please register both brightness sensors.
2024.02.03-02:
- Opening the blinds only until time_down_early. Otherwise, overlaps may occur if the brightness values are not set correctly. Avoid bouncing the blinds.
2024.02.06-01:
- Added: Helper length validation
- Comprehensive JSON changes / Now multidimensional JSON
- Roller blind movements can now only be executed once a day when the helpers are used.
2024.02.07-01:
- Fixed weather.get_forecasts: The response from the service is a dict with the target entities as keys
Thanks! Could you please explain this?
@Sushibomba You can set negative values in the elevation of the sun. Sunset is at 0° Take a look at the Sun integration entities. There you can see how many degrees it is half an hour after sunset.
You have to set your Elevation. You can use the Website www.suncalc.org to look was is good for you.
can you please advise what the maximum acceptable numerical value is for the position tolerance? I have entered 100% but it appears with a red underline.
In the YAML file you can see how the value was previously limited to 9. In the current version I have already gone up to 20%.
But very important: It is the tolerance! A tolerance of 100% is definitely wrong and would ruin everything. Then 0 = 100 and 100 = 0. Total nonsense.
Memo: I have one roller controller, which reports a wrong value after some time, I.e. open instead of closed, which causes the automation not to run in the morning to open the rollers.
It depends on how the values change. Pure percentage calculation.
But I can’t predict the oddities of your blinds.
Tip: Use the Helper in the current version and the problems should be gone.
I think you’re confusing something here.
Sun Elevation is used for opening and closing. And these values must remain floats. It has been working smoothly for me for years.
Sun Azimuth is only used for shading. These are angle values from 0-360 and are integers without decimal places.
I now save the opening and closing times for every direction.
And I only drive if I haven’t already driven on the same day.
Conclusion: Every opening, shading, ventilation and closing operation is now only executed once a day.
Next time it would really be easier if you post the YAML code of your configuration. The screenshots are a bit more awkward. Visually beautiful, but very impractical on a smartphone.
Is it possible that the position was changed in the meantime and the roller blind was not at 100%?
If you were to use the helper version and also update the blueprint, it would be more “bullet-proof”.
I made a conscious decision not to use sunrise and sunset. Depending on the time of year and where you live, this cannot be used all year round.
You have a lot more setting options via the height of the sun and can adjust it much more precisely.
@Herr.Vorragend
Yes, I also controlled the shutters manually in between because of the sun. Am I not allowed to do that for the automation? If not, it would be pretty stupid.
I’m sorry. Next time I’ll post the YAML file.
Ok, does that mean I should use the sun.sun entity instead of the sun elevation?
And is it possible to automatically close the shutters a little bit at a certain sun position?
So when the sun is at 12 o’clock and the brightness sensor is at 100lux, for example, I lower the roller shutters by 10%. If the sun then goes down by 10%, lower the roller shutter by 10% again. i hope you understand what i mean.
And isn’t it also possible to select several roller shutters in one automation or to include the function? I thought that was great in iobroker and shutter control before. then I didn’t have to write a separate automation for each roller shutter.
and if that were possible, it would also be a good option to set a time-delayed lowering of 10 seconds or so, for example, so that there are no disruptions if all shutters are lowered at the same time and the loads on the circuit are so high.
And one more thing… From your username you seem to be German.
Is there a possibility to translate the blueprint into German or have you already done so? That would probably also help me and the German community.
What happens if, for example, you were to open a window several times during the night? Would ventilation only be activated on the first opening, and then not anymore for subsequent openings?
It works as desired. No need to worry.
New update. To be honest: not yet fully tested. Will know more tomorrow morning. 
2024.02.09-01:
* Streamline the code
* Added option to enable time control via external schedule helper
* Added more options for manual time control (drive up - late on non-workdays / drive down early and late on non-workdays)
Possible breaking change:
You should reconfigure the times in your CCA automations!
I’m setting up the new blueprint. A question, Time For Drive Up - Late is for workdays or the latest point at all?
Yes, already fixed but not yet uploaded.
See: Add configuration option for "time for drive up - late on non-workdays" · Issue #10 · hvorragend/ha-blueprints · GitHub
Really? I think you should see this while configuring the blueprint. The sun elevation is an attribute of sun.sun. That is why I wrote this in the config.
There is just one shading position.
You can try the custom component “Adaptive Cover” with his own blueprint.
You can choose a cover group.
It is not possible to select multiple cover entities. Not planned atm.
You’ll have to go through that now. It also makes sense, because each roller blind could be at a different angle or generally positioned differently to the sun.
It is only shaded once anyway.
Honestly? You’re asking a lot. Sorry, but development takes enough time as it is. I can’t take everyone by the hand.
Hi, just installed it 2 days ago,
we have a small dog
and the doors to the garden has a sensor
in the past i use fhem and i had a function
if the cover is closed in the evening and i opened the door the cover goes up automaticly
when the dog comes back inside and i closed the door the cover goes down also
also the cover shouldn t go down when the door is still open
haven t found a solution yet to make it with your CAA
with the open door i think a lot of people has this problem
would be great if someone has the soulution