I think there's some confusion here, the thread veered from "OpenWrt integration into HomeAssistant" into "running HomeAssistant on OpenWrt". Both are interesting topics, but the latter is not what this thread is about.
3 Likes
I LOL'ed.
Maybe we need to reconsider this whole feature requests section.
2 Likes
1 Like
As an avid OpenWrt and Home Assistant user, I also think that it would be awesome to have a complete integration between them.
However, I think you guys are barking the wrong tree: OpenWrt already provides a hook for the connection (ubus), now it's the job of the Home Assistant developers to improve the integration.
Tuya, Asus, Netgear, ... none of them developed the Home Assistant integration for their device, it was the Home Assistant developers.
17 Likes
I plan to manage HomeAssistant locally and provide the necessary files. Perhaps someday someone will want to install HomeAssistant on OpenWRT and test it.
That is different from OpenWRT integration in homeassistant
what else are we looking for, it's already there
Maybe some people are curious to install HomeAssistant on OpenWRT like OpenLumi did and have toys on OpenWRT
1 Like
First two are just presence sensors.
This is a presence detection scanner for OpenWrt using luci
if you want more than that please contribute there
Given how the HA developers have reduced the ways HA can be installed over the last year or so - see https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/ for details - it's extremely unlikely that HA will ever run, itself, on OpenWRT.
It could of course be run inside a docker container but OpenWRT’s focus on resource constrained router devices is likely to make that very difficult to achieve.
In terms of integration though, that word means many different things. Do we want to be able to have full control of the router configuration from HA (my inclination here is “hell no”)? Do we just want to collect data, and if so, what? Do we want to be able to make HA do things based on events/triggers/thresholds/templates etc? We've got device tracking/detection in the integrations mentioned, what else would people want?
2 Likes
I don't need Docker to use HomeAssistant. No one is suggesting you install HomeAssistant on your device or anyone else's. However, some people want to run HomeAssistant on OpenWRT, and HomeAssistant won't be in the OpenWRT repositories. And you need expertise to use HomeAssistant on OpenWRT. And no one is suggesting you use 32-bit.
What I want is Openwrt sensors data being stored on HA, on router we often hear about flash weardown, that is not such an issue on Homeassistant instances.
We could adjust router firewall rules based on certain condition e.g certain firewall being enabled if certain areas in the house are occupied using radar presence sensors etc.
Routers temperature data being stored in HA and external fan is controlled using that data. (Infact I use this with Fresh tomato router and external fan)
Possiblilties are endless,
Edit:
Most Routers on board sensors don't provide humidity sensor, but we can feed that using many cheap and easily available sensors and can even control our router fans using that. 
First you say you do not want to install Home Assistant on the device, then you say you want to run Home Assistant on OpenWrt… this does not make any sense.
I think that what you mean to say is that you want to integrate OpenWrt into Home Assistant, is that correct?
1 Like
When talking about openwrt integration maybe the best example would be opnsense integration.
In ha it has a lot of entities including all connected devices using dhcp leases and it look like this.
If you ask me this is how openwrt integration for home assistant should be.
3 Likes
I use HA for monitoring my wan IP on my old router, if it changes (once every 24 years) it happens when I'm on the other side of the world. So HA mails me the new IP, and I can fix stuff. That could be a lifesaver.
Other stuff I would like is monitoring CPU/RAM/'disk' space, temp maybe. Just to be ahead of troubles. And restarting interfaces would be nice, or restarting the router itself. But there are scripts for this.
But I guess I could fix a lot of this through the SSH integration in HA anyway. I will look into this. I think Luci (or ssh) should be the primary way for configuration tasks. Personally I don't really care about leases, statistics etc. 24/7. When I need it Luci suffices.
A nice HA integration is always welcome, but time is scarce, so better spend it on OpenWrt itself I guess.
just my two cents.
For monitoring there’s already prometheus-exporter/telegraf available. I think grafana have an integration in HA OS? Not sure about influxdb. I run it as a container plus a separate stack in with Loki & Promtail so it can ingest my syslog from my devices as well.
1 Like
Yeah, there is Grafana and InfluxDB in HA. I just checked, the SSH plugin gives all the essentials like cpu/ram/temp. There to put in InfluxDB/Grafana if needed. And the ability to send commands, so you can make your own stuff if needed.
Like a toggle for adblocking (forget about that), with an automation to toggle it back on after x minutes.
While an integration with HA could probably easily handle this information, there is an easier method... just use dynamic DNS. There are tons of options, many of them free. Then you just use the domain name registered against the ddns account/client and it all automatically updates as needed.
You can also have scripts on the router itself to inform you when the wan IP changes by means of an email or similar. Again, ddns is usually the preferred method, but if you need to work with raw IPs, there are methods already available within OpenWrt to handle the task.
2 Likes