[APP][Pro] Ubiquiti UniFi Protect

Is there any way to get a line crossing trigger, it seams there is triggers for everything else but line crossing

I do line crossing triggers in Home Assistant using webhooks so I assume you can use webhooks in Homey the same way. I currently do not have a Homey setup or I would try it and let you know for sure.

The latest homey pro changelogs have the following information:
The Web App now supports showing video streams. Playback outside your local network should also work in most cases. Streams are served via a WebRTC proxy by default, improving compatibility across frontends. Developers can opt out using the disableWebRTCProxy option.

It seems that most cases does not apply to the Unifi protect app. Is it possible to make the Unifi streams work with remote viewing?

Have you already restarted the app? It works for me right away!

I’m using homey self hosted on 12.12. Attached is the error message from the web interface. But not sure if this is a Homey error or something the Unifi Protect app can fix.

Strange, it works for an couple of seconds sometimes and then crash. It looks like a Homey error.

I have this exact issue as well.

I’m using Homey Pro (early 2023) and a UDM Pro. The protect app is on version v6.2.88, Homey is running v12.12.0, and the Ubiquiti UniFi Protect homey app is on version v1.8.17.

The video appears as a black rectangle on the Homey web app and the iOS mobile app.

I was able to produce a couple of extra error messages in the console when looking at the doorbell device in Homey. The RTSPS-links are set up correctly in Protect.

console.js:36 [VideoError] 
{category: 'camera', technicalMessage: 'Missing video configuration', timestamp: '2026-02-27T00:31:55.293Z'}
fetch.js:43 
 POST https://66e57ca….homey.athom-prod-euwest1-001.homeypro.net/api/manager/videos/video/dfb276e0-9778-4e50-ae99-406756e23005/offer 400 (Bad Request)
console.js:36 
useWebRTCConnection: Error initializing WebRTC: TEe: Video source URL not available
    at ManagerVideosLocal.videoOffer (file:///app/packages/homey-local/lib/ManagerVideosLocal.mts:56:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
console.js:36 [VideoError] 
{category: 'generic', technicalMessage: 'Video source URL not available', timestamp: '2026-02-27T00:31:56.750Z', stack: 'Error: Video source URL not available\n    at Manag…ections (node:internal/process/task_queues:103:5)'}
console.js:36 [VideoError] 
{category: 'camera', technicalMessage: 'Missing video configuration', timestamp: '2026-02-27T00:31:56.757Z'}

Is live-viewing of camera streams dependent on the RTSPS-links being input in the device settings in Homey?

Edit: Another thing I can mention; clicking the speaker-icon to enable the audio-stream just results in horrific noise, then the rectangle that’s supposed to show the camera feed turns green.

Hi There,

Recently I’ve added some camera’s to my homey. The G5 bullits are streaming perfectly, Also a G5 dome is doing fine. But there are 2 G5 flex models that will not stream, but the this will pop up:

Somebody else have this issue?

Regards,

F.

You should report your issue in the app topic:

This is the app topic :wink:

I am transitioning to Homey and am having some issues with my Protect cams. I am currently using the UI NVR connected to a Dream Machine SE. I can see the cams as well as snapshots but can’t seem to get the live feeds to display. I am mostly interested in showing the live feed from the G4 Doorbell Pro on my Homey Dashboard. Any guidance or tips appreciated. Thanks.

I may be stupid – but here we go!

I have added the network app., created a user and connected and signed in. All good.

Added the protect app (version 1.8.17) – tried the same user (full mgmt for network and protect) but get “invalid credentials”, tried creating a new local user with only full access to only protect, same error…and the credentials are correct.

What the hell am I doing wrong? :melting_face:

Disregard that – a small “http://” had sneaked in to the IP address :man_facepalming:

The IP address is null, which means, it isn’t configured.

I have installed the Unifi G6 doorbell, and added a NFC tag in protect, then added the doorbell to homey with the unifi protect and access app, and try to get a message to see the data of the tag (to later use this to open my door), but when I create a flow “when doorbell has detected a NFC tag send message” with all the available tags inside, nothing happens even though protect confirms the NFC tag. Am I doing something wrong or do I need to set something specifically inside protect to allow sending this to homey?

If I use the tag doorbell pressed it does send a message, so the link with the doorbell works fine, I just do not get any message for detected NFC.

If I look in the Unifi log it also shows that the NFC tag was used, so I do not understand why I do not get any result in Homey?

image

In the app all seems ok too:

However nothing happens when using this card:

Any help appreciated :slight_smile:

1 Like

If I buy a G6 Bullet, is it possible to use license plate recognition and create a flow to open the gate using a Shelly?

Is this error something you’re aware of or that you’re working on / have fixed in a test version - or is it, as you said; a Homey error?

Kinda sucks not having a live feed in Homey from my shiny new Unifi G4 Doorbell Pro :frowning:

It looks like a Homey error, I will send an e-mail to support about it today.

Not sure if anyone else had this issue that from the homey app the video stream was always giving me a black box no video. The snapshot worked. What I found that seemed to “fix” it, was to change a setting in the camera settings within the unifi protect application (not homey app) within playback settings I changed the encoding to standard which was set to enhanced.

When i connect my G5 Turret Ultra, the snapshot function is working, but the livestream i can’t get to work. I accidentally got it working but it stopped after a few minutes. Is there anything i need to check or change? (screenshots are from web app, but its the same in the app)