Update to 0.65 - Google Assistant no longer controls thermostats

Installation Home Assistant OS
1

Prior to Hassio 0.65 I had Google Assistant working fine for lights, fans, Z-wave thermostats. After the update,all the devices still work in HA but the thermostats alone no longer work with Google Assistant. I can get an update if the thermostat is on/off and what the temperature is, so there is still some connection, but if I say “OK Google, set bedroom thermostat to 20 degrees” I get the error response “I’m sorry, but that mode is not available for your thermostat”. Has anyone else noticed the same problem?

TLDR - all worked fine, after the update to 0.65.4 can’t control the thermostats anymore

2

Same here. Using Xiaomi Aqara Sensors , exposed domain climate to Google Assistant.
Was working in 0.64 (but with an override via type, which is now obsolete)

3

Same here, and same error message from google.

4

Did you resync your devices in Google?

5

yup known issue unfortunately…hopefully it will get fixed soon.

6

yes type was removed and labeled as a breaking change in 0.65 release notes…I would bet official sensor support is around the corner now that Nest sells them.

7

Thanks, I searched the forums but didn’t check the issue log. I saw the change in the release notes for 0.65, but since my climate setup doesn’t use type I did not think that would be the problem.

8

FYI for anyone upgrading the problem remains open for v 0.66. I’m stopped at v 0.64.3 for the time being.

9

There’s been some discussion within the Gitbub Z-wave component thread, but it’s unclear when or if anyone can add back the voice control functionality. I’d prefer to stay with HA if possible, but while waiting to see if a change comes or trying OpenHAB, I’ve fallen back to my original workaround using IFTTT to make a web request. For anyone interested in the broad steps:

-Setup IFTTT in Home Assistant
-Enable Google Assistant in IFTTT

  • In your configuration.yaml google_assistant section remove any lines that expose the ‘climate’ devices you want to control, or set ‘expose’ to ‘false’ so that Google Assistant does not try to control them directly.

  • For each device set up an IFTTT Google Assistant applet
    If this - choose Google Assistant
    Trigger - Say a phrase with a number
    What do you want to say? Set the bedroom thermostat to # degrees

Then That - choose Webhooks

URL https://“yourduckdnsURLhere”:8123/api/services/climate/set_temperature
Method POST
Content Type application/json
Body {“entity_id” : “climate.THENAMEOFYOURZWAVEDEVICE_heating” , “temperature” : {{NumberField}}}

Use whatever the entity_id of your device is as shown in HA.

10

I solved it (controlling the target on my Z-wave enabled radiator valves AND getting the current room temperature from another sensor) by using the Generic Thermostat component. The genetic thermostat component is exposed to Google Assistant and I have an automation keeping the generic thermostat and the Z-wave radiator thermostat in sync.

11

Great, I had looked at the generic thermostat and it seemed like it would be hard to still control the thermostat manually without the automation overriding it (ie someone turns up the bathroom thermostat and it should stay up until the next automation trigger time) . Is your solution working like that?

12

My automation:
#Kids Room ClimateSync
- id: ClimateSync Kids Room alias: 'Climate Syncronization Kids Room' initial_state: True trigger: platform: state entity_id: climate.kids_room_temperature_generic action: - service: climate.set_temperature data_template: entity_id: "climate.thermostat_kids_room" temperature: '{{ float(states.climate.kids_room_temperature_generic.attributes.temperature) }}

I only have one way sync (we almost never touch any buttons, but use voice control and HA-automations a lot), but I guess it could be done with another automation going the other way?