From ThingSpeak to ThingTweet

I have been using ThingSpeak for a while now and I decided to create my own API for logging IoT readings. The main reason for this is that ThingSpeak require me to manually set it up for each thing I want to log. I think this is tiresome and not as easy as I want it to be. Also I need one api key for each of my connected things. Last, but not least, I don't know how long my data is my data. They may "pull the plug" at any time and have me pay for the service (something I can easily understand).


Wireless temperature sensors - Prototypes

Now I have a few prototypes ready and working. It took me a while. I ran into a problem when connecting a USB Moteino to my server. It works OK in Windows, but I needed it connected to the Linux running in VirtualBox. The problem is that the Moteino USB did not reveal itself as a /dev/ttyUSB0. It turned up as a /dev/ttyS0.

Wireless temperature sensors

This information is obsolete - New information under Multi purpose Moteino sensor

As I have several projects down the line I had to start somewhere. In this project I will build a wireless temperature sensor system. The main goal of the project is to be able to see the temperatures in several rooms at home when I'm away. I will also have a temperature node outside.

To manage this I will use Moteinos. I spent some time trying to find the best hardware for this. Before I decided I looked at XBee, JeeNode, PanStamp among others. They all have their uses, but I felt that Moteino would do the job best for this specific project. For later projects I just might try out the PanStamp as well.

Subscribe to RSS - Thingspeak