Google home thermostat support

[bruceyeg]

I have another thermostat problem. I have two Insteon thermostats  which I call "main thermostat" and "bedroom thermostat". The first controls my furnace and is hard-wired. The bedroom thermostat is battery powered.

 

GH works fine with the main thermostat, but it does not work at all with the battery powered thermostat. If  I use the buttons on the bedroom thermostat to change the set points, it takes about 6 seconds before the change appears in the admin console and in the Agave app on my phone. But every time I ask GH about my bedroom thermostat, it always says "I'm sorry. There was an error."

 

Is this a timeout problem? Maybe the battery powered thermostat is responding too slowly.

[bruceyeg]

My wireless Insteon thermostat problem vanished after I re-linked the Portal to Google Home. Now my thermostats work perfectly.

[bmercier]

My wireless Insteon thermostat problem vanished after I re-linked the Portal to Google Home. Now my thermostats work perfectly.

 

Thanks for the update. I'm glad to see the problem is resolved!

[bruceyeg]

I'm having trouble setting the temperature with my Insteon thermostat. Suppose my thermostat is in the Program Auto mode, and the heat and cool set points are 19 and 27. Suppose it is cold outside and my furnace has warmed the house to 19.

 

Now, suppose I want the house to be 20, If I tell Google to set the temperature to 20. Google will then change the set points to 16 and 24. The midpoint between these numbers is the 20 degrees that I requested. However, because it is cold, my house will cool down to 16.

 

The problem is that to change the temperature I have to change the heat set point.  Instead, Google is shifting the heat and cold set points so the middle of that range is the temperature I asked for. To get my house to warm up to 20, I would have to tell Google to set the temperature to 24. That would raise the set points by 1 degree to 20 and 28. My furnace would come on and warm the house to 20.

 

My thermostat is using "Program Auto" mode. If I switch it to "Heat" mode there is no problem. However, I need to have my thermostat run a program. The only modes available for my thermostat are:

 

off, heat, cool, auto, program auto

 

The problem would be solved it I could put my thermostat into a "Program Heat" mode. This mode must be available for other thermostats because it appears as an option in the Admin console. However, my thermostat doesn't have that mode. The only way to run the thermostat's program is to use "Program Auto" mode.

 

The problem would be fixed it I could say

 

"OK Google, set main thermostat heat set point to 20"

 

If I give this command Google says "Sorry. I do not understand".

 

Can you make this work?

 

Another way to solve the same problem is to tell Google to raise the temperature of the main thermostat by 1 degree. That does work. However, I would still like to be able to tell Google what temperature I want and that should also work.

[bmercier]

When asking to change the setpoint, just ask google to set the heat setpoint.

 

Example: Ok google, set heating to 19 on <thermostat>

 

If you are in Auto, only your heating setpoint will be set, and it will have the temp requested.

 

Benoit

[bruceyeg]

Thanks. The key words to use are "set heating" and that always works. It changes the heat set point leaving the cool set point unchanged.

 

I also tried to use "set cooling" even though I don't have AC so this doesn't really matter. This command causes erratic unpredictable results.

 

For example, my set points were originally 20 and 28. I said "OK Google. Set cooling on the main thermostat to 29 degrees". My Google Home changed the set points to 25 and 33. This is not at all what I want.

[bmercier]

There must be other ways to say it. At the API level, I can assure you this is supported.

 

Unfortunately, the speech recognition is not perfect,

 

Benoit

[Ebrune]

Hello all,

 

Thank you everyone for all of the information. Unfortunately it seems I have a similar issue regarding different UOM. My thermostat is set to 71 and 79 on Program Mode. When I ask Google Home what is the indoor temperature it correctly states the indoor temperature is 70 degrees with a set point of 71 and 79 degrees. So Google Home is reading in the correct unit of measure at this point. When I ask Google home to set the heating temperature to 72 or increase the temperature by 1 degree it replies that it has adjusted the temperature with no problem. When I go to look at the display on the thermostat the heat set point says OF, what I assume is off, and the cool set point is in Celsius reading 26 or 27. I tried removing the device from ISY Portal and re-adding it then unlinking and linking to to Google Home again. But the problem persists. Just seems strange that Google Home is speaking the same language as the thermostat until I change the temperature and things go sideways.

 

