If you want arbitrary names then the Toggles trait is what you want. Otherwise I would recommend thinking in terms of what the device represents and adding appropriate traits (i.e. TransportControl for a media player, etc) rather than thinking in terms of what you actually have. It may make sense to create some extra virtual devices and use Rule Machine or something to map your logical devices to appropriate button presses.
I'm seeing this error in the log for Google Home Community and my Google Home app on Android is showing every Hubitat device as offline.
I have just recently attempted modifying my Google Home Community app so something there may be messed up. I wound up adding a new type, adding a new Google API service as directed by the instructions. I already had set up something similar in the past. Perhaps more than one is a problem?
1 Like
First all thank you for your amazing work, I got it to work for my garage door and it worked perfectly. My question is can I just require a PIN for voice and not for app use? I want a PIN to open the garage door with the voice command, but not if i'm inside the app.
Make sure you do at least one manual sync first to register your app with Google. If you don't do a manual sync then Google won't know about your app and can't do an automatic sync.
Sadly that's not possible. There's no way for the Hubitat app to differentiate between a request that came from the Home app vs one that came from a voice command.
I got an email about a Migration: Smart home Actions migration overview | Cloud-to-cloud | Google Home Developers
Do I need to make any changes? Perhaps the installation instructions will need changes?
I could be misunderstanding something here, but the second part of this setup process for a new build seems to be deprecated. When I try to go to console.actions.google.com, it informs me that Conversational Actions have been sunset. It appears that the sunset started June 13 2022, and it went into deprecated state one year later. Is there any word on how to set this up since the deprecation?
Looks like it still works, navigation and sites have changed. new site is https://console.home.google.com/ Instructions can be followed still more or less.
1 Like
I have the same offline issue - how can I perform a manual sync?
Either swipe down in the Google Home mobile app until the little refresh arrow appears or say "Hey Google, sync my devices" to a Google Assistant device.
2 Likes
Did you ever find out what was causing this error, I see the same error in the logs after I make changes and then save the settings in the app?
Everything seems to be working fine, so I really didn't pursue it any more. More just curious if I can just continue ignoring it.
Make sure you've done at least one manual sync. That will register your hub ID with Google so that the app can automatically requests it to sync when changing things.
Just so I am clear the manual sync is going into the Google Home app and telling it sync devices correct?
Correct. Do the "swipe down to refresh" gesture on the devices page in the Google Home mobile app.
Yeah that is what I did. It only shows the error when I hit done/save in the GH community app. I don't see it normally.
i would love to know how you got this to work. i am stuck at conversation actions. can anyone please spend a minute looking at this and giving me some guidance? Troubleshooting Google Home Integration Issues 🛠️ | Loom
@mbudnek i would love to know whether this is still supposed to work with Google having deprecated conversation actions. loved my google working, but i switched google accounts and cannot resetup what I enjoyed so much. please spend a minute looking at this and giving me some guidance? Troubleshooting Google Home Integration Issues 🛠️ | Loom
Smart Home actions are still fully supported. I haven't updated the instructions for Google's new Developer Console that replaced the old Actions Console, but it's fairly similar. The basic flow is to go to "Cloud to Cloud -> Develop -> Add Integration -> Next -> Next". All of the account linking and fulfillment URL options are there. The biggest change is that you have to select all of the supported device types, but you can just select all of them (ctrl+a in the dropdown will select everything).
yup. got it to work!!!
@mbudnek
Recently migrated my system from C-5 to C-8 and while the integration and associated devices and rules copied over properly, it looks like Google is not actually connected to the new Hubitat. If I re-enable the integration on my old C-5 it still works there, so I'm guessing there is something I need to do to get it to connect to the C-8 instead of the C-5, but I'm not sure how to do that.
At a minimum you'll probably need to unlink and re-link the integration in the Google Home mobile app. Before that make sure to check your OAuth client ID and secret and your fulfillment URL. I don't remember if those changed or not when I migrated my hub.
