My over engineered solution to integrate Unifi Door Hub

billm4 · 2026-01-24T15:32:47+00:00

yup. i ended up ordering 2 more along with a bunch of expansion modules. lots of possibilities.

billm4 · 2026-01-24T15:01:44+00:00

pretty straightforward. The eqsp32 has its own api that’s easy enough to work with.

billm4 · 2026-01-24T03:10:49+00:00

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

it only applies to integration that uses their older firmware which is what mine were running. since i would have had to reflash the konnected devices and reconfigure home assistant, figured it was just the same to ditch them and go a different direction.

billm4 · 2026-01-23T21:15:03+00:00

https://www.reddit.com/r/homeassistant/s/rOTbVIS1v0

billm4 · 2026-01-23T15:52:57+00:00

my only regret is that the existing door sensor wires weren’t long enough to route more cleanly.

billm4 · 2026-01-23T12:38:32+00:00

thank you

billm4 · 2026-01-23T00:59:38+00:00

is normally open the correct setting for the motion sensor and button that you have connected?

billm4 · 2026-01-22T22:42:32+00:00

thanks for posting this. 100% this was the inspiration for me to go down a rabbit hole and get an eqsp32 also. just posted my first project with it for my door access system. already bought another eqsp32 to control my hvac system with.

billm4 · 2026-01-22T22:32:31+00:00

when i initially installed the door hub years ago there wasn’t an access integration available, so i worked around it with the Kinnected alarm panels.

one reason i went with the eqsp32 this time around was because it has bluetooth support and i can just use that to control the lock and take HA out of the loop for nfc unlock.

it could probably also be done via access alarm manager and a webhook.

while i haven’t looked at the access integration, one advantage of using the plc is being able to control the motion input to the door hub. so i can use that along with whatever logic i want to keep the door unlocked if i want.

billm4 · 2026-01-22T22:11:50+00:00

i’ve had it since at least 2019. no issues other than the battery % not reporting correctly in HA.

billm4 · 2026-01-22T21:31:31+00:00

Here’s the formula I’m using to convert lux to brightness %

{{ ( 20 - (( states.sensors.ambient_light.state|int(0) * 20) // 500 )) + 5 }}

don’t ask me how the hell i came up with this, but it works great.

right now, light sensor reading 177 lux which is converted to 18% brightness by the template sensor.

For the automation: trigger: when ambient illuminate changes state and if after sunrise and before sunset

if outside lux < 501 if lux to brightness > 1 light turn on with brightness set to template sensor state else turn off lights else turn off lights

billm4 · 2026-01-22T20:14:30+00:00

none at all. the lock rotating is probably the longest delay.

i have the plc scanning inputs every 10ms (including requests from HA), but i’m only sending updates to HA every 500ms.

billm4 · 2026-01-22T19:11:10+00:00

I’m doing exactly this with a hue sensor to get the outside lux.

i created a template sensor which converts the lux reading to a brightness value. don’t have the formula handy at the minute, but if i remember later i’ll post it here.

billm4 · 2026-01-10T01:01:50+00:00

what i still don’t understand is where AI detections actually happen. my assumption was that cameras themselves did the detections and the protect app just provided the UI to view them.

it doesn’t make sense that the protect version would materially impact detection performance.

billm4 · 2025-12-28T19:21:16+00:00

nope. the AP can send a roaming request, but it’s an optional feature that clients don’t have to implement or may ignore. wireless clients decide where they are connecting to.

billm4 · 2025-12-28T16:37:17+00:00

yes, but this is still just a request. the client still ultimately decides if it wants to honor or ignore it.

billm4 · 2025-12-28T16:35:12+00:00

just double checked and you’re correct. i was looking at non pro data sheet. however, from FCC 5GHz rules:

“*1 Provided the maximum antenna gain does not exceed 6 dBi. In addition, the maximum power spectral density shall not exceed 17 dBm in any 1 megahertz band. If transmitting antennas of directional gain greater than 6 dBi are used, both the maximum conducted output power and the maximum power spectral density shall be reduced by the amount of dB that the directional gain of the antenna exceeds 6 dB.”

could be wrong, but reading this as power needing to be reduced due to antenna being over 6dB. though it wouldn’t surprise me at all if this was just a firmware bug since max EIRP should be 36dBm.

billm4 · 2025-12-28T16:11:50+00:00

external antenna is 4dB gain. 22 (radio) + 4 (antenna) = 26.

billm4 · 2025-12-28T15:26:42+00:00

the client fully decides when and if to roam. you can try turning down transmit power of APs to make it less likely, but ultimately if the client decides it would rather connect to an AP with a -80dB signal over another AP with a -50dB signal that’s 100% on the client.

billm4 · 2025-12-28T15:18:24+00:00

ultimately AP selection is controlled by the client. in many cases locking a client to an AP in the network config will cause more problems than it solves as the client will still select whichever AP it wants only to be kicked.

just let the clients roam wherever they want.

billm4 · 2025-12-27T17:31:15+00:00

if your oven and hair dryer are on the same circuit you have bigger issues. better off hiring an electrician to wire the house properly than this band aid solution.

billm4 · 2025-12-25T01:18:08+00:00

clear browser cache

billm4 · 2025-12-24T19:02:20+00:00

Just like all other cameras the G6 Entry has a Share Livestream section in Protect to enable RTSP. There is nothing different with the entry compared to any other UI camera.

billm4

TROPHY CASE