You can control locks with a simple workaround. This works a bit nicer with Alexa becuase it doesn't have to respond with a different voice, but it's not bad.
You'll need a Stringify account and an IFTTT account.
Create a flow like this in Stringify. If you've never used Stringify, there's a trick to making certain flows and this is one of them. For unlock, the location should be added for security. For lock, you can just go from Google to IFTTT.
First you will add some kind of language for unlock [door] to the Google Assistant "Thing" in Stringify. Doesn't particularly matter because you'll define the exact phrase in a Google Assistant Routine to make it more natural to say. Then for the response, you will want to add something, otherwise Stringify will be overly verbose with it's own voice too, which is kind of jarring the first time you're expect the Google Assistant voice you have set. I like to keep it at "OK"
Next you tap on the IFTTT "Thing" and let it generate an ID for IFTTT, then just click OK. It's weird the first time you do it, but that will be an identifier in IFTTT for this Stringify Flow.
Now drag a connection between the Google Assistant "Thing" and the IFTTT "Thing". You have to make sure you do it in this order, otherwise the direction for IFTTT will be wrong and you can't complete the flow. If you make a mistake, just drag the "Thing" to the bottom and a trash can will appear so you can delete it, add it back and set it up again.
Lastly, you add the Location, but again this is just an added security measure so someone can't just say unlock my door. I'm not a fan of voice codes, because they can just be heard and used by anyone. Set the location to "Only if - I'm at a location" and then of course set it to your house. You might want to test without the location setting on and then add it later. Otherwise, it won't work until your phone leaves and re-enters the Geo-Fence. However, I have been able to simulate that by powering my phone off and back on.
Head over to IFTTT and create an applet as follows. If you've used IFTTT, this is pretty straight forward. Obviously, you must enable the Hubitat IFTTT application. In the Stringfiy service (IF This), you'll have a drop-down and in there you should see the name of your Stringfiy Flow with the ID shown in the Stringify IFTTT "Thing" used in your flow.
Set the (Then) to be the lock activation. I like to use virtual switches linked to a lock, but you can use a lock too. I have my lock actions, for example tied to virtual switches that trigger the lock to activate only if a rule is true, which requires the door contact sensor to be engaged.
Lastly create a routine in Google Assistant for when you say something like "Hey Google, Unlock the front door" then Google Assistant should send "Tell Stringify unlock front door" or whatever phrase you entered in the Google Assistant "Thing" in Stringify from Step 1.
Ironically Google responds properly to my Chamberlain Garage Doors with the MyQ integration. I can actually say "open/close" door x and it will respond correctly. Alexa did not work with "open/close" I had to say turn on/off instead.
They didn't just add support to for contact sensors and locks? I swear I saw them announce for that. It would also support the fact that contact sensors and locks just started showing up in my Google Home app from my SmartThings system a couple of weeks ago.
Has anyone had google home successfully set their thermostat? If I ask google to (or adjust it on the home hub- excellent interface) it says "sure setting it" and I see no errors in the google home app log on HE but the thermostat is never adjusted. At first I assumed it was adjusting the wrong set point (IE Air con when the heats on) but none get changed. Using the built in zigbee thermostat driver.
Both of my are ported so I don't doubt it. StelPro Ki for my baseboard heat and 2gig CT100 for the furnace/ac.
So I set my CT100 to the generic driver to see. Even more interesting. House initially set at 67deg heatsetpoint and 75deg cooling setpoint. Issue the command to set the "House Thermostat" to 66 degrees. I ended up with a heating setpoint of 63 (cooling didn't change) and a 'thermostatSetpoint" of 66. Looked on the actual thermostat and it's showing 63 deg setpoint. I asked for it to be raised to 67 again and the heatsetpoint went up to 64. themostatSetpoint went to 67.
If you have to use a ported driver to support your device, then you might try creating a RM rule to follow a virtual thermostat. Then get Google Home to adjust the Virtual Thermostat.
I have a Telguard GDC1 for my garage door. It pairs as a simple on/off switch. So I can say "turn garage door on" to open it. Google is smart enough to understand commands like "open the garage door". Very cool.
I've also noticed much flexibility in other commands. "turn on dresser lamp", "turn on the dresser light" "Turn the dresser lamp on" all result in positive actions.
As far as thermostats, I've given up trying to get Hubitat to accurately control my ecobee. I am leaving that connected to ST and they have native GH support so it works perfectly.
That was my thinking as well. Google home has native Ecobee support wich does almost everything I'd want to do with it (but not quite). There are some complex situations that I still use webCoRE for.
