I hereby claim:
- I am paraphraser on github.
- I am paraphraser (https://keybase.io/paraphraser) on keybase.
- I have a public key ASAEuq9mHBtAWcvqsEvFAC-CtHGqjRDtQU3Ht7YY0MrSJQo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
Getting data produced by IoT sensors into a database is practically a mandatory step before effective visualisation (eg dashboards).
This recipe shows you how to get an MQTT payload into an InfluxDB database using three Node-RED nodes. It makes the following assumptions:
This gist explains how to activate a theme for the Node-RED graphical user interface under IOTstack.
This gist is a response to a Discord question. It explains my approach to deciding whether barometric pressure is rising, falling or remaining steady.
I do the trend calculation in Arduino (ESP8266) code. I tried to mimic the idea of setting the reference needle on a real barometer, waiting an hour, then seeing which way the pressure needle had moved with respect to the reference. The wrinkle is that "the last hour" is a moving window that updates every 10 minutes.
The BMP085 sensor is polled every 10 minutes. Until there are six observations (eg after a reboot) the code returns "training".
After that, the code does a least-squares regression on the last six observations (ie the last hour of data) to find the linear equation of best fit. In effect, the algorithm assumes that knowing the time (independent variable on the X axis) at some point in the past hour would permit the pressure at that time (dependent variable on the Y axis) to be estimated with some degree of
Assumptions:
This tutorial is specific to SensorsIot/IOTstack. You're on your own if you "get creative" and choose different ports or database names.
Note: This tutorial is specific to SensorsIot/IOTstack.
If you want to fix a bug or propose an enhancement for IOTstack, you will need to prepare a Pull Request (PR).
Please don't try to do anything in this gist inside an ~/IOTstack
folder on a Raspberry Pi that is also being used to run your Docker containers. It's easy to get confused and you could accidentally break your own working IOTstack.
You can do everything on the same Raspberry Pi that is running your IOTstack but it's usually easier to work on a desktop or laptop. If you accept this advice, there's no risk of breaking your running IOTstack.
This guide barely scratches the surface of Pull Requests. There is lots of advice on GitHub and Google will find plenty of hits for any question you might have.
My Raspberry Pi 4 kept losing its wlan0
interface. I could usually reconnect via Ethernet but, from time to time, I noticed that the eth0
interface would also go walkabout.
I tried a lot of things but the one described here seems to have cured the problem. I have no idea why it works. It just does.
The script shown in the next step should be created on your Raspberry Pi. Please do not make the mistake of selecting the text, copying it into a text editor on your Windows machine, saving the file, and then moving the file to your Raspberry Pi. Unless you take precautions, Windows will add its 0x0d 0x0a
(CR+LF) line endings and those will stop the script from working properly on your Raspberry Pi.