# \[APP\]\[Pro\] Ubiquiti UniFi Protect

**URL:** <https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966>\
**Category:** Apps\
**Tags:** app, camera\
**Created:** [February 14, 2021, 9:51am UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966 "2021-02-14T09:51:40Z")\
**Posts on this page:** 20\
**Page:** 45

<div class="post-metadata">

**Author:** ![stogs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stogs/32/120883_2.png) [@stogs](https://community.homey.app/u/stogs)\
**Post date:** [March 12, 2026, 2:28pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/896 "2026-03-12T14:28:16Z")

</div>

Did you try the setting I mention in the post above [https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/894?u=stogs](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/894) ? That is the same behavior I was seeing.

---

<div class="post-metadata">

**Author:** ![FGM28](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fgm28/32/155503_2.png) [@FGM28](https://community.homey.app/u/FGM28)\
**Post date:** [March 12, 2026, 3:10pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/897 "2026-03-12T15:10:52Z")

</div>

Thanks, but yes the default recording quality is standard, so i’ve never changed it. Figured it could be something else.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/2/82a01b891a7cfffb9f96efec8c21d7443de9e64e.png)

---

<div class="post-metadata">

**Author:** ![FGM28](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fgm28/32/155503_2.png) [@FGM28](https://community.homey.app/u/FGM28)\
**Post date:** [March 12, 2026, 3:19pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/898 "2026-03-12T15:19:17Z")

</div>

Update: the error i’m getting is: Video source URL not available

 ![IMG_1628.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/e/eeeda08bf6747e6c7659bcd5b5d58dfe6bb3f847.jpeg)

---

<div class="post-metadata">

**Author:** ![ObelixNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/obelixnl/32/172250_2.png) [@ObelixNL](https://community.homey.app/u/ObelixNL)\
**Post date:** [March 12, 2026, 3:42pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/899 "2026-03-12T15:42:27Z")

</div>

Encoding: Standard ← also the fix for when the connection break after couple of seconds  
Enable Stream with in Settings → Share Livestream → Enable Secure RTSPS Output → High Resolution

[piperalpha](https://community.homey.app/u/piperalpha) Set encoding to Standard and update to latest Homey version. That did the trick today.

---

<div class="post-metadata">

**Author:** ![piperalpha](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/piperalpha/32/156597_2.png) [@piperalpha](https://community.homey.app/u/piperalpha)\
**Post date:** [March 12, 2026, 4:28pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/900 "2026-03-12T16:28:44Z")

</div>

No idea what I’m doing wrong then. There are no available updates for my Homey and I’m still just getting a black rectangle instead of the video feed (on mobile). Encoding has been standard since before I reported initially.

 ![IMG_2325](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/2/1296dcc6753daa3fbce56b1014938bb1cf9d5c17.jpeg)

 ![IMG_2323](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/1/91724580887a1aabf10a739668b61d280013b9e6.jpeg)

 ![IMG_2324](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/8/28d6d6c81209663be5242d75a96c5482c137a57b.jpeg)

---

<div class="post-metadata">

**Author:** ![ObelixNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/obelixnl/32/172250_2.png) [@ObelixNL](https://community.homey.app/u/ObelixNL)\
**Post date:** [March 12, 2026, 4:57pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/901 "2026-03-12T16:57:30Z")

</div>

Please remove the rtsp urls from the settings and restart the app.

---

<div class="post-metadata">

**Author:** ![piperalpha](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/piperalpha/32/156597_2.png) [@piperalpha](https://community.homey.app/u/piperalpha)\
**Post date:** [March 12, 2026, 5:12pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/902 "2026-03-12T17:12:37Z")

</div>

There we go!

I asked previously in this thread wether the RTSP-links were necessary. Evidently they’re not 😊 I did try removing them, but I didn’t think to restart the app.

Thanks a bunch for the help and for the app, sir 🙏

---

<div class="post-metadata">

**Author:** ![Tjar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tjar/32/61177_2.png) [@Tjar](https://community.homey.app/u/Tjar)\
**Post date:** [March 13, 2026, 7:22pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/903 "2026-03-13T19:22:21Z")

</div>

hi all,

so I have the Unifi chime (wall power socket) and added it to protect and homey. But somehow I cannot het it to play through homey, by pusshing the button in the device cars nor via the flow.

Did someone have this working?

I do not have a unifi doorbell (the flow is triggered by a shelly device input).

The protect app makes the chime play with a test button (ding dong), but complains that I need doorbell connected. Is that manditory?

best regards!

---

<div class="post-metadata">

**Author:** ![Stan\_M](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stan_m/32/78863_2.png) [@Stan\_M](https://community.homey.app/u/Stan_M)\
**Post date:** [March 14, 2026, 10:52am UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/904 "2026-03-14T10:52:21Z")

</div>

I’m having the exact same issue. Have you found the answer to your question?

---

<div class="post-metadata">

**Author:** ![Arjan\_Neet](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arjan_neet/32/17808_2.png) [@Arjan\_Neet](https://community.homey.app/u/Arjan_Neet)\
**Post date:** [March 14, 2026, 11:17am UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/905 "2026-03-14T11:17:39Z")

</div>

Unfortunately not, and I think it might be because it is connected to the hub, the message in the unifi log is nfc card used by doorhub mini, not by G6 doorbell, so probably that is why the doorbell tag nfc detected in homey doesn’t work?

However the hub doesn’t have any tags in homey, and as far as I know the NFC on the doorbell only works if you connect it to the access hub, not if you connect it directly.

This really sucks cause I bought the hub specifically to be able to use the NFC, cause my alarm also works with a nfc tag and then I could use the same tag.

---

<div class="post-metadata">

**Author:** ![PJ-AU](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pj-au/32/17303_2.png) [@PJ-AU](https://community.homey.app/u/PJ-AU)\
**Post date:** [March 15, 2026, 10:17am UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/906 "2026-03-15T10:17:50Z")

</div>

> [@PJ-AU](#):
>
> Anyone noticed UniFi Protect video feed stopped working with either latest IOS or Android 9.7.1 with Homey Mobile App? It appears to play audio, just black screen for video. Either Homey Dashboard or via Device object.

Just chiming in to see if anyone has seen this issue where all you see is a black screen with Video. You can hear audio, but nothing but black screen for video. The screen capture appears to work.

This previously worked when initially released, but believe stopped working recently. I have tried reinstalling UniFi app, but no luck. Not sure if issue on Unifi or Homey side.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/1/017238d635e93ad684f46c3e3f8a6e91888adb01.jpeg)

---

<div class="post-metadata">

**Author:** ![ObelixNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/obelixnl/32/172250_2.png) [@ObelixNL](https://community.homey.app/u/ObelixNL)\
**Post date:** [March 15, 2026, 10:29am UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/907 "2026-03-15T10:29:40Z")

</div>

> [@ObelixNL](#):
>
> Encoding: Standard ← also the fix for when the connection break after couple of seconds

Can you try this?

Encoding: Standard ← also the fix for when the connection break after couple of seconds

---

<div class="post-metadata">

**Author:** ![LundGuld](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lundguld/32/80542_2.png) [@LundGuld](https://community.homey.app/u/LundGuld)\
**Post date:** [March 15, 2026, 11:31am UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/908 "2026-03-15T11:31:37Z")

</div>

Hi everyone!

I’ve had a Homey flow using: WHEN **a person is detected** , THEN do whatever. It’s been working fine for years. But recently it has stopped working.

I’ve set up some test flows to narrow it down. I can trigger the flow if I use the motion detected, but I run with motion detection disabled, because they are too sensitive in my setup.

Person detected is what I would like to use.

I have uninstalled the app in Homey, re-added all cameras and made sure that they are connected and working. And like I said, the motion flow works fine.

Anyone knows what the reason is?

Appreciate any help!

---

<div class="post-metadata">

**Author:** ![PJ-AU](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pj-au/32/17303_2.png) [@PJ-AU](https://community.homey.app/u/PJ-AU)\
**Post date:** [March 15, 2026, 8:22pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/909 "2026-03-15T20:22:41Z")

</div>

That fixed it. Don’t recall changing this, but must of. Thanks @ObelixNL ! Assume this is by design?

---

<div class="post-metadata">

**Author:** ![ObelixNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/obelixnl/32/172250_2.png) [@ObelixNL](https://community.homey.app/u/ObelixNL)\
**Post date:** [March 15, 2026, 11:20pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/910 "2026-03-15T23:20:42Z")

</div>

We are going to report this to Homey, since the latest version the beter encoding is not working for the new WebRTC functionality in Homey.

---

<div class="post-metadata">

**Author:** ![Rasket787](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rasket787/32/138382_2.png) [@Rasket787](https://community.homey.app/u/Rasket787)\
**Post date:** [March 17, 2026, 8:44am UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/911 "2026-03-17T08:44:54Z")

</div>

Yes I have the same problem. Which

> [@LundGuld](#):
>
> Hi everyone!
> 
> I’ve had a Homey flow using: WHEN **a person is detected** , THEN do whatever. It’s been working fine for years. But recently it has stopped working.
> 
> I’ve set up some test flows to narrow it down. I can trigger the flow if I use the motion detected, but I run with motion detection disabled, because they are too sensitive in my setup.
> 
> Person detected is what I would like to use.
> 
> I have uninstalled the app in Homey, re-added all cameras and made sure that they are connected and working. And like I said, the motion flow works fine.
> 
> Anyone knows what the reason is?
> 
> Appreciate any help!

I’m experiencing the exact same issue.

I had an open support ticket with UniFi, and they provided me with a bugfix — but it required installing the Protect 7.0.73 release candidate version. I have a feeling the problem might be related to that, so hopefully it gets properly fixed by the time it reaches the official release.

What Protect version are you currently running?

---

<div class="post-metadata">

**Author:** ![LundGuld](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lundguld/32/80542_2.png) [@LundGuld](https://community.homey.app/u/LundGuld)\
**Post date:** [March 17, 2026, 9:15am UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/912 "2026-03-17T09:15:57Z")

</div>

Hi Rasket787  
Thanks for your reply. It’s nice to hear that I am not alone on this.

I am on Protect 7.0.88.

---

<div class="post-metadata">

**Author:** ![Rasket787](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rasket787/32/138382_2.png) [@Rasket787](https://community.homey.app/u/Rasket787)\
**Post date:** [March 17, 2026, 9:32am UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/913 "2026-03-17T09:32:59Z")

</div>

Ah, that might explain it — it’s probably related to the major version change. The last official release was 6.2.88, and now we’re already on the second release candidate in the 7.x line, so the full release is likely very close.

I’m guessing this is something that needs to be fixed on the Homey UniFi Protect app side to properly support the new version. Hopefully it gets addressed soon, since it’ll likely affect all of us once 7.x becomes official.

---

<div class="post-metadata">

**Author:** ![LundGuld](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lundguld/32/80542_2.png) [@LundGuld](https://community.homey.app/u/LundGuld)\
**Post date:** [March 17, 2026, 9:55am UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/914 "2026-03-17T09:55:50Z")

</div>

That makes sense! I was not aware that I was that far ‘ahead’ on the Protect version. I did intentionally agree to run beta versions, but blissfully forgot the implications/issues I could run into when it comes to it working with Homey and other systems, that has to catch up first.

I will wait for it to support the new version. Until then, I can play around with the motion detection a bit.

Thanks again, Rasket787!

---

<div class="post-metadata">

**Author:** ![ObelixNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/obelixnl/32/172250_2.png) [@ObelixNL](https://community.homey.app/u/ObelixNL)\
**Post date:** [March 21, 2026, 9:40pm UTC](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966/915 "2026-03-21T21:40:08Z")

</div>

Fixed in [Ubiquiti UniFi Protect and Access | Homey](https://homey.app/en-nl/app/com.ubnt.unifiprotect/Ubiquiti-UniFi-Protect-and-Access/test/)

[Previous page](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966.md?page=44)

[Next page](https://community.homey.app/t/app-pro-ubiquiti-unifi-protect/42966.md?page=46)
