How to properly add a temperature sensor to google home

For all that want to know how to ask your google what the temperature is and have it read a temperature sensor or motion sensor with temperature, here it is.

  1. make a virtual thermostat for every device you wish to add, and
  2. after making said thermostat IMMEDIATELY add to google home BEFORE creating any rules that change values. I don't know why, but any rule set to change the value based on something else makes the google home incapable of recognizing it unless it's already been added.
  3. Use rule machine to create a rule as follows

Trigger; must be the temperature device in question, the easiest way to do it is to have the device changing the temperature value as a trigger.

Action: a custom action to set the value of temperature as a DECIMAL. And add %value% as the value, it will select the value of the trigger device. (Why trigger cannot be periodic schedule but must be device)
That's it. No documentation anywhere shows how to do this. But this is how.

DO NOT REMOVE DEVICE FROM GOOGLE HOME OR YOU WILL NEED TO DELETE THE DEVICE AND RULE AND START ALL OVER yerp. The alpha google home app just throws errors so this is the only reliable way.

2 Likes

Really? I have added all my temp sensors directly to the Google Home Community app with no issues:
image
Most of these sensors are Ecowitt, with some Hubduino thrown in for good measure. Here is an Ecowitt:


Even though the temperature reads with one decimal place, when I ask Google Assistant for the temperature, it rounds to the nearest degree.

Google doesn't recognize my temperature sensors. Two are z wave and 8 are iris v2 zigbee motion sensors that happen to have Temperature. This is the only way I can get them to reliably work. For anyone concerned.

1 Like

:point_up: This is the key portion to making this work. Using that community created Google Home integration instead of the built-in Hubitat integration makes a huge difference is what is possible currently.

Otherwise, @jatgm1’s solution is effective when using the built-in GH integration.

Ya I would but it threw and error on the second step and I'm not gonna deal with more issues than I have to. Plus manually getting an API key or whatever is just more of a pain in the a$$ then it needs to be. I'd rather just pair it and make virtual thermostats. I mean when something gets updated it's probably just gonna break.