Capability
Home Assistant bridge
XOBIT can expose script-defined controls and values to Home Assistant so a prototype can become part of a living environment instead of staying isolated in the browser.
How It Works
- The sketch declares entities. API calls such as `haSwitch()`, `haLight()`, and value helpers describe the entities.
- The firmware publishes availability and metadata. Home Assistant can discover and interact with the declared controls through the firmware bridge.
- Events return to the script. A Home Assistant change can be consumed by the running sketch just like browser UI events.
- The script can update state. It can report values, light state, switch state, and button-like events back toward Home Assistant.
Design Notes
- Use stable ids for entities so dashboards and automations do not break between uploads.
- Keep UI names human and object-specific, for example “Hourglass brightness” rather than “slider 1”.
- Keep fast animation inside the board; expose intent, state, and controls to Home Assistant.