HomeKit_controller cover doesn't recognise STOP function about core HOT 5 OPEN

Hey there @Jc2k, @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit_controller) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

homekit_controller documentation
homekit_controller source
_{^{(message by IssueLinks)}}

from core.

Based on the information available, this is likely a limitation of your Legrand/Netatmo covers.

As you have noted, other covers do support "stop" and it works with homekit in HA. The code for it is trivial (here and here), but unfortunately "stopping" is an optional part of the homekit spec and some vendors do not support it for whatever reason, even though they do through their own apps. You'd have to ask them why.

As you can see via the links, we are looking for the POSITION_HOLD characteristic in the homekit api. That detection will work regardless of vendor, if they actually have that characteristic that is. And if they don't, only a firmware update from the vendor will help.

If you get a diagnostic file (the one that the ticket template asked for) you can look for this uuid: "0000006F-0000-1000-8000-0026BB765291". You shuld see that its not in the file for your homekit covers that don't have a stop function. But it will be for homekit covers that do have a stop feature.

from core.

from core.

Cover definitely has STOP (HOLD) capability, because via Netatmo integration it is there, as well as using the wall switch as well.

We can only do what the core Apple Home app can do. It's on Netatmo to expose the functionality to the HomeKit API's. If they fix their firmware, it will just work.

I wonder, wouldn’t it be possible to emulate this POSITION_HOLD capability using POSITION_TARGET and POSITION_CURRENT which are provided by HomeKit integration of Legrand/Netatmo covers?

Not really. There is no API contract about how quickly POSITION_CURRENT updates (if at all). Some covers don't update at all until they reach target. Some update every 10seconds. There is a spectrum of rubbishness. You'd have less of a "Stop" feature and more of a "Rewind X%" button, where the percentage would vary wildly between devices.

Even if it worked well enough for you and your device, that'd be a feature that would get me tickets telling me "Stop" wasn't stopping, it was reversing. And anyway, it's actually not allowed (AIUI) to emulate missing features in integrations.

What you can try to do is use the template cover entity - https://www.home-assistant.io/integrations/cover.template/ - to wrap the homekit entity and add your own stop that does what you say - you can make a script or automation that calls set_position with the current position, and have the template entity call it.

from core.

from core.