Docker won’t make much sense if you don’t understand the underlying Linux systems and/or applications.

It’s similar with Wine and Bottles. If you don’t get what’s in the bottle, then running the bottle won’t make sense.

Find tasks that run on the native OS. learn to manage Linux itself. skip containers, Snap, virtual machines, etc.

try running a web server using httpd or something.

deleted by creator

Depends on the specific Zigbee switch, but generally yes.

The magic is in the fact that you can decouple the relay, and use the switch as a sensor that triggers things that may or may not be related to the physical switch position.

The other reason I like it better than a typical “smart switch” is that I can use the shellys with whatever switch I want, so I can have it match my dumb switches and use different colors.

shelly relays will do exactly what you want. just wire them as disconnected switches. i do this to simulate 3-way switches, but it’ll work just as well to swap circuit behavior.

you can use a homeassistant action if you’re already using HA, or you can have the shellys call each others web api when it senses the switch.

So… you’re afraid of the command that does the thing you’re trying to do?

I’m surprised no one’s mentioned the security implications. Mounting with nosuid and nodev options can undermine rootkit or privileged escalation exploits.

Flatpak is itself a file manager.

That duplicate of your folder in /run is due to filesystem links (or more likely a fuse mount, I’ve never actually looked into how flatpak works). But either way, they aren’t copies of the data.

deleted by creator

Don’t “declutter” manually. Use your package manager.

You’re going to want to look up things like symlinks, hard links, fuse filesystems, and bind mounts among other concepts. Your “whole directory” and other duplicates are artifacts of how the filesystem and process management works, and simply running fsearch or find over them is going to be confusing if you don’t know what you’re looking at.

One Unix concept that carries over to Linux is that everything is a file. Your shared memory space, process data, device driver interfaces, etc, all of it is accessible somewhere in the same virtual filesystem tree as the actual files.

Because of this, there’s very little reason to have the whole filesystem indexed from root. If you’re worried about space usage, you want to work with packages through the package manager. If you’re worried about system integrity, you’ll want package validators.

The above is accurate, and can be considered accurate for any directory below or at well.

Per /run, it’s also mounted in memory, so trying to “declutter” it won’t get you anywhere and things will return on reboot.

I actually want to learn enough code to contribute, but there’s this gap between “how to code” and “how to participate in a modern software project”.

Like, I’ve created plenty of little things. Discord bots, automation scripts, plenty of sysadmin stuff for work, etc. But like, I clone a git repo cause there’s a home assistant bug I’d like to fix for example, and I’m immediately lost on where to start.

Fair enough, just seems like a lot of work vs. 2 clicks on the filters.

You don’t need to ground your Shelly if the circuit is otherwise properly grounded. The Shelly will fail open if something internal shorts.

Per the rest of the discussion re: hot wire loops to switches with no neutral or ground, just put the Shelly into the upstream junction box. (Wherever the switch wire branches from the circuit. Usually that’s where the light is.)

… Why? They exist for a reason, the interface has filter and sort options.

Specifically: https://www.amazon.com/gp/aw/d/B095KSZQGD?psc=1

And

https://www.amazon.com/gp/aw/d/B0BCHBXZ8D?psc=1

And several of the a19 and br30 models.

If you scroll to the Phillips hue list on ZigBee.blackadder.com, you’ll see the lack of ZHA support.

ZHA isn’t compatible with a lot of recent Hue bulbs. It’s a bit frustrating.

deleted by creator

Would be real nice if the blackadder list somehow flagged devices that are no longer available.

OP asks for “lowest latency” but HTTP is fast enough, and later in the thread says “perceptibly instant” is the goal. HTTP is going to be your slowest option, almost certainly, but even the slowest solution is “instant”.

What exactly are you trying to do, OP?

(Esphome seems like the answer you’re looking for. It’s faster than MQTT and you can program parts of the automation and service management in the ESP hardware. RF is probably the only way to go faster.)