-
esp-homekit-devices
Advanced firmware to add native Apple HomeKit and custom configurations, compatible with any SoC based on ESP32, ESP32-S, ESP32-C and ESP8266 series. (Shelly, Sonoff, Electrodragon, Tuya...)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Tasmota
Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
-
You can flash the esp8266 with HomeAccesoryArchitect. After initially setting up the devices they can be added to the home app just like a HomeKit device sold by a manufacturer. If you want to also expose them to google home you can integrate that with HomeAssistant running on a raspberry pi.
https://www.zigbee2mqtt.io/ is another daemon now running on the Raspi. It controls a 20€ USB stick and publishes found devices in real-time via the same HASS auto-discovery on the MQTT broker. This went much smoother than anticipated. ZigBee has some advantages over WiFi (not occupying IP addresses, less power) and I like being able to use more appliances with my OSS setup.
https://tasmota.github.io/docs/ was helpful, but I had to play around with the tasmota setup, gradually adding more software around it in order to appreciate what I got now. Tasmota itself was enough to get my first switch WiFi-controlled, which was the first milestone.
https://homebridge.io/ was the next thing I brought up and running, on a Raspi. Using a plugin to connect to tasmota directly was possible (and the next milestone - „hey Siri!“) but fragile - if the Webserver on the ESP did not answer fast enough, iOS would display „appliances not responding“. I used the official Raspi image and a brand-new SD card (got a lot of problems at first due to an old card with spurious problems).