Engine Monitor

Lots has changed for me.

An MQTT GPS module, what good could that be in a home automation system?

I have given up on building a standalone engine monitor.

I was looking at laying out a prototype board, something better than the proto board I am using now.

I finally did it.

I've had several posts about using NodeRed for home automation, communicating with various nodes over MQTT.

I guess it is that time of year, people are building Eggbots.

Big news this week, Apple, Google, Zigbee Alliance, Amazon, Samsung, Ikea, and every other company in the world are getting together and building a new standard for home automation!

I've been promising for a while to write about the time keeping on the network.

If you want to demonstrate cloud computing vs edge computing, why not build something to demonstrate the ideas.

I've finally got it working the way I want.

Almost everything can be voice controlled these days.

As promised, I am going to present the flow used for the thermostat node.

I don't know if I will cover all of this in one post or two.

I am writing about another input node.

The beauty of Node-Red is it's flexibility.

Node-Red is amazingly powerful, and flexible.

In the last post I mentioned that I would build an input node.

This will be the start of the Node-Red posts.

This post will be about using MQTT from the command line.

The ESP8266 is a wonderful kludge.

In the previous post, I talked about how MQTT came about.

What does this have to do with an engine monitor?

The building that I work in is extremely cold in the winter time.

I am sure everyone has heard of uavionix by now, but wow!