Thanks for the suggestion, I've heard about Homebridge but have been worried that future updates would bork it. I might seriously have to look into that though.
I’ve been running it for over a year on a little Raspberry Pi I bought for it. At first I was using it for three things: -
- Multiple people presence logic, before Apple added it natively to HomeKit. A rather complex setup using dyndns, webhooks for geofencing when out of home and wi-fi polling when in home. Sounds rather complicated but it wasn’t difficult to set up and it worked extremely reliably. I removed it when Apple added the functionality to HomeKit.
- Garage door: Before Chamberlain (finally) released their HomeKit system, Homebridge was really the only option. Again, works extremely reliably. Saw no need to throw money at Chamberlain to fix a problem I no longer have.
- Fake/virtual switches. These show up as switches in HomeKit but have no real world device. Essentially I’m using them as logic gates for more elaborate automations. At the risk of repeating myself, completely reliable.
The ironic thing about this setup is, apart from Lutron Caseta stuff, these are the
only HomeKit devices that have never given me any grief with “Not Responding” messages.
I also use that little Pi as a home VPN. They are well worth the small investment if you don’t have one.
With all this said I don’t think HomeBridge can easily answer all needs. There are going to be some devices where either the protocol is too obscure/proprietary/secure that you cannot (easily) emulate it, or devices which have physical limitations. An example of the latter are cheapo robovacs with only IR connectivity*. Deep links in apps could certainly solve the former issue, though not the latter.
*though I’m working on a for-fun project to do exactly that with the Pi, an IR LED and mqtt software.
[doublepost=1531174020][/doublepost]
Thanks for the Homebridge tip. I’ve got several non-HomeKit devices and all have plugins. This will be great!
Highly recommend getting a Pi to run it on too.