← Back to the chapter · Previous detail
Technical detail · Smart Home and Environmental Kits
Boundaries to verify before a pilot
The state that a screen displays and the state a device reaches can differ. Keep these boundaries with the test record so the next prototype can repeat the relevant checks.
- State boundary: separate desired state, reported state, physical state, cached state, retained MQTT messages, device-shadow versions, dashboard labels, and notification payloads.
- Fallback boundary: verify wall switch, local button, valve handle, thermostat control, lock override, reset path, and safe default before app or cloud control is trusted.
- Sensor boundary: check placement bias, vent drafts, sun exposure, enclosure openings, filter loading, condensation, cable routing, calibration drift, and battery replacement access.
- Operations boundary: verify pairing, rejoin, OTA update, credential rotation, hub replacement, rule rollback, audit logs, support diagnostics, and data deletion before a pilot.
The kit is ready to hand off only when the next prototype knows which state, sensing, privacy, and fallback tests must repeat after the physical or automation form changes.