Posted by jpluimers on 2026/02/16
Yes, I know: Ring and controversy.
Still need to figure out how to replace their ecosystem without shelling out far above 1K of money though, so for now – as our main doorbell is showing deterioration and hoping there would be PoE powered ones – a comparison chart PDF:
Posted in Hardware, IoT Internet of Things, Network-and-equipment, Power User, Ring Doorbell/Chime (Amazon) | Leave a Comment »
Posted by jpluimers on 2026/02/03
[Wayback/Archive] From Meh to WOW – With 1 “Tiny” Hack! – YouTube shows an interesting but convoluted solution to solve temperature drift on a cheap Tuya WT410-BH-3A-W thermostat (there are similar models, see below) based on the replacement sensor [Wayback/Archive] WSEN-TIDS Temperature Sensor IC & EV-Kits | Sensors | Würth Elektronik Product Catalog.
Luckily the commenters stepped in and suggest better and easier ways.
On the other hand, the solution is nice to know as it allows plugging in a remote thermostat that sits in a better place to read the temperature while the control bits stay in a place where it is easier to manually adjust.
Chapters:
Posted in ARM Cortex-M, Development, Domotics/Smarthome, ESP32, ESPHome, Hardware, Hardware Development, Hardware Interfacing, Home Assistant, Homey, IoT Internet of Things, Network-and-equipment, Power User, STM32 | Leave a Comment »
Posted by jpluimers on 2026/01/30
It’s a tricky process, but I might need this in the future:
–jeroen
Posted in Hardware, Network-and-equipment, pfSense, Power User, routers, Virtualization, VMware, VMware ESXi | Leave a Comment »
Posted by jpluimers on 2026/01/22
Nice videos about USB-C receptacles replacement that might fit old mini-USB and sometimes micro-USB ones.
Before applying, check out the tables in USB hardware: Compatibilities – Wikipedia and the table I copied from USB hardware: connector dimensions – Wikipedia to ensure there is enough space to fit the USB-C receptacle in:
Posted in Development, Hardware, Hardware Development, Power User, Soldering, USB, USB, USB-C | Leave a Comment »
Posted by jpluimers on 2026/01/21
Interesting video explaining on Intel’s Management Engine which has been the Intel Inside part of about every Intel Chipset since 2008: [Wayback/Archive] The Intel Nobody Can Remove (Not Even You) – YouTube
This is very relevant as it runs on a lightweight operating system called Minix, and there is a move from attacks on end-user operating systems personal computers and mobile phones towards edge devices running lightweight operating systems (not limited to Citrix, Ivanti, Fortinet, Palo Alto, Cisco, SonicWall and Juniper – for a potential OS list see Category:Lightweight Unix-like systems – Wikipedia).
More sources have started warning for this, see for instance [Wayback/Archive] Network security devices endanger orgs with ’90s era flaws | CSO Online and [Wayback/Archive] Security Appliance Vulnerability Bingo 2025 – Google Regneark.
Hopefully [Wayback/Archive] Dr. Christopher Kunz | heise online will have created a cku.gt/appbingo26 this year.
--jeroen
Posted in CPU, Cyber, Hardware, Infosec (Information Security), Intel CPUs, Power User, Security | Leave a Comment »
Posted by jpluimers on 2026/01/21
This should stau stays pretty up to date over time:
…
Simply pulling
lscr.io/linuxserver/wireguard:latestshould retrieve the correct image for your arch, but you can also pull specific arch images via tags.The architectures supported by this image are:
Architecture Available Tag x86-64 ✅ amd64-<version tag> arm64 ✅ arm64v8-<version tag> armhf ✅ arm32v7-<version tag> …
–jeroen
Posted in Cloud, Containers, Docker, Infrastructure, VPN, Wireguard | Leave a Comment »
Posted by jpluimers on 2026/01/15
On OpenWRT GL.iNET based devices, the WireGuard client does not restart upon reboot, even if it was started before rebooting.
Hopefully the /usr/bin/wireguard_watchdog script will help with this as others indicates it should.
My first try was no succes, but since it is supposed to run from cron it does no output. The script on GL-SFT1200 firmware version 3.215, script /usr/bin/wireguard_watchdog is different from the one in the OpenWRT repository, so it needs some investigation.
Some links for checking this out:
Posted in *nix, *nix-tools, ash/dash, ash/dash development, Development, GL-AR300M, GL.iNet, GL.iNET GL-SFT1200, OpenWRT, Power User, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2026/01/14
TL;DR: the connection problem was because of a public key mismatch between the pfSense central location and GL.iNET peer.
Since the pfSense cannot export configuration in either text or QR format (see rcmcdonald91/pfSense-pkg-WireGuard: This is a port of the original WireGuard UI bits as implemented by Netgate in pfSense 2.5.0 to a package suitable for rapid iteration and more frequent updating on future releases of pfSense.), I made a copy paste mistake.
This resulted in the WireGuard client connection indicator on the GL.iNET to turn yellow instead of green. This means that the handshake is only partially completed (there is a WireGuard connection but there is no returning traffic on it).
GL.iNET VPN status explanation:
Posted in GL.iNet, GL.iNET GL-SFT1200, Hardware, Network-and-equipment, pfSense, Power User, routers | Leave a Comment »
Posted by jpluimers on 2026/01/12
Some links and notes that might help me getting WireGuard site-to-site VPN working between GL.iNET and pfSense.
Posted in GL.iNet, GL.iNET GL-SFT1200, Hardware, Network-and-equipment, Power User, VPN, Wireguard | Leave a Comment »
Posted by jpluimers on 2026/01/06
The algorithm got me to the first video of this list: [Wayback/Archive] pierogi engineering – YouTube – search – hard drive
It’s similar to a longer second video that also does balancing using the gyroscopic effect of the moving platters.
Nice!
Video links:
Posted in 18650, Batteries, Development, Hardware, Hardware Development, HDD, Li-Ion, Power User | Leave a Comment »
The Wiert Corner - irregular stream of stuff 