I appreciate any thoughts on this one.

 

Thanks a bunch,

Eric

Edited January 2, 2018 by Ebrune

[James Peterson]

Hello all,

 

Thank you everyone for all of the information. Unfortunately it seems I have a similar issue regarding different UOM. My thermostat is set to 71 and 79 on Program Mode. When I ask Google Home what is the indoor temperature it correctly states the indoor temperature is 70 degrees with a set point of 71 and 79 degrees. So Google Home is reading in the correct unit of measure at this point. When I ask Google home to set the heating temperature to 72 or increase the temperature by 1 degree it replies that it has adjusted the temperature with no problem. When I go to look at the display on the thermostat the heat set point says OF, what I assume is off, and the cool set point is in Celsius reading 26 or 27. I tried removing the device from ISY Portal and re-adding it then unlinking and linking to to Google Home again. But the problem persists. Just seems strange that Google Home is speaking the same language as the thermostat until I change the temperature and things go sideways.

 

I appreciate any thoughts on this one.

 

Thanks a bunch,

Eric

 

I can not be sure, but this sounds like something that may have been discussed before.  It may have something to do with the stored temp preference.  You may have to remove and re-add the device to the ISY portal setup. 

[Ebrune]

Yes, that's what I thought as well. I did as you said and removed it from ISY Portal and added it again with no luck. After adding it again to ISY Portal I then unlinked/linked to Google Home with no success.

[bmercier]

Yes, that's what I thought as well. I did as you said and removed it from ISY Portal and added it again with no luck. After adding it again to ISY Portal I then unlinked/linked to Google Home with no success.

 

To diagnose this one, I would need a copy of /rest/nodes/<your thermostat address>

 

Please PM me that, along with your uuid. I may need to look at the logs as well.

 

Thanks,

 

Benoit

[Ebrune]

Will do, thanks.

[bmercier]

Hello all,

 

Thank you everyone for all of the information. Unfortunately it seems I have a similar issue regarding different UOM. My thermostat is set to 71 and 79 on Program Mode. When I ask Google Home what is the indoor temperature it correctly states the indoor temperature is 70 degrees with a set point of 71 and 79 degrees. So Google Home is reading in the correct unit of measure at this point. When I ask Google home to set the heating temperature to 72 or increase the temperature by 1 degree it replies that it has adjusted the temperature with no problem. When I go to look at the display on the thermostat the heat set point says OF, what I assume is off, and the cool set point is in Celsius reading 26 or 27. I tried removing the device from ISY Portal and re-adding it then unlinking and linking to to Google Home again. But the problem persists. Just seems strange that Google Home is speaking the same language as the thermostat until I change the temperature and things go sideways.

 

I appreciate any thoughts on this one.

 

Thanks a bunch,

Eric

 

Please try this; ask "Ok google, sync my devices", then try again to control your thermostat.

 

I have investigated and here's what I saw;

- In ISY Portal, your thermostat is correctly detected as using Fahrenheit (The spoken records states that the thermostat works in F).

- Google Home requests are coming in with values in the Celsius range

 

Here's what I think happened:

- A long time ago, there was a bug where thermostat added to ISY Portal GH spokens had a UOM incorrectly detected.

- When you sync with GH, that UOM is passed to Google

- When requests come in, they come in in that UOM.

- I believe you removed and re-added your thermostat, which made it detect correctly the UOM as F, but then did not re-sync with GH. This would explain why requests that you speak in F are passed as C.

 

Benoit

[Ebrune]

Hey Benoit,

 

Alright I asked Google to "sync my devices" and Google acknowledged it will now sync devices for Universal Devices. I then waited a minute or so then asked Google to "Set my thermostat to 71 degrees". Display on thermostat for heat unfortunately changed into Celsius again.

 

Eric

[bmercier]

Hey Benoit,

 

Alright I asked Google to "sync my devices" and Google acknowledged it will now sync devices for Universal Devices. I then waited a minute or so then asked Google to "Set my thermostat to 71 degrees". Display on thermostat for heat unfortunately changed into Celsius again.

 

