ESPHome installer
Board selection, setup steps and hardware-oriented onboarding that belongs inside ELARIS.
ESPHome & Hardware
Hardware onboarding is part of the product story.
ELARIS is not just a dashboard that waits for hardware to magically exist. It already includes an ESPHome installer, board flows, generated YAML, flash logs and peripheral growth on existing devices.
➕
Add peripheral to existing device
Grow a live board with extra sensors or inputs instead of recreating the whole definition every time.
🌡️
Useful sensor growth
DHT22, DS18B20, analog inputs and pulse-based flows make the installer story much stronger in the field.
📥
Pending IO after report
After a successful update and device report, new hardware can appear in Pending IO for approval and mapping.
🧠
Board-aware validation
Pin checks, conflict checks and warnings belong here because they save time and bad field mistakes.
Board approach
Use board labels where they exist. Stay generic where they do not.
Friendly labels
Boards like A16 can expose installer-friendly labels such as HT1, HT2 or analog inputs.
Generic GPIO fallback
The hardware flow should still work for boards without rich labels by validating real pin input intelligently.
Not locked to one board family
The ELARIS hardware story should stay broad enough to keep expanding across supported ESPHome-capable boards.
Next hardware step
Modbus is one of the next major integrations.
This is worth saying publicly: ELARIS is under heavy development, and Modbus is an obvious next step because it opens the door to more industrial and commercial devices without losing the same ELARIS mapping model.
Short term
More boards, cleaner peripheral templates and stronger field validation.
Next major layer
Modbus support for broader integration with controllers, meters and industrial-style devices.
Longer term
Broader hardware bridges that still land in the same entity + module workflow.