Honeywell T6 PRO Z-Wave Thermostat and Alexa

🛎️ Get Help
1

I finally included my new thermostat into the mesh and it works great. The only problem is that the Amazon Alexa skill does not work with this device. I have checked the box for the Alexa skill and deleted the link and renewed it several times but for some reason it is not recognized by the Alexa skill. All my other devices work fine. Is this a known problem? The device driver is set for the Hubitat included driver for the Honeywell T6 Pro Z-Wave Thermostat. Any help appreciated.

UPDATE: Did some research and this model does not share Z-Wave data. Other Honeywell stats do. I am going to keep it in the system though.....buyer beware....this device will not work with Alexa .....

2

The alexa skill doesn’t support thermostats yet

1 Like
3

I'm not sure what you're talking about when you say "share z-wave data". In any event, as @bcopeland said, the Hubitat Alexa skill doesn't currently support thermostats (any thermostat). Although there are simple workarounds. For example, I have the same thermostat (Honeywell T6 Z-wave Pro) and I can tell Alexa to:

  1. Set the thermostat to any temperature (between 65 and 75)
  2. Set the thermostat to heat or cool
  3. Turn on the thermostat fan

I do this using:

  1. 2 virtual switches and a virtual dimmer
  2. Rule Machine rules that match
    a) switch position to thermostat heat/cool and blower on/off
    b) dimmer level to thermostat set point.

Works very well ....

1 Like
4

Hello, New user here so please excuse any infractions of protocol. I have the Honeywell T6 ZWave and it will work with both Alexa and Google nest but I have to ask twice.
Me: "Alexa, set the thermostat to 74 degrees."
Alexa: "Sorry, thermostat is not responding."
Me: "Alexa, set the thermostat to 74 degrees."
Alexa: "Thermostat is set to 74." {And it does actually change}

Google just says ok and it does not happen. Ask it again and it happens correctly.

If I ask either device for the current temp that is set first to try and wake the stat it does not help. The correct temp is reported but still have to ask twice.

Trying to figure out how I make a log file available so you all can view it. Is that something typically done?

5

You can enable logging on the Device page on Hubitat Device screen by going to Preferences and ticking "Enable descriptionText logging". The Alexa App works fine now with this thermostat. You may have connection issues with the hub depending on signal strength. You also can enable "Hub Mesh" on the same device page.....I would add it to the mesh for that purpose especially if you have other Z-Wave devices on the hub.

6

@mrstanley Thanks for your quick reply.
Logging was enabled. I'm just asking how to I post logs so others can view without including them here in the chat window?
I turned on "Hub Mesh" and this did not correct the issue.
My HE and the stat are only about 6 feet apart with no obstructions.
Oddly when working with the Nest Mini, which still has the same issue as Alexa, after the second ask it remains working for some yet to be determined time. But if it's working with the Nest it does not fix the issue when walking over and asking Alexa to change the temp. It also must be asked twice.
It's very odd. Would it help to create a work around like a Rule that wakes the stat every 5 mins or something like that? Can the Honeywell T6 firmware be upgraded or does that happen automatically? Should I go find another driver?

7

I don't think you understand what Hub Mesh is.

Hub Mesh has nothing to do with z-wave or zigbee meshes. It permits users with multiple Hubitat hubs to seamlessly share devices between those hubs. This sharing has zero implications for z-wave or zigbee mesh networks.

You can turn this off unless you want to share your thermostat with another Hubitat hub.

Cut and paste a screenshot of the logs.

8

Still having the "ask twice" issue with both Alexa and Google. One thing I noted in the logs is that there is a parameter called thermostatSetpoint and one called coolingSetpoint. Anyone have any other ideas about what is going on? Can I create a virtual device or something as a work around? Any advice about how to debug?

Here's the two lines in the logs

dev:32021-04-07 12:36:54.494 pm infoThermostat thermostatSetpoint was set to 79.0°F

dev:32021-04-07 12:36:54.492 pm infoThermostat coolingSetpoint was set to 79.0°F

9

Solution: Created a rule to send the setThermostatMode to Cool every three minutes. This keeps the thermostat awake and ready to accept commands at all times. Never sleeps.

Issue: Behaves as though the Honeywell T6 goes to sleep every 3 mins and when the Alexa or Google issue the setPoint command it takes too long for the Honeywell to wake up and acknowledge the command. So Alexa says "Sorry, thermostat is not responding." Google just sends the command and does not wait to actually see if it was accepted.

I tried 5 mins and tested it. Five minutes is too long. Even after four minutes the thermostat does not accept the command. The count must be three. Three is the count.

image

Can anyone else confirm this behavior. Anyway to know if the thermostat is actually going to sleep or at least the ZWave function?

10

I'm trying to get my T6 Pro working with Alexa and every time Alexa just says the device didn't respond.

The T6 is recognized in the Alexa app and shows the set points and current temp, but it can't change the temp.

I've removed and re-added the device multiple times from the Amazon Echo Skill and have tried all combinations of the Respond immediately setting and the Advanced mode.

Any ideas?

Thanks,
Charlie

11

Turns out it doesn't respond when the thermostat is set to Auto. I can tell Alexa to change it to Cool and then I can set the temp. But I can't set a temp when it's on Auto.

Anyone know if this is normal behavior?

Thanks.
Charlie

12

Are y'all that were having response issues - eg, having to double-state an Alexa command - running your thermostats on battery only or on 24V power (with the C wire hooked up)?