Honeywell Wifi Thermostat (RTH9585WF)


#1

Hi all,

I did a search for this particular model and didn’t see anything posted. Not a huge deal, but I was hoping I could make a piston that would detect when it was turned “on” or “off.” There is an off selection and on would be “automatic” “heat” and “cool.” I ran a quick piston that said if the thermostat changed to …“off” then send me a notification, etc…

I watched the piston under the live logging and didn’t see the device being picked up on WebCoRE…my guess is because of the how it is integrated with ST, there is a problem with how it communicates? Not sure.

Anyone have any luck with monitoring these conditions?

P.S. I can control issuing a command to it through WebCoRE (on, off, etc…) just can’t pick up states as indicated above…


#2

When building the IF statement you get a dropdown to the right of the device selection for selection of ‘attribute’.

Can you post a screenshot of the attribute options you are being presented with.


#3

Sure:

19 AM

02 AM


#4

If you select ‘thermostat mode’ what options do you get?

Can you type ‘Automatic’ / ‘Heat’ / ‘Cool’ into the box at the bottom manually?

Example:

IF thermostat’s Thermostat Mode IS Automatic
Then
do stuff


#5

No, it only gives me the option to select from the pull-down…

The piston can see the status (e.g., ‘auto’) when the piston first starts up (= true), but that’s it…

Once I try testing with full logging (from auto to off, etc.) it doesn’t pick it up…

I think I know why…the ST thermostat ‘thing’ is not showing the updates…but the Honeywell app is…so, it seems clear ST is not receiving this information possibly? Therefore, it’s unlikely WebCoRE will see it, either…

Update: WebCoRE only picks up the change if I change the setting in the ST ‘thing’ for ‘thermostat.’

Each time I changed the setting there, it picks it up right away. If I update it from the thermostat itself and/or from the Honeywell app, ST doesn’t see it…so it’s not a WebCoRE issue, clearly, it is how the integration is between Honeywell and ST…

As an example, if I manually change the setting on the physical thermostat, it reflects on the Honeywell app…and vs. versa…

Oh well :frowning:


#6

Have you tried polling the thermostat?

with thermostat
Poll


#7

If this is the way you meant, it didn’t work…

55 PM


#8

The rest is just send me a notification, else, send another notification (e.g., off)


#9

We already know the trigger (mode changes to) doesent work as the message isn’t even making it to ST, let alone WC… the poll command needs to be triggered another way, maybe via change in temperature or something so it fires all the time.

The poll should refresh the state of ‘thermostatMode’ which in turn can trigger another piston.


#10

You have to select Thermostat as the attribute. You should be able to see in live logging what the different states it sets them for are. With my 6000 series thermostat it sets to “off” when the thermostat is idle, “Healthing/cooling to temp **” when you change the temp manually and to “Waiting for equipment” when it is heating/cooling automatically from an already set setpoint. This just started working about a month ago. It was a bug in Honeywell that it didn’t send the correct attributes when it was running. The pic below is what live logging reports for my thermostat when it’s heating normally.


#11

Mine doesn’t report off/auto etc…maybe it does if it is on in the sense that the HVAC is actually running…But, I’m trying to measure whether the entire thermostat is off or in auto etc (meaning, not that the HVAC is actually running, but what it’s state is…) Live logging doesn’t show it…thanks :slight_smile:


#12

You mean what setting you have set the Thermostat for (as in heat or A/C)? That is the Thermostat operating state. But why do you want to measure this? This isn’t being changed automatically is it? What are you actually trying to do with the piston? You can’t poll the thermostat because it’s a refreshable device not a pollable one. Also, how are you trying to measure it? It is only in a state. You can’t measure that state.


#13

It defaults to off if any smoke is detected. My goal was to get a confirmation that it was switched to off…


#14

This dormant thread inspired me when searching around for a way to get ST / WC working with a Honeywell 8000/9000 thermostat…and it now seems to be working. I posted this on a ST forum and wanted to also post it here just for continuity (and to see if @Robin had any thoughts). Yeah, the integration is hokey between Honeywell and ST but unless Honeywell would have the ability to trigger like a real device this might be the best we can do…dunno.

Here’s the post. The context is me wanting to force a Window AC unit on when the thermostat central AC turns on. Any feedback or improvements are appreciated!

<<
I confirmed that the delay is due to the polling cycle which is exactly 5 minutes. So, depending on when the Thermostat kicks on you might have up to 5 minutes delay before it reports that status to ST / WC. That’s not ideal and there doesn’t appear to be any easy way to change the polling frequency of the default Honeywell device so what I did was simply create a WC piston that is set up to run every 30 seconds and if the thermostat isn’t set to “off” then do a Poll. I also tried executing a generateEvent() and that also seemed to work but I ended up with Poll.

Regardless, it forced ST to actively poll Honeywell and now the window AC outlet (Zooz Power Switch actually) turns on within 30 seconds. The same worked with turning the temp up (forcing the AC off) or changing the Thermostat to another mode than cool. I went with 30 seconds because it discouraged setting an interval for more than 30 seconds but I am betting it would work if you went less…just a lot of junk traffic though.

Here’s the simple 30-second “AC Poller”:
image

Which then forces events (visible in ST logs) and feeds this “AC Tracker”:
image

Pretty crude but I am not sure offhand of a more elegant way of doing this short of using a local device to detect whether there is 24vac flowing to the AC circuit.