Eric

 

 

I looked at the logs, and I see the sync with the correct uom set to Fahrenheit. Yet, whenever you make a request, Google sends degrees in celsius (there is no uom, but the values are in the celsius range, like these: 18.88888931274414 to 24.4444446563). I'm sure you did not say those numbers

 

I think there is a bug at google where the uom is not updated.

 

I would suggest to:

- Remove the thermostat from ISY Portal

- Sync, and make sure the thermostat disappears from the GH device list

- Add the thermostat to ISY Portal

- Sync again

 

You could also try to unlink and relink, but you will have to redo the room assignments.

 

Benoit

[Ebrune]

Still no luck. I'm starting to think I may need to find a workaround. Thanks for your help so far.

 

Eric

[bmercier]

Still no luck. I'm starting to think I may need to find a workaround. Thanks for your help so far.

 

Eric

 

Somehow, google is sending setpoints in celsius.

 

Perhaps they changed something and it now uses a preference somewhere?

 

Could you try "Ok google, change temperature to Fahrenheit"

 

Normally, that should only affect things like weather services. The UOM for a thermostat is normally sent when synching (and yours is definitely set to F, I double checked the payload).

 

Benoit

[Ebrune]

Yes, I tried that earlier today as well. It didn't affect anything. The interesting thing is when I ask Google to set my temperature to say 72 degrees GH even replies back "ok, setting the temperature to 72 degrees". Of course it could be saying one thing but doing another.

 

Eric

[bmercier]

Yes, I tried that earlier today as well. It didn't affect anything. The interesting thing is when I ask Google to set my temperature to say 72 degrees GH even replies back "ok, setting the temperature to 72 degrees". Of course it could be saying one thing but doing another.

 

Eric

 

At the API level, I confirm that it passes the temperature in Celsius.

 

Then, to get to the bottom of it, I would suggest to unlink and relink.

 

Benoit.

[Ebrune]

I unlinked/relinked. Unfortunately I am getting the same results.

 

Eric

[bmercier]

I unlinked/relinked. Unfortunately I am getting the same results.

 

Eric

 

Ok thanks for the feedback.

 

I took another look at the logs, and the setpoints are still passed in celsius.

 

I noticed something strange though - When  GH queries the thermostat, the temperatures returned are in the celsius range. There's no reasons for this, unless the thermostat is working in celsius. I'm lacking the time for further investigation as I'm leaving on vacation early tomorrow morning. I will look into this in about a week.

 

Benoit

[bmercier]

@EBrune, I investigated further, and the query works as expected. 
Contrary to what I said above, it's normal that temperatures are passes in celsius at the API level.

 

I contacted Google Home support. Please try this;

Open your GH app, click on the upper left icon, and go to More settings/My Day/Weather

Set it to Fahrenheit.

 

Please let me know if that helps.

 

Benoit

[bmercier]

@Ebrune, forget it, I found and fixed the problem.

 

The issue was specific to the Auto mode, when using F.

 

Benoit

[handyman300]

I am having the same problem.  I have an ISY 994i with an Insteon thermostat.  I was using the Amazon echo to control it and it worked fine.  It reported the thermostat setting in Fahrenheit and settings were made in Fahrenheit.  

I recently switched to google home.  Same ISY Portal, same settings.  The thermostat with Google Home now reports in Celsius and settings have to be made in Celsius.  

I have tried everything but cannot get the thermostat to work in Fahrenheit..

[bmercier]

16 hours ago, handyman300 said:

I am having the same problem.  I have an ISY 994i with an Insteon thermostat.  I was using the Amazon echo to control it and it worked fine.  It reported the thermostat setting in Fahrenheit and settings were made in Fahrenheit.  

I recently switched to google home.  Same ISY Portal, same settings.  The thermostat with Google Home now reports in Celsius and settings have to be made in Celsius.  

I have tried everything but cannot get the thermostat to work in Fahrenheit..

Try this:

1. In ISY Portal: Remove the device from your GH list, and re-add it.
2. Sync your device with GH (With button in the UI, or vocally)

The thermostat uom is detected by ISY Portal when it is added to your GH list of devices.

Benoit