Early Access warning dismissal constantly reappears #118134
Comments
|
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) unifiprotect documentation |
|
I have been having the same issue also. I even removed my protect from early access and it still alerts. |
|
Found a solution (maybe?) - tick the unlabelled box in the UniFi Protect HA Integration Configuration and submit: With that in mind - perhaps this Issue should be updated to label that box? |
This did not work for me. |
|
If the issue is the nagging reminder that you installed an unsupported version, then it is not a bug but intentional. I believe it re-appears at every boot which due to all my tinkering with HA and the underlying Proxmox is often enough to make it irritating. When I asked about it (thought it wasn't supposed to keep showing up) I got schooled on how inefficient and annoying it is for tons of users demanding developers fix unsupported Unifi software, and I totally understand them! We (users) are told to file github issues when stuff doesn't work but that only applies to what is intended to work... fine line that is not always obvious. Anyway there is a fix, and I hope I won't get chastised for sharing it openly (it was shared with me as a hint to figure out so not as openly). There is an Edit: In the spirit of being helpful, if you need extra information to make the above change, then please don't do it and please don't ask me for help as I don't want to be responsible for broken HA installs :) I mean this in the most kind way possible! Edit2: Once removed, please remember not to complain/nag when using unsupported Unifi software and stuff breaks as that was the intent of the nag. However, EA stuff becomes GA quite fast with Unifi so.... wouldn't it help devs to know in advance when stuff is going to break? Maybe a dev can suggest a way for us to help in that regard. |
That's a bug. It should warn once, force an acknowledgement, then not warn again (at least not for a minimum period of time - say 90 days - or no version change). Any more than that is just keeping with the previous maintainer's hatred for Ubiquiti.
I think there's a difference between demanding something work, and using the EA versions to figure out what is going to break, and reporting it accordingly to those maintaining those things. That is, after all, the intent of an EA program -- discover what needs to be fixed so when it is released, the various integrations are ready to handle it, rather than being broken for several weeks while they go through a release cycle. The previous code maintainer for this integration is quite the piece of work (there are a few threads around with how he's taken his ball and gone home -- changing the license for his work with a poison pill aimed at Home Assistant). With the vitriol he was putting out, you'd think people were sending him body parts of his relatives as threats.
If anyone chastises you for something like this, that's their problem, not yours. |
|
@doctorkb While I agree the warning should be shown once, I believe it was the dev you are referencing that told me it was intentional and therefore not a bug. Either way, he did drop a hint (see my post above) on how to get rid of the nag. I figured out what he meant and very happily fixed it on my end. Unifi EA software is meant to help Unifi fix their issues. However, if I were a HA integration developer, I would likely want to be on the forefront (aka use EA) so that I can fix stuff before it becomes GA... BUT... at least one developer wrote he uses his own system and running EA would require him to have duplicate hardware which can be problematic at times especially when you consider their development and support efforts are contributed for free. My concern about being chastised for sharing it, is mostly because I am trying to help users WITHOUT causing more work/issues for HA developers. Anyway, I don't want to get tangled in a what is right or wrong debate but rather provide relief from the nag by sharing that tip in my previous post. |
|
I also think that like it is now is not intended... I am quite a while on the EA channel and also using the HA integration and up to now I got the warning only once and after updates. Now I get it all the time - I accept it and some seconds later it appears again. For me this is no big problem, but I am quite sure it is not intended to behave like this... |
|
There were some fixes in 2024.6.3 that may have solved this, but I don't have a system running EA to validate the fixes with so I'm not sure either way. Maybe someone can report back. |
|
it seems that it is fixed. I updated to 2024.6.3 (and I am on EA) and the message didn't pop up since then. Thanks! |
The problem
The "UniFi Protect Early Access Enabled" repair re-appears often, despite having been dismissed.
This shouldn't be a warning but once -- it should be switch or check-box in the Integration configuration, which can be retained.
What version of Home Assistant Core has the issue?
core-2024.5.5
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
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: