✅ Yubii Home / Fibaro HC3/HC3L
✅ Standalone
The UniFi Protect plugin connects AutomationBridge to your Protect console using a local API key. It discovers your cameras and provides motion sensors, doorbell press events and supported camera controls.
This guide covers UniFi Protect 7.2 or later running on a UniFi OS console.
Before you start
Make sure:
UniFi Protect and your cameras are working in the UniFi Protect app.
AutomationBridge has the software update containing the API-key connection.
Your Protect console has a fixed local IPv4 address, either configured directly or reserved through DHCP.
AutomationBridge can communicate with the console and cameras over your local network.
The API-key connection retrieves snapshots through Protect. You do not need to configure anonymous snapshots on individual cameras.
1. Create your API key
Open your UniFi console directly using its local address and sign in as an administrator.
Open Protect → Integrations. On some versions, this is under Settings → Control Plane → Integrations.
Create an API key named AutomationBridge (with permission to read your cameras and events and manage camera streams and LEDs if required).
Copy the key. UniFi displays it only when it is created.
Use the integration key from the local console running Protect. The plugin’s local connection requires this key rather than a Site Manager or Fabric cloud API key.
2. Connect AutomationBridge
For an existing username/password installation, follow the upgrade instructions in the next section.
Open Network Devices/Plugins on AutomationBridge.
Add the UniFi Protect (UniFi OS) plugin.
Complete the connection fields:
| Field | What to enter |
|---|---|
| Protect address | The local IPv4 address of the console running Protect |
| HTTPS port | Normally 443 |
| RTSP port | Normally 7447 |
| Protect API key | The key created in the previous step |
Select Test and connect.
Keep the page open while AutomationBridge checks the connection. This may take a few minutes.
When the connection succeeds, select Open camera settings.
The connection test checks the Protect version, camera access, snapshots, live events and RTSP playback. It can enable the stream quality needed by the plugin.
If a certificate error is reported, expand Console certificate help, select Install certificate, then reboot AutomationBridge. Return to the connection page and repeat the test.
Upgrading an existing connection
Use Upgrade connection to retain your existing camera and sensor devices.
Open the UniFi Protect plugin settings and select Upgrade connection.
Create a local API key using the instructions above.
Enter the key and check the RTSP port. Your existing console address and HTTPS port are retained.
Select Test and upgrade and keep the page open until validation finishes.
The upgrade preserves camera and sensor IDs, existing automation links and HomeKit pairing identities. Existing camera names and HomeKit recording preferences are retained.
If validation fails, follow the displayed instructions and retry. If the connection is saved but a device or service refresh needs another attempt, open camera settings and select Sync.
Recording controls on Fibaro HC3 / HC3L
The new API does not provide the previous Never, Always and Detections recording-mode controls. Manage these settings in Protect’s Recording Manager.
If your existing HC3 installation contains the plugin’s {camera name} CAM recording-control Quick Apps, those obsolete controls are removed after the upgrade completes successfully. Camera, motion, doorbell and supported LED devices remain.
Any scenes that reference the removed recording-control Quick Apps will need updating. New installations do not create these controls.
3. Review your cameras and devices
The plugin settings page shows your cameras, snapshots and associated device IDs. It also displays Doorbell: Yes or Doorbell: No.
Depending on the camera and platform, the plugin provides:
| Device | Purpose |
|---|---|
| Camera | Camera entry and snapshot |
| MOTION | Activates for motion and supported object detections |
| DOORBELL | Briefly activates when a recognised doorbell button is pressed |
| Status LED | Controls the camera’s status LED where supported |
| Package camera | A separate camera view where provided by Protect |
Supported object detections, such as people and vehicles, activate the same motion sensor as ordinary motion events.
Select Sync after adding cameras or changing relevant settings in Protect. Sync discovers new cameras and refreshes existing connections while retaining existing device identities and names. Existing cameras are kept if they are temporarily offline.
To replace an API key, select Update API key beside Sync, enter the replacement key, then select Test and update key.
4. Add cameras to Apple Home
Enable the cameras you want to use with HomeKit from the AutomationBridge home page, then open the HomeKit page.
Each camera or doorbell must be added individually in Apple Home:
Open Apple Home on your iPhone or iPad.
Tap + → Add Accessory → More Options.
Select the camera or doorbell.
Enter the HomeKit code displayed on AutomationBridge’s HomeKit page.
Complete the room and naming options, then repeat for each camera.
The code is displayed in ####-#### format.
Pairing the AutomationBridge bridge does not automatically pair its cameras. Cameras already paired before an API-key upgrade retain their pairing.
Doorbell notifications
Recognised doorbells appear as Doorbell on the AutomationBridge HomeKit page.
Use an Apple Home with a connected Apple TV or HomePod home hub. You can check its status under Home Settings → Home Hubs & Bridges. See Apple’s home hub setup instructions.
Open the doorbell’s settings in Apple Home, select Status and Notifications, and enable Doorbell Notifications. Press the physical doorbell button to test.
Two-way audio
Supported doorbells can provide two-way audio through Apple Home.
Ensure the doorbell’s microphone is enabled in Protect, then run Sync. Open its live view in Apple Home and use the Talk or microphone control.
Availability depends on the microphone and speaker capabilities reported by Protect. Talkback uses the main doorbell view; package camera views do not provide a separate talkback connection.
5. Optional HomeKit Secure Video
HomeKit Secure Video—HKSV—allows activity clips to be recorded and viewed in Apple Home. It is off by default and is configured separately for each camera on AutomationBridge’s HomeKit page.
You need an Apple TV or HomePod home hub and an iCloud+ plan with an available camera allowance. See Apple’s HomeKit Secure Video requirements.
To enable it:
Open the HomeKit page on AutomationBridge.
Select the gear icon beside the camera.
Review the camera feed check.
Enable HomeKit Secure Video and select Save. HomeKit accessories briefly reconnect when the setting changes.
In Apple Home, open the camera’s Recording Options and choose Stream & Allow Recording for the required Home and Away states.
Apple Home also controls whether recordings include audio.
An H.264 feed is required to enable HKSV. If the feed uses H.265, the page displays a warning and does not offer the enable option. Change the camera’s stream to H.264 and reopen the page. Enabling is also unavailable if the feed cannot be checked.
Some H.264 feeds still need conversion to match HomeKit’s recording settings. Review any warnings and start with one camera before enabling additional cameras.
The HomeKit page’s HKSV column shows whether recording support is enabled on AutomationBridge. Apple Home’s settings determine whether recording is currently allowed.
To test, trigger motion in front of the camera and check that a new clip appears and plays in Apple Home. Protect must generate the detection event, and Apple Home must allow recording for your current Home or Away state.
Google Assistant
Where Google Assistant is configured, supported cameras and motion sensors can also be enabled from the AutomationBridge home page. Camera viewing depends on the receiving device and the capabilities of the Google integration.
Troubleshooting
| Issue | What to check |
|---|---|
| Connection test fails | Confirm Protect is version 7.2 or later, the console address is correct, and the API key was created on that console with the required access. |
| A camera is missing or offline | Check that it is available in Protect and accessible to the API key, then select Sync. |
| Motion does not reach AutomationBridge | Confirm Protect itself shows a matching detection. Check detection settings and any recording or Home/Away schedules. |
| Doorbell notifications are unavailable | Confirm the camera is identified as a doorbell, run Sync, and check that its Apple Home has a connected home hub. |
| HKSV cannot be enabled | Check the feed warning. A confirmed H.264 stream is required. |
| No HKSV clip appears | Check both the AutomationBridge HKSV setting and Apple Home’s recording settings. Trigger a real detection and confirm that Protect receives it. |
Incoming motion, object detection and doorbell events can be checked through Bridge Logs in the unifiprotect_uoswatcher log. Event timestamps use the bridge’s local time.