AirPi & Ubidots Configuration

I wanted to use an IoT platform to publish real time data from the AirPi. The original AirPi creators used Xively. However, this has subject to some takeovers and didn’t seem the right thing for me.

I hunted around and looked at ThingSpeak – but after a bit of trying and failing to make it work, I moved on and went on to the last option I had: Ubidots.

It works and you can see the results – or at least those that I have included in a Dashboard here :

The set-up is relatively straightforward, but there are a couple of gotchas that aren’t documented.

Step 1 – once you have your Ubidots account set-up, don’t use the Default Token. Create a new one, named usefully (in my case – AirPi1). This isn’t revelatory, but worth doing.

Step 2 – This is the single most important thing. When you are creating the Variables (this is the Ubidots nomenclature for each of the sensors within the AirPi) there must be a one-to-one mapping between everything you want to send data to Ubidots for and Ubidots variable to receive that data.

To describe it another way. If you do not comment out the sensors you have not created in the Ubidots website from the Ubidots area of outputs.cfg the entire upload will fail. There are no error messages that tell you this – either within the AirPi software or Ubidots.

See the outputs.cfg file listing below; clearly some entries are obfuscated to prevent naughtiness.

filename = ubidots
enabled = yes
showcost = no
token = A1E-Ujd8BOBFUSCATEDGawQQfytKo
ID-BMP085-temp = 5984cOBFUSCATED6d268e561
ID-BMP085-pres = 5984dOBFUSCATED8ac6fefca
ID-DHT22-hum = 5985eOBFUSCATEDf3129180e
ID-DHT22-temp = 5985eOBFUSCATEDf31291818
ID-LDR = 5985eOBFUSCATED077552f3a
ID-TGS2600 = 5985eOBFUSCATED0141de29a
ID-Microphone = 5985eOBFUSCATED159fd412b
calibration = off
target = internet

Notice how the MiCS-2710/MiCS-5525/Raingauge are commented out.

Hopefully this might help someone who has encountered this issue.

Leave a Reply

Your email address will not be published.