Closed tethlah closed 10 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)
@home-assistant close
2.9.x is supported in 2023.11.3. The scheduling mode itself is a new feature and Github is not for requesting new features. You will need to make a post on the community forums
Let me repeat since you did not seem to read the previous message:
2.9.x is supported in 2023.11.3
Protect 2.9.42 changed the way it defines recording modes. I didn't change anything in my configuration, the settings I had prior to protect updating were exactly the same, the problem is that Protect is now reporting a different value than what it previously reported.
So no, Protect 2.9.x is not supported in 2023.11.3 as Protect 2.9.42 changed a reported value that your addon is throwing an exception for that is causing the addon to not load. Now, if you want to say "2.9.41 and below is supported in 2023.11.3" that would be a true statement, but 2.9.x is categorically false.
2023.11.3 isn't released yet. It has the the updated pyunifiprotect version for the recent protect changes.
LOL my bad, supervisor is on 2023.11.3 so I got confused.
The problem
Unifi Protect has updated how it's scheduling works, the new mode isn't supported in the current protect integration. I had to switch all my cameras from schedule to always record in order to reload the integration and get it working again.
What version of Home Assistant Core has the issue?
2023.11.2
What was the last working version of Home Assistant Core?
2023.11.2
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
It's literally just a new recording mode that's causing the problem. The error is "schedule is not a valid RecordingMode", "Unknown video mode: sport" and "Unknown video mode: slowShutter".