Skip to content
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

Closed
tylerwatt12 opened this issue Jul 5, 2022 · 6 comments
Closed

Camera rename, camera component error in HA #175

tylerwatt12 opened this issue Jul 5, 2022 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@tylerwatt12
Copy link

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.

Screen Shot 2022-07-05 at 11 41 07 AM

Screen Shot 2022-07-05 at 11 41 17 AM

@kramttocs
Copy link
Collaborator

Thanks. I've seen this one myself but haven't tracked it down.

#157 (comment)

@kramttocs kramttocs added the bug Something isn't working label Jul 5, 2022
@shawnhaywood
Copy link

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.

@navydavid
Copy link

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.

@navydavid
Copy link

I HAVE found a workaround for the issue:
The easy way is to delete the integration and start over, but I found that kind of annoying as I've got a lot of automations on them in addition there's a bunch of HA clean up that would have to occur.

The workaround:

  1. I changed one settings and clicked submit. It told me where it was upset. (CameraName) is not a valid entry.
  2. I went into Blue Iris and CREATED that camera, just cloning it of off another camera temporarily.
  3. Restart HA (you can probably just reload integrations)
  4. You'll have to do this process a few times, each time you'll find where the "problem object is" sometimes, it's cause you cloned camera doesn't have an audio feed, so you'll need to enable it. Go back and start over.
  5. Eventually, you'll be allowed to save the config.
  6. THEN you'll to UNMANAGE in HA all the objects you created. (In each section.)
  7. Verify that there's no more issues (you can change something on the fly)
  8. Then delete everything you don't want in Blue Iris.
  9. Then re-validate.

@peter--s
Copy link

peter--s commented Oct 8, 2022

Thanks. I've seen this one myself but haven't tracked it down.

#157 (comment)

See home-assistant/frontend#10608, which also features a nice workaround (editing /config/.storage/core.config_entries).

kramttocs added a commit to kramttocs/ha-blueiris that referenced this issue Dec 4, 2022
… 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...)
@kramttocs kramttocs self-assigned this Dec 4, 2022
@kramttocs
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants