Unifi Protect integration incorrectly reporting use of Early Access

[slyglif]

The problem

Since upgrading Protect to 6.0.41, the integration has been opening a Repair issue each morning stating I'm running with either an Early Access release or have set Protect to the Early Access channel. Neither is correct. Screenshots attached.

What version of Home Assistant Core has the issue?

core-2025.6.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Unifi Protect

Link to integration documentation on our website

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

Diagnostics information

config_entry-unifiprotect-01J6MT5QH7PRM7KHHWVX90TYC2.json

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

[github-actions]

🔍 Potential duplicate detection

I've analyzed similar issues and found the following potential duplicates:

• #147002: Unifi Protect Integration failing since Unifi upgrade to 6.0.41

What to do next:

1. Please review these issues to see if they match your issue
2. If you find an existing issue that covers your problem:
   • Consider closing this issue
   • Add your findings or 👍 on the existing issue instead
3. If your issue is different or adds new aspects, please clarify how it differs

This helps keep our issues organized and ensures similar issues are consolidated for better visibility.

This message was generated automatically by our duplicate detection system.

[slyglif]

This issue is not a duplicate. The "potential duplicate" is about an outright failure, while this is a reporting problem and doesn't care about the camera data.

[RaHehl]

@home-assistant close No HA or integration issue — I'm currently not being offered the installation of version 6.x on either a Cloud Key or a UDMP, so it's also not a released version for integration at the moment.

[alvinchen1]

RaHehl, thanks for all your work on this integration since the last owner left. Your responsiveness to issues has been nothing short of amazing. But I do also get this error as well, and am not on Early Access. I tried to look in the code for where it determines what the stable official version is, to raise the error, but haven't found it yet.

Also Unifi Protect Application version 6.0.41 is now stable / official as of 3 days ago... My UCK G2 Plus has this queued up for update / installation this Sunday and I'm not on Early Access.

https://community.ui.com/releases/UniFi-Protect-Application-6-0-41/f3b23ab2-5bed-4d37-906c-0ae94d797f80

https://community.ui.com/releases/UniFi-Protect-Application-6-0-41/f3b23ab2-5bed-4d37-906c-0ae94d797f80#comment/eb03b6f1-1d2a-425b-9c45-730683658a50 UI-Team announcing promotion to Stable/Official June 17th.

Also, I do also remember the frustrations the last owner of this integration had when Ubiquiti would release a new major version and being the sole developer would facing a flurry of issues once people started to upgrade to the latest version if there were some breaking change. Will say, you are handling it with quite a bit more grace and care than the last developer often did. I seem to recall some drama when Frank and Paulus ended up having to ban them because they had violated the Code of Conduct so many times. Regardless, I totally understand how frustrating things can be and only wish I could code enough to help contribute.

[RaHehl]

Hey, thanks for your comment — it’s refreshing to read something appreciative.

About the issue: I haven’t looked at the code again, but I’m pretty sure there’s a check somewhere for the UI release APT repo. Yesterday, I checked two Protect installations that I manage to see if the 6.x update is installable — and it wasn’t.

There are really only two possible reasons for that: either they’ve pulled the release on the UI side, or they’re doing a staged rollout.

Since the integration is technically behaving correctly in this case, I don’t plan on taking any action for now. My hope is that we’ll soon be able to switch to the public API, which will hopefully be somewhat stable — and that we can establish a proper collaboration with UI moving forward. That would also help us catch changes (maybe even planned ones) early enough to respond in time.

If that happens, I’d also be open to revisiting the whole EA situation in the integration. Personally, I don’t really have a problem when someone reports EA incompatibilities — in fact, I appreciate it when someone says something like:
“Hey, I’m using EA with camera model XY, and I know it’s not officially supported, but just wanted to let you know I’m seeing this issue.”
That kind of bug report is super helpful.

What really frustrates me is when people update to EA, don’t update Home Assistant, then open bug reports for issues that have already been fixed — and don’t even mention that they’re using EA. Even worse is when someone jumps into an issue with a completely unrelated error message and says something like:
“Yeah, I didn’t feel like opening a new issue for this.”

[alvinchen1]

Of course, it's always nice to try and see the human beings on the other side of these conversations!

So very curious that you aren't seeing the update. I looked through the entirety of the thread

https://community.ui.com/releases/UniFi-Protect-Application-6-0-41/f3b23ab2-5bed-4d37-906c-0ae94d797f80?page=1

And while there are a lot of reported issues (not surprising whenever there is a major release of an Ubiquiti product), the UI-Team hasn't pulled the release like I've seen them do in the past. Even versioning-wise, the next EA is already 6.0.45 (vs 6.0.41 which is this stable/official). So I'd concur this is probably a staged rollout (or some other factor like maybe not being offered to Cloud Key 1 and UDM or something like that, which frankly finger wagging at Ubiquiti for not being more transparent about).

Given that, however, I would respectfully still argue that this is still a very minor issue, but an issue nonetheless. Not to generalize, but Home Assistant users (and especially those who would actually file a Github issue) are likely going to be early adopters and / or going to install stable software whenever it is available. As such, I do think it makes sense to review how we determine what is EA and what is stable/official, and ensure there is timely and ACCURATE flagging of the repair as such. If we insist that user NOT use EA for supportability reasons, I agree with that, BUT we should in turn make sure that when something actually gets to Stable/Official (or staged rollout like this appears to be), it's my opinion we should adhere to the same line in the sand standard and NOT flag the repair. I also completely agree that using the public API might help to eliminate many of the things we might currently be doing with this and I'm glad to see Ubiquiti moving towards a public supportable API. And again, I truly do appreciate your efforts getting us there.

And finally, yes, nothing irritates me more than someone yelling, "it's not working / fix it / code monkey!" and not paying attention to release notes, and standard update procedures (of which I feel this repair warning is designed to address). But let's just flip this for a second, maybe my earlier point will be more clear. If we insist that users upgrade to the latest supported Home Assistant to get all features and bugfixes, then doesn't it also make sense that if a user upgrades to the latest stable /official and supported Unifi Protect, they can reasonably expect that they won't be chastised for installing EA when they aren't in EA? In my mind, yes, I think so. Also I completely concede, all the user has to do is click Submit to dismiss so like I said a VERY minor issue, but an issue nonetheless.

I generally try and keep an eye on the integrations I use and guide folks if they are attaching different issues to the same issue etc and / or ask for more information, logs etc to help the devs get to resolution faster. It's the least I can do since I can't code, (I am a consultant at a major software company, so I get it).

Thanks again, hope this makes sense.

[RaHehl]

First UCK not update installed while autoupdate active:

on RC showing the update

back to release not available:

same on another UCK:

and on a UDM Pro:

[kimpenhaus]

@RaHehl maybe its a phased rollout? I have auto update enabled and am on the official release channel. My protect was updated 3 days ago ... seeing the same warning/repair in HA

and from the logs

in HA

[JukeboxBill]

I have the same issue since today.
I do not use Early Access in HA and Unifi Protect is running v.6.0.41 from the official release.