In part II of the tutorial, we got our NodeMCU flashed, and optionally set up some sensors on another NodeMCU. In this tutorial, we’ll set up our MQTT and Node-Red servers, which will give us the ability to relay and take action on data that we receive.
In part I of the tutorial, we got our relay hardware all set up and ready to go. Now it’s time to get the our NodeMCU firmware squared away. Optionally, at the end of this tutorial, I’ll show you how to set up another NodeMCU with some sensors.
My newest hobby is mucking around with the Internet of Things (IoT). A while back I bought several NodeMCU’s from eBay for almost nothing. Along with a relay board (also from eBay), some creative wiring, and a bit of software, I’ve managed to put together a neato remote controlled relay board. In this demo I’ll actually use two NodeMCU’s, one to handle capturing some data from some sensors, and another as part of the relay build.
If you follow this tutorial in entirety, you’ll get a completely functional system where you can remotely turn outlets on/off, and add rules and logic to your setup to do have the outlets turn on and off under certain situations. We’ll be setting our system up to turn on an outlet when our sensor node detects humidity over a certain level.
At this Metro Detroit WordPress Meetup, several different presenters talked about their favorite productivity and workflow apps/hacks. Here’s a short summary of each presentation with links to their recommended tools.
I’ve tinkered with microcontrollers on-and-off quite a bit throughout my life, mostly sticking with the Arduino boards. My first one was an Arduino Duemilanove circa 2009. As part of a larger project I wanted to dive into something a bit more advanced. By sheer coincidence I came across an advertisement for a NodeMCU. For under $5 you get an Arduino-compatible microcontroller with built-in WiFi. Absolutely perfect for your IoT project. If you hunt around eBay and don’t mind waiting several weeks, you can get them as cheap as even $3 or so.
I’ve placed myself on a path to better get a grip on git and actually use it in my day-to-day development of this site. In looking up the best practices for running WordPress under git, I ran into a handy slide deck from my WordCamp Columbus buddy @stevegrunwell titled Keeping WordPress Under [Version] Control with GIT. How fancy!
If you noticed the tagline of my site “Ink Blots and Other Thoughts” you may be curious about the whole “blots” part of that. Short answer is, I have a slight obsession with fountain pens.I bought my first fountain pen on eBay, it was a very cheap vintage Arnold pen. It’s a small, finicky, but very fun lever-fill pen that immediately drew me in.
I haven’t had Google Analytics installed on this site for quite some time. Knowing that, you’ll understand why I was surprised to log into GA to get my tracking code, only to see 178 “visits” to my site in the last 30 days. Quickly my hatred of Google Analytics spam came flowing back into my mind.
Making progress on getting my personal site up-to-snuff, I installed JetPack and ran into some strange issues trying to enable features. I kept getting errors such as “Failed to fetch” when toggling settings in JetPack. Using Chrome’s developer tools, I noticed Chrome was blocking admin.js from being called due to mixed-content errors. I immediately suspected SSL as being the culprit. My site runs on SSL – WordPress was loading on SSL – so why the errors?