Docs

Public docs that make the platform easier to trust.

The public website does not need to mirror every field in the app. It needs to explain the structure clearly: what ELARIS does, how the hardware flow works, what the module model is and where the project is going.

Module reference

Use this page to explain the idea of the module library, then send deeper readers to GitHub and in-product help where needed.

Climate
Thermostat, hydronic and thermal control flows for real heating and plant-side work.
Lighting
Switches, PIR, presence, lux and dimming logic with schedules and scenarios.
Shading
Awning and blind modules with weather and travel protection logic.
Water
Irrigation, pump and leak-aware logic with outdoor and utility relevance.
Energy
Monitoring, load shifting and power-aware decisions.
Custom
Industrial and bespoke logic when a project goes beyond generic templates.

Hardware flow

Boards publish config and telemetry, ELARIS turns them into entities, and those entities are mapped into modules.

ELARIS flow
device/config  → announce capabilities and entities
device/tele/* → send sensor and live values
device/state/* → send relay/output state

ELARIS discovers → Pending IO → approval → entity naming → module mapping.

Entities and zones

This is one of the strongest ideas in the product. Raw device IO becomes readable building language before it enters automation logic.

Readable naming

Outdoor temp, salon light relay, awning wind sensor and similar names are far better than raw pin thinking.

Reusable mapping

Once the entity exists, the same platform can map it into any module that needs it.

Next public docs pages

Hardware catalog

Supported boards, common sensors, practical pin notes and good starting kits.

Module pages

A public module page per major module family with readable examples and screenshots.

Changelog

Show how actively the platform is moving.

Security / local-first

Explain the privacy and local operation story directly and clearly.