I finally gave up on the Honeywellhome plugin which was controlling my nice ($) T10 thermostat. I searched the plugins and found Jimbo.Automates's HomeKit plugin. As the T10 is HomeKit compatible, I gave it a try. Spent all day yesterday with Jim and he got it working perfectly. So, no need to throw away your Honeywell thermostat.

I have the HomeKit Hub plugin installed and I was able to pair my Honeywell T10+ with the plugin and it is showing up as a node in the IoX node tree. However, it is just an entry and not functioning like a thermostat node. Any insight or assistance would be appreciated.

Edited September 10Sep 10 by hawk4974
Added pics

@hawk4974 I had the Honeywell plugin but couldn't get a developer account from Honeywell to use the plugin. I assume that they have stopped issuing them since they were bought by (or bought) first alert and are consolidating their apps and products. I gave up on the plugin.

I installed the HomekitHub V2.0.17 and have eight Honeywell T9 thermostats working with it. You need to use the professional version of HomekitHub and enable the generic frameworks in the configuration screen, both under custom parameters "generic_nodes_enable" (change to true) and under the last line of each Homekit pairing slot under "Create generic IoX control nodes (Professional)" (also set to true).

Discovery only worked for 3 of my thermostats with older firmware. The newer ones I purchased wouldn't show up in discovery, whether they were in Homekit Discovery mode or not. To get them to connect to HomeKitHub, I looked up the thermostats in my router to get their IP address and network name. I then manually added them in HomeKit pairing slots filling in slot number (use next available), HomeKit pairing code (choose Connect to Homekit on your thermostat and write down the eight digit number), the Name substring (network name: TSTAT-XXXXXX where XXXXXX is the last 6 digits of the mac address), LAN host:port (ip address + :80, i.e. 192.168.1.100:80), stable node key can be left blank, and final entry should be "true". Save the configuration, wait several minutes, and then restart the plugin. Sometimes, I had to restart several times.

Eventually you should get a notification when the plugin restarts either that it paired with a 12 digit address (which looks like a mac address, but isn't) or a notification that the device rejected the Homekit code. I am not sure, but I think that it won't make the initial connection until the thermostat times out and leaves Discovery mode, but then the Homekit code is no longer valid. If you get the second notice, then go back into the thermostat and get a new Homekit code (they change every time you go into Connect to Homekit) and update the Homekit pairing code in the configuration and save the changes. Restart if necessary.

Once you get the notification that it paired, copy the 12 digit address from the notification and update the Accessory id in the HomeKit pairing slot for the device on the configuration page so it can find it again next time.

When pairing is successful, it will create multiple nodes. The one you have (TSTAT-DFF263) under HomeKit Hub only indicates the pairing status (and it isn't always accurate- sometimes mine said it was paired when it wasn't). It will also create an additional TSTAT-DFF263 under at the IoX level with subnodes under it. The subnodes will be called "TSTAT-DFF263" and "TSAT-DFF263-motion" (or some of them on mine were "T9 thermostat-motion"). It will also create subnodes for any room sensors you have connected to the thermostat. In my case, all of the relevant information and controls was in the TSTAT node under IoX. Although there are parameters under each of the subnodes, the populated data was not correct. I tried changing the generic nodes to false and it eliminated the subnodes, but the data under the main node was then no longer correct and the controls didn't work.

You can verify that the thermostat paired by going back to the thermostat and choosing Connect to Homekit. It should tell you that pairing was successful. If it gives you a new code, the pairing has not succeeded. If for some reason you have to delete this pairing and start over, you can reset Homekit pairing on the thermostat from the Advanced Setup>Reset menu.

Once everything is paired and working, you can move the nodes from IoX to the appropriate room or folder you want it to appear in. I also renamed this node in IoX and on the configuration page to something more descriptive and it doesn't seem to have broken the pairing connection, but I only got it working yesterday so time will tell.

Dave

Edited Tuesday at 01:44 PM2 days by DNewkirk