Dashboard
Real-time clock with 7 display styles, weather from Open-Meteo, one-tap scenes, recent events and system health. WebSocket pushes updates without page refresh.
Features
The full chain, not one screen.
ELARIS connects hardware onboarding, entity management, module commissioning and real-time operation inside one platform. Here is what actually ships today.
Operations
The pages you use every day.
Module-driven design
Reusable automation with clear IO contracts.
Each module explains itself
Every module declares its required and optional IO, setpoints with defaults and ranges, and a help description. Installers see what they need before mapping.
Visual mapping & readiness
Map entities to module inputs with drag or dropdown. The platform validates completeness and shows a readiness score. No module runs with missing required IO.
Per-module settings
Each instance has its own settings: PIR timeout, lux thresholds, schedule times, zone setpoints. Settings persist in SQLite and survive restarts.
User control & engineer locks
Modules can be locked by engineers to prevent accidental changes. User control permissions are per-module, per-site. Roles: User, Engineer, Admin.
Installer & entities
Approve IO once, reuse it everywhere.
1
Device discovery
ESPHome boards publish config to MQTT on boot. ELARIS receives the JSON, extracts entities (relays, DIs, sensors), and creates a device record with board profile, transport type and status.
2
Pending IO
New channels land in a staging queue. They are not yet part of any module or automation. This prevents raw device channels from accidentally triggering logic.
3
Entity naming & zoning
Raw channels like di_1 become "Front door sensor" in zone "Ground floor". The entity registry is the single source of truth for all module mappings.
4
Module mapping
Entities are mapped into domain modules with visual validation. The platform checks for conflicts (same entity mapped to two modules) and shows a summary before saving.
🧪
ESPHome installer
5-step wizard: transport (USB/OTA), device name, board profile, network config, flash. Real-time compile logs in the browser. Board profiles for KinCony KC868-A/B/F series with pin/bus/entity defaults.
➕
Add peripheral OTA
Add BME280, DS18B20, INA219, CCS811, MH-Z19, PZEM-004T and 12+ other sensor types to existing devices without rebuilding the full YAML. The platform injects the peripheral, validates pin conflicts, and pushes OTA.
📦
Pending auto-register
After an OTA update, new peripherals from the device report land in Pending IO automatically. No manual discovery needed — the device announces what changed.
🛡️
Managed devices
Devices can be marked as "managed" with custom MQTT topic roots. Native ESPHome topics are skipped for state caching — only the managed elaris/
Local-first
Your data, your hardware, your network.
Runs on your Pi
Raspberry Pi 4 with NVMe recommended. Node.js backend, SQLite database, Mosquitto MQTT. No cloud dependency, no external API calls for core operation.
Role-based access
Three roles: User (sites they're assigned to), Engineer (all sites + device management), Admin (everything + shell console). Session-based auth with CSRF protection.
WebSocket heartbeat
30-second ping/pong detects dead connections. Dead clients are terminated and cleaned up. No memory leak from silently-dropped TCP connections.