HA makes it a lot easier to log and automate this without requiring too many coding skills.
I use my own domain, so I just need to change the dns record once. Or use the IP until I'm home. But it rarely happens anyway. My old router was a ISP one, so I had to use HA.
Some dynamic DNS services can handle that for you using your own custom domain. Or you can just lean on the domain names that are offered from the ddns services.
Aside from OpenWrt, you can usually run a ddns client on almost any host.
But, the point of this thread is about a home assistant integration... this stuff isn't theoretically that hard once someone writes the integration, so I would imagine it will be included should someone take on the task. However, I was just pointing out that there are already methods to handle your needs without requiring HA or an integration specific to OpenWrt+HA.
Right, maybe that's the 'problem'. Most stuff is doable without a HA integration, especially for those who are able to write the integration, which means they won't write the integration 
If you catch my drift.
But a good integration would make OpenWrt as a whole more attractive...
That is
Exactly, that is the whole point.
Openwrt is maybe the best or one of the best possible solution for smart home. You have batman-adv as a must as it can do vlans over wifi if you use mesh wifi.
How many commercial solutions can do that? Well not many. On paper maybe few, in practice probably unifi only. If it is hard to set up, hard to integrate, hard to do this to do that.. well majority of people will skip it. Why bother anyway.
I agree. But I disagree that it needs to be limited to, and specific to HomeAssistant. Maybe it'd be worthwhile to create a native, lightweight MQTT client. One that is also able to receive commands, and one that is not tacked onto the huge collectd baggage. (Personally, I'd like to have my OpenWrt devices both in HomeAssistant for immediate observation and in InfluxDB for long-term statistics.)
Yes, MQTT would be even better indeed. If somebody wants to build a HA integration, he/she could use that and otherwise it would serve more people.
I just stumbled upon this Integration for HA:
It's fairly new and needs some work (doesn't use https for instance).
And it cannot stop/start an interface, that's what I need 
Should be easy, maybe somebody here can help extracting value from ubus response: https://community.home-assistant.io/t/extracting-data-from-response-variable/959349
It is good. Things are much better then they were when i started this thread.
This integration will create a lot of senors and it is not that difficult to implement. Maybe it could be better if added custom commands like you can do in ssh integration. I use ssh integration for measuring throughput between batman nodes.
I noticed that those senors that are created will not be stored for log term statistics in influxdb and probably one will have to create template senors for storing statistics that it find important.
Maybe give my new integration a try, I tried to consolidate all features and more into one integration:
FaserF/ha-openwrt: Home Assistant integration for OpenWrt devices
Looks very promising, congratulations!
I will give it a try as soon as I can.
In case it might be of interest to anyone, I also found you can send high frequency data (e.g. 20-50Hz) to HA via MQTT. I wrote a script to do this for cake-autorate:
So now I can make plots in Grafana of cake rates, achieved download/upload rates and download/upload latencies.
To store such high frequency data I excluded these sensors from the recorder and instead store them in InfluxDB.
It could be adapted to send other things.
Iām already using your integration and it is really great. Thank you for the effort.
Maybe a better support for batman-adv, but it is not a big deal. Everything is working fine.
Thanks for the feedback, I am going to add support for this in the next release, but I wont be able to test it, since I dont use batman-adv
I can test it. But you should try batman-adv. It is really THE MESH network, incredibly.
it can be done with any user, that has the required permissions. The automatically generated "homeassistant" user from this integration currently has had not the permission to do so afterwards
I will improve this in the next release 2.0.3 to extend the HA user with the permission, to include a MQTT deployment permission check and provide better Feedback in the setup flow.
Can now be tested with release 2.0.0 and newer 
Why not do a PR for official Homeassistant integration instead of going the HACS route?