Trying to update devices in Google Home and I get an error every time “Something went wrong. Try again”
Existing linked devices seem to be working still.
I go through the normal sequence of
Have tried several times including rebooting the hub.
[null] is linked
Something went wrong. Try again
Sorry for the confusion. You do not need to reauthorize the Hubitat service to add new devices to the Google Home app. Once you have established the connection to your Hubitat hub, and have added some devices, then you need to go into the Google Home app in the Hubitat interface and add new devices to the previously authorized devices. See this section of the Google Home integration document: Google Home | Hubitat Documentation
Once you select new devices, they will appear in your Google Home app at the bottom of your Google app under "Linked to you" section.
That feature does not work for me as advertised. I've had to add new devices through the GH app by forcing a repolling of Hubitat since the GH integration redesign.
I currently have a few devices (two are lights) checked in the Google Home app not showing up in GH, not even as "linked to you".
I went through and unchecked all the new devices and and still getting warnings and errors in the logs for Google Home
I am unable to replicate this issue by using the proper method (going into Google Home app in the Hubitat interface) or by refreshing the token on the Google side. But our engineers are further looking into it.
To be clear the "proper method" (selecting devices in the Google Home app on Hubitat and waiting for them to show up as "Linked to you") has never worked for me.
I have always had to go into Google Home and have GH's "Works with Google Home" Hubitat devices integration "Check for new devices".
Now neither method works for me and I am getting Google Home app errors in the Hubitat logs. Existing linked Hubitat devices continue to function in Google Home as expected, but I cannot add any new/additional Hubitat devices to Google Home.
Maybe you have authorized some devices that are not compatible with Google Home in a prior version that wasn't checking for device compatibility. It's the only thing I can think of. Do you have lots of routines in Google Home? May need to remove and readd the integration.
I have no routines in Google Home. I use it simply as an interface to do manual on/off from mobile devices. All automation is done exclusively on Hubitat.
I've tried unchecking all not already listed devices in Google Home and it has not resolved the errors. FWIW, this started with the 192 release for me. Prior GH adding devices using the Google Home app was working as I expected.
At this moment (retested) I currently only have Hubitat devices selected that are Leviton or Minoston Z-Wave, or Smart by Bond (community app integration). All devices that seemed to have worked fine in the past with Google Home. I am still getting the same warnings and errors (screenshots above) in the Hubitat logs.
Update: I think I found the cause of the errors.
I am using a community Bond Home Integration because the built-in Bond support had some limitations.
Only the fan devices cause the errors, if I disable the Bond fan devices in Google Home, Google Home app goes back to working as I expect. Note: the Bond lights do not trigger the Google Home errors and I can and have left them enabled.
My guess is that the improved Hubitat Google Home Fan support is expecting more device data then the community Bond driver exposes/populates? Is there a way to see what changes where made by Hubitat to the Fan interface to see what fixes would be needed in the community Bond integration driver?
Please enable debug logging in the GH app, then re-add the problem fan, then post the live logs from the GH app!, thanks!
@mike.maxwell (hit the wrong reply button, hence the edit to include a tag)
Enabled debug in the (Hubitat) Google Home app. Added one of the offending fans (Gazebo Fan) using the GH app interface and got these logs:
Another pass adding the device using the Google Home Mobile app (Add Devices -> Works with Google Home -> Hubitat -> Check for new devices):
The Warning (unknownError: java.lang.IllegalArgumentException: Text must not be null or empty) always follows getDeviceAttributes trait:FanSpeed on any of my three Smart by Bond fans (as managed by the community integration app linked above). Those are immediately followed by the Error syncResponse Error: {"error": {"code": 500, "message": "Internal error encountered.", "status": "INTERNAL"}}.
can you send me a link to the bond integration that you're using?, I don't think its filling out the supportedFanSpeeds attribute, also a screen shot of the driver current states for the fan in question
It's one of Dominick's -- he put this Bond integration out long before the native integratioin was published, so it carried the water for many of us Bond users.
AFAIK, it hasn't been maintained by anyone since he stopped using Hubitat quite a while ago.
well that integration's not going to work with fans, it's setting all fan types to dimmers and switches.
Based on other reports, dman is no longer an active member of the Hubitat community having moved on.
I was using the Hubitat native/built-in app for Bond and ran into some annoying limitations, the details of which I since have forgotten. Maybe I'll have to fork his code and see if I can fix the driver for fans to expose itself as a proper fan and to report correctly when queried by the Google Home and other apps.
Until the .192 Google Home updates, that Bond integration was oddly working as expected for all my use cases. What's really funny is the .192 update FIXED another Z-Wave fan driver I am using that didn't as-was work with the older Google Home app integration.
It looks like his original development process might have left some legacy code in some of the driver files. I'm just guessing based on some basic troubleshooting but the Smart by Bond device is exposing itself as a single entity, and I bet he wrote the original fan driver that way before splitting out light control as its own child device.
curl -H 'contentType: application/json' -H 'BOND-Token: XXXXXXXXXXXXXXXX' http://192.168.50.183/v2/devices/1
{"name":"Gazebo Fan","location":"Backyard","type":"CF","actions":["TurnOn","TurnOff","TogglePower","SetSpeed","IncreaseSpeed","DecreaseSpeed","TurnLightOn","TurnLightOff","ToggleLight","SetBrightness","IncreaseBrightness","DecreaseBrightness","CycleBrightness","SetTimer","BreezeOn","BreezeOff","SetBreeze"],"_":"ce0213b3","__":"9828f715","state":{"_":"3475c60a"},"properties":{"_":"259520d0"},"skeds":{"_":"00000000"},"power_cycle_state":{"_":"51c4b4bd"},"addr":{"_":"6d75fb39"}}
Although I am staring at a Z-Wave fan control driver (that does work with the updated Google Home app) and I do not see how it responds to the FanSpeed trait. I'm new to authoring Hubitat drivers.
Thanks for looking at the community bond code. I'm still using this bond integration too. For me, the native integration wouldn't always set up correctly and when it did, would throw a ton of errors. I no longer remember the errors. I tried to get to the bottom of the errors but the community couldn't figure it out and support never responded to multiple requests for assistance.
I hear ya -- I started off with dman's Bond integration, but I got nervous when he departed the fix and no one else picked it up... I have a very vanilla (old) fan, so I'm fortunate that the native Bond app ended up working fine for me, but I feel for folks who need a bit more and are now stuck in the middle.
It would be a really nice win if Hubitat could shore up the native Bond integration.
As @oldcomputerwiz and you note, the HE Bond integration has been left alone for a while, other priorities taking precedence. Also works pretty well for me, as I have simple three-speed fans w/toggle lights. Maybe after the 2.4.0 release arrives and settles in there may be some time to attend to the HE Bond app.
Download the Hubitat app
