Being away from home makes me appreciate how accustom I’ve become to my home automations…
At the beginning of the year, I wrote about using
nsd3 to run my own nameservers: “Authoritative DNS with redundancy, using
nsd and Debian Wheezy“. That post focused on the public-facing benefits of running my own nameservers, notably the flexibility it gives me with regard to record types and update frequency.
As I’ve added more and more services to the Raspberry Pis running on our home network, the flexibility I have has demonstrated another benefit: assigning a domain name to the network’s ever-changing IP address. Time Warner doesn’t offer static IPs for consumer accounts, which presents a challenge to using our router’s native VPN functionality. To make it convenient to connect to our home network from afar, I’ve employed an open-source script and a custom DNS zone to provide dynamic DNS via my own servers.
For quite some time, I avoided acquiring any Rasbperry Pis. I already have four VPS, and I genuinely wanted to avoid expanding the number of Linux instances I was responsible for. My hesitation was for good reason; less than a month after acquiring my first Pi 3, I found a reason to add a second to our home network.
To be clear, I’ve nothing against the Raspberry Pi; I simply knew that my addictive personality would compel me to find ever-more uses for the devices, compelling their multiplication.
As is the case with many things I post, this is mostly a reminder to myself of the math behind
x = 1(execute)
w = 2(write)
r = 4(read)
In the month since I first posted about how I am using Home Assistant, I’ve made a number of improvements to my configuration. These changes were mostly focused around usability–removing clutter from the interface and simplifying the layout–without losing any functionality. Two changes in particular really simplified the default view, making our light groupings more manageable and less overwhelming.
At the time, someone asked why my post in response to the Orlando nightclub shooting didn’t support comments or WordPress.com likes. The answer is simple, sad, and a bit insidious: given the subject, I was concerned about the response, and any undue attention that those interactions might draw.
I installed a GE switch that supports Zigbee, so the painful florescent light in our kitchen doesn’t glare at me any longer without recourse.
I’m absurdly happy about being able to control a built-in light from Home Assistant.
I’ve also learned that GE’s Zigbee line is far more reliable than Leviton’s Z-Wave products.
There are several reasons why a robust, reliable home network are important to my husband and me. First, we both work from home. Second, the vast majority of our entertainment is streamed. Lastly, the mobile phone reception in our apartment complex is poor. In many ways, our connection to the internet is our only connection to our lives and livelihoods.
We’re fortunate, as far as networking is concerned, to have all of our connected devices concentrated in two areas of two adjacent rooms. As a result, only one long cable run was needed to wire all but our mobile phones to the network. We’re also lucky enough to live in part of Time Warner Cable’s territory that offers 300mpbs service, providing further incentive for a strong home network.
Last week, I provided an overview of how I’ve introduced automation and control to our apartment by combining various smart-home devices with a robust platform to manage those inputs. My earlier post described, in broad terms, the hardware and software I’ve leveraged, and some of the automations I’ve implemented. Today, in anticipation of releasing the software configurations that make this possible, I’ll inventory the devices used and explain their roles in the overall system.