Homekit shutter/shade integration glitch

Third party integrations
21

That’s great news!

If I may, are You also experiencing that the blinds are not reacting to HomeKit calls when the cover has moved all the way down, but is tilted to 0°? In the Home-App the cover then reports 98%.

22

I only had this problem before this workaround, as a result of the re-tilting at the end. But even then only as an nuisance in the UI. It never stopped reacting. It is probably fair to say that I control the blinds either through KNX (physical keys around the house) or HK. HA is dealing with the different system translations in the background.

23

Same here, my primary use-case for home assistant is integrating everything and exposing control to Homekit and KNX.

When it comes to blinds / covers our household uses Siri to open / close all within a room or on a floor. And there, I think that the my observation stems from. To be more precise, following is the behavior:
We command Siri to close all blinds in a room. With this automation one cover will close completely. The others may remain in the state of 98% open with 0° tilt.

My assumption is that this relates to the single mode setting of the automation, so I will try changing that.

I am afraid though that a mode other than single may result in infinite loop. As the call to set cover tilt service might (?) also trigger the automation again. Am I right / wrong?

24

Is should not since the position and tilt are different services.

25

I have changed the mode-setting to parallel and now it works as expected.

The drawback of this automation is that once closed, the tilt-(re)setting of the actuators is configured to 100%. So opening will not restore any previous tilt setting. But, I think this can be ignored/solved differently. I am thinking of scenes or activating the automatic tilt positioning of the MDT actuators.

26

Thank you :slight_smile: that helped me a lot !
I d like to add one point here because iam using homekit and saying “close all covers” the maximum rate ( set as default is 10) so i extended your code with the counter of all Covers i have in my house. Only if someone also faces this problem :slight_smile:

alias: Cover Position Automation
trigger:

  • platform: event
    event_type: call_service
    event_data:
    domain: cover
    service: set_cover_position
    condition:
  • condition: template
    value_template: “{{ trigger.event.data.service_data.position in [0, 100] }}”
    action:
  • service: cover.set_cover_tilt_position
    data:
    entity_id: “{{ trigger.event.data.service_data.entity_id }}”
    tilt_position: “{{ trigger.event.data.service_data.position }}”
    mode: parallel
    max: 35
27

Great to hear :+1: I did start having some issues (after a while!) where two of the blinds only tilt-up (without fully raising in the morning). Tried parallel and queue, but still without success…

Would be great to hear your experience after a while.

1 Like
28

Works without a flaw for me. Only the non-tiltable covers that I have complain that they can’t tilt, which I believe could be solved, too. For now, it’s only a warning in the log, but other than that behavior is what I have asked for.

29

I will update you :slight_smile:
Did you check the logs ? I checked for example the automation logs and found out the limit of the max basic value… maybe if you start listening to the service you find out more what is happening

30

I have the same constellation :slight_smile: i thin the solution is to create a separated automation for each entity :slight_smile: i will try to figure that out and test a little bit

31

Since I‘m having a naming convention for the devices, in my case it probably can be solved by filtering out those entities that have „rollo“ in the name.

So it could even be incorporated into the same piece of automation code.

1 Like
32

Hi everyone, I´m facing a similar problem with Homematic IP Wired. In my case the shades are going down correctly with tilt_position 0 and after a few second they are going up again for 1-2 percent. And after that the tilt_position is 100. Any idea how to solve it?

Kind regards,
Tobi

33

Please provide more information, specifically:

  • Do your actuators contain a setting that influences the tilt when reaching end positions?
  • Do You use or try the automation described in this thread?
  • Is the issue only occurring when using HomeKit / Siri?
  • Are there any debugging / logging facilities on HomeMatic that help to determine what Home assistant is sending and what the CCU is doing two seconds after the end position is reached?
34

You would need thr
service: cover.set_cover_tilt_position
As mentioned in my messages above