Hardware Project Planning


Understood: the HTTP API must set and read back each of the five lights and buzzer, and Home Assistant must receive state updates even when a webhook changes them directly. I recommend one shared device state, with HTTP endpoints for control/readback and MQTT state publishing for Home Assistant; this reports commanded status, not proof that a lamp physically illuminated.
In Agent mode, I’ll look up the LTA-5055TJ wiring and electrical ratings, verify the integration approach, and design the ESP32 interface around your existing hardware.
What is Agent mode?
Agent mode lets Flux build, do deep research, validate designs, and work through complex assignments.
Chat mode is just as smart and has the same engineering knowledge, but it cannot work autonomously.
Only Agent mode consumes your plan's included AI usage (measured in ACUs).
Continue in Agent Mode
I’ll check the tower’s wiring and ratings, confirm how HTTP changes will stay synchronized with Home Assistant, and record the interface design before choosing the output drivers.
ESPHome supports HTTP control/readback and live state updates to Home Assistant without an MQTT broker, so it’s the simpler approach here. I found LTA-505 family listings, but no verified wiring or current ratings for your exact tower; I won’t assume its wire colors or polarity.
Created a project doc

Project Specification

View Document

Project Specification Project Overview
  • Status: Draft; interface architecture researched, physical wiring not yet verified.
  • Controller for the user's existing LTA-5055TJ-marked, five-color 12 V status pole with 12 V buzzer, using an existing ESP32 development board.
  • Goal: independent local HTTP control and readback, with Home Assistant seeing the same commanded output states regardless of command source.
  • Current deliverable: requirements and integration contract. No schematic, firmware, pin mapping, PCB, or electrical validation has been completed.
Intended Use
  • Assumed indoor, local-network status indicator prototype; not a safety alarm or machine safety interlock.
  • A local script/webhook sender changes an output over HTTP; Home Assistant displays that change and can...
I confirmed that ESPHome supports HTTP set/readback with live Home Assistant state updates—no MQTT broker required—and saved the approach in your project files: Project Specification.
The driver circuit is blocked by unverified wiring polarity and current ratings for your exact tower, so I haven’t added circuitry yet. Can you upload a photo of the tower’s label and wiring diagram?

Waiting for input

No schematic yet

Talk to Flux to get started.