Thermostat
How can one temperature measurement produce stable on/off behavior instead of rapid chatter?
A thermostat closes an information-feedback loop: a sensor estimates temperature, the controller compares it with a setpoint, and an output requests heating or cooling. The environment changes slowly, so the next measurement reflects the result after delay. Hysteresis—different turn-on and turn-off thresholds—prevents rapid switching near the setpoint. A real building adds electrical ratings, equipment modes, minimum run times, fail-safe behavior, installation rules, and professional commissioning that the LED analogue does not provide.
Follow the flows
Energy makes change possible. Information selects, sequences, and corrects that change.
Energy
- Building energy source
- Heating/cooling equipment
- Thermal transfer to or from room
- Walls, air, and contents
- Stored heat and losses to outdoors
Information
- Temperature sensor and setpoint
- Error plus prior state
- Hysteresis/timing logic
- LED request in the analogue
- Changed environment returns to sensor
Subsystem map
Observe externally first; documentation fills in what the enclosure deliberately hides.
Temperature sensor
Convert local physical temperature into a measurement with finite accuracy and response time.
- Energy or signal
- Ambient heat affects sensor; digital measurement enters the controller.
- Observe
- Compare displayed temperature with location, drafts, sunlight, occupancy, and time rather than assuming it equals every room surface.
Setpoint and mode input
Capture the desired threshold and heating/cooling/off intent.
- Energy or signal
- User command becomes a stored setpoint and operating mode.
- Observe
- Change one setting during normal use and note requested versus measured temperature and any delayed response.
Comparator and state logic
Calculate error, apply hysteresis and timing rules, and choose an output state.
- Energy or signal
- Measurement + setpoint + prior state → heat/cool/off request.
- Observe
- Record the points where an indicator turns on and off; different thresholds reveal hysteresis.
HVAC output and environment
A real system safely commands separate equipment that transfers thermal energy; the room feeds a new measurement back.
- Energy or signal
- Control request → HVAC energy transfer → room temperature change → sensor feedback.
- Observe
- Use documentation and normal indicators only; do not access building wiring, combustion equipment, or refrigerant systems.
Test the idea safely
Proposed, unvalidated bench exercise: an original Pico reads an Adafruit BME280 and drives a low-voltage LED request indicator using explicit hysteresis and fault handling. It is not an HVAC controller, household-equivalent thermostat, safety device, or completed BOM.
Goal
Measure a BME280 temperature signal and use an LED to compare single-threshold control with hysteresis.
Procedure
- Verify the exact breakout, headers, voltage, interface, address, and Pico pin wiring from current documentation before power.
- Log stable room readings first and choose a nearby demonstration setpoint; record sensor resolution and observed variation.
- Predict LED behavior with a single threshold, implement it, and gently warm the nearby air with a hand held at a distance—without touching or heating the board directly.
- Add separate on/off thresholds, repeat the same observation, and compare the number of transitions and threshold crossings.
- Disconnect or mis-address the sensor in a powered-off setup, then verify that the program reports a sensor fault rather than requesting heat.
Observe
- Measured temperature over time
- LED transition temperatures
- Transition count near setpoint
- Sensor-fault behavior
Diagnose
- No sensor data: remove power and check board identity, address, interface, wiring, and pull-ups/documented library setup.
- Chattering LED: inspect threshold order, measurement noise, update interval, and retained prior state.
- Large offset: examine placement, self-heating, airflow, and reference uncertainty before applying a calibration correction.
Limits
- The LED is only a request indicator; it must not be connected to building HVAC wiring or power equipment.
- Do not control combustion, mains, compressor, heat-pump, or life-safety equipment with this exercise.
- The bench result does not electrically qualify components or validate a thermostat product.
Learn and source deliberately
Lessons explain the transferable concepts. Supplier links identify exact candidates; they are not approval, availability, or a completed order.
Sensor shopping and assembly guide →
Open the Pico + BME280 starter →
Prerequisite lessons
Candidate parts — incomplete list
Choose supplies, connectors, mounting and tools before treating this as an order list.
- The sensor starter targets the original non-wireless Pico. Pico H adds fitted headers; confirm its firmware target. Pico W and Pico 2 require a separate firmware/pin review, not a silent substitution.
- Confirm header population, Micro-USB data cable, logic voltage, and power arrangement against the exact board before wiring.
- This is the Adafruit breakout board, not a bare BME280 sensor or a similarly named BMP280 board.
- Confirm supply voltage, I²C or SPI wiring, fitted headers, address, and environmental placement before use.