C-8 Pro can't connect to Google Home

[jaredeaves]

On the C-7, google home worked seamlessly. I could add everything and it just ignored anything that wasn't compatible. No issues at all.

I've upgraded to the C-8 Pro and can't get it to work at all. I don't want anything super complicated, just the same function as the C7. When I add Hubitat to my google account (works with google), it logs in successfully and asks for a list of devices to add. Once I click authorize, Google Home shows up on the app list in the hub but no devices sync.

When I try to re-sync my google devices through home, it says hubitat is not available. When I try to reconnect hubitat through the google account, it says "could not reach Hubitat. Please try again later."
When I restart the hub there is no change.
When I remove google from the hub and hubitat from my google account and try again, it's the exact same result.

When I do all of this and only select one or two devices, it works and they show up in google home. Then I have to go back into google home on hubitat and select two more devices, then go back to google home and resync devices, then go back to hubitat and select two more devices, then go back to google home and resync devices, then go back....you get the idea. It works until it doesn't, which is about halfway and then nothing works after that, even removing the last two I added and resyncing. Then I'm stuck with half the devices and have wasted hours going back and forth only to have it time out. I have somewhere around 200 devices so this takes forever and there's no guarantee that it will work or how far I'll get in that process.

Everything is on the same network and all worked before the C-8 Pro installation. Both have consistent internet and DHCP reservations, so they're always at the same address. The C-8 Pro is at the same address as the C7. There seems to be something different in the way the C-8 Pro handles or connects to google that isn't working.

I'm sure I'm missing some info, but I've tried so many things I probably omitting a few steps here. I have some routines that are triggered by google prompts and none of them work anymore since the upgrade.

Please help!

[Rxich]

C'mon you can't really expect a billion dollar corporation to get things right

I think I read a possible solution, delete your entire home from G-Home and start over. I know a real pain. Sometimes it's a single device that can cause issues, but locating that device could be lots of hours, easier to start over.

[jaredeaves]

We don't have that elaborative of a setup that I couldn't do that. But that does sound like a pain.

The part that flags for me though is that when I plug the c7 back in, everything works fine. So (for me), that points to a device on the c8 or the c8 itself rather than Google home being the issue.

[croweflight]

Google home works fine with my C8 Pro. But I did not migrate. So perhaps there is something to starting over. Maybe delete one device then put it back. Test

[jaredeaves]

It may come down to adding one device, but I just don't have time. With so many devices and flipping back and forth to resync devices each time. There has to be an easier way. I did migrate though so maybe that is the issue. At this point though, I've unlinked and uninstalled on both sides, so it shouldn't be holding anything.

Google just can't seem to see hubitat after the initial account linking.

[jaredeaves]

I guess I"m getting 404 errors on the logs. I didn't think I was, but after digging a little deeper, they are there. I also had a few 500 errors in the logs. Does this shed any more light on it? It doesn't help me, but I'm hoping someone can see something that's causing this issue. The night time not working is killing us.

"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:52:01.386

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:49:45.102

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:46:57.362

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:44:41.377

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:44:20.046

error

syncResponse Error: {
"error": {
"code": 500,
"message": "Internal error encountered.",
"status": "INTERNAL"
}
}
, giving up for now

app:25202026-01-04 06:44:19.876

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:44:09.902

error

syncResponse Error: {
"error": {
"code": 500,
"message": "Internal error encountered.",
"status": "INTERNAL"
}
}
, giving up for now

app:25202026-01-04 06:44:09.802

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:44:09.732

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:44:04.259

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:43:58.557

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:43:53.715

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:43:53.097

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:43:47.644

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:43:42.199

warn

unknownError: java.lang.IllegalArgumentException: Text must not be null or empty

app:25202026-01-04 06:43:36.838

info

updated...

app:25202026-01-04 06:41:33.505

info

updated...

app:25202026-01-04 06:40:00.614

info

updated...

app:25202026-01-04 06:35:27.398

info

updated...

app:25202026-01-04 06:34:51.291

warn

deviceNotFound: Device '1075' not found

app:25202026-01-04 06:34:51.001

warn

deviceNotFound: Device '1100' not found

app:25202026-01-04 06:34:40.744

info

updated...

app:25202026-01-04 06:33:40.564

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:33:22.983

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:33:20.077

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:33:10.380

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:33:05.344

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:44.509

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:44.421

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:44.397

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:44.343

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:44.335

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:44.261

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:44.243

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:44.044

warn

app 2520 has 10 pending asynchronous HTTP requests

app:25202026-01-04 06:32:44.021

warn

app 2520 has 9 pending asynchronous HTTP requests

app:25202026-01-04 06:32:43.993

warn

app 2520 has 9 pending asynchronous HTTP requests

app:25202026-01-04 06:32:43.970

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:43.963

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:43.963

error

reportStateResponse Error: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}
, giving up for now.

app:25202026-01-04 06:32:43.941

error

reportStateResponse Error: {

[jaredeaves]

WELL....IT IS FIXED....posting just in case anyone else has this issue, maybe it can help them. This one might be unique.

I think it's two different things that happened almost back to back. Quick summary...connection issue and a corrupt Lutron Device .

First, the 404, 500, and other connection errors: I did every combination of disabling GH on hubitat, unlinking from third party apps, clearing cache/data on GH, uninstalling GH and restarting phone, restarting the hub, etc. Basically everything all the threads said fixed it on other C8 hubs. The connection error never really went away. However, it would never get any further than the initial sync, then it would never connect again and would not carry the devices over. It would throw the error highlighted in green, then start throwing the blue highlighted error.

At some point, possibly out of desperation, I checked the modes in the drop down (had not done that previously) and changed the "device offline polling interval" to 5 minutes. All of the sudden, it started showing a huge list of "getdeviceattributes" in the log and was actually pulling info from the list. It failed, but at least it was seeing the devices at that point rather than just timing out.

I reset the offline device polling to disabled and started really watching the log. I added a few at a time and they were actually showing up at this point. I watched and kept getting "updated" until I got to the "den fan" and immediately got the java.lang error.

I took it out and just got "updated" with no errors. Added it back and got the same error again. Took it out and added the rest of the devices successfully. The den fan is a lutron fan switch (we have two). I compared it to the other fan switch and really didn't see ANY different except the info in the current state section. Literally everything else was the same (type/driver, settings, device info, etc.). The master fan had "Supported fan speeds" in the current states and the den fan (problem device) didn't.

I tried to changed it to a virtual fan driver, then back to lutron fan control. That didn't seem to work and didn't update the current state to match the other fan. I ended up (reluctantly) going into the lutron integrator and changing the device ID to an unused number, saving, then changing it back. That created another device, so I had to delete it, but once I re-saved the lutron integrator and turned on the fan, it gave me the supported fan speeds state and matched the other fan exactly (minus the unique device ID and network ID). Then I added it back into google home and it updated with no issues.

I now have google home working after a few days of headache, no solution in sight, almost two hours wasted on the phone with google tech support (useless), etc. They wouldn't have been able to track down the rogue device anyway, but it's finally back to normal!

The only other thing I did was change the hub name. It has parentheses in it. I don't think that was an issue, but I took them out in case that was causing an error like it does in some file names or addresses.

Thank you to those that have replied here and on other threads where I've asked questions. It's been a pain to track down, but all the info helped me get into the tracking mindset to figure it out.