New UniFi Access Module & Unlock Automation Issues?

solutionsix · April 10, 2026, 12:24am

We have a UniFi Access system which we’ve tied into a third party deadbolt through HA using the unofficial GitHub integration, “hass-unifi-access”. That’s been working great for a while, but I noticed that an official integration was recently added to HA and wanted to give it a shot. I removed the sideloaded version and converted to the official release this week, but I have an issue with the new automation triggers.

The problem I’m running into is the new integration does not appear to have a standard UNLOCK device or entity trigger that we can use to kick off an automation as the previous GitHub project did? I have not been able to find a way to kick off an automation based on the UniFi door hub being unlocked using the visual builder and I’m curious if I’m overlooking an event or device trigger somewhere?

I was able to load the “UniFi Access door access notification” blueprint provided by @RaHehl and modify that to trigger an automation whenever the UniFi door hub is unlocked, so it does appear that the functions exist, but I can’t seem to find them in the UI when I build an automation from scratch? For the time being, the blueprint has our locks working, minus some of the additional IF/ELSE criteria we’d normally had in there, which I’d like to bring back.

I had THOUGHT this was correct after looking at the blueprint, but the automation never triggers:

trigger: state
entity_id:
  - event.front_door_access
attribute: event_type
to:
  - access_granted

Curious if I’m missing something in the trigger setup or if anyone has any idea how to trigger an event using the visual editor UI when a UniFi door hub unlock is detected?

Kudos to the devs for the new release, which is otherwise working reliably for us.

Thanks!

solutionsix · April 10, 2026, 2:04am

Well I answered my own question after inspecting the trace on the automation configured from the blueprint – should have realized the config was available right in the trace window.

This is now working with the STATE configured as a condition of the event, which makes sense. I had incorrectly assumed that the state would be parsed as a part of the actual event as the UI made it appear, but that was not quite right. Oddly, it worked that way for a while but then suddenly stopped so I’m not sure why, but its back now with this new config. Here’s the correct format that is now working for me for our UniFi Access system to unlock our Yale (August) deadbolt:

Recently connected the deadbolts via Bluetooth so our system would work even if the Internet was down, and they typically unlock within 1 second of the UniFi system approving an authorization at a keypad. Works pretty well to authenticate face ID, QR codes, RFID, and Touch Pass into really any lock type supported by HA.

Thanks again for the devs who have been working on this integration release!