You can also click on the icons in the trace. Then you can see a little more. It was stopped here because your trigger was “unavailable” or similar.
This will resolve itself tomorrow at the latest.
But I also have the feeling that your blueprint version is not up to date. Yesterday I fixed a bug that no longer recognises previous unavailable triggers (from_state). Only the “to_state” must be filled with plausible values.
thanks, when you say the time 06 and 22 is default and every day in the trace it’s ok, but it was the first day and there it was a little bit confusing.
I am not sure if i understand the role of the status helper.
My blind was closed, then i moved it manually to a position which is not defined in the blueprint.
But the blind hasn‘t closed at elevation end.
The blueprint works only if the blind is in a defined position.
yes i tried to open and close the covers only with the sun values (NOT daily) and maybe the temp of an external sensor! And it also should close to 1 defined postion!
For example:
closing azimuth: 140
closing elevation: 30
opening azimuth: 270
opening elevation: 20
cover position: 60
so the cover only should close to 60 if the sun values are above the given “closing” values and should open if the values are above (az) /below (el) the given “opening” values.
So i thought its enough to use the sun and shading automation!
Today something happend. At around 11:30 the cover closed
But the conditions didn’t fit to the given values
I added the trace for that situation: ce202b8c - cover close without close and opening automation (hopefully now its the right one
This blueprint is pretty interesting but I’d like to see two enhancements
open (and don’t close) screen when wind speed >= X
detect if external action is taken (eg physical keypress) and pause automation for X time (the inverted is possibly easier, eg if screen was not triggered by blueprint pause actions for X time)
for me it sounds the same…for the automation with the sun values the cover should close if the elevation is above a value and it should open if its below a given value!
So i agree that the description could be wrong!..if i don’t forget i will test what will happend if there are diferent values!
We have already discussed this several times here in the thread and on GitHub. You can achieve all of this with the additional conditions and the additional actions. But not everything in the blueprint itself. This will be too customized and you will have to prepare it yourself so that CCA can use it.
ok…i have to try some more situations, because in some situation its necessary to use the elevation and in some the azimuth or a combination of both!..So in need both the control via sun elevation (has the elevation) and the automatic shading (has the azimuth). I’m right?
What does “Ignore after manual position changes” mean ? Will this force the movements through your blueprint whatever the actual status of the blind is ?