home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.16k stars 30.2k forks source link

HmIP-ShutterGroup does not fully close the shutters #114266

Open mastameista opened 6 months ago

mastameista commented 6 months ago

The problem

After updating shutter devices (HmIP-FBL) in HomematicIP native App to version 1.10.16 homematicIP shutter group entities do not fully close the shutters anymore.

This happens when closing a shutter group through Lovelace UI or calling the service cover.close_cover. Behaviour: Shutters close 100% (fully closed like it should be), but shortly after slats turn to 0% which means they are open (horizontally aligned).

This does not happen if one calls the service for a single shutter. It's just happening with HmIP shutter group entities.

What version of Home Assistant Core has the issue?

core-2024-3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

homematicip_cloud

Link to integration documentation on our website

https://www.home-assistant.io/integrations/homematicip_cloud/

Diagnostics information

No response

Example YAML snippet

service: cover.close_cover
data: {}
target:
  entity_id: cover.groundfloor_shuttergroup

Anything in the logs that might be useful for us?

No log entries

Additional information

No response

home-assistant[bot] commented 6 months ago

homematicip_cloud documentation homematicip_cloud source

issue-triage-workflows[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

mastameista commented 3 months ago

Update to latest version and it's still the same issue. When closing shutter groups from HMIP Mobile App, it works.

mastameista commented 3 months ago

Simple Test with an automation:

trigger:
  - below: "-5.0"
    entity_id: sun.sun
    platform: numeric_state
    value_template: "{{ state_attr('sun.sun', 'elevation') }}"
condition: []
action:
  - service: cover.close_cover
    metadata: {}
    data: {}
    target:
      entity_id: cover.erdgeschoss_shuttergroup
mode: single

Closes all shutters of the group and after some seconds, slats turn to 0% (horizontally aligned)

HA-Logbook: Shows close, then open image image

Automation Trace: also shows close, then open image

If the shutters are already closed and the automation is executed, the slats turn to 0%. The Loogbook and automation trace is different (only shows open event):

Trace: image

Replacing the shuttergroup entity with a shutter entity in automation When not using a shuttergroup entity in the automation, it works like expected, although the trace shows the same sequence of close / open event: image

Using the Lovelace UI Same behaviour as when using the automation. The UI shows, that covers are not closed after the automation ran. image

Using HMIP Mobile APP Works like expected. All shutters are closed, slats turn to 100%

issue-triage-workflows[bot] commented 1 week ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

mastameista commented 1 week ago

Update to latest version and it's still the same issue.