How to use Codex to diagnose local HVAC telemetry
Codex helped build a local HVAC controller and interpret its telemetry. A real RS485 fault was diagnosed and restored while deterministic control stayed local.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Inspect these RS485 registers, ESP-NOW telemetry and alarm logs from my local HVAC controller. Separate evidence from hypotheses, identify the communication fault and propose a narrow firmware or wiring check. Keep deterministic control local; ask me to confirm physical behavior before declaring restoration.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Mirek Gryzlo
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The submission reports a working local controller and a real RS485 fault traced through diagnosis to restored operation. Further ventilation expansion and cloud integrations remained plans.
- Human involvement
- Gryzlo designed hardware architecture and operating logic and checked the real communication fault and restoration demonstrated by the project.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Gryzlo designed the replacement controller and supplied its hardware and operating logic.
- Codex supported firmware and service-dongle work while interpreting collected registers and alarm history.
- The demonstration checked detection, analysis and restoration of a real RS485 communication fault.
Mirek Gryzlo used Codex while building a replacement controller after his solar-thermal controller failed. As a structural engineer rather than a professional software developer, he supplied the hardware architecture and operating logic while the agent supported implementation and diagnosis.
The system used ESP32 devices programmed in C++ with Arduino, communicating locally through RS485 and ESP-NOW. A service dongle collected registers, status and alarm history. Codex interpreted that diagnostic evidence and explained faults in ordinary language rather than becoming the controller's real-time decision maker.
The project demonstration followed a real RS485 communication fault from detection through diagnostic analysis to restored operation. That specific sequence supports more than a dashboard mockup: the control system, collected data and repair outcome were connected in the account. Intermittent faults and noisy physical equipment were the difficult part of integrating sensors, actuators and communication paths.
Gryzlo kept essential automation deterministic and independent of cloud access. The touchscreen exposed configuration, alarms and graphs, while further recuperator work and optional Home Assistant integration remained plans. The reported outcome is a working local controller and diagnostic workflow with human-designed logic, not an autonomous language model entrusted with every equipment-control decision.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Devpost · Mirek Gryzlo
Frequently asked questions
Does the controller need cloud access?
The author says essential control remains local and cloud-independent.
What evidence did Codex interpret?
Machine registers, status, telemetry and alarm history collected by the service dongle.
What fault was demonstrated?
An RS485 communication fault followed through diagnosis to restored operation.
More details
About this account
Gryzlo designed the replacement controller and supplied its hardware and operating logic. Codex supported firmware and service-dongle work while interpreting collected registers and alarm history.
Original project account opened. A real RS485 fault and restoration are reported; the controller stays deterministic and cloud-independent. Future recuperator expansion and Home Assistant integration are not treated as shipped. Suggested prompt written by Agents In Use; no original task prompt was published in the verified account.
Credit: Mirek Gryzlo — Devpost
Source published
Added to Agents In Use
Source checked
Tools and topics
Codex · ESP32 · RS485 · ESP-NOW · Arduino
HVAC diagnostics · Local control
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.