With 5 to 10 calls a day there was no remarkable discharge of the battery pack.
In order to accelerate the discharge of the battery pack, I simulate 288 calls/day by a periodic reboot every 5 min. After about 9.5 days of operation the battery pack should be discharged. This will give a better verification of the forecast for discharge.
The voltage under load conditions is saved in a Google spreadsheet again.
Continue reading “IoT Button (4th)”
To set the right colors for an RGB LED we have to set the appropriate values for R(ed), G(reen) and B(lue).
On this website I found this image explaining the composition of colored light from R, G and B.
You can step over the ratio axis and can generate all colors building a rainbow beginning from Red over Yellow, Green and Blue to Magenta and back to Red again.
If you start with three data points then you will get Red (0), Green (1/3) and Blue (2/3) only. The more equidistant data points are used, the finer the color gradation.
The required data points can be calculated with the Cosinus function to get a table of RGB values for controlling a RGB LED or Neopixels etc.
Continue reading “Rainbow Colors on WS2812”
I started the test after building this test environment:
Three Energizer max AA cells power the IoT Node. Normally the IoT Node sleeps.
After pressing the reset button the IoT Node is connecting to the home network via Wifi, measured the battery voltage, and send a message to IFTTT.
There are two IFTTT receipts. One sends a Twitter direct message (to me) and the other makes an entry into a Google spreadsheet. Follow the link to see decharging my power pack by this IoT button app.
To reduce the power consumption of my IoT button it must go into sleep mode after sending its message. I measured a current consumption of about 100 μA in sleep mode w/o any hardware changes. To get further reduction of current consumption you can remove the LED at pin D0 (GPIO16), for example.
Continue reading “IoT Button (2nd)”
Amazon introduces its Dash Button to order much needed goods. But there are alternatives. Two of them are bt.tn and flic.
bt.tn and flic are just what the name suggests: connected push buttons that can trigger actions. Together with IFTTT they can trigger a growing number of services. Relating to the connectivity bt.tn and flic differ.
The bt.tn has built-in internet connectivity and needs no smartphones or apps to pair with. Flic uses a Bluetooth low energy connection to an Android or iOS smart phone and the flic app for network connection.
These offers are interesting to experiment with. But, we can build such an IoT Button by yourself and save a lot of money.
D1 mini combined with an 1-Button shield is one solution. You can buy both for $ 4.99 from Aliexpress.
IFTTT offers channels for bt.tn and flic. IFTTT’s Maker Channel allows you to connect IFTTT to your personal projects like this IoT Button.
This time my IoT Button sends a Twitter Direct Message after pressing it. It’s a starting point to test the mechanism.
The configuration of IFTTT is well documented and should be no problem.
For a door contact application step-by-step instructions for IFTTT setup are in my book “IoT Node for les than 15 $”.
This time I work on reducing power consumption to get a battery-powered solution.