Updated October 21, 2026: DESLOC is now available in the default HACS catalog. The optional dashboard card is still awaiting its separate catalog review.
I wanted to use my DESLOC C100 Plus from Home Assistant, so I built an unofficial cloud integration and a separate dashboard card.
Source, stable releases, and English instructions: DESLOC for Home Assistant.
What it does
- Cloud lock/unlock and reported bolt state.
- Battery percentage and Wi-Fi signal.
- Creation of regular users with permanent PINs through the integration’s Configure form.
- Automatic addition of every lock returned by the DESLOC account during setup or reconfiguration, with separate entities for each lock.
Install the integration
- Open HACS and search for DESLOC.
- Download the latest stable release and restart Home Assistant. Keep prereleases disabled for normal use.
- Go to Settings → Devices & services → Add integration → DESLOC and complete setup.
The integration no longer needs to be added as a custom repository. Your lock must already be paired with the DESLOC app and support working cloud control. The README covers requirements, authentication, and manual installation without HACS. To discover a lock paired later, run Reconfigure on an existing DESLOC entry; normal polling does not add devices.
Optional dashboard card
The DESLOC Lock Card displays reported state, battery, Wi-Fi signal, and one action button that changes with the reported lock state, with confirmation before unlocking. It has a visual editor and light/dark theme support.
The card is not yet in the default HACS catalog. In HACS → Custom repositories, add the card repository URL linked above as Dashboard, download the latest stable release, and reload your browser. Then add the card to a dashboard and select your entities in its editor.
Model compatibility
- C100 Plus: maintainer-tested, including locking, unlocking, and creating a permanent PIN through HA and using it at the keypad.
- D110 Plus: community-reported working, with a second owner reporting working PIN functionality.
- K120: reported working by Chief915E, with the card’s entities available. Individual lock/unlock and PIN tests were not documented.
Other account-returned models are added for community testing. Models without maintainer validation retain an experimental runtime label. Discovery alone does not prove full compatibility. See the compatibility notes for the scope of the evidence.
Authentication and limitations
Email/password login with email-code verification works, but a new login can invalidate the phone app’s session. The authentication guide explains how to import the current app session for simultaneous use of the same account. No proxy is needed for normal operation afterward. A revoked session needs reauthentication; HA does not automatically log in again.
The K120 owner also reported sharing the lock to a second DESLOC account and using that account for HA while keeping the primary account in the phone app. This is a community-reported alternative, not a guarantee for every account or shared-user permission set.
This uses the undocumented DESLOC cloud API, with no local, offline, or Bluetooth control. Cloud telemetry can be cached, and reported bolt state is not a door-open sensor. Activity history, jam detection, and PIN editing, deletion, or schedules are not implemented. Locks paired only with TTLock or Tuya accounts are outside its scope.
Reports from other models are welcome through the repository’s compatibility issue template. Include model and software versions, plus the features actually tested. Please omit credentials, session tokens, PINs, private device identifiers, and raw captures. We will fix compatibility where the API permits it and document or exclude models that cannot be supported. This project is independent of DESLOC, Home Assistant, and HACS.