software engineers shouldn’t use soldiering irons…

After a brief hiatus of 15 years, I picked up a new soldiering iron and I am actually building hardware again. I’m slowly rebuilding my lab from scratch.  The new house is going to come in handy because I actually want space for a workbench and some decent magnifying glasses, and the usual crap.

As a reflexive problem, I figured out my first new project, because I need a lab, because of the new house, oh whatever…

I’m going to try my hand at building a wireless internet thermostat for the SF house.
As it turns out, good thermostats are more complicated than one would expect.  We want hysteresis in the system so it isn’t firing and shutting down the heating/cooling units, plus, with multi-stage equipment (small and large furnace burners and small and large air conditioning) we want to intelligently maximize the use of the small (eco-friendly) stage, but kick on the big stage when the energy differential between the desired and current temperatures is high.

I just want to be able to turn off the damn heat when I’m out of the house for a few days.. or turn it on when I’m driving up from the Peninsula so it’s not freezing when I get there.