Closed holdestmade closed 4 months ago
Hey there @angellusmortis, @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!
(message by CodeOwnersMention)
unifiprotect documentation unifiprotect source (message by IssueLinks)
@holdestmade are you sure you're running Protect 2.11.21? The error is showing the new "readlive" permission which was only recently added into the 3.0.10 EA version.
I had upgraded, then downgraded again and I have the same issue. It's already fixed upstream https://github.com/AngellusMortis/pyunifiprotect/commit/077e9c8120016e825d658cbbe1119971765557b0
Same here, I did upgrade to v3 but downgraded to 2.11.21 after it failed to start. I'll wait for the fix, thanks
I manually applied the patch on my install and it resolved the issue.
I manually applied the patch on my install and it resolved the issue.
How? Im stuck with the same problem. Downgraded and it still shows that error
EDIT: Oh I assume you dont run HAOS? Just pulled their container?
Is there some way to pull those updates into HAOS or no?
I run HAOS, I docker exec
'd a shell in the hass container and used vi to edit the file.
I am running HAOS and I have the same issue. I also upgraded and downgraded. Thanks
I run HAOS, I
docker exec
'd a shell in the hass container and used vi to edit the file.
You have core then? In HAOS I dont have those files as its built into hass itself. Or is still on the filesystem somewhere? Where was the file?
If we are lucky it might make it into ha 2024.3 tomorrow ? (or a subsequent rev 2024.3.x)
Upgrading and then downgrading is still not supported. Do not use EA.
@home-assistant close
And it will not be in the release tomorrow. The new EA version dropped on a Monday morning right before the beta ended.
HA will not be getting a update PR until at least this weekend because I do not have time to upgrade my Protect instance this week to test everything and add support.
Upgrading and then downgrading is still not supported. Do not use EA.
Well we know that now. We didnt know that before. Mine just auto updated because I had changed it to EA to update the network app. Nothing we can do to get around it? Guess this is my sign to stop using HAOS and goto core.
Restore a 2.x backup. Otherwise no. The docs are very explicit about not using EA versions if you depend on HA and do not want it to break.
This is essentialy my personal open source project. That means I work on it when I want and in my time. UniFi does not have an open API and does not give me any kind of special access so I cannot fix things before others have access to them.
Restore a 2.x backup. Otherwise no. The docs are very explicit about not using EA versions if you depend on HA and do not want it to break.
This is essentialy my personal open source project. That means I work on it when I want and in my time. UniFi does not have an open API and does not give me any kind of special access so I cannot fix things before others have access to them.
I did restore a 2 backup. thats what i mean.
Edit: well I guess I downgraded. thats not really the same
I understand that you cant do EA stuff. I dont think thats what anyone was asking here. We were all looking for a temp workaround or fix.
@CoreyJ87 it's not difficult to fix it for yourself. Figure out how to get a shell inside the homeassistant
Docker container. You can use something like docker exec -it homeassistant bash
on a HAOS shell. Then do something like vi /usr/local/lib/python3.12/site-packages/pyunifiprotect/data/types.py
and bang in the fix from https://github.com/AngellusMortis/pyunifiprotect/pull/354.
@CoreyJ87 it's not difficult to fix it for yourself. Figure out how to get a shell inside the homeassistant Docker container. You can use something like
docker exec -it homeassistant bash
on a HAOS shell. Then do something likevi /usr/local/lib/python3.12/site-packages/pyunifiprotect/data/types.py
and bang in the fix from AngellusMortis/pyunifiprotect#354.
I know how to exec into a docker container. Thats not the problem. I dont have a docker container. Im running HAOS. Which is not core. Which is what you're running. HAOS standalone(non docker version) does not have the files you have. If it does. Its in some other place that I dont know of.
➜ ~ uname -a
Linux a0d7b954-ssh 6.1.73-haos-raspi #1 SMP PREEMPT Mon Feb 26 10:59:01 UTC 2024 aarch64 Linux
If you want to discuss doing unsupported shit, I recommend doing it somewhere else. EA is not supported. Period. If you do not want your HA to break, do not use it. Encouraging people to use hacks and workaround to make it work just add more support burden and spam on me. Do it somewhere else.
I was trying to get the guy off your back, but I understand where you're coming from :+1:
If you want to discuss doing unsupported shit, I recommend doing it somewhere else. EA is not supported. Period. If you do not want your HA to break, do not use it. Encouraging people to use hacks and workaround to make it work just add more support burden and spam on me. Do it somewhere else.
Sorry, I didnt know it was continuing to ping you. Also, it broke accidentally cus we didnt know that it was unsupported(our own fault not yours). It also auto updated. So it was random. Jesus christ chill. Were not all just running EA against better advice. We ended up here because of outside influences. We tried to downgrade.
and @kudos thats in the docker container version only. Those files dont exist in the standalone one. Or they are placed somewhere else. but w/e im just moving to the docker container version
I've had the same issue (using HAOS on raspberry pi). Upgraded (automatically) to EA then downgraded (From what I remember, by recovering an old backup of my dream machine - but this was 2 weeks ago). I've since disabled all EA channels / auto-update.
When is the fix referred in https://github.com/AngellusMortis/pyunifiprotect/pull/354 expected to make it into HA Core?
Just a FYI, official release channel now has Protect version 3.0.22. Upgraded and lost connectivity to HA.
Came here to say the same. Updated to the latest Protect 3.0.22 (stable) today and that led me here after I lost all my motion sensors.
The problem
When trying to install (clicking on configure when it is auto discovered), after inputting username and password, get an unknown error message and the error in logs (see below). If I put an incorrect password in, it says invalid credentials
What version of Home Assistant Core has the issue?
2024.3.0b5
What was the last working version of Home Assistant Core?
2024.2.x
What type of installation are you running?
Home Assistant OS
Integration causing the issue
UniFi Protect
Link to integration documentation on our website
https://rc.home-assistant.io/integrations/unifiprotect
Diagnostics information
Not available as won't install
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
Running Protect v2.11.21 Official