Comments (10)
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!
from core.
Hey there @bdraco, 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)
from core.
I have been having the same issue also. I even removed my protect from early access and it still alerts.
from core.
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?
from core.
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.
from core.
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 "allow_ea_channel": true
option in core.config_entries file that defaults to false
which can be easily changed with a text editor... BUT... DISCLAIMER: You can easily break HA by modifying that file, and who knows maybe even end up needing to reinstall so only do this at your own risk and without expecting HA developers to fix your issue (I can't speak for them, but I'd say "you are on your own" is most reasonable here).
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.
from core.
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
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.
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
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.
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).
If anyone chastises you for something like this, that's their problem, not yours.
from core.
@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.
from core.
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...
from core.
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.
from core.
Related Issues (20)
- Smartlife (Tuya) missing entities/scenes HOT 1
- Blocking call inside the event loop by integration ZHA HOT 3
- TP-Link Smart Home - P110 plug failed to setup HOT 2
- TP-Link plugs have cryptography error after upgrade HOT 2
- Helper - Derivative Sensors - Metric Prefix Field HOT 3
- Error in logs when switching on washing machine HOT 2
- Unifi protect unknown error (aiofiles) HOT 1
- Unifi Protect - not naming entities uniquely or consistently in format HOT 1
- From time to time tessie integration won't fetch data until I open tessie app in the phone HOT 13
- bug in automation trigger id HOT 6
- Tibber integration connection errors after power off HOT 2
- Metoffice integration Unit of measure sensor.met_office_gogerddan_visibility_distance_3_hourly HOT 2
- Renault integration battery_avaible_energy disappeared HOT 2
- diivoo single water timer don't start from home assistant HOT 2
- HomePod Remote cannot turn on HOT 6
- Unit for entity changed but then statistics does not reflect it HOT 3
- Lovelace cast dashboard to Nest Hub does not render HEVC camera HOT 1
- 2024.7.2 still cause requiring arm code issue with aqara M2 hub HOT 3
- [Unifi] If url returns 403 the extension can't be reconfigured. HOT 5
- Cant connect to matter devices working in Alexa , Apple home and Google home wifi and Thread HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from core.