Yes, it is its own child bridge. I did not consider the Bridge aspect as being an issue. I had to follow the same proceeddure to get it to show as noted.
Connect to HomeKit
Disconnect from homekit
wait 1 minute
reload devices
Connect to Hubitat (Of note here, if I don't connect within a few seconds the first time, when I try it then say device is unavailable, but if I restart the child bridge in Home Bridge it comes up again and connects, just like power cycling a device as is suggested by others)
Interesting. Never thought about using it that way. Will have to try this with HA HomeKit devices to see if it works. Would be nice to remove the reliance on HomeKit automation wherever possible.
Unfortunately my older Ozmo 937 is unsupported by the HA integration and they have no intention of adding it unless Iām willing to take a deep dive into python [no thanks].
Iāve been trying to build a Hubitat app to directly control it, however, I canāt succeed in the login for some reason. So, this seems to be an alternativeā¦
Hey thanks for the idea! I setup a child bridge and the HA HomeKit Device integration sees the bridge perfectly. I can now pass the entities back to Hubitat via HADB and not longer need HomeKit automations.
This would be great directly into Hubitat's HomeKit Controller if that's a future possibility, but for now this is fine. I'm already running HADB for many other devices, so adding entities for one more device is no big deal.
I've really latched onto Hubitat for its simplicity. HA was not what it is now when I started. AN HomeKit has become my go to for UI as I use apple phones. However, I have preference for a single piece hardware solution, running multiple bridge servers is not something I like. Hubitat is a great piece of hardware, and I look forward to its improvements over time.
Same problem here, tried pairing 3 ecobee thermostats (previously working fine through HA's HomeKit emulation); get the "Pairing has completed successfully." message and status changes to "This device is already paired to another HomeKit controller", and no devices get created.
This clarifies that there seems to need to be a specific driver in Hubitat?That kinda sucks. I was assuming/hoping that it supported devices just like HomeKit does, i.e a switch is a switch , a contact sensor is a contact sensor and so on an so forth.
Not sure i agree with that. I managed to add a Eufy camera and it did create a device for it. It was non functional, but it did add it and create a device.
Not exactlyā¦ HomeBridge does not present connected devices as individual HomeKit devices. Instead, HomeBridge presents itself as a HomeKit Bridge device. One HomeKit Bridge can share multiple physical devices to a HomeKit Controller. Currently, it appears that Hubitat does not yet support HomeKit Bridge devices. Thus, the reason your experiment trying to connect HomeBridge to Hubitat using the HomeKit protocol was not successful.
When I add the thermostat to Homekit normally, the process kicks off something in the thermostat to display the needed code to add it to Homekit. When trying to add it to the Hubitat Homekiit controller it doesn't display the code on the thermostat.
I logged into my hub but didn't see an alert for an update but I'll go ahead and force a check this afternoon and see if the update has any impact. Thx.
Normally the thermostat also has a menu sequence that will display the code and QR (sometimes the code is printed really small inside the QR code space).
There should be a menu item like Settings -> HomeKit or something similar.
If the thermostat is not currently paired, going into that menu item will generate the 8 digit code to use with a HomeKit controller (including but not limited to our implementation). If it is paired, unpair it first. If there's no code, no controller will work. This has to be triggered from the thermostat itself.
It adds to Apple's controller without issue, I start the pair process in Homekit and then the code shows on the thermostat. Once fully removed and reset from Apple controller the same behavior does not happen in Hubitat. I see the device in the Hubitat homekit controller and once I start pairing the code to enter never appears on the thermostat. There is no way to view the code until something from the Homekit controller side triggers it from the research I've done and no way to complete the pairing process without the code unless I am missing something.
Ok making some progress, if I put in a dummy code and hit pair, it will show the code on the thermostat for like 10 second, this of course doesn't help because its already trying to pair with the wrong code. Canceling and starting again doesn't work as each pair request generates a new code. Anyway to put it in pairing mode and then ask for the code?
I just got this working. Unfortunately i had to resort to doing a full factory reset of my Ecobee. It isn't a great solution, but it is the only thing that finally made mine work. One thing that tells me though is that it wasn't a Hubitat problem, but a Ecobee issue instead.
Got it working, for anyone having trouble with Honeywell T6 or device that acts in a similar manner, what you need to do is start the pairing in the Apple Home app so that the Thermostat or device will display the code but don't go any further in the Home app or cancel the pairing and then start the pairing in Hubitat and enter the code displayed.
