Let's Build! (Advanced)

Okay, okay, we get it. You aren't basic. You are advanced. Here is the stuff for you!

Now that we got some building blocks, we need to go over a few techniques and theories when it comes to HomeKit automating. for those who aren unfamiliar, HomeKit does not expose the full API to us users in the Home app. there are far more things we can do in third party apps (seen here: HomeKit Apps) than are exposed such as multiple triggers, multiple conditions, and alternate triggers. in this section we will talk about how they work on top of covering some other technologies/bridges such as homebridge, Puschut Automation Server, or the json-server self hosted REST API. some of these things are intimidating and some are VERY simple. lets go over a few of the COMMON technologies. lets start with Homebridge.

Homebridge is a very simple install. If we go to their github wiki, you can see there are MANY ways and systems to install it on. chances are, you already have a computer ready to go! but for those looking to build from the ground up, a Raspberri Pi 4 is a cheap and easy way to go that can have it installed 3 of the ways listed here (docker, Rasbian/linux installs, or the official image). 2 things are needed though. 1. machine needs to be always online and on network (no laptops that leave with you) 2. it needs to have enough power to run it. this isnt a high bar as you can install it on a Pi Zero. but bare in mind that if you are driving cameras, a Pi Zero isnt going to cut it for more than 2. It is heavily discouraged to buy a HOOBS kit if you want to build Homebridge. Homebridge's official raspberry pi image is more maintained and would actually be cheaper to run. at the end of the day, its about as easy to run. Docker is installable on ALL of these OS's (macOS, Windows, Linux) but Homebridge sepcifically cant be done with docker using macOS or Windows due to a broken/unsupported argument needed to make the pairing work. a docker install is totally worth it for other stuff on these platforms, but not for homebridge (unless using linux). WHAT DO THO?

simple, it can be used to bridge unsupported accessories (famously, TP-Link Kasa Plugs) or create virtual accessories (dummy switches, Roomba's, Virtual Occupancy Sensors, etc) giving you more room to expand on HomeKit beyond native accessories. it can also be our gateway to creating more sophisticated automations in HomeKit. to install it, follow the directions on their github :) and if you have troubles, you can reach out to their subreddit, discord, or Github issues tab. its pretty easy these days though. so i wouldnt be too worried it will fail.