Hello,

As of 12/30/24 I was able to get this node working with my T9 thermostat.  Helpful hints:

Trying to piece together documentation fixes/help from others into one place (these fixed my problems).

Developer, greatly appreciate your updating your documentation in all locations. Or at least make this post sticky. Thanks.

 

1. Documentation link to API website is no longer valid.  Ie. https://developer.honeywell.com is a dead link.  It is now: https://developer.honeywellhome.com

2. If you have an existing account already set up, and it has been a year or more since you set it up, you may be using the OLD Callback Url. If you are trying to replace a Honeywell Tstat, you may need to change/update the "call back url".

Or, you get the following error when logging into udi-honeywellhome-auth.azurewebsites.net 

 "code": 400, "message": "The redirect URL provided does not match the redirect URL registered for the app."

Then do the following:

Open https://developer.honeywellhome.com 

Login as normal.

Goto "My Apps"

Select your app, in my case it was called ISY Nodeserver

Hit the pencil edit button.

Change the Callback Url from the old one to the new one:

https://udi-honeywellhome-auth.azurewebsites.net/auth

Once that is corrected you can proceed to add the new Tstat.

 

Edited December 31, 2024Dec 31 by glenn_steiner
Added that I got it working

@glenn_steiner this plugin hasn't been updated in ages and assumed no longer being supported by the developer. Many users have moved to different brands of thermostats that use different plugins. If you're able to get it to work that's great! I tried with an older thermostat a couple of years ago and never got things sorted out so don't have it incorporated into the eisy/PG3x system. Which is fine as I don't really need to automate the thermostat much beyond it's abilities. 

Thanks, but I got it working.

2 hours ago, Geddy said:

@glenn_steiner this plugin hasn't been updated in ages and assumed no longer being supported by the developer. Many users have moved to different brands of thermostats that use different plugins. If you're able to get it to work that's great! I tried with an older thermostat a couple of years ago and never got things sorted out so don't have it incorporated into the eisy/PG3x system. Which is fine as I don't really need to automate the thermostat much beyond it's abilities. 

Thanks, but I got it working.  This is my way of letting others know it is still working and hints to get it working.

I would still like to get this working, but I have continued to get stuck when, after finding my thermostat and selecting it (still no "enable future devices" option as shown in the instructions) from azure website.  Because of this post, I decided to try again and, after four attempts, I received a response with user id.  I was finally able to configure the nodeserver and, suddenly, mine is working.  

We will see for how long, but thanks for the motivation.