You know I did that, Now I gotta figure out how to do that for my MagicMirror server and get it to run as a service.
I think the end result of my work is that the fist install asked for a config.json file under .homebridge directory, then when I implemented the UI, it puts it wherever it wants and that is fine by me.
Pretty splendid project, so I was compelled to make a modest donation as soon as I got it running and saw how capable it is.
Copy. They are now up and running as well.
I know right? Really good stuff... I promise I won't try and tempt you with Node-RED (too late)... 
Got an elevator pitch for node red?
What an I missing?
After getting HUBITAT + RING + ALARM.COM integrated into HOMEBRIDGE so easily, I feel like I need to do more until it all comes crashing down in a blaze of glori..fied failure.
I'd go to the node red discussion to get the pitch, but after developing in both node red and RM, I prefer nr. Plus the added integrations there complement Hubitat integrations.
Node-red is about as powerful as it gets for automating complex automations. It's very visual which makes flows easier to work out.
You can also code logic using Javascript which is really helpful.
Thank you, thank you, thank you OP. I set up homebridge on my MacBook, installed this on my Hubitat and my smart home set up has just got a whole lot smarter (Apple Home Automations connecting video cameras to Hubitat devices).
@tonesto7 I just got the plugin installed on Hubitat and HOOBS 4 to control my generic z-wave (Bali Autoview) shades. Control seem to be working great from HomeKit, with one exception.
Can you think of any reason why commands are being sent to the shades approximately every 5-10mins wanting them to open or close? We are not sending the commands but I do see them in the log. Thanks in advance for the help!
the plugin never sends commands without events from HomeKit. Check to see if there are any automations configured in the Home App or ShortCuts
I would like to announce to those who are reading this note:
I just purchased a Raspberry Pi Zero2W - which has a retail cost of approx. $15.
I loaded it up with Debian Buster (version 10), and Homebridge according to instructions in the git hub.
It works without any issues - including the config web page at port 8581.
I tested it out with approximately 50 devices, and have found the response time to be within acceptable norms.
Amazing!
Not a Hubitat issue but posting here because there appears to be no one monitoring the 'unifi-protect' Discord channel.
I am using the 'Homebridge UniFi Protect' Homebridge plugin and I've created an Automation in the iOS Home app that will turn on a vDoorbell switch when the 'G4 Doorbell Doorbell Trigger' turns on and that automation is working perfectly but If I turn on 'G4 Doorbell Doorbell Trigger' via the Homebridge UI, the vDoorbell does not turn on.
Any ideas how to fix?
@Busthead I wonder if it has something to do with where the "trigger event" is taking place.. does it show up as happening on the Home App when you trigger it from Homebridge? Maybe the automation ignores the local (on homebridge) event for some reason.
Also if you manually toggle the vDoorbell switch in HomeBridge does it work that way?
I don't use that particular plugin so can't really help all that much - sorry. You might want to open an issue on their github page..
The 'G4 Doorbell Doorbell Trigger' accessory isn't listed in the iOS Home app. Maybe that's the issue?
I don't know enough about the Home App automations to speak with expertise here so cannot say. I was just wondering if there were a difference in triggering from HB (assume you are doing this via the accessories page) vs the "real" triggering from Unifi and that maybe Apple Home could tell the difference.
I use Node-RED to read values from HomeBridge for things like my Ring Doorbell and can then translate them to the Hubitat where I sound a door chime via an old Aeotec Siren. I also use the Unifi node in Node-RED to detect connections to WiFi for a simple presence detection.
I've got a couple of issues. I'm trying to do away with my Alexa integration and use Homebridge instead. It's far better as I always have my iPhone close by & Apple Watch on so "Hey Siri" works well. The problems:
1 - I have a Honeywell EvoHome zoned heating system which has a working integration on Hubitat. It works perfectly with Alexa. However in Homebridge the zoned radiator valves don't appear in the correct capability list (Heat only thermostat). I can only select them as "Sensor" or "Other". When I say "Hey Siri - Set the lounge heat to 20 degrees" - I get some strange results as it try to set both a heating and cooling setpoint. I don't seem to be able to alter anything to get it working correctly. It seems I can put the temperature up but not down.
2 - All of my shades show a spinning icon as if the status is updating. They are open but say "closing" The state of the device (Qubino Flush Shutter) is "open"
I moved my Hubitat devices from Hubconnect Homebridge integration to Homebridge Hubitat v2 today, so I already had an existing Homebridge installation working with my iOS Devices.
It appears everything moved over fine, I can see the devices in the logs for Homebridge and can control them when on my wireless network. When I'm not on my local lan/wireless (i.e. on cellular), my devices show as "not responding" in the Home app.
I thought my Apple TV just handled the translation for things being toggled off network and spoke to things on the local network. Am I missing something? I do know that with the old Hubconnect integration, I could control things when off of Wifi. The reason for switching is I'm not sure how much that integration is supported these days.
I made the switch from Hubconnect to this app earlier this year for the same reason. I can control my devices when off Wi-Fi. I just tested this by turning off Wi-Fi on my phone and launched the Home app and it worked. It took a bit longer to update the status at first but it does work.
I think it has something to do with mDNS..
·2y
Your hub can’t connect is the short answer. Either it’s not seeing mDNS packets to know where your Homebridge is, or something else is going on that’s blocking it.When you’re home, your iPhone talks directly to Homebridge, which it finds via mDNS multicast broadcast packets. When you’re away, your phone talks to iCloud, which talks to your Hub through a persistent connection, and your Hub talks to Homebridge, again, by finding it through mDNS broadcast packets.
https://www.reddit.com/r/homebridge/comments/ek5bma/no_response_when_away_from_home_network/
Sorry @ritchierich meant to respond to @brianwilson!!
I don't have an iPhone but I do have an iPad and my neighbors WiFi. Maybe will give it a whirl and see what happens.
I have "Ciao" set as my mDNS advertiser in the Homebridge settings.
It works fine for me, is your Apple TV showing as a hub? It looks like it needs to be 4th gen or newer
Download the Hubitat app
