A native Flipper Zero app for controlling Home Assistant. It talks to a small local Python bridge, so your Home Assistant token stays on your computer and the Flipper only stores a bridge URL plus a shared key.
- Adds Home Assistant switches, lights, dimmable lights, and routines to a Flipper Controller screen.
- Shows current states after refresh, including dimmer percentages.
- Queues commands so you can tap through a few actions without waiting on each request.
- Lets you reorder and delete Controller rows on-device.
- Lets you choose a Home Assistant
climate.*entity for the Thermostat screen. - Keeps the Home Assistant bearer token off the Flipper.
- A Flipper Zero.
- A Flipper Zero WiFi Developer Board running FlipperHTTP.
- A Home Assistant instance and access token.
- A computer that can reach Home Assistant and run the Python bridge.
- Python 3.10 or newer for the bridge.
ufbtif you want to build the Flipper app yourself.
Flipper app -> WiFi Dev Board / FlipperHTTP -> local bridge -> Home Assistant
The bridge exposes compact /v1/... endpoints for the Flipper. Home Assistant sees normal service calls, and the bridge writes a local command log for debugging.
- Copy
.env.exampleto.envand add your Home Assistant URL, token, and bridge key. - Start the bridge:
python bridge\ha_state_bridge.py --env .env --host 127.0.0.1 --port 8765- Verify the bridge from the same computer:
$key = (Select-String .env -Pattern '^FLIPPERHA_BRIDGE_KEY=(.+)$').Matches.Groups[1].Value
Invoke-WebRequest -UseBasicParsing "http://127.0.0.1:8765/v1/setup/check?k=$key"- Build and install the Flipper app:
cd flipper_app
py -m ufbt build
py -m ufbt launch- Copy
examples\bridge.example.cfgto the Flipper SD card at:
/ext/apps_data/flipperha/bridge.cfg
-
Edit
bridge.cfgsourl=is the bridge URL reachable by the WiFi Developer Board andkey=matchesFLIPPERHA_BRIDGE_KEY. -
Open FlipperHA on the Flipper. Use Controller -> Add to browse entities, and open Thermostat to choose a
climate.*entity.
- Controller -> Info should show
Cfg:fileoncebridge.cfgis loaded. /healthzshould returnokfrom the bridge computer./v1/setup/check?k=...should returnokbefore you test from the Flipper.- If the app shows
no board, confirm the WiFi Developer Board is attached and FlipperHTTP is running. - If the app shows
get timeout, the board probably cannot reach the configured bridge URL.
- Bridge setup
- Flipper SD-card app config
- Troubleshooting
- WiFi Developer Board notes
- Release build notes
- Migration notes
- Host tooling and logs
Do not put your Home Assistant bearer token on the Flipper. Keep it in .env on the bridge computer. Treat FLIPPERHA_BRIDGE_KEY like a password, especially if you expose the bridge through a tunnel.
For local HTTP bridge URLs, keep the bridge on your trusted LAN. For remote or HTTPS testing, prefer an access-controlled tunnel.
The default Controller starts blank, and users add their own Home Assistant entities on-device.
MIT. See LICENSE.



