

~/copypasta/gunfortheprinter.odt but it’s a JTAG header for the vacuum


~/copypasta/gunfortheprinter.odt but it’s a JTAG header for the vacuum


I tacked a CT onto my sprinkler esp so the Mrs can be certain she turned everything off, so I’ve been living with this

I have 3 Kauf RGB switches that I use for garage door interfaces spread through the house. Off means closed, orange means reed switch and range sensor don’t agree (moving), white means open, red means fail to close.
The little corner light is for the pedestrian door.
The garage door itself has a konnected gdo.
https://konnected.io/products/smart-garage-door-opener
Spiders like to obscure the range sensor ~twice a year, and it probably best practice to not have all the inputs coming from one device. One day I’ll move the reed switch to the i4 dc shelly that reads the door switches. Maybe try ratgdo, the clone/knockoff I bought was not very reliable.
https://us.shelly.com/products/shelly-plus-i4-dc
https://konnected.io/products/contact-sensor-recessed-magnetic-for-doors-or-windows


That is a weird combo. And designed to lock you into their ecosystem. Absolutely proprietary.
https://www.athom.tech/blank-1/bthome-door-contact-with-tempreture-and-humidiy-sensor
This one runs BTHome, part of the Open Home Foundation. I have two mmWave presence sensors from the same company. They offer tasmota and esphome firmwares for them, I chose ESPHome. It’s been great.


Probably every 2 months. When I have a day off work with nothing to do. I have a few VMs that are more fragile than I want to admit and if something breaks I want to have time to tinker instead of just restoring a backup.


Esphome based, so the learning curve it kinda steep of you just want a simple on/off bulb BUT it will open your eyes to what’s possible. This also avoids zigbee and z-wave. The state of those Z radios is so bad that Home Assistant released their own.
Are you dual booting windows by chance?
Maybe check if there is newer firmware available for the chip set.


https://www.pentestpartners.com/security-blog/z-shave-exploiting-z-wave-downgrade-attacks/
I really hope the current production isn’t vulnerable to an 8 year old exploit.
It’s worth stepping back to through the “latest” 6.11 hwe and 6.8 hwe kernels to see if it improves.
That’s too modern 🤣
My Lenovo t14 amd 360 misbehaves on 6.11, but is great on 6.8
https://github.com/advplyr/audiobookshelf
I manually grab what I want from mam
Some reolink cameras (B800 for sure) scramble the encoding to lock them to reolink NVRs. I used two of them with frigate by running neolink because fuck vendor lock in
https://github.com/QuantumEntangledAndy/neolink
I had problems with the 0.6.x series but 0.5.18 ran well enough. I abandoned those cams because they would occasionally switch to sending static to frigate and locking it down.


There is a dlna server but it has “totally unintentional” memory leaks that cause it to crash after a few days and they refuse to fix.
Surely the TPM has this power
That post inspired this one :)
Don’t you put that voodoo on me!
Not ironic variations on that theme are available here:
https://web.archive.org/web/20250000000000*/stallman.org/stallman-computing.html