Replies: 1 comment
|
Nothing's blocking it: 52% is what the pipeline actually computed as the target, so it's not sitting there waiting on something else to let it deploy. The real question is why the target landed at 52% instead of 100% when the sun's out of view. Best way to find out is the decision trace. With the sun outside the window, 52% usually comes from one of: a default or sunset position that isn't set to 100%, a min/max position limit clamping it, a custom position slot, or climate mode parking the cover somewhere specific. I don't want to guess which one without seeing your trace. Paste the decision_trace state plus the reason and position_explanation attributes and I can tell you exactly what's setting it. Separate thing worth checking once the target itself looks right: if the physical cover still isn't matching it, look at For details, see the Troubleshooting wiki page. |
Uh oh!
There was an error while loading. Please reload this page.
I am just starting to set up my Adaptive Cover Pro and on my first attempt I was surprised that the target position of the cover was not actually deployed:
My understanding of my status is that the window is outside of the sun, so the target position should move to 100%. It is still sitting at 52%, though.
Is there something blocking the deployment, or did I misunderstand the status?
All reactions