In hope of reconnecting my Honeywell T10 thermostat, I downloaded the trial version of HomeKitHub professional. It appeared to download, but showed as a big red "disconnected" and running discovery did not find the thermostat.

Did you do this as mentioned on the announcement post? Please make sure you have done a recent Upgrade Packages: https://github.com/jimboca/udi-poly-homekit-hub/blob/main/DEBUGGING.md#common-causes

If so, review: https://github.com/jimboca/udi-poly-homekit-hub/blob/main/DEBUGGING.md#discover-does-nothing-or-adds-no-rows

On 7/5/2026 at 4:34 PM, Jimbo.Automates said:

Did you do this as mentioned on the announcement post? Please make sure you have done a recent Upgrade Packages: https://github.com/jimboca/udi-poly-homekit-hub/blob/main/DEBUGGING.md#common-causes

If so, review: https://github.com/jimboca/udi-poly-homekit-hub/blob/main/DEBUGGING.md#discover-does-nothing-or-adds-no-rows

OK. It is now "connected". Discover did not find the Honeywell T10 thermostat. I manually added the eight-digit HomeKit code and this did not work, either. I am wondering if the prior pairing with the Honeywell node server is interfering with the discovery process. I may fool around a bit more with it.

18 minutes ago, oberkc said:

OK. It is now "connected". Discover did not find the Honeywell T10 thermostat. I manually added the eight-digit HomeKit code and this did not work, either. I am wondering if the prior pairing with the Honeywell node server is interfering with the discovery process. I may fool around a bit more with it.

Are you running the lastest HomeKitHub Version 2.0.14? That one had some improvements to the code which helped another user find their device.

and there are some other issues mentioned here: https://github.com/jimboca/udi-poly-homekit-hub/blob/main/DEBUGGING.md#d-accessory-not-visible-on-the-lan-mdns

51 minutes ago, oberkc said:

OK. It is now "connected". Discover did not find the Honeywell T10 thermostat. I manually added the eight-digit HomeKit code and this did not work, either. I am wondering if the prior pairing with the Honeywell node server is interfering with the discovery process. I may fool around a bit more with it.

Just released 2.0.15 which has more improvements on searching for devices...

3 hours ago, Jimbo.Automates said:

Are you running the lastest HomeKitHub Version 2.0.14?

Yes.

3 hours ago, Jimbo.Automates said:

Just released 2.0.15 which has more improvements on searching for devices

Perhaps I will try it. Edit: 2.0.15 appears available only for the standard version. Since I thought I needed the pro to do what I wanted (Honeywell T10) thermostat) I did not try the standard version.

12 hours ago, Jimbo.Automates said:

and there are some other issues mentioned here: https://github.com/jimboca/udi-poly-homekit-hub/blob/main/DEBUGGING.md#d-accessory-not-visible-on-the-lan-mdns

Yes, I read this. Unfortunately, it uses terms and expressions that have no meaning to me (for example: Run Zeroconf diagnostic on the controller!!??), and I am still trying to decide if the amount of time that I would have to spend to understand this is make it work is the something that I want to expend. My system is feeling pretty fragile as it is (the matter devices I have fail regularly and a zwave lock loses function) and I am already spending too much time keeping it running.

Thanks for the advice so far. I will let you know if I progress any further.

Edited July 7Jul 7 by oberkc

I have the a disconnected status too. I just installed the trial version, 2.0.17 and performed an update packages, so I am at PG3x Version 3.4.19. I have tried a few things to resolve this issue but I am stumped, can you assist with troubleshooting.

I have attached the log package.

Thank you in advance.

HomeKitHub_7-25-2026_80606_AM.zip

Never mind, it working now. I read the instructions more carefully and I didn't reinstall the node server after the Update Packages.

Cheers,