Since I finished the example of how to operate the Iris Smart Switch with a Raspberry Pi, I couldn't wait to hook it to something and do something real with it. I decided to measure the power usage of my refrigerator. First, about the refrigerator: It's a refrigerator only, it doesn't have a freezer section; I have a separate freezer in the kitchen also. There's a reason for this besides showing off. Out here in the sticks where a trip to the grocery store is a major undertaking, we don't go very often. That means plenty of food storage; I have a pantry, an upright freezer and separate refrigerator in the house and a chest freezer in the garage. Yes, I can go about two weeks before I even have to go for bread and milk. This makes things like a shopping list that is up to date a valuable skill. I keep it up to date and every time I'm forced into town, it goes with me. I don't want to waste a trip.
Anyway, I put together some code and read the switch, recorded the readings in my database and updated Xively with the data. Then I suck the accumulated data from Xively and graph it to see what the appliance is doing. I didn't implement the ability to turn the switch on and off since who wants to shut their refrigerator off?? Here's a days worth of data on the refrigerator:
![]()
![]()
Notice how it's only on for a short amount of time and that, other than the spike when the compressor starts, it doesn't use much power? It's on roughly 15 minutes, and off for about 30 minutes in repeating cycles. Here is an expansion of a portion of it:
![]()
The large spike on the first 'hump' is where the compressor kicks on. It takes a lot of power to get the compressor going, but it drops off rapidly. The granularity of the readings is only a minute, and if I was graphing every few seconds, you would see spikes on all the humps. However, this is an accurate representation of what is happening overall. Notice that the 550W spike is short and that the current draw decreases over time. The average usage is probably around 110W or so for the period where the compressor is on. That's the amount of energy used by some incandescent bulbs ! Let's see what a door open does to the chart:
![]()
Notice that the power usage jumps (the hump on the right) to 300W when the door is open? It's pretty sobering that the power used by the lights when the door is open is actually more than the power used to keep the darn thing cold. Now see why they say to close the door to save energy? They just didn't tell us that the power loss was due to the bulbs, not the fact that we're warming up the fridge. I'll probably get arguments from the energy nerds out there, but for my appliance, this is true. Or, at least it is right now; I plan on getting LED bulbs to take care of that silly problem in the next couple of weeks.
Of course, there's the compressor kicking on right after I closed the door because I left the door open for a couple of minutes and it had to recover the temperature. That's why the hump for the lights is on the far right, I actually went over and opened the door to get this reading.
All in all though, the fridge is not a huge power consumer. It's less than running a 100W bulb all the time. Actually, it's probably close to a 40W bulb since it's off twice as long as it's on in any given period.
Let's review. I hacked into the Lowe's smart switch using an arduino (it's what I had to play with)<link>, ported the code to python so I could run it on a Raspberry Pi <link>, and then hooked it up to an appliance and learned that it was actually doing a good job. Actually better than I expected. Was it worth it? Of course it was. Now folks out there can take my example and measure their own appliances to compare them to their own expectations and needs.
Soon, I'll get another Smart Switch and put it in the circuit for the freezer and see how much power it uses. I expect it to be higher than the fridge because it has the same set of lights, a bigger compressor and the circuitry for auto defrost. Auto defrost is a real power monger since it actually warms up some areas of the appliance and drains the water out to be evaporated away. I also want to see how often it cycles since it could happen that the compressor on the freezer and the compressor on the fridge could overlap their cycles. That would cause a spike in power usage for the overlap period, which in turn, could cause my demand usage to rise. That's the kind of thing I want to keep track of. Demand billing is a painful thing because a simple mistake in power usage could double your monthly power bill. I have a long discussion about my experiences here <link>.
Now, go out and get your own system of monitors running. Take control of your house.
Anyway, I put together some code and read the switch, recorded the readings in my database and updated Xively with the data. Then I suck the accumulated data from Xively and graph it to see what the appliance is doing. I didn't implement the ability to turn the switch on and off since who wants to shut their refrigerator off?? Here's a days worth of data on the refrigerator:
Notice how it's only on for a short amount of time and that, other than the spike when the compressor starts, it doesn't use much power? It's on roughly 15 minutes, and off for about 30 minutes in repeating cycles. Here is an expansion of a portion of it:
The large spike on the first 'hump' is where the compressor kicks on. It takes a lot of power to get the compressor going, but it drops off rapidly. The granularity of the readings is only a minute, and if I was graphing every few seconds, you would see spikes on all the humps. However, this is an accurate representation of what is happening overall. Notice that the 550W spike is short and that the current draw decreases over time. The average usage is probably around 110W or so for the period where the compressor is on. That's the amount of energy used by some incandescent bulbs ! Let's see what a door open does to the chart:
Notice that the power usage jumps (the hump on the right) to 300W when the door is open? It's pretty sobering that the power used by the lights when the door is open is actually more than the power used to keep the darn thing cold. Now see why they say to close the door to save energy? They just didn't tell us that the power loss was due to the bulbs, not the fact that we're warming up the fridge. I'll probably get arguments from the energy nerds out there, but for my appliance, this is true. Or, at least it is right now; I plan on getting LED bulbs to take care of that silly problem in the next couple of weeks.
Of course, there's the compressor kicking on right after I closed the door because I left the door open for a couple of minutes and it had to recover the temperature. That's why the hump for the lights is on the far right, I actually went over and opened the door to get this reading.
All in all though, the fridge is not a huge power consumer. It's less than running a 100W bulb all the time. Actually, it's probably close to a 40W bulb since it's off twice as long as it's on in any given period.
Let's review. I hacked into the Lowe's smart switch using an arduino (it's what I had to play with)<link>, ported the code to python so I could run it on a Raspberry Pi <link>, and then hooked it up to an appliance and learned that it was actually doing a good job. Actually better than I expected. Was it worth it? Of course it was. Now folks out there can take my example and measure their own appliances to compare them to their own expectations and needs.
Soon, I'll get another Smart Switch and put it in the circuit for the freezer and see how much power it uses. I expect it to be higher than the fridge because it has the same set of lights, a bigger compressor and the circuitry for auto defrost. Auto defrost is a real power monger since it actually warms up some areas of the appliance and drains the water out to be evaporated away. I also want to see how often it cycles since it could happen that the compressor on the freezer and the compressor on the fridge could overlap their cycles. That would cause a spike in power usage for the overlap period, which in turn, could cause my demand usage to rise. That's the kind of thing I want to keep track of. Demand billing is a painful thing because a simple mistake in power usage could double your monthly power bill. I have a long discussion about my experiences here <link>.
Now, go out and get your own system of monitors running. Take control of your house.