[RELEASE] Beta 1 - version of Honeywell Home Thermostats (Lyric etc...)

⚙️ Custom Apps and Drivers
,
345

@WindowWasher, thank you for your prompt reply. You are awesome!

Regarding my use case, here are some clarifications:

  1. Hardware

Two Honeywell T-9, one for each floor of my house. They have several sensors each.

  1. What I want to do:

Turn off or change the temperature if a floor of my house is vacant.

  1. Implementation strategy:

I only have limited knowledge of programming and absolutely no experience with modern programming languages or the Honeywell API. Having said that, I would imagine three implementation steps:

a. Make sure to only implement a hold if necessary.
If you turn the thermostat on or off manually, it does not go into a hold. This implies that the hold is set either in the API or the driver.
If the hold is set in the driver, just remove that capability if only the status of the thermostat (on, off, ...) is changed.

b. Implement a strategy to remove an existing hold

c. Implement a strategy to query and manage holds (like temporary, permanent, or remove a hold)

Hope that helps. And thank you again!

346

Thanks for documenting what you are looking for. One question - Are you comfortable with Rule Machine and/or webCoRE? The reason I ask is that adding the ability to set/clear or query hold status should be pretty straightforward in the driver and then you could use either RM or webCoRE to do what you want.

For example, I currently use webCoRE to change my thermostat heating setpoint - 62 deg. at 9:00 pm and back to 68 deg. at 6:30 am. It's a pretty simple automation and would be easy in RM, too.

347

@WindowWasher ,

Yes, I use Rule Machine (and Basic Rules). No WebCoRE (yet).

348

Okay, great. Let me take some time to digest what you are asking for. I haven't looked at the code in ages, so I need to do that as well.

One question: Are you using schedules in the Honeywell Home app? It sounds like you might be, based upon your request.

349

Thank you, @WindowWasher , and take your time. No hurries, no worries... :grinning:

The above-mentioned step a) should only need some adjustments in the driver. Steps b) and c) would need some changes in my rules as well.

350

Are you using schedules in the Resideo app by any chance? It seems like it, as changes that the driver currently makes to holds could affect schedules in the Resideo app.

351

Yes, I do. And, that's what this is all about - if I turn a Thermonstat status to ON, I still want the schedules to run.

352

Has any progress been made on the ability yo clear the hold that gets set when you adjust the temperature?

353

I put a change in back in July to expose the Hold State in the driver and made changes to respect the value set if it was set outside of the app. Have you tried the updated code?

Edit: Sorry, I now realize that I didn't publicize the change. So I am not surprised that you didn't see that there was a change. Give it a try and let me know if you still have problems.

1 Like
354

I noticed that so I went and pulled it from Github. I see the new options in the device and it seemed to work but I was using the default token so only got one chance before it maxed out the token. Once I get my account approved and I have my own token I will give it a shot. Thx!