Really - the two options are great options and I have tried both. The other option I have tried is the homebridge for hubitat app too.
HubConnect adds a lot of functionality and if you have multiple hubs alongside hubitat (like smarthings which many do) is probably the best option.
I prefer HOOBS/MakerAPI option as it is the fastest integration. It is nearly instant with a small footprint. MakerAPI is a Hubitat focused tool and is solid. Now that hubitat is my only hub (other than my apple tv homekit), I'm focused on stability and speed. As I have been a former smarthings, wink, and homeassistant....I have moved towards one 'brain' which is hubitat and one 'ui' which is homekit.
As a total noob, would you have any tips on the best way to kick start this on Windows10 server? I already have NodeJS + Sonos HTTP running there for better Sonos control through HE and would like the easiest path to get HomeBridge running on it as well.
I set this up successfully once but deleted it and have been getting "accessory not found" when I try to re-add HOOBS as an accessory in iOS for the last few days. After some googling, I thought I would share what I found as the fix, as it was not obvious to me. Context: your phone and the hoobs device are connected wirelessly.
Make sure you are on the same Wi-Fi network as HomeBridge is. Yes the Wi-Fi bands matter too.
The bands part is what I didn't catch at first. Hope this helps anyone else who may run into trouble setting this up.
Hello and thanks for sharing this Hubitat/homebridge bridge through MakerAPI,
I'm new in home automation and even more in the HE environment. So i followed what was presented here but I keep getting the same connection error that seems to send info from the homebridge to the Hubitat:
[2020-09-18, 10:00:23 a.m.] [Hubitat_MakerAPI hhm:0.4.11] attempt connection to ws:///eventsocket
[2020-09-18, 10:00:23 a.m.] [Hubitat_MakerAPI hhm:0.4.11] HE Eventsocket encountered error: getaddrinfo ENOTFOUND eventsocket Closing socket
[2020-09-18, 10:00:23 a.m.] [Hubitat_MakerAPI hhm:0.4.11] HE Eventsocket is closed. Reconnect will be attempted in 5 second.
He recently added the "I need this for HOOBS" toggle to make it even simpler/better.
For MakerAPI You only need two pieces of info.. the IP address of the always-on system that will be running Homebridge. And a copy of the first URL found at the bottom of the MakerAPI screen.
Couple clicks later and you'll have a paste-able config that HOOBS will just eat right up.
This might be a dumb question, but if I don't have a Synology NAS, could I install HOOBS on a raspberry pi and use MakerAPI to connect Hubitat to HOOBS to homekit?
Just a heads up for anybody using regular Docker not on Synology, I ran into issues with the mdns implementation within the official hoobs/hoobs distribution. It appears the Homebridge is using their own HAP stack which doesn't provide a means of defining which network interface to broadcast its services. The container appeared to be running fine, as well as handling the MakerAPI, but I just couldn't add the accessory in Home Kit. Performing a network scan for Bonjour services just would not find Hoobs' HAP on my docker host no matter what I seemed to do.
In any case, rather than reverting to installing on yet another Pi, the "easy" Docker method was to provide the container with its own IP address on the LAN using a bridge network configured with macvlan. The benefit of doing so is not just that the Hoobs install will then have its own ip address, but it also alleviates port conflicts many of us might have with other containers. And of course, since the mdns stack has direct access to the LAN, the HAP is actually visible to your Home Kit device when trying to add the accessory.
I have this running and seems for the most part to work great the only issue I seem to get is arming and disarming HSM from HomeKit. It seems to disarm or arm on Hubitat but seems like the status never gets back to HomeKit and it just sits on disarming... or arming....
Mine is now working not sure exactly what I did but here’s my configuration that I played around with a bit, I’m still only learning hubitat too so I used the tool in the how too to make my configuration up but I since modified it and now it works. I think it was some exclusions in the original.
Thanks! I just switched devices around on the home vs away triggered and it started working. Not sure if it just didn't like one of those, or if I needed to have a contact sensor for the home mode to work
Thanks for this guide. I've had a successful Hubitat/Homebridge integration for several months now. This is the reason I purchased my Elevation.
However, having trouble getting a dual relay device (ZBLC15) to expose both relays to the Homebridge app on my Elevation. I'm using a custom driver from the manufacturer that allows the Hubitat itself to control both relays, but that component device information is not getting passed to the Homebridge app on my Elevation, which, in turn, means none of the second relays are exposed to HomeKit.
Then create two virtual switches and add some rules to keep each sync'd to each other. Expose the virtual switches to HomeKit. I did that for a long time with a Garage door opener once upon a time In fact, I still do it for Presence.