“Like most makers, my home is automated - not with off-the-shelf IoT devices, but with home-built switches and relays, Raspberry Pis and ESPs.
My first remote switches - all controlled through ESP8266 01s- were mostly built with Blynk. I’d contentedly call up the app on my phone and tap things on and off.
This was fine until the emergence of voice assistants like Alexa and Google Home. Now, I was no longer satisfied with the Blynk app. Instead, I wanted Google to do the job at my verbal command.
This required a bit of engineering. I’d need to use a combination of Blynk, IFTTT, and Google Assistant to achieve it. It worked fine for a while. I blogged about it here.
The Dreaded STT
Before I continue, we really need to talk about the elephant in makers’ collective rooms. We are all very familiar with the Spouse Tolerance Threshold - the point over which we must never roam, lest our wires, connectors, and improvisations be banished forever from the family abode. (I’ve been informed more than once, that if my wires have to go, I’ll probably have to join them.)
I, like so many of us, have been living on the cusp of the STT for as long as I can remember. Over the years I’ve learnt that this threshold is dynamic - moving up and down in direct correlation to whether my devices continue to function or not. Unfortunately, as we’re talking about home-made gadgets, I tend to teeter on the edge of the abyss.
Then Google Screwed Me
One of my favorite Blynk/ESP switches is attached to the reading light above the matrimonial bed. At the command, “Reading Light Off” we’re plunged into darkness without the need to interrupt our semi-conscious state to stretch up to flick the switch. Significant Other grew accustomed to my nightly mantra, even participating herself when I’d fallen into premature slumber.
But then the calamity happened. For some spurious “security” reason, Google decided that its connection to IFTTT would only work for the voice of the principal account holder. In other words, Significant Other could no longer turn our Reading Light on or off!
“Get that bloody thing fixed or get it out of here,” was the general drift of what I heard.
I stalled. As far as I was concerned, the voice-controlled reading light was an essential part of my automation armory. How could I placate Significant Other without upsetting my digital karma?
It was while I was scouring the IKEA website, seriously considering a Tradfri bulb, that my eyes fell on the ThingsonEdge Cricket that has adorned my desk - in test mode - for several weeks.
“Wait a minute,” I thought, “why buy an IKEA remote bulb when I can just as easily rig up a remote switch with the Cricket that will work with my existing Blynk relay?” The Cricket is an easy board to work with and with its power management, the battery would last for years.
When I first thought of the idea, I didn’t really know how to do it - but isn’t that the essence of a maker’s soul?
Cricket, Node Red, & MQTT
I’m not going to explain much about the Cricket here. I’ve blogged about it before. In short, with just two wires, a momentary push-button switch, and a couple of AA batteries, I had the hardware constructed literally (no, not figuratively - l i t e r a l l y ) in three minutes.
But how to get the Cricket to talk to the Reading Light?
I could dismantle and re-flash the ESP8266 that controls the Blynk relay. That would mean taking it off the wall, opening the box, pulling it all apart, installing an MQTT script, then putting it all together again.
Mindful of Significant Other’s watchful eye, disruption had to be minimized. Perhaps there would be a way of doing it without producing more dust in the bedroom? Maybe even, without touching the Blynk setup?
This is where Node Red and MQTT came in.
My home automation revolves around Node Red running on a Raspberry Pi. I have plugins (pallets) for almost everything - including the Blynk API. I already turn Blynk ESPs on and off to control my garden lights through Node Red. Integrating the Cricket would be just another step.”