Nope, they should not be executable.
I just put it in my dryer at 40C for a few hours with little regard to a target humidity. I also live in a dry climate where the ambient humidity is low, so maybe it's not enough in wetter climates, but this works for me.
urxvt is the only terminal I'll use. Every time I try something else I come back to it because of some basic thing that's not right - usually font rendering which urxvt is one of the few that works well with scalable fonts. It's fast and simple and does everything I need without any bloated stuff I'll never use.
Yep, it's because of that proprietary and "every device must be licensed" nature of Z-wave that I use Zigbee devices - I'll pick an open platform everyday over a closed one, even if it has limitations.
I don't have an exact answer to your problem, but I do have a few ideas to think about. I've got a few ESP32 WROOM boards running in various applications, so I'm a bit familiar. So here's my thoughts:
- I only plug the module into data USB (computer) for the initial firmware provisioning. After that, it's 100% wifi and USB is only for power using a power supply, not the computer. And I do the initial provisioning with just the bare ESP32 - no breakout board, nothing plugged into GPIO. Get the device up on wifi with NO other configuration in the firmware.
- I use the "arduino" framework. I don't know if that's correct or really matters, I've heard it's the same as "esp32dev" but I don't really know. I use "arduino" because that's what the examples used when I setup my first board.
- Is it possible that the sensor module/board is using the same GPIO that the USB UART uses? There is a lot of shared usage of the GPIO that you've got to be careful to work around. The dev tools will often catch this when you compile your firmware, but not always. Again, using wifi after the initial provisioning might be enough if it is sharing GPIO with the serial port.
- If you repower the ESP32 too many times rapidly it'll boot into safe mode. You can change the settings on that, but you can also just work slowly - make sure the device is powered on for a few minutes to record a good boot in the flash. It outputs a message in the logs, so it's handy to always be running the log command in a terminal while developing.
Hope that helps! They are a lot of fun to integrate with HA.
In a word - yes - i3 is incredibly productive and customizable, but it's not for everyone. I've been using i3 with no DE or DM for about a decade. Every time I try to use a full DE like KDE, Gnome, etc, it's just so slow and bloated, and gets in the way. And there's 100's of extra packages that get installed, and be updated, that I don't use. I don't need anything but terminals (of which I have about 40 open in 12 different virtual desktops), a browser, and an editor when vim isn't enough. So for me, it's perfect and simple. I don't know what will happen when Wayland finally wins, but that's 5-10 years away before it really wins.
YouTube links are fine - I hate those stupid bots that spam posts about such links.
Exactly this - FreeCAD is great, but you have to learn to do things its way if you want stable designs. While there is a learning curve, it's really no worse than Fusion360 was in figuring out how to achieve my design goals. There are fantastic YouTube channels out there, like MangoJelly when you do get stuck. I converted all my older designs from Fusion360 to FreeCAD, and everything since is in FreeCAD, and I haven't looked back. I think many people are just afraid to admit they are daunted by FreeCAD, and rather than work to understand it, they just complain and say it's bad, without ever actually putting any effort into learning the platform.
This isn't an issue with hackers though - this is people legitimately using the devices that they paid for with Home Assistant and other automation systems.
It's just the same thing as man -k
.
I use i3-wm and just set my laptop display and external monitor to their native modes manually with xrandr. Been doing it this way for years without an issue. The only time I've seen the output get chopped like you mention is with mirroring, where you have to use the lowest common mode - but I don't mirror, I set each display independently as a separate output for i3 (but on the same X DISPLAY).
I also don't use a login manager, I login to a VTY and startx, old school but simple and reliable.
ZFS for nearly everything plus ZFSBootMenu EFI on root data pools. Get a bad upgrade? No problem, boot a previous snapshot (auto created with a pacman hook), which I had to do recently when 6.6.39 LTS kernel had a bug. Snapshots are also great when doing things such as upgrading postgres, hass, Plex, etc.