Thanks for searching, I do have the (2) entity, but it is automatically deactivated once you set the Roller Shutter to Venetian blind mode. I do have the same Roller Shutters for normal blinds, there is no other entity then.
But other than the post you linked says, I do have only 1 cover entity with the (I assume correct) attributes, you may double check to make sure it is what your integration expects:
Thanks, I tested it again, but it seems to be the case that the blueprint uses the target value provided by the sensor of the integration to set the position of the blind and NOT the tilt. The position matches exactly with the target of the sensor. The tilt is not set at all it seems.
Maybe there is something wrong in the blueprint? I used the one you provided in the other thread as the āAuto Generationā of the blueprint failed.
If you use the latest version you will not need the blueprint anymore as the integration itself calls the needed services.
You can find more info about the update in this topic Custom Component - Adaptive Cover
Maybe there is some bug in the blueprint, but never received an issue ticket for it and donāt have tilted blinds myself.
It seems that was the case, I had a fairly old version, even though I installed the integration only maybe one or two weeks ago. Now it seems to use the tilt attribute. Will test and provide feedback.
However I still do not understand what the standard and maximum position settings mean.
Is there any way to define that the blinds should receive the command āopen_coverā instead of the percentage value to open completely?
If the blinds should open completely at the end of the day (=no sun) and receive the percentage value from the automation (I think fully open would be 100%, right?), they sometimes do not open completely, as it always seems to lead to greater deviations during the day, after each movement of the blinds.
Sending the command open_cover is the same as sending 100% with set_cover_position.
As regards to the cover not opening completely, thatās an issue with your system. Either your cover motor is not correctly calibrated or itās not powerful enough. Perhaps your system has a calibration method you can do? You could also use something like this template sensor to calibrate it correctly: factor for position percentage #129
But can you explain to me why the command āopen_coverā and āset_cover_positionā (to 100%) should be the same? Iām pretty sure that moving to 100% position is not the same command as āmove up completelyā.
Arenāt two different commands sent to the cover?
The command āset_cover_positionā is used to move to a percent-position and āopen_coverā gives the command to open completely. Can you explain to me why HA should send the same command to the blinds in this cases (āopen_coverā and āset_cover_positionā to 100%)?
When the blinds receive the command to open, they do so as far as they will go, without Home Assistant having to do anything. However, if a percentage position is to be approached, there is a completely different logic behind this. Especially if the blinds do not have an exact position.
I donāt know why you think it would send the same command to the blinds, but maybe there is someone else here who can comment on this and explain your answer to me.
Because setting the position to 100% is the same thing as telling it to open completely. 100% is completely open.
No, itās the same thing. You can check this by going to dev tools and calling the āopen coverā service. You will see the position is changed to 100% like it should. It would be very strange if they did something different, because then you would never be able to use the full range of the cover position with the set_position service.
Okay, then I completely misunderstood the two commands. I assumed that āopen_coverā simply gives the command to move to the āstopā and āset_cover_positionā moves to a ātheoreticalā position of 100%, which then perhaps does not trigger the limit switch but, after the blind has moved up and down a few times a few percent, has a falsified position.
Well technically the integration has the freedom to implement it how they want to. But if you look at the tuya code for example, it just sets the position to 100%. So I assume it doesnāt even have a limit switch.
Like I said, if your blindās position is unreliable then you can calibrate it. (or perhaps itās just broken)
I know the blinds are calibrated in their settings. My questions and concerns were not about knowing where to configure this.
According to previous answers, it should always execute the same commands, whether I move the blinds to a fixed position or open them completely. In both cases, it should move to 100%, right? But that is not the case. According to Home Assistant, the blinds should now be fully retracted (100%), but they were at approx. 96%.
I then gave the command to move to 100% again, but nothing happened. Then I moved the blinds to 96% and they moved a little further down.
When I moved them back to 100%, they retracted as before (not completely up, approx. 96%).
After I gave the command with the āup arrowā (=retract) instead of the 100% position, the blinds retracted completely.
For me, this is a indication that not the same commands are being executed.
What integration integrates your covers into HomeAssistant? A position of 100% is defined within HomeAssistants logic as fully opened. cover.open_cover preforms the opening until it receives the status of fully opened, so setting the position to 100% and just opening the cover can be considered as the same. This is also confirmed by this statement from you:
Which also should mean that HomeAssistant shows that they are 100% opened.
My best guess is that the API of the cover motor does not communicate well enough with HA to report the correct state. In most cases this is not a problem that should be solved at HAās side but at the side of the hardware.
And yes you are correct that they are not the same exact command is executed but the outcome should be exactly the same. What does the cover itself reports outside HA if it is at approx. 96%?
Edit: Do you use the adaptive cover integration, the blueprint or the plain jinja macro? This is not exactly clear to me from your posts.
