OpenWrt
FaserF/ha-openwrt · vv2.5.3
Home Assistant integration for OpenWrt devices
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
light | Light | |
switch | Switch or outlet | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
device_tracker | Presence (as an occupancy sensor) |
What people report
Router-level integration; firmware updates work on a FRITZ!Box 4040 after a fix, and CPU/temperature sensors can be blocked by rpcd ACLs.
- Works1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| AVM FRITZ!Box 4040 running OpenWrt 25.12 | Works Local | Firmware update silently failed on 25.12; fixed in release 2.4.4Saved copyEnvironment - Integration version: 2.4.3 (ubus/HTTP connection mode) - OpenWrt: 25.12.0-rc4 → 25.12.5 - Device: AVM FRITZ!Box 4040 (ipq40xx/generic), ASU flow (standard flow equally affected) - HA: 2026.7.4 ### Bug Firmware install runs apparently fine (pre-update backup OK, image downloads on the router, services stop, router reboots after ~1 minute), but after the reboot the router is still on the old firmware. Reproducible on every attempt, and completely silent: no errors in the HA log (the install flow only logs at INFO level). ### Root cause `install_firmware()` in `api/ubus/system.py` … Excerpt saved from GitHub on 2026-10-23. | Issue #115 · 2026-08 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Found automatically over
- DHCP
- SSDP/UPnP
Details
| Installs (analytics) | 447 (0.06%) |
|---|---|
| GitHub stars | 121 |
| Latest version | v2.5.3 (2026-10-20) |
| Set up in the UI | Yes |
| Maintainers | @FaserF |
| License | MIT |
Limitations from the README
- CPU Usage: Many OpenWrt releases do not expose CPU statistics directly via Ubus. The integration attempts to read /proc/stat, but this is often restricted by default rpcd ACLs. If CPU usage stays at 0%, this is likely a permission limitation.
- System Temperature: Access to thermal data (e.g., /sys/class/thermal/...) is frequently restricted via Ubus. If the temperature sensor is missing, it's due to these security restrictions.
- Disk/Storage Usage: Similar to CPU/Temp, detailed filesystem info might be restricted.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/FaserF/ha-openwrt
- Source code: https://github.com/FaserF/ha-openwrt
- Issues: https://github.com/FaserF/ha-openwrt/issues
- HACS: https://hacs.xyz
