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 ? That is the same behavior I was seeing.
Thanks, but yes the default recording quality is standard, so i’ve never changed it. Figured it could be something else.
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 Set encoding to Standard and update to latest Homey version. That did the trick today.
1 Like
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.
Please remove the rtsp urls from the settings and restart the app.
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 
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!
I’m having the exact same issue. Have you found the answer to your question?
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.
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.
Can you try this?
Encoding: Standard ← also the fix for when the connection break after couple of seconds
1 Like
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!
1 Like
That fixed it. Don’t recall changing this, but must of. Thanks @ObelixNL ! Assume this is by design?
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.
Yes I have the same problem. Which
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?
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.
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.
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!
1 Like
