Rogue Google Devices

[Shaneb]

Hi,

I was removing some google devices via the app and some didn't fully remove now they just show as 'offline' I have 0 devices in the app and I have unlinked the account and re-linked it and can't remove them.

any help @bobbyD

[bobbyD]

Wow, I've never seen this one before. It sounds like Google has introduced a bug recently, as I was doing the same the other day and didn't happen to me. I'll try to replicate, here shortly. If you can provide more details to help me replicate, that would be great.

[andy.pober]

Did you try, "Hey, Google. Sync devices"?

[Shaneb]

I'll detail my process as much as possible.

1. go into Google Home app

2. uncheck device and click update

3. click done

4. go to googme home app on Pixel 3a

5. ask google to sync my devices
   -----repeat till all devices are gone
   I noticed some devices still there but display as 'not responding' so I went to the google home app in HE and added them again and tried to remove them, but instead it added it as a new device
   6)re-link hubitat in google assistant (+>add device>already have device setup etc..)
   -------Did nothing

6. unlink hubitat completely and relinked it
   8)hubitat displays 2 devices connected
   

   

7. I have no devices selected in google app in HE
   

   

8. there are 4 rogue devices in google home app that are not responding
   

   

9. when I click cog wheel the 'unlink' option is greyed out and gives me this message
   

   

10. syncing with google just says 'sorry the hubitat can only be synced by the user who added it in the google home app' - I am that user

11. the logs are showing the following
    app:3902020-09-03 03:10:55.133 pm infouninstalled...

app:3902020-09-03 03:10:39.726 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 03:10:39.719 pm warndeviceNotFound: Device '865' not found

app:3902020-09-03 03:10:38.554 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 03:10:38.550 pm warndeviceNotFound: Device '865' not found

app:3902020-09-03 03:10:18.657 pm infoupdated...

app:3902020-09-03 03:08:51.468 pm warndeviceNotFound: Device '865' not found

app:3902020-09-03 03:08:51.426 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 03:08:51.131 pm warndeviceNotFound: Device '865' not found

app:3902020-09-03 03:08:51.095 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 03:08:50.326 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 03:08:10.112 pm infoupdated...

app:3902020-09-03 03:06:27.363 pm infoupdated...

app:3902020-09-03 03:02:35.431 pm infoupdated...

app:3902020-09-03 03:00:04.270 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 03:00:01.226 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 03:00:01.187 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 02:59:48.790 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 02:59:42.657 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 02:59:35.505 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 02:59:35.504 pm warndeviceNotFound: Device '1100' not found

app:3902020-09-03 02:59:28.867 pm infoupdated...

app:3902020-09-03 02:50:50.437 pm infoupdated...

app:3902020-09-03 02:49:07.444 pm infoupdated...

app:3902020-09-03 02:48:04.202 pm infoupdated...

app:3902020-09-03 02:47:40.011 pm infoupdated...

app:3902020-09-03 02:46:46.121 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:46:38.328 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:46:38.228 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:46:03.305 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:46:03.082 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:46:02.972 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:46:02.537 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:45:56.906 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:45:56.314 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:45:55.642 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:45:52.168 pm infoupdated...

app:3902020-09-03 02:45:40.461 pm infoupdated...

app:3902020-09-03 02:44:36.810 pm infoupdated...

app:3902020-09-03 02:44:07.799 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:44:04.870 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:44:01.849 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:43:51.111 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:43:47.121 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:43:46.458 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:43:36.931 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:43:36.658 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:43:36.116 pm errorsyncResponse Error: { "error": { "code": 429, "message": "Resource has been exhausted (e.g. check quota).", "status": "RESOURCE_EXHAUSTED" } } , giving up for now

app:3902020-09-03 02:43:26.069 pm errorsyncResponse Error: { "error": { "code": 429, "message": "Resource has been exhausted (e.g. check quota).", "status": "RESOURCE_EXHAUSTED" } } , giving up for now

app:3902020-09-03 02:43:25.345 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:43:17.969 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:43:10.354 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:43:08.350 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:42:51.800 pm infoupdated...

app:3902020-09-03 02:42:16.584 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:42:06.030 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:42:05.964 pm warndeviceNotFound: Device '1030' not found

app:3902020-09-03 02:30:11.971 pm infoupdated...

--- Loading Past Log
app:10262020-09-03 03:21:58.657 pm infouninstalled...

app:10262020-09-03 03:20:09.076 pm errorsyncResponse Error: { "error": { "code": 403, "message": "The caller does not have permission", "status": "PERMISSION_DENIED" } } , giving up for now

app:10262020-09-03 03:19:59.030 pm errorsyncResponse Error: { "error": { "code": 403, "message": "The caller does not have permission", "status": "PERMISSION_DENIED" } } , giving up for now

app:10262020-09-03 03:19:16.778 pm infoinstalled...

--- Loading Past Logs... ---

app:10262020-09-03 03:21:58.657 pm infouninstalled...

app:10262020-09-03 03:20:09.076 pm errorsyncResponse Error: { "error": { "code": 403, "message": "The caller does not have permission", "status": "PERMISSION_DENIED" } } , giving up for now

app:10262020-09-03 03:19:59.030 pm errorsyncResponse Error: { "error": { "code": 403, "message": "The caller does not have permission", "status": "PERMISSION_DENIED" } } , giving up for now

app:10262020-09-03 03:19:16.778 pm infoinstalled...

[bobbyD]

This is what is expected to happen when you remove a device from Google Home app in Hubitat (anyone is welcome to email me to say hi)

And this is what is expected to happen when you add a new device from Hubitat is selected. Note, there is no need to ask Google to sync lights or anything.

I suggest removing the app from Hubitat and unlinking the service from Google Home, then go to below post and make sure that Hubitat doesn't remain linked on Google side.

Google home app

I am just dealing with this problem. I figured it out. I am assuming you connected at least once. The problem I had was Google Home shows Hubitat as unlinked but it really isn't. 1. Go to https://myaccount.google.com/ 2. Click on the security tab [Screenshot_20190718-215259] 3. Near the bottom find: [Screenshot_20190718-215259] 4. Find Hubitat and click on the unlink icon [Screenshot_20190718-215742] 5. Go back and do the normal Google connection steps. Mine worked after that.

[Shaneb]

Thanks @bobbyD I tried all that but it didn't work. For future reference I resolved it by creating a new home and moved all my Devices over and deleted the old one...although in hindsight I think leaving the home and being invited back would have solved it