Your question is a bit older. Have you already been able to solve it?
I would use the additional actions here. And you have to deactivate the execution of the actual commands in the blueprint: “Prevent ‘set_cover_position’ and ‘set_cover_tilt_position’”
Note:
- However, after forcing a state, you must ensure that you move to the correct target position yourself. You are responsible for getting CCA back on track.
- This cannot be performed in CCA and must therefore be done via a separate automation. Presumably in the same automation that sets the "Force"-boolean. It is sufficient, by the way, if a configured position is targeted. CCA then recognises the status.
- Force is a final state that cannot be cancelled or resetted by CCA.
If you remove the automation from the rhythm, CCA no longer knows exactly what the status is afterwards. So you have to fix it yourself. There is currently no other way.
There are a few oddities here. Firstly, the fact that your helper is configured incorrectly has already been described.
This may not play a role, but you seem to live in Germany. So where do these extreme values come from?
sun_elevation_down: 56
sun_elevation_up: 229
But the biggest problem will be this:
shading_position: 0
This means that the shading position is identical to the close_position. This will not work. Please also note the information under “Position Tolerance”.
Please deactivate the option “Enable brightness control (in addition to daily opening and closing)”. This is active for you, but you have not configured a brightness sensor. It could be that the conditions are then always valid and therefore the earliest time is used.
Please let us troubleshoot individually, otherwise I will lose the overview here in the thread.
Please write me a specific problem.
What did not happen at what time. And what should have happened.
Then please add the corresponding trace to the post. Maybe even the traces before and after. This plays a major role in shading.
Please excuse me if I’m asking a slightly daft question. I’ve been using FHEM since 2013 but only a few months in HA. Everything has worked so far, so I’ve never had to do any deeper troubleshooting.
What do you want to see from the trace menu if you want to see a ‘trace of triggering’?
The automation is working fine so far with the nightly closing, but now I started with setting up the sun protection, and unfurtunatly, it is not working as expected.
I am especially wondering why the helpers, that are set up as a text input, stay on unknown. This is my config:
Does anybody of you have an idea what I am doing wrong? the temperatur is at 25°, azimuth at 227°, and sun elevation at 47° so I really wonder where the problem is coming from.
The helper remains empty if you have never triggered automation. But I can’t imagine that. Or have you just created them?
Or the helper is configured incorrectly. Does it have a length of 254 characters?
You have only activated shadowing. Nothing more. Then these values don’t really matter. They’re probably still legacy, right?
Show me a trace of a triggering and I might be able to recognize what’s wrong with the helper.
Side note: You know that numerical triggers are only triggered when the threshold is exceeded, right?
Once it is above the temperature, there is no further trigger.
I set it up 2 days ago, for several shutters seperat automations, and some of them also close in the evening and open in the morning - and also there, the helper says unknown. I wonder wher I can adjust the length? I checked the helper but couldn’t find a setup.
Regarding these legacy things, I use that in winter, but deacivated it in summer.
I will send you a trace as soon as I have it, but somehow my feeling is that it is connected to the helper issue.