Shrapnel

AT&T uses loophole to deny low-income internet discounts

This actually makes me angry, and I donā€™t even live in a country where AT&T operates.

Thereā€™s something wrong with a marketplace where a company can exhibit this kind of behaviour and remain not just a player, but a force. Unfortunately that kind of market very much exists here in Canada too: choosing a cable company is not about which provider is good, itā€™s about which provider is least terrible. And that makes me sad.

</rant>

AT&T uses loophole to deny low-income internet discounts

Blog

NodeMCU, MQTT, IoT & Other Letters I Find Exciting

If youā€™ve been keeping up with my #SmartHomeĀ series (and if you havenā€™t, why not?) youā€™ll already know that I have plans to make more of my home ā€œsmartā€ using Home
Assistant
as the software that ties everything together, and some DIY NodeMCU-based hardware that Iā€™m going to build myself as a learning opportunity.

Another important piece of the puzzle, but one that I havenā€™t previously mentioned, is MQTT.

MQTT is ā€œa publish-subscribe-based lightweight messaging protocol for use on top of the TCP/IP protocol,ā€ at least according the slightly suspect grammar of the person that wrote the Wikipedia article about it.

image

I learned about MQTT at the same time I learned about Home Assistant, although I didnā€™t initially appreciate its power. Iā€™ve been using it from the start to enable Home Assistant to know where we are: our phones run an app called OwnTracks which publishes
location data to an MQTT ā€œbrokerā€ (server). Home Assistant subscribes to these updates, which means it immediately knows about it when our location changes.

I love this whole solution, not least because itā€™s very easy to run my own MQTT broker (Iā€™m running MosquittoĀ in a Docker container on my home server) and Iā€™m therefore entirely in control of our location data ā€“ itā€™s not being shared with the developer of some app or service I have no insight into.

This publish/subscribe model and the lightweight nature of MQTT makes it perfect for ā€œInternet of Thingsā€ (IoT) devices to communicate with each other, and when you add Home Assistant into the mix it gives me all the tools I need for any sensors I build
to feed their data into my smart home ecosystem, and for my smart home controller to feed commands to any devices.

Indeed, Iā€™ve already built my first little NodeMCU app that leverages the technology.

Iā€™ve ordered almost all the components I need for my upcoming hardware projects from China, and theyā€™re only just starting to arrive. Happily the NodeMCUs themselves were amongst the first shipments to land on my doorstep, so even though the only thing I can really do with them right now is programmatically turn their internal LED on and off, I have still been able to use this to start learning: Iā€™ve made it an internet controlled
LED.

[youtube https://www.youtube.com/watch?v=JLETpLMicYs?feature=oembed&enablejsapi=1&origin=https://safe.txmblr.com&wmode=opaque&w=540&h=304]

As promised, Iā€™m going to be sharing both the hardware and the software as I take this DIY Smart Home journey. There is no DIY hardware here, just the NodeMCU itself, but Iā€™ve published both the Arduino sketch and Home Assistant configuration Iā€™ve used for the video.

Enjoy!

Blog

[wpvideo Tkoe72i4]

I have begun to learn how to program my NodeMCU.

Granted, all itā€™s doing here is running the example ā€œBlinkā€ program that comes with the Arduino IDE, but the important point is that the little light is turning on and off because I uploaded some code that tells it to.

Itā€™s not connected to a computer here. The USB cable is simply plugged into a power outlet.

Blog

[wpvideo Tkoe72i4]

I have begun to learn how to program my NodeMCU.

Granted, all itā€™s doing here is running the example ā€œBlinkā€ program that comes with the Arduino IDE, but the important point is that the little light is turning on and off because I uploaded some code that tells it to.

Itā€™s not connected to a computer here. The USB cable is simply plugged into a power outlet.

Blog

Smart Home Adventures

Ever since I bought my own home nearly a year ago, Iā€™ve
become increasingly interested in making it smart.

Right off the bat, I feel like I should clarify what that
means to me. The ability to turn some lights on or off with an app is not
smart, in my opinion ā€“ the smart way of controlling lights is by flicking a
switch conveniently located in the room you wish to illuminate.

A smart home needs to be much more intelligent. Itā€™s about
automation. Itā€™s about the home being able to notify me if something is
happening that I need to know about. Itā€™s about being able to accomplish things
with minimal difficulty, not adding complexity and more steps.

Thatā€™s where off the shelf ā€œsmart homeā€ solutions really
started to fall down for me. I could spend hundreds or maybe even thousands of
dollars, for what? The ability to turn on my living room lights while Iā€™m still
at the office? Why would I ever need to do that?

Nevertheless, the lack (in my opinion) of a pre-packaged,
useful, holistic solution that accomplished my vision of what a ā€œsmart homeā€
should be didnā€™t deter me from tackling things bit by bit. It started with our
burglar alarm. It has internet connectivity which sends me alerts in the event
that something unexpected is happening, and lets me arm or disarm the system
from my phone ā€“ which I actually do find useful.

Next up was our thermostat. The one that was installed when
we bought the house was an old-fashioned one with a simple mercury switch
inside. You set the temperature, and that was it. We replaced that about a
month ago with something programmable (it doesnā€™t need to be as warm in here at
night as it does during the day; it doesnā€™t need to be as warm if nobodyā€™s
home), and I took the opportunity to get one with WiFi so I can set the
temperature remotely. Thatā€™s not useful in and of itself, but if you take that
functionality and look at it in the context of my wider vision then the
thermostat is certainly something Iā€™d like to be able to programmatically
control.

It was around this same time that I discovered home assistant, and now my dream is
starting to come alive.

image

Home Assistant is an open-source project that runs on a
variety of hardware (I was originally running it on a Raspberry Pi, and Iā€™ve
since switched to running it in a Docker
container on our home
server
). It has a ton of plugins
(ā€œcomponentsā€) that enable it to support a variety of products ā€“ including our
existing alarm, thermostat, streaming media players, and others (including,
somewhat ironically, the colour-changing lightbulbs we have in our family
room). It includes the ability to create scripts and automations, it uses our
cellphones to know our locations, and can send us push notifications.

My initial setup was all about notifications. If we both
leave the house but the burglar alarm isnā€™t set then it tells us (and provides
an easy way to fix the issue). If we leave one of the exterior doors open for
more than five minutes, it notifies us (or just one of us, if the other is
out). I also created a dashboard (that you may have seen in my last post) to display some of this stuff on a monitor in my office.

Since installing the thermostat Iā€™ve added more automation.
The time we go to bed isnā€™t always predictable, but when we do go to bed we set
the alarm. So, if itā€™s after 7pm and the alarm goes from disarmed to armed, the
thermostat gets put into night mode. If nobody is home then the temperature
gets gradually turned down based on how far away we are.

If nobody is home at dusk then it turns on some lights and
streams talk radio through the family room speakers to give the impression that
someone is.

This stuff meets my definition of smart, and Iā€™m barely
scratching the surface. The open nature of the platform not only means that Iā€™m
not tied to a particular vendor or technology, but also means that I can add on
to the system in a DIY way.

Which is exactly what Iā€™m going to do. Iā€™ve bought some NodeMCU microcontrollers which are
WiFi enabled, Arduino IDE-compatible
development boards designed to the basis for DIY electronics projects.

Watch this space, because over the coming months Iā€™ll be
connecting our doorbell, garage door and laundry appliances to Home Assistant.
Iā€™ll be learning as I go, and Iā€™ll share the hardware and software.