Unifi Protect Integration: Early Access Warning : solved in 2025.8.x

[SBergers]

The problem

I've just updated to 2025.6.2 and now the Unifi Protect Integration is warning me that i'm using an early access version of Protect (6.0.41).

Ofcourse, i'm not.
My Unifi Protect is running on the official release channel and 6.0.41 is the latest.

What version of Home Assistant Core has the issue?

2025.6.2

What was the last working version of Home Assistant Core?

2025.6.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Unifi Protect Integration

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

No response

[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)}}

[craigwitter]

Mine is telling me the same. Thus far, I haven't seen any issues with this. The error does come back up each time Home Assistant is restarted, even after it was dismissed previously.

[keatre]

Third for this issue, as well. No reported issues with the integration itself, outside of the warning message that requires a dismissal.

[alexmarsaudon]

+1 for me - latest integration, Unifi Protect, no EA, and I get the warning banner every restart. Afaik it is cosmetic (though I am far from a power-user; I leverage Frigate for my object detection)

[bitcrumb]

Same issue here while I am just following the official release channels (and not the early access ones).

[actionpotato]

+1 same issue for me:

`
UniFi Protect Early Access enabled
Warning · Reported by UniFi Protect
You are either running an Early Access version of UniFi Protect (v6.0.41) or opt-ed into a release channel that is not the official release channel.

As these Early Access releases may not be tested yet, using it may cause the UniFi Protect integration to behave unexpectedly. Read more about Early Access and Home Assistant.

Submit to dismiss this message.
`

[mvanlijden]

Same issue. I expect this to be related to the fact that Unify released the 6.0.x version just now and the integration does not recognize this as a proper stable release yet.

[RaHehl]

F.Y.I. #147432

[SBergers]

F.Y.I. #147432

Saw this popping up earlier.
Seems like a quick fix and I support your reason.
If you're running the beta version, you don't need a warning in HA.
Just place it somewhere in the prerequisites on the wiki.

[Mariusthvdb]

not sure if this #147432 should be the fix.
removing the checks would only be sushing the repair, and not the underlying 'issue'?
Why would the integration think it is a EA channel in the first place. Seems that would need fixing, instead of silencing the warning after the act..

btw, since there was no screenshot posted yet:

[RaHehl]

Did you read my comment there in full?

[Mariusthvdb]

Did you read my comment there in full?

you mean this:

On top of that, UI seems to be moving away from the old logic of distributing releases via the traditional APT repos, and it looks like they’re also introducing staged rollouts, which means the EA check logic is now broken. Right now, I don’t see an easy way to fix this. Looking ahead, I’m hopeful that we’ll be able to switch to the new public API and that the EA issues will mostly resolve themselves as a result.

yes I did.
I just dont think silencing a valid (well, at least to the integration) repair is the way forward, not even temporary

[RaHehl]

No, I meant completely — including what’s written above.