2026
Home Assistant
Smart gates, built into Home Assistant.
- Role
- Integration & code owner
- Years
- 2026
- Stack
- Python, Home Assistant, Fluss+ API, Wi-Fi
An official Home Assistant integration for Fluss+: every device becomes a button, and gates with a sensor open, close and report their state.
The signal path
Transport
Commands reach the device over Wi-Fi, the same path the Fluss+ app uses from anywhere.
Cloud
The Fluss+ API, authenticated with an API key from the account. Home Assistant polls it every 30 minutes and refreshes straight after each command.
Interface
Home Assistant entities, set up from the UI: a button per device, and a garage cover with live open/closed state where a sensor is fitted.
Context
Home Assistant is the open-source smart-home hub. Fluss+ gates and garages sat outside it, in a separate app.
The problem
Make Fluss+ devices first-class in Home Assistant: set up from the UI with nothing but an API key, and usable in automations like anything else in the house.
What I built
- The integration in Python, from the first commit through review by Home Assistant’s maintainers to release in Home Assistant 2026.1.
- The Fluss+ API side: the endpoints and account API keys the integration authenticates with.
- Setup through a config flow: paste the API key, and every device you have access to appears.
- A button for every device, which triggers it over Wi-Fi like a tap in the app.
- A garage cover for devices with an open/close sensor: open and close commands, with the state shown live.
- Polling every 30 minutes, plus a refresh straight after each command so the state doesn’t lag.
Outcome
Fluss+ has been part of Home Assistant core since 2026.1, rated Bronze on its quality scale, and gates and garages now sit in the same automations as the rest of the house.