Skip to content

Add description for possible permission problems for HmIP-DLD in HomematicIP-Cloud integration #38853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 5, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions source/_integrations/homematicip_cloud.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,14 @@ Groups are instantly created in Home Assistant when created in the native Homema
Devices are created with a delay of 30 seconds in Home Assistant when created in the native HomematicIP APP.
Within this delay the device registration should be completed in the App, otherwise the device name will be a default one based on the device type. This can easily be fixed in the Home Assistant entity registry afterwards.

## Use HmIP-DLD Door Lock Drive in Home Assistant

If you are unable to control the **HmIP-DLD** device via Home Assistant, you may need to allow the Home Assistant device to control the **HmIP-DLD** in the HomematicIP app.

To do this, navigate to the **Access Control** section in your HomematicIP app and enable the necessary permissions.

Currently, the **HmIP-DLD** can only be used in Home Assistant without a PIN. Ensure that no PIN is set for the device in the HomematicIP app.

## Implemented and tested devices

- homematicip_cloud.alarm_control_panel
Expand Down