-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Camera rename, camera component error in HA #175
Comments
Thanks. I've seen this one myself but haven't tracked it down. |
I'm curious what you did? Did you regenerate config files or reinstall the integration? I'm having a similar problem with same error message. |
I am having this issue as well: I have several groups that were no longer in Blue Iris after a recent crash. I was able to add those back in Blue Iris, but the camera name changes are still there. The issue seems to be that we're not able to remove "orphaned" items. They show in the line in the config, but not in the drop down. |
I HAVE found a workaround for the issue: The workaround:
|
See home-assistant/frontend#10608, which also features a nice workaround (editing /config/.storage/core.config_entries). |
… Cameras* The 'checked' list of cameras in the Options window is now filtered to only show those that exist in the list retrieved from BlueIris. Prior to this all previously selected cameras were showing which was causing an error of: ~The-Camera-Name~ is not a valid option for dictionary value @ data['allowed_camera'] elad-bar#175 elad-bar#157 *The same logic has been applied to all dropdowns (sensors, profiles, schedules...)
After renaming a camera in BI, the old camera name still shows in the "options for blue iris" page of the BI Integration.
I am unable to deselect the old camera name, and unable to change any settings because when I hit save, i get an error:
User input malformed: LivingRoom is not a valid option for dictionary value @ data['allowed_camera']
Where LivingRoom is the old camera name.
I know resetting the plugin would probably fix this, but I wanted to bring it to your attention.
The text was updated successfully, but these errors were encountered: