CodeRigor

GUIDED LESSON / 5 OF 6

Turn readings into a desk instrument

Gather real evidence and decide whether a kit adds anything you need.

What moves through this step
  1. 01Serial records
  2. 02LED observation
  3. 03Failure recovery
  4. 04Build notes

Make the output easy to inspect

Place the board and sensor on a stable nonconductive surface. Keep the sensor away from the board's own warm components when comparing readings. The DHT11 is a basic learning sensor; repeatable operation is a different claim from calibrated accuracy.

Save a small sample of JSON lines from the serial console, along with the firmware version and wiring you used. Use a trusted reference instrument if you want to investigate error, and record placement and delay as part of the experiment.

If you reached this stage using desktop replay and now want the physical parts, the kit below is one route. No extra display or cloud service is needed for this build.

Device evidence

Show a successful reading, a deliberately disconnected data signal, recovery after restoring the signal and the corresponding LED states. Do not heat electronics or force the room to reach the thresholds. Test the 28/26 °C transitions using the pure function's synthetic inputs instead.

Try it

Add an on-screen or written legend explaining that both LEDs off can mean an unknown reading. A useful instrument makes missing data visible instead of relying on someone to remember a code convention.