[Alpha] Community-maintained Google Home integration

Hello, I have tried various ways to do this and can't seem to accomplish it. I understand if this may just be how it is due to Google Home but I figure perhaps someone here has done it successfully before I declare defeat :wink: . Essentially, I have 2 Nest Protects (fully migrated over to Google Home). Meanwhile on the Hubitat, I created a set of Virtual devices (Smoke Detector, CO Detector, Presence, and Motion) and exposed them via GHC. For the virtual Smoke Detector, I have setup Google automations to have the smoke alarm Nest Protect be the trigger and open/close of the Virtual Smoke (as the action) and it works just fine. However, I cannot seem to do the same pattern with the Virtual CO (Google indicates that device as greyed out and "Support coming soon"). I have tried various ways to configure it in GHC and to no avail. Any suggestions? Currently, in GHC, I have that Virtual CO configured as Device Type=CO Detector; Google Home device type=Carbon Monoxide Sensor; Traits=Open/Close, SensorState. Previously, I tried removing the SensorState trait and it still didn't change matters as I know that the actual field doesn't exist in Hubitat's virtual CO detector driver.

PS> I know that the Presence and Motion of the Protects aren't exposed in Google Home, but I like to be thorough and represent my devices as accurately as possible and with wishful thinking perhaps there would be a way that I later figure out how to get those working too :D.

is anyone else getting lots of errors recently?

1 Like

Yep, I've been seeing the same for about a month now.

1 Like

Interesting, I haven't seen anything like that myself. Is it consistent, or does it only happen intermittently?

Seems to happen every day

Another question. Why do I get test returned false:

That message just means that the app is waiting for the device to reach the desired state before reporting to Google that the action was successful. I assume you have a fade time on that dimmer so it takes a few seconds to reach full brightness.

1 Like

I have migrated to a C8 Pro hub. I can't get Google Home to connect. I have tried everything that Gemini and Chat GPT has suggested. When I try to update my hub ID in the Developer tool I keep getting this error.
Error creating account linking for project(hubitat--community-82d74) due to (INVALID_ARGUMENT: com.google.identity.accountlinking.error.AccountLinkingException: generic::INVALID_ARGUMENT: privacy_policy_url cannot be empty [type.googleapis.com/util.MessageSetPayload='[google.rpc.error_details_ext] { message: "privacy_policy_url cannot be empty" }']).Please try saving again.
Does anyone have any suggestions?

I haven't seen that. Can you give more information about exactly where you saw that message, and the steps you took up to that point?

It's been a while since I changed hubs, but IIRC there are three things you need to update when moving to a new hub:

  1. The OAuth Client ID
  2. The OAuth Client Secret
  3. The Cloud Fulfillment URL (which contains both the hub ID and the app instance ID, both of which will likely change)