-
Notifications
You must be signed in to change notification settings - Fork 75
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
Cannot Delete Orphaned Devices #620
Comments
I can confirm the same behavior in 1.9.15 running on 2022.12.8 Let me know if I can assist in any way. |
I believe I have the same issue and have been for a bit, but haven't been able to find any discussions on it or dig into it. The only difference between the dupes listed on my setup seem to be "Manufacturer" "Google Home" vs "google_home". Seems to have led to getting odd responses to assistant commands like asking to turn off lights, which it does, and then responds that "I can't seem to reach (x) lights. Sorry, it looks like (x) things aren't available right now". Which I assume are the dupes that no longer exist. |
I have the same issue, and have for at least 1 year now. Currently running v1.10.0, and with the latest home assistant OS. |
Same issue here since over a year. |
Probably there is a way to remove such devices on integration level which someone needs to implement. But there is hacky way if these devices really bother you. Simpler way is probably removing the integration and adding it again. But make sure you can get master token before doing that. |
Describe the bug
After moving some devices around, removing them from the google home app and re-adding them. The integration hasn't forgotten about them. The cannot be deleted. This clutters the UI and leads to confusion.
Version of the integration
If you are unsure about the version check the github release here.
Logs
The text was updated successfully, but these errors were encountered: