We probably know from Debian-based systems that the use of TTY devices isn’ŧ for everyone—you need to be a member of the dialout group. Which doesn’t exist on Arch.
(For firmware flashing via websites like ESPHome you also need a Chromium-based browser, Firefox can still not do it.)
I’m in the process of making EOS my daily driver and building a new Home Assistant voice satellite, so I needed to flash firmware into its ESP32.
Long story short, on Arch & EOS you need to be member of the uucp group (not tty as one could assume), otherwise Chromium tells you it cannot open the serial port. The old Unix-to-Unix-Copy-Protocol revived, unbelievable… 
(Well, actually not, but the group, hee hee.)
Is this what you call ‘recycling’ ? 
1 Like
Why can’t my Web Browser flash a microcontroller via serial? What is the point of a Web Browser anyway?!
PS: Yeah, I get it, having set up a QMK/VIA keyboard via the webbrowser USB access without any other software installed is magical. It’s scary and amazing.
Home Assistant, ESPHome, and few others try to make complicated things “easy for the masses”… Successfully, I must say.
Thinking of how it was before—setting up complete IDEs, installing packages & repos, doing everything by hand, needing fancy flashing adapters.… Must say even I (who can still do all that) get lazy and start using these modern, scary and magical tools. 
Makes for more free time one can spend with other things (like tinkering w/ EOS). After finding that uucp thing, I set up a completely working DIY HA Voice Assistant Satellite in 15 minutes. Good thing.
1 Like
I had a raspberry pi running some home automation over the past years (mqtt server, node red, ..,). In the last two weeks I finally got Home Assistant going.
That’s a rathole. Tinkering options for ages.
Currently I’m trying to get reliable home presence detection going.
Yup. Rabbit holes and ratholes everyhere…
Use LD2410’s. PIR are sh*t. Only problem: Can’t be run on batteries, need too much power.
1 Like