your home automation SUCKS!!

About this video

NetworkChuck replaces cloud-based Alexa control with Home Assistant running locally on a Raspberry Pi, motivated by a household problem: if the bathroom door is left open with the toilet lid up and nobody inside for 30 seconds, his youngest daughter throws a whole roll of toilet paper in the toilet. His planned response, ‘Operation Toilet,’ flashes every light red, enables a firewall rule that cuts internet for everyone but him, and loops a prerecorded ransom-style message on every TV. He installs Home Assistant OS via the Raspberry Pi Imager (Pi 3, 4 or 5 works; he uses a 5, with Ethernet and ideally an SSD for longevity), reaches it at homeassistant.local on port 8123, and explains its model of integrations, devices and entities. He integrates his Philips Hue hub, adds his UniFi network (which exposes 11 devices, including individual firewall rules he can toggle), sets up a Zigbee network via an adapter for low-power local mesh devices, and adds the mobile app so phones become sensors for location and battery. A sponsor segment shows reaching Home Assistant remotely for free via Twingate, using a Docker connector installed through Home Assistant’s add-on terminal rather than exposing ports. He then builds automations from triggers, conditions and actions: a contact sensor turns a lamp on and off, and the full Operation Toilet chain uses a proximity sensor, toilet-lid and door contact sensors, and a helper toggle switch to drive separate automations that run the TVs and looping Plex message in parallel, flash lights red with a two-second wait between flashes, enable the UniFi firewall rule, and finally restore everything to normal, waiting about 10 seconds before powering TVs down.

Key takeaways

• Home Assistant runs locally and open-source on a Raspberry Pi or VM, unifying many brands of IoT gear that would otherwise each need their own app and cloud account
• Its structure is integrations (connections to platforms/hubs) that expose devices, which are controlled and monitored through entities
• Zigbee is presented as a preferred device protocol because it is low-power, local and mesh-based, needing only a USB or Ethernet adapter on the Home Assistant box
• Complex automations are easier to manage when split up: a detection automation flips a helper toggle, and separate automations keyed to that toggle run and later reverse the response
• Remote access does not require exposing the home network: a Twingate connector running in Docker inside the network provides per-resource, per-user access

Episode details: published October 25, 2024 · 43:50 long. Summary written by Self Growth Videos from the episode itself. Business results and any income figures mentioned are NetworkChuck’s own claims, shared for education — they are not typical or guaranteed.

← Previous: so…I put a Time Server in my HomeLab · Next: my local, AI Voice Assistant (I replaced Alexa!!) →

All NetworkChuck videos · NetworkChuck profile · NetworkChuck on YouTube