Delay in camera feed (up to 30 seconds) label:"integration: unifiprotect"

[Mishta]

The problem

Streaming video is massively delayed (e.g. 20-30 second).

This situation makes the stream unusable.
I intended to use it on a TV (via Chromecast) to show the Doorbell streaming.

My current configuration and usage involves the following equipment:

• Home Assistant
  • Core 2025.1.3
  • Supervisor 2024.12.3
  • Operating System 14.2
  • Frontend 20250109.0
• Installed as a VM on a Proxmox VE v8.3.3
• Unifi Environment:
  • Network v9.0.108
  • Protect v5.2.46
  • Camera: G4 Doorbell (Firmware v4.74.88)
• Chromecast 4k

What version of Home Assistant Core has the issue?

2025.1.3

What was the last working version of Home Assistant Core?

2025.1.3

What type of installation are you running?

Home Assistant Core

Integration causing the issue

unifiprotect

Link to integration documentation on our website

https://www.home-assistant.io/integrations/unifiprotect

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

This issue is not new, as it has been presented earlier (as early as 2022) in the Home Assistant Community

• Unifi Protect integration - useless
• Unifi Protect camera streaming issues
• Another raised Issue (since Mar-2022) that was closed, with same problem, but no solution
  • UniFi Protect video delay #67888

The Stream Integration, with LL-HLS - Low Latency HLS does not solve the issue.

[home-assistant]

Hey there @RaHehl, mind taking a look at this issue as it has been labeled with an integration (unifiprotect) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of unifiprotect can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign unifiprotect Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

unifiprotect documentation
unifiprotect source
_{^{(message by IssueLinks)}}

[home-assistant]

Hey there @hunterjm, @uvjustin, @allenporter, mind taking a look at this issue as it has been labeled with an integration (stream) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of stream can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign stream Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

stream documentation
stream source
_{^{(message by IssueLinks)}}

[RaHehl]

Actually, it's a topic I've wanted to delve into at some point—excluding the Chromecast issue. For low-latency video that doesn't continuously drift into delay, I also use go2rtc and "WebRTC Camera" from HACS.

Additionally, it would, of course, be great if this worked seamlessly with HA out of the box. However, I seem to recall that this might be due to an architectural decision regarding the stream type—but that's just a guess on my part. I'll need to look into it in more detail.

[allenporter]

Just so I understand: go2rtc / WebRTC is built into home assistant blog post as of a few releases ago.

Are you saying its not working or something else?

[RaHehl]

Interesting, I'll have to take another look at it. I believe I reviewed it again at the end of last year and it worked better than before, but I still experienced a slightly higher delay.