Home Assistant custom integration for BragerOne web service.
Status: Stable (Production/Stable)
This custom component provides integration between Home Assistant and the BragerOne system, allowing you to monitor and control your devices through the Home Assistant interface.
- Real-time parameter monitoring
- Device control via Home Assistant
- Configurable through Home Assistant UI
- Support for multiple device types
- Per-module cloud connectivity diagnostic (SPA
connectedAt/module.connection.*labels) on a separate child device ({devid}:module.connection, linked withvia_device); this is intentional in flat and group-by-menu alike — parameter entities go unavailable when the module is offline; writes are refused while offline. Module offline is observe-only (wait for the plant to reconnect). - Separate Cloud API session diagnostic (library↔cloud Socket.IO) on a config-entry service device — detectable and self-healing; never folded into module
connectedAt. Config-entry diagnostics includelast_param_update_age_s(seconds since the last parameter snapshot/delta) to distinguish a live session from a frozen push stream. - Optional device grouping by menu (options: flat default vs group-by-menu child devices per parent menu route with
via_device)
- Copy the
custom_components/habrageronedirectory to your Home Assistantcustom_componentsdirectory - Restart Home Assistant
- Go to Configuration > Integrations
- Click "Add Integration" and search for "BragerOne"
- Add this repository to HACS as a custom repository
- Install via HACS
- Restart Home Assistant
- Configure the integration
Testers: enable HACS Show beta versions to install alpha / beta / rc tags before they hit the default (stable) channel. Maintainers always smoke-test a pre-release on a live HA instance before cutting the matching stable tag — see DEVELOPMENT.md.
The integration can be configured through the Home Assistant UI. You will need:
- BragerOne / TiSConnect credentials and backend platform
- Installation and module selection
- Device grouping (flat = one HA device per internet module for parameter entities; group by menu = child devices per parent menu route, linked via the module — remaps device membership when changed). In both modes the connectivity diagnostic stays on a separate
{devid}:module.connectionchild (via_device), so it is not folded into the module device in flat mode.
Every permission-gated parameter becomes an entity — there is no separate UI/permissions filtering mode to choose. Entities that are outside the everyday BragerOne web UI (installer-only panels, or panels the SPA itself hides) are still created, but start disabled in the entity registry; enable them manually if you need them. Enable/disable state can be changed per-entity at any time from the entity registry.
If you want to contribute to this, please read the Contributing guidelines and Development guidelines. Use the issue forms and the pull request template.
For issues and questions:
- GitHub Issues (templated): https://github.com/marpi82/ha-bragerone/issues/new/choose
- Home Assistant Community: https://community.home-assistant.io/
Do not file security issues publicly — see SECURITY.md.
MIT License - see LICENSE file for details.