Why can’t you just have a long lived internally signed cert on your archaic apps and LE at the edge on a modern proxy? It’s easy enough to have the proxy trust the internal cert and connect to your backend service that shouldn’t know the difference if there’s a proxy or not.

Or is your problem client side?

Automated certificates are relatively new and pretty neat. Killing off the certificate cartels is an added bonus.

You could try a path unit watching the cert directory (there are caveats around watching the symlinks directly) or most acme implementations have post renewal hooks you can use which would be more reliable.

You could try using the DNS challenge instead; I find it a lot more convenient as not all my services are exposed.

I have smart plugs from Innr, Samsung, Aqara (I think) and have never experienced the problem you’re speaking of. Mine are all ZigBee – not sure what yours are.

That said, I just got a bunch of Shelly EM Mini G4 and put them in some PowerPoints and they work great.

If you don’t mind some basic wiring they’re easy to set up.

Nym looks interesting and I hadn’t heard of it before, but based on my reading I wouldn’t say it supports wireguard.

It implements wireguard but it still looks like you need to use their client instead of a vanilla wireguard one.

Cisco, HP, and many other “Enterprise” switches will take a minute or two to start forwarding frames after boot.

Doesn’t really excuse Ubiquiti but that’s what they’re trying for.

Why are you searching for a solution to a problem you don’t have?

There’s nothing wrong with systemd.

What excuses are you referring to?

Are you also arguing that if a problem isn’t in your immediate periphery then it doesn’t exist? We are all human beings, living on the same planet.

There’s nothing wrong with feeling a modicum of empathy for those less fortunate by circumstance of geography or socioeconomic influence.

Even more simply:

Government: closes their curtains in the evening.