Picture of TempBug: internet-connected thermometer
Last January, we had some trouble with the heat in my office. Specifically, the kind of trouble wherein the heat is not on, you turn it up, and it still not on. This went on for more than a few days, and finally ended a day or two after we got an email announcing that the heat was broken and speculating that it had probably been down for a few days. My teammates and I laughed a bit at this - we knew exactly when the heat had stopped working. We had a continuous record of the temperature in the office going back months, with 10-minute resolution.

You can do this too, and it's quick, cheap, and easy! This little gadget is built around an electric imp, and you can push the data from the imp out to anywhere you want. In my case, I found it handy to push the data to a neat service called Xively, which stores and graphs the data for free.

This project takes about an hour to two hours, if you've never done a project with an electric imp before, and when you're done you'll have a thermometer that you can toss anywhere with wifi and collect data for months to years on a single battery, depending on how often you check the temperature.
Remove these adsRemove these ads by Signing Up

Step 1: Gather the parts

Picture of Gather the parts
Here are the parts you'll need to build your internet-connected thermometer:
  1. An electric imp (currently available on Sparkfun and Adafruit) - $30
  2. An electric imp breakout board (again, Sparkfun or Adafruit) - $12.50
  3. A 9V battery - $2.00
  4. A 9V battery clip, like this one from Sparkfun (we're just going to cut the end off of it, so the connector doesn't matter) - $1.25
  5. A big capacitor, like this one on Digikey (220 uF, 50V). Make sure it's at least rated to 16V if you're going to connect it to a 9V battery, or you'll have a bad time. - $0.40
  6. A 100kΩ resistor, preferably 1% tolerance, like this one on Digikey. - $0.10
  7. An NTC (negative-temperature-coefficient) Thermistor. I used this one on Digikey. It needs to have a room-temperature resistance equal to your resistor (#6) - this one is 100kΩ at room temperature. - $3.25
Parts total: $49.50

You'll need some tools and supplies, as well:
  1. Soldering iron
  2. Solder
  3. A bit of foam tape or other thick, double-sided tape for securing the battery to the breakout board
  4. Angle cutters / wire cutters
  5. Wire strippers
  6. A smart phone for using BlinkUp to put the imp on your wifi network
  7. A computer to program the imp 
Alright! Let's get started!

Step 2: Wire it up

Check out the breadboard diagram in the photos to see how we'll be wiring up your tempbug. 

First, connect the battery clip to the breakout board.
  1. If your battery clip has a connector on the end, cut it off. Strip about 1/8" off the end of each wire and twist the strands to keep them together. If you don't want long leads hanging off your tempbug, you'll want to cut the wire to about 2" long or a little less.
  2. Secure your electric imp breakout board to your work surface and heat up your soldering iron.
  3. One pad at a time, use the soldering iron to heat the "P+" and "P-" battery pads on the breakout board. For each pad, when it gets hot, flow a good-sized bead of solder onto the pad. Take care not to short the pads together.
  4. Place the red lead from the battery clip against the bead of solder on the "P+" pad and heat the pad and wire together with the soldering iron. When the solder flows, hold the parts together and remove the iron. Let the solder cool, then let go.
  5. Repeat previous step with black lead and "P-" pad. Refer to photos to see how this should be arranged. Note that you should follow the label on the board, not right vs. left, as your breakout board may have the pads on opposite sides.
Connect the Capacitor

When the imp turns on its WiFi transmitter, it can draw a lot of current (up to 400 mA, during initial calibration) from your power supply. To keep this sudden current draw from "drooping" the power supply and browning out your tempBug, we've got a BIG HONKING CAP. We'll connect the capacitor in parallel with the battery, the battery will charge the capacitor to the same voltage as the battery, and if the imp suddenly demands more current than the battery can dish out, the capacitor will pitch in to help out. 
  1. The leads on the capacitor go through the breakout board at "VIN" and "GND" which are next to each other along the bottom edge of the board. Note that the negative side of the capacitor is marked with a big stripe with a "-" sign in it, and should go to ground
  2. One pad at a time, use the soldering iron to heat the wire and the pad, then flow some solder onto the joint and remove the iron.
  3. When you're all secure, trim the excess from the capacitor leads with your angle cutters or wire cutters.
Connect the Resistor
  1. The 100kΩ resistor can go either way around and is connected between pin9 and 3V3 on the electric imp breakout board. 
  2. Bend the wire leads to fit and push them through the holes marked "3V3" and "Pin9".
  3. Just as you did with the capacitor leads, solder ONLY THE 3V3 SIDE to the breakout board. The thermistor needs to share the Pin9 pad with the resistor, so don't solder that side yet!
Connect the Thermistor
  1. Just like the resistor, the thermistor is a passive component and can go either way around. If you bought the same one as me, the wire ends come pre-stripped. Push one end through the Pin9 hole and the other through the hole marked "Pin8". 
  2. Now, solder the resistor and thermistor leads together through the Pin9 pad.
  3. Lastly, solder the last thermistor lead into the Pin8 pad.

Alright, all wired up! Let's take a look at what you just built.

Step 3: How's this thing work?

Picture of How's this thing work?
The operating principle behind the tempbug is really simple. All we're doing here is making a resistive divider using a resistor and a thermistor, and measuring the voltage in the middle using an Analog-to-digital converter in the electric imp.

Wait, what's a thermistor?

A thermistor is a temperature-dependent resistor; it has a specific resistance at room temperature, and its resistance varies in a known proportion with the temperature of the component. In our case, we've selected a NTC, or negative-temperature-coefficient thermistor; the resistance of the part will decrease as temperature increases.

Got it, but what's the deal with the resistor? 

Together, the resistor and thermistor form a resistive divider; the two resistors, wired up in series (end-to-end) have an effective resistance equal to the sum of their individual resistances. This determines the amount of current that flows through them: V=I*R (ohm's law), V=3.3V (from the imp breakout board's 3.3V on-board power supply), R = the 100kΩ + the thermistor's resistance at the current temperature -> now we know how much current is flowing through the circuit. 

Going back to Ohm's Law, we know that the voltage across the thermistor = I*R, where I is the current through the divider (they're in series, so both components see the same current), and R is the current resistance of the thermistor. Therefore, if we can measure the voltage at pin 9, we can solve for the resistance of the thermistor. Given the thermistor's resistance, we can determine the temperature of the part.

Hey wait, the other side of the thermistor isn't connected to ground!

Right you are. It's connected to pin 8. This is a sneaky trick we'll use to save the battery. Current flowing through the resistive divider drains the battery, so we'll only let the current flow when we want to measure the temperature. We do this by programming pin8 to be a digital output. When we set pin 8 high, the voltage drop across the divider is 0V, so no current flows. When we want to take a measurement, we drive pin 8 low and sink current from the divider through the imp. 

How do we actually do the measuring?

To measure the voltage across the thermistor, we set up pin 9 as an analog-to-digital converter, which allows us to take an accurate measurement of the analog voltage on the pin using the imp. Check out the software in a few steps to see how that's done. 

Step 4: Power up!

Picture of Power up!
Ok, enough math, let's get to the actual temperature-measuring part. 

Connect the battery

To secure the battery to the breakout board, a little square of foam tape will do the trick. Cut a small piece off with a pair of scissors and stick the sticky side to the back of the breakout board. Peel back the backing film, and stick the battery on, making sure to keep it nice and square - this stuff is sticky! Once you've got it stuck in place, go ahead and connect the battery clip.

Check the jumper

Make sure the jumper on your breakout board is set to connect the middle pin and the "BAT" pin. Check the photos if you're not sure. If your imp doesn't power up when you click it into the socket, double-check the jumper.

Plug in the imp

Insert your imp into the socket on the breakout board, and it should start to blink red or orange (unless you've connected it before on this network, in which case it will just connect again). Congrats! You're powered up and ready to blink up and program.


If you haven't already registered as an electric imp developer, you'll need to do that now. Head to to sign up (it's free). You'll also need to download the electric imp app on your smart phone, which is also free - just search for "electric imp". Log into the app with the same account credentials you used to register at 

Once you're logged in, add your wireless network to the list of networks in the electric imp app. If you're on iOS, it will prompt you to allow it to use the network you're already on, and you'll just need to add the password yourself. To add a new network manually, select "other network" and type in your SSID and password. Check the "save this network" button!

Once you've added the network, you're ready to configure the device with BlinkUp. Make sure the imp is powered up. If it's powered up but stopped blinking, reset the power by "push-pushing" the card (push once to disconnect, count to 3, push again to reconnect) so you can be sure it's listening for the BlinkUp signal. 

Hold the screen of your phone against the top edge of the imp and press "send BlinkUp" in the electric imp app. The screen on your phone will begin to blink quickly for about 10 to 20 seconds, then stop. The imp should blink green once ("got it!"), then start to blink red/orange ("found the network, connecting to the electric imp server"). After a second or so, the imp should be able to phone home to the electric imp server, and will start to blink green. You're connected. Excellent.

Now it's time to program the imp! Head to the next step.

Step 5: Setting your imp firmware

Picture of Setting your imp firmware
Point your browser to again and log in. This takes you back to the IDE window.

If you've connected this imp breakout board before (you pro), it will pop back up in the IDE under the model it was last a part of. If this is a brand-new breakout board, it will appear in the IDE's left-hand nav panel under "New Devices", at the top of the panel. You'll see a little number in this panel showing the number of new devices there waiting to be configured - probably just one!

Click "New Devices" to see the list of new devices. Again, if you've never configured this device before, it won't have a name, so it will default to a long hex string (this device's Device ID). Click on the device to open up the settings for the device. This is where you can name the device and assign it a model. Go ahead and name it whatever you like, and create a new model by typing a name for your new model in the model drop-down. When you hit "save changes", you'll be taken to the code window for this new model, and you'll see your new device is now listed under that model in the left-hand nav.

A model has two parts: an agent and a device. The device firmware is simply the code that runs on the imp itself. The agent is that device's partner - a tiny server that runs in the electric imp cloud. The device and agent can send information back and forth, and the agent can talk to the rest of the internet and has its own URL. You get to write code for both of them.

... Or you can use the code that's already written for you :) Head to github, and notice that there are two files here - one for the agent and one for the device. Accordingly, there are two windows for you in the IDE - one will say "agent" and the other "device". Copy the correct code into each window.

If you hit "Build and Run" now, you'll see the device read the temperature and then go to sleep, but the agent will have an error when it tries to log the data to Xively because you haven't added your Xively account yet. Let's do that next. If you did do this, and your device has gone to sleep for 15 minutes, you can disconnect and reconnect power (by simply pulling and re-inserting the jumper) to get the imp to wake up again. 

Let's connect your new thermometer to Xively to log the data, then we can come back and take a look at what makes the firmware work. 

Step 6: Connecting to Cosm

Picture of Connecting to Cosm

To connect your thermometer to Xively, you'll first need a Xively account. Head to and register if you haven't already (again, it's free). When you register, you'll be taken to a page which enthusiastically encourages you to create a new device. Go ahead and click the big plus button. Creating a new device is quite simple: name it, describe it, click the "Private Device" radio button (unless you want a public device!), and click the "add device" button. This will take you back to the dashboard for your new device, where there's some important info waiting for you.

Inside the dashboard for your newly-created device, you'll find your API key and a "feed ID" for the feed you've just created. You need to add these parameters to the agent in order to get things working. Copy each from the channel dashboard and use them to fill in lines 7 and 8 of your agent firmware.

The agent is set up to create a temperature channel for you inside this feed, so you don't even need to do that. You can go ahead and hit "Build and Run" in the agent now, and you're off to the races.

After a few updates, you'll have a nice graph of the history of your datastream!

Let's head back to the code editor and take a look at how the imp is working this magic.

Step 7: Digging into the Code

Picture of Digging into the Code

Imp firmwares are written in an object-oriented language called squirrel, which looks and feels a lot like javascript. Squirrel runs in a virtual machine on top of the imp OS inside the imp, so runtime errors won't knock your device offline, and you have access to a lot of nice OS-based features, like buffered serial input and easy one-line APIs to set GPIOs or communicate with peripheral devices.

To take a look at all the things you can do in your imp firmware, check out the electric imp API reference and electric imp worked examples page. To see which pins can do what, check out the imp pin mux.

Our code here is pretty simple. Here's our basic operating procedure:

  • Set some constants
  • Define a class for our temperature sensor
  • Instantiate our class to create a temperature sensor object
  • Read the Temperature Sensor
  • Send the datapoint to the agent
  • Schedule ourselves to wake up in a bit and do it all again

The constants on lines 9 to 12 look a little ominous, but they're simple. These are the parameters for your thermistor - you can find them on the datasheet for the thermistor you're using. If you're using the thermistor I linked to earlier, you can even keep the parameters already set here.

Lines 22 to 83 are a class definition - this is basically a set of instructions for how to do various important things with a thermistor, like read the temperature. This comes straight from github - it's a nice, modular piece of code so that it can easily be reused.

After that, we just need to define our high-level logic. On lines 91 to 95, we configure the two pins we're using. Remember from when we built the device - one of the pins is an enable pin, which will allow current to flow through the thermistor when it is set low. The other pin is our analog input pin, which we'll use to read the voltage across the thermistor.

// Configure Pins
// pin 8 is driven high to turn off temp monitor (saves power) or low to read
therm_en_l <- hardware.pin8;
// pin 9 is the middle of the voltage divider formed by the NTC - read the analog voltage to determine temperature
temp_sns <- hardware.pin9;

On Line 99, we call on our class definition from earlier to create a thermistor object. This object takes in the constants we set earlier, and has methods that allow us to read the temperature in Celsius or Fahrenheit.

// instantiate our thermistor class
myThermistor <- thermistor(temp_sns, b_therm, t0_therm, r_therm, 10, false);

Lines 101 to 109 are where the magic happens - we enable the sensor, take a reading, send it to the agent, and disable the sensor again to save battery.

// enable the temperature sensor
local id = hardware.getdeviceid();
local datapoint = { "id" : id, "temp" : format("%.2f",myThermistor.read_f()) } agent.send("data",datapoint);

And lastly, schedule a wakeup in fifteen minutes. We'll go to deep sleep in the mean time, saving the battery:

//Sleep for 15 minutes and 1 second, minus the time past the 0:15
//so we wake up near each 15 minute mark (prevents drifting on slow DHCP)
imp.wakeup(3, function() { server.sleepfor(1 + 15*60 - (time() % (15*60))); });
// full firmware is reloaded and run from the top on each wake cycle

That's the device firmware - let's take a look at the agent. You've already seen part of the agent - we set the Xively API Key and Feed ID on lines 7 and 8 of the agent earlier. Below that, we have more class definitions - three of them. Just like the class definition that gave instructions for working with a thermistor, these class definitions give instructions for sending and receiving data from Xively over HTTP.

Lines 135 to 137 are a really interesting bit of code - this is the hook that the agent uses to receive new temperature data from the device. This is done by registering an agent "callback" with agent.on. This says, "when the device sends you an event called "temp", call the following function with the data marked with that tag". Looking back at line 108 of the device firmware, we see that we sent data marked "temp" with a function called "agent.send". This is where that data went!

device.on("data", function(datapoint) {
postToXively(datapoint.temp,; });

Lastly, we see the agent do two things when it first starts running. The first: it sends a log message letting us know that it started and is ready to get data. Second, it instantiates two of the Xively objects we defined earlier, letting us use the methods of those classes to send data to Xively as it comes in.

The agent doesn't restart or sleep; it starts the first time the device boots with this model, and continues to run forever, handling each new datapoint when it comes in by calling the "device.on" callback. It's the device's brain in the cloud!

That's the firmware! Enjoy your new internet-connected thermometer.

1-40 of 84Next »
achary5 days ago

hello sir i need to build a wake up signal with int pin with other exisiting pins through pushbutton, like pin1 can be wake by pin2 and pin5 via pushbutton pressed..

Ryan1219782 months ago

Thanks for making this easy to build! but I'm having a problem Xively isn't allowing any new accounts now. so i have this but have no where to sent the info. i tried to use another site but the code wont work with the way its wired. i was wondering if you have any ides what i can do. thanks for any help you can give!

tombrew (author)  Ryan1219781 month ago
Wondered if that would happen. has a nice graphing front end for devices like this. They built their front end on top of Sparkfun's data store. It looks pretty good - I should get around to switching my examples all over to it. Try it out here:

Hi, I just found a blog entry about temperature logging using the Electric Imp and using a graph from ThingSpeak here:

I'm a novice at programming, but do you think it would be possible to reuse the code from Slickstreamer in the Tempbug project?

ThingSpeak graph.png
raydlettca2 months ago

I had the thermometer up on Xively yesterday, but was having trouble with measuring temperature. Then I tried to modify the code, made a mess, and then decided to start from scratch and got rid of everything on electric imp. I started by attempting to relink via BlinkUp and can't get it to link up. Any thoughts on how to get BlinkUp to work again?

tombrew (author)  raydlettca2 months ago

You actually don't need to BlinkUp again; you can just edit the code in the model you've already created. When you hit "build and run" in the IDE, the code you have in the IDE is built and sent to the imp, wiping out the previous code.

BlinkUp is only needed when initially configuring or changing the WiFi credentials on the imp. As long as you're in the same Electric Imp account and on the same WiFi network you were on before, there's no need to do it again.

If you've lost your WiFi configuration and are now having trouble using BlinkUp to get it back, you can take a look at the documentation and tips on BlinkUp here:

KRS Test3 months ago

Thanks for a great list of instructions. You really have done an outstanding job making this manageable for a for someone with limited tech skills!

I have been able to setup the code and the integration to Xively but am having trouble with the readings. The readings remain steady at say 50 for quite a while then spike up to 120 or plunge to -119. Sometimes they stay at say -10 for an extended period of time. Attached is a picture of the Xively graph.

Have tested the readings by placing the E-Imp next to hot and cold items but there is little fluctuation in the readings.

No doubt I have made a simple error somewhere but am struggling to find it.

For the moment the power supply is by USB from a laptop. Am planning on soldering on the battery once the readings work properly.

Any feedback or suggestions would be appreciated.

Thanks again!

Electric Imp output.jpg
tombrew (author)  KRS Test2 months ago

Sounds like a flaky connection somewhere in your thermistor circuit. Go back over your solder joints and make sure they're all holding together properly. It might be a good idea to look up a tutorial on soldering if you're unfamiliar; I've covered the basics here but a more in-depth of cold solder joints and how to avoid them might save you some time.

lathyrus1 year ago
Wow! Despite not having soldered anything for about 30 years, I was able to build this thermometer without any real difficulty in a couple of hours, and I understand how it works! Thanks Tombrew for the excellent instructions. The only problem I had was that the guy in Maplins gave me the wrong size fixed resistor, so the first time I built it the reading in my livingroom was a chilly -159 degrees C... but with the correct 100k Ohm resistor everything is fine. I also couldn't get blinkup to work with my Sony Android phone so I had to borrow my wiffe's iPhone to do the setup. And getting Xively (Cosm) to draw graphs was tricky until I figured out that I needed a MASTER API key, available under the Settings tab.
lathyrus lathyrus5 months ago

Follow-up: The tempbug has been running smoothly in my attic for 9 months now. My first 9 volt battery lasted only a month, checking the temperature every 15 mins. So I changed the interval to 2 hours and my second battery lasted 6 months. I also noticed that the first temperature reading in each cycle is a bit higher than the others (by about 0.5 degree, I don't know why) so I modified the code to ignore the first reading and average the next 10:

2014-07-14 06:00:08 UTC+1[Device]ignore: voltage: 3.315 temp: 19.4 C2014-07-14 06:00:08 UTC+1[Device]loop: 0 voltage: 3.313 temp: 18.9 C2014-07-14 06:00:08 UTC+1[Device]loop: 1 voltage: 3.311 temp: 18.4 C2014-07-14 06:00:08 UTC+1[Device]loop: 2 voltage: 3.311 temp: 18.2 C2014-07-14 06:00:08 UTC+1[Device]loop: 3 voltage: 3.311 temp: 18.1 C2014-07-14 06:00:08 UTC+1[Device]loop: 4 voltage: 3.313 temp: 18.2 C2014-07-14 06:00:08 UTC+1[Device]loop: 5 voltage: 3.309 temp: 18.3 C2014-07-14 06:00:08 UTC+1[Device]loop: 6 voltage: 3.311 temp: 18.2 C2014-07-14 06:00:08 UTC+1[Device]loop: 7 voltage: 3.313 temp: 18.2 C2014-07-14 06:00:08 UTC+1[Device]loop: 8 voltage: 3.311 temp: 18.6 C2014-07-14 06:00:08 UTC+1[Device]loop: 9 voltage: 3.311 temp: 18.1 C

Building and programming the Imp was so much fun that I bought 2 more and made a phone-controlled electric gate opener, and a gizmo for forcibly rebooting my Wowwee Rovio...

Thanks again Tombrew for the great intro and instructions!

how did you change to a 2 hour interval? was it in the code inserted into electric imp? if so where?

Here's the complete Device and Agent code that I'm using. It logs the temperature on odd-numbered hours (1 a.m., 3. a.m. etc). It uploads to Xively the temperature (Celsius), WiFi signal strength, battery voltage, and lag (how long it took to do the measurement cycle).

//KW tempbug device code v2 20nov2013
// April with a 100k resistor from 3V3 to pin9 and 100k NTC Thermistor from pin9 to pin8
// pin8 TEMP_READ_EN_L - drive low to enable temp reading (great for batteries!)
// pin9 ANALOG NTC value
// benchmarking runtime: first tick with hardware.micros
local tick = hardware.micros();
// turn on WiFi powersave to reduce power consumption when awake
// WiFi is not used until line 44 (no communication with agent until end of program)
// Configure Pins
// pin 8 is driven high to turn off temp monitor (saves power) or low to read
// pin 9 is the middle of the voltage divider formed by the NTC - read the analog voltage to determine temperature
// all calculations are done in Kelvin
// these are constants for this particular thermistor; if using a different one,
// check your datasheet
const b_therm = 4450;
const t0_therm = 298.15;
// turn on the thermistor network
// gather several pin9 ADC and battery voltage readings and average them
// (just takes out some noise)
local val = 0;
local v_high = 0;
//skip first measurement (always low)
local v_high_now=hardware.voltage();
local v_therm = v_high_now * val_now / 65535.0;
local r_therm = 100000.0 / ( (v_high_now / v_therm) - 1);
local ln_therm = math.log(100000.0 / r_therm);
local t_therm = (t0_therm * b_therm) / (b_therm - t0_therm * ln_therm) - 273.15;
local t_str = format("%.01f", t_therm);
local batt_str = format("%.03f",v_high_now);
server.log("ignore: voltage: " +batt_str +" temp: " +t_str+" C");
//then measure 10 times
for (local i = 0; i < 10; i++) {
val_now =;
v_high_now = hardware.voltage();
v_therm = v_high_now * val_now / 65535.0;
r_therm = 100000.0 / ( (v_high_now / v_therm) - 1);
ln_therm = math.log(100000.0 / r_therm);
t_therm = (t0_therm * b_therm) / (b_therm - t0_therm * ln_therm) - 273.15;
t_str = format("%.01f", t_therm);
batt_str = format("%.03f",v_high_now);
server.log("loop: " +i +" voltage: " +batt_str +" temp: " +t_str+" C");
val += val_now;
v_high += v_high_now;
val = val/10;
v_high = v_high / 10.0;
// turn the thermistor network back off
// scale the ADC reading to a voltage by dividing by the full-scale value and multiplying by the supply voltage
local v_therm = v_high * val / 65535.0;
// calculate the resistance of the thermistor at the current temperature
local r_therm = 100000.0 / ( (v_high / v_therm) - 1);
local ln_therm = math.log(100000.0 / r_therm);
local t_therm = (t0_therm * b_therm) / (b_therm - t0_therm * ln_therm) - 273.15;
// format into a string for the string output port
local t_str = format("%.01f", t_therm);
server.log("Current temp is "+t_str+" C");
// update the current battery voltage with a nicely-formatted string of the most recently-calculated value
local batt_str = format("%.03f",v_high);
server.log("Battery Voltage is "+batt_str);
// benchmarking runtime
local tock = hardware.micros();
server.log(format("Read cycle took %d us", (tock-tick)));
local lag = ((tock-tick)/1000000.0);
local lag_str = format ("%.06f",lag);
//log WiFi signal strength
function ReportRSSI() {
local rssi = imp.rssi();
if (rssi < -87) {
server.log("WiFi signal is: " + rssi + " dBm (0 bars)");
else if (rssi < -82) {
server.log("WiFi signal is: " + rssi + " dBm (1 bar)");
else if (rssi < -77) {
server.log("WiFi signal is: " + rssi + " dBm (2 bars)");
else if (rssi < -72) {
server.log("WiFi signal is: " + rssi + " dBm (3 bars)");
else if (rssi < -67) {
server.log("WiFi signal is: " + rssi + " dBm (4 bars)");
else {
server.log("WiFi signal is: " + rssi + " dBm (5 bars)");
return rssi;
local rssi = ReportRSSI();
//attempt to send it to Xively...
agent.send("Xively-temp", t_str); // send data to Xively
agent.send("Xively-lag", lag_str); // send data to Xively
agent.send("Xively-battery", batt_str); // send data to Xively
agent.send("Xively-rssi", rssi); // send data to Xively
// wake up every 2 hours on odd-numbered hours (prevents drifting on slow DHCP)
imp.onidle( function() {
local secsToEvenHour = (1+ 120*60 - (time()%(120*60)) );
local secsToOddHour = secsToEvenHour - (60*60);
if (secsToOddHour < 0) {secsToOddHour += (120*60);}
local snoozelength = secsToOddHour;
server.log("snoozing for " + (snoozelength / 60) + " minutes and " + (snoozelength % 60) + " seconds" );
// full firmware is reloaded and run from the top on each wake cycle, so no need to construct a loop
##################### CUT HERE ######################
//KW tempbug agent code v2 20nov2013
//********************BEGIN XIVELY********************
//Code written by @beardedinventor modified for use by Joel Wehr
API_Key <- "pdyL6p9fp9zVtakiNqFGTaKGXPwqnMuxCdfM7258b1D8D6LI"; //Type your Xively API Key
Feed_ID <- "1282406454" //Type your Feed ID
/// Channel_ID <- "thermistor"; //Type your Channel ID -- modified by KW - see bottom of program
Xively <- {}; // this makes a 'namespace'
class Xively.Client {
ApiKey = null;
triggers = [];
constructor(apiKey) {
this.ApiKey = apiKey;
* method: PUT
* IN:
* feed: a XivelyFeed we are pushing to
* ApiKey: Your Xively API Key
* OUT:
* HttpResponse object from Xively
* 200 and no body is success
function Put(feed){
local url = "" + feed.FeedID + ".json";
local headers = { "X-ApiKey" : ApiKey, "Content-Type":"application/json", "User-Agent" : "Xively-Imp-Lib/1.0" };
local request = http.put(url, headers, feed.ToJson());
return request.sendsync();
* method: GET
* IN:
* feed: a XivelyFeed we fulling from
* ApiKey: Your Xively API Key
* OUT:
* An updated XivelyFeed object on success
* null on failure
function Get(feed){
local url = "" + feed.FeedID + ".json";
local headers = { "X-ApiKey" : ApiKey, "User-Agent" : "xively-Imp-Lib/1.0" };
local request = http.get(url, headers);
local response = request.sendsync();
if(response.statuscode != 200) {
server.log("error sending message: " + response.body);
return null;
local channel = http.jsondecode(response.body);
for (local i = 0; i < channel.datastreams.len(); i++)
for (local j = 0; j < feed.Channels.len(); j++)
if (channel.datastreams[i].id == feed.Channels[j].id)
feed.Channels[j].current_value = channel.datastreams[i].current_value;
return feed;
class Xively.Feed{
FeedID = null;
Channels = null;
constructor(feedID, channels)
this.FeedID = feedID;
this.Channels = channels;
function GetFeedID() { return FeedID; }
function ToJson()
local json = "{ \"datastreams\": [";
for (local i = 0; i < this.Channels.len(); i++)
json += this.Channels[i].ToJson();
if (i < this.Channels.len() - 1) json += ",";
json += "] }";
return json;
class Xively.Channel {
id = null;
current_value = null;
{ = _id;
function Set(value) {
this.current_value = value;
function Get() {
return this.current_value;
function ToJson() {
local json = http.jsonencode({id =, current_value = this.current_value });
return json;
client <- Xively.Client(API_Key);
//********************END XIVELY********************
device.on("Xively-temp", function(v) {
channel1 <- Xively.Channel("temperature");
feed1 <- Xively.Feed(Feed_ID, [channel1]);
device.on("Xively-lag", function(v) {
channel1 <- Xively.Channel("lag");
feed1 <- Xively.Feed(Feed_ID, [channel1]);
device.on("Xively-rssi", function(v) {
channel1 <- Xively.Channel("WiFi");
feed1 <- Xively.Feed(Feed_ID, [channel1]);
device.on("Xively-battery", function(v) {
channel1 <- Xively.Channel("battery");
feed1 <- Xively.Feed(Feed_ID, [channel1]);
lathyrus lathyrus2 months ago

Here are the graphs on Xively for 3 months

lathyrus lathyrus2 months ago

And here's what my code writes to the Electric Imp IDE log window every 2 hours.

BenC43 months ago

What kind of wireless range does the imp have?

lathyrus BenC42 months ago

Similar to a laptop's wifi card. My Imp in the attic and the router is in the hallway 2 floors below it on the opposite side of the house. When the Imp's battery begins to run out, the WiFi signal it detects drops, and when if falls below about -93 dBm it can't connect anymore.

raydlettca2 months ago

Thanks for the instructions, there were one thing that was not mentioned in putting this together, the 2 pin jumper. I temporarily made one from wire. One problem that I am having is I am not getting temperature reads. The request log is running properly - there are request and responses - but nothing shows up in the graph to the left. Any thoughts?

Try to write the temperature as a server.log() statement in the Imp IDE first, to make sure the thermistor is working correctly, before you try to draw graphs in Xively. Uploading data to Xively is tricky - I eventually got something to work, but I don't really understand how it works!

lenny20207 months ago

I tried to build it--great, thorough, easily understandable instructions, but I am not getting any info posted to Xively. I copied the info for lines 7 and 8, and although the project seems to cycle as expected, the log states:

Posted to Xively: 120.21, got return code: 56, msg: <html>

<head><title>400 Bad Request</title></head>

body bg color="white">

<center><hi>400 Bad Request</hi></center>




I am getting no data posted, and the Request log sits empty with the "waiting for requests area" just cycling. Where have I screwed up? I could send you any additional information you request, if needed

tombrew (author)  lenny20207 months ago

Hi Lenny,

Sorry, that sounds frustrating! Let's look over your code on a direct message.

davemack tombrew4 months ago

I have also just built this and get this message when it tries to send data to Xively. Perhaps I have the same issue as Lenny.

2014-07-21 14:45:04 UTC-4
Posted to Xively: 71.60, got return code: 56, msg: <html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>

davemack davemack4 months ago


With Lenny's help I found the problem! The Feed ID is a number and should not have quotation marks around it.

My unit now works.



HandyFrank6 months ago

I've been wanting to create a wifi thermometer for a while, this plan looks perfect! I'm a newbie when it comes to building electronics so I have a few questions if you can share some knowledge.

Are the 2 breakout boards you link to different from each other, or one an older version or something? I noticed one is the April breakout and is green, and the other just lists as a plain breakout board and is red. Any different and is one better than the other? I see in your pics you used the green april breakout board I think.

Any way to add a humidity sensor into the mix? Would that require a whole set of different details, or can it be blended into the existing coding and add either a combo temp/humidity sensor, or a separate humidity sensor?

I can in theory build this on a mini breadboard before doing any soldering, right? Maybe i'll do that and practice my soldering skills on a test board so I don't mess up the breakout board.

Any recommendations on a soldering iron that is decent, but won't break the bank for someone who hardly does soldering? Any tips on resources for getting into learning more about how all of this works? I'm a complete newbie so I can use tips on soldering, recommended entry level equipment, understanding of circuits and all the components, etc. I see that Amazon (and AdaFruit) sell breadboard starter kits that mention Arduino. Is that a good thing to buy to start playing and learning? Is Arduino way harder to use vs. Electric Imp?

Seems like DigiKey has everything needed to build this, I think i'll order from them.


tombrew (author)  HandyFrank6 months ago

The green and red breakout boards are identical - use either of the ones I linked to.

This instructable doesn't cover what you need to do temperature and humidity sensing, but you might take a look at the electric imp reference code for the DHT11:

You certainly can build this on a breadboard, but you'll need to make sure you get an electric imp breakout board with headers, or put headers on your breakout board. You should check with google for the best soldering iron recommendations; I've got a pretty nice one and am therefore spoiled.

Arduino vs. Electric Imp isn't really harder/easier; they're different device with different purposes. I can't speak to much on Arduinos goals as a project or tool, but I can say the Electric Imp is made specifically to connect things to the internet, and it does that quite well.

Best of luck and have fun!

illiac46 months ago

I have made it but it shows around 80. I assume thies is in fahrenheit. What do i need to change that it will be displayed in celsius? TNX

tombrew (author)  illiac46 months ago
Yep, it defaults to fahrenheit. You can change it to celsius by calling "read_c" instead of "read_f" on line 103 of the device code.
dbehman7 months ago

Excellent article! I'd like to build this for a swimming pool thermometer. Do you think this would work with the sensor submerged?

tombrew (author)  dbehman7 months ago

I think it could (not the imp and power supply, though!) The longer the leads on your thermistor, the less accurate it will be. A creative mechanical design could help, or you could look into thermocouples.

byron1127 months ago

hi im trying to build the temp bug and i have it all wired up and i have used the imp before to turn on and off a light. but now that i have it programed and all hooked up and cap hooked up the right way. the imp card blinks red 3 times then flashes green for half a sec then it turns off. what does this mean??? Ive tried powering it via usb and 9v battery. same thing... any help would be great!

tombrew (author)  byron1127 months ago

That's actually just it working! The three red blinks are the imp attempting to connect to your WiFi, the one green blink happens when it connects. As soon as it connects, it runs the entire firmware and uploads the measurement in about a second, then goes to deep sleep - which is why you see it stop blinking. You should see it do this once every 15 minutes.

ai4px8 months ago

THanks.... just what I was looking for! Didn't even know about IMP.

365nice made it!9 months ago

A quick follow up - I added 3 sensors to measure temperature at several points (which works reasonably well). Note: the imp libraries have been changed - with new agent code that runs on a server to connect to Xively (was Chosm). There are examples on the imp site. This said - this was the article that inspired me - so thanks!

ygodnik 365nice9 months ago


I saw that you added sensors. I am reasonable at making circuits, but am very poor at coding (basic python and a matlab experience). I have two questions. Could I see a copy of your code? Also, if someone is fairly illiterate in coding, is there a place one can go to get the basics on squirrel? I look online and what I find is, which assumes a solid level of coding knowledge initially. It is like he is trying to explain how to speak chinese to me in swahili. I would really like to learn some nuts and bolts so I can modify things and trouble shoot reasonably intelligently.

For example,

therm_en_l <- hardware.pin8;

In this command, it seems like "therm_en_I" is one piece, but is it an built in command? I see the "<-" piece and I don't know what it means. It seems like the "." links objects together, but I am not sure when it is allowed, how it functions, etc.

Thank you for your time, and thank you to the author for the tutorials.

tombrew (author)  ygodnik9 months ago
Hi ygodnik,

I actually did link to the source code for the project in the instructable - it's all at

The line of squirrel you referenced is not a built in command; that line "aliases" the hardware.pin8 object with the name "therm_en_l".

I don't know of any really good squirrel-specific tutorials, but the language is in many ways similar to javascript. There are a boatload of places online to learn how to write decent javascript for free.

Thanks for the feedback and good luck!
ygodnik tombrew9 months ago

Thanks a bunch Tom. I did get everything working with one sensor, but I am afraid if I tried to change to much in your script with my current knowledge, I would just get myself in trouble. I will learn Javascript for dummies and then come back and see if I can get multiple components and new configurations figured out effectively.

Thank you again for the excellent program (with helpful comments) and for your help here.

discostu95610 months ago
Very nicely written. Answered questions that popped up along the way, and explained why you used what at each step. Learned a lot reading this. Thanks for such a good instructable, look forward to making one
(removed by author or community request)
tombrew (author)  smilesfromnowhere11 months ago
Hi smilesfromnowhere,

I've just pushed a small update to the github code that removes a deprecated call that may have caused errors device-side. I'm running this code on my own tempbug right now and things are working properly.

I also added two things to the agent code:

1. The agent now logs the data sent and the return code and message from Xively when attempting to PUT to the feed.

2. The agent now appends the device ID from the specific tempBug to the Xively channel name. This allows you to have many tempBugs on a single Xively feed, so you can view all the graphs on one page if you want.

Give this a try and let me know if trouble persists. If nothing else, logging the response from Xively should give us something to go on.


I was an *idiot*. The original problem was from having the feed id and the api key switched.

I get errors with the new code:
"the index 'resp' does not exist"
"at postToXively:152"
"from unknown:159"

...I have multiple thermistors wired up to this board but don't know how to 'instantiate' four different thermistors (yet).

Best Regards,
tombrew (author)  smilesfromnowhere11 months ago
No worries! I've published things with bigger mistakes than that ;)

Have you pulled the code from github again since you switched the Xively parameters back? I believe I pushed a fix for the error you're seeing above.
1-40 of 84Next »