I use OpenWRT now and would really rather avoid it. I want a central controller, not having every AP have its own UI. Plus firmware updates area always an adventure.

> Plus firmware updates area always an adventure.

To somewhat eliminate the chances of adventure, I’ve profiled the setup for each of my many OpenWRT devices and created unique profiles for them in a (reasonably) simple Git repo[1].

All I need to do to get device-specific firmware is to update the OpenWRT version-number in a single makefile and the rest happens automatically.

I’ve even setup Github Actions to build the firmware for me (basically, run make), so I can even get/build new firmware from my phone.

I’ve yet to have any issues when flashing these builds. It used to be much worse when flashing the regular “official” OpenWRT image and restoring packages afterwards.

Couldn’t be simpler! (With the regular Linuxy you-have-to-build-it-yourself-first clause)

[1] https://github.com/josteink/openwrt-build

This is cool! Forking.

I need to get back to trying to build a custom build for my KanKun smart plugs.

About 5 years ago I would do the same thing. I want to set it up such that if I with the lotto and move away, the rest of my household can continue using the system without having to learn a CLI.

OpenWRT also provides SSH access and CLI tools, so if needed things can be automated the old-fashioned way.

I don't know about you, but I "automate the old-fashioned way" at my day job, I want the damned thing to just work without me bothering with "SSH access and CLI tools" at home.

and how many APs do you have at home?

Right now? 1. But that's about to change, that's why I'm reading these comments. I was planning on buying a bunch of Ubiquiti APs.

I'll let you in on a little secret, Ubiquity runs openwrt as can be seen by sshing into any uaps

That’s fine. I think it’s a great project. But I want someone else to worry about what happens during each firmware update. It’s not trivial.