ansible-openwisp2 VS Reticulum

OpenWISP (https://openwisp.org) tries to do this and it's Python and Django based.

Last time I checked it out, it seems like they keep configuration in an intermediate format that is then translated to manufacturer-specific formats, so it should be possible to build a Unifi converter for that.

OpenWISP (might be closest thing I've seen to what you're looking for)

Time to flash openwrt and use openwisp?

For those using OpenWRT looking for a central controller which can be installed on-premise: https://openwisp.org/

I think you are wrong. I have been working on https://openwisp.org for some time and implementing a controller which is robust and can handle many different corner cases and offer good functionality and also ease of use is a challenge and requires several people working full time on it. Even simple functionality it's a lot of work, unless for simple you mean really trivial. If it wasn't hard, there would be many alternatives but as far as I know there aren't many.

One neat thing I've figured about SimpleX's relay/proxy model (and also Nostr's) is that, since servers don't connect to each other, you can more easily run it on alternative networks such as https://reticulum.network. No bridging is necessary.

Reticulum Network Stack (https://github.com/markqvist/Reticulum) - Basically a new kind of network stack that doesn't rely on IP. It works over LoRa, Ethernet & even packet radios.

If you use it with any of the software I have released that supports it, everything be completely encrypted, since all of that is built on Reticulum, instead of TCP/IP. More on that in a bit.

This on-board repository also contains all the software, guides and information needed to set up emergency (or permanent) wireless mesh-networks for basic communications using the Reticulum mesh networking system, with programs like Sideband or Nomad Network.

Yes. An app like Sideband provides basic text comms, but anything is really possible, since it provides a full networking layer through Reticulum. It's also pretty easy for other developers to write their own programs, apps and services that can run over the network.

You can then use the Reticulum protocol on top of that, which is designed to allow fully functional, encrypted and self-configuring mesh networks, even over extremely slow mediums. Everything else, that is actually useful for general purpose comms, fails at less than a few kilobits per second.

You could think of it as a really long range WiFi card for your phone, computer or other devices. It's much slower, but has range in the kilometers instead of 50 meters. It does not use the typical WiFi+IP+TCP stack that most things use these days (which makes them fail as soon as centralised infrastructure fails), but a networking protocol called Reticulum, which was designed to work even when everything else fails.

I'll go through it after work. I always wondered on how mature Rust is for embedded systems programming. So this will be useful. My hope is to be able to write something like Reticulum related firmware in Rust.