You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of a hint to any other new Homebridge users out there. If you name your device in Homebridge to the same name as a grouping of items in HomeKit, then motion detection for that device may not work. In my case, I left my Doorbell Camera as "Front Door", but I have other things in a HomeKit associated in a "Front Door" group.
The only hint that this was problematic was when I tried to update the motion settings in HomeKit for the Doorbell, it showed me an error along the lines of "Cannot set that name as it is already used" (even though it's a grouping and not a separate device). It was only after I renamed the doorbell, via HomeKit, to "Front Doorbell" that I began receiving motion notifications. Of interest, in the Homebridge accessory list, I was able to observe it detecting motion before and after the rename.
I came from Scrypted for managing my UniFi Protect to HomeKit setup, but it suddenly stopped working after upgrading to macOS Sequoia, so I made the switch to Homebridge.
After configuring Homebridge (for anyone curious, the same user permissions work from UniFi).
Homebridge UniFi Protect Version
v7.11.0
Homebridge Platform and OS
macOS Sequoia 15.3.1 (Mac Mini M2 Pro 32 GB)
Homebridge Version
v1.9.0
Node Version
v22.14.0
UniFi OS Version
v4.1.11
UniFi Protect Controller Version
v5.2.49
Describe the problem
This is more of a hint to any other new Homebridge users out there. If you name your device in Homebridge to the same name as a grouping of items in HomeKit, then motion detection for that device may not work. In my case, I left my Doorbell Camera as "Front Door", but I have other things in a HomeKit associated in a "Front Door" group.
The only hint that this was problematic was when I tried to update the motion settings in HomeKit for the Doorbell, it showed me an error along the lines of "Cannot set that name as it is already used" (even though it's a grouping and not a separate device). It was only after I renamed the doorbell, via HomeKit, to "Front Doorbell" that I began receiving motion notifications. Of interest, in the Homebridge accessory list, I was able to observe it detecting motion before and after the rename.
I came from Scrypted for managing my UniFi Protect to HomeKit setup, but it suddenly stopped working after upgrading to macOS Sequoia, so I made the switch to Homebridge.
After configuring Homebridge (for anyone curious, the same user permissions work from UniFi).
Homebridge HBUP JSON configuration
Relevant log output
Acknowledgment that you are only running UniFi OS and UniFi Protect releases from the Ubiquiti Official release channel
The text was updated successfully, but these errors were encountered: