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/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
Everytime when installing a pfSense router from scratch, I seem to re-learn a few of the below quirks. So it was finally time to document them (:
Quite a few of my pfSense configurations are just doing routing between various networks, should not provide DHCP leases and do not always need or have a WAN connected (i.e. they are LAN-only).
Posted in Communications Development, Conference Topics, Conferences, Cyberchef, Development, DHCP, Encoding, Event, Hardware, HTTP, Internet protocol suite, MikroTik, Network-and-equipment, pfSense, Power User, routers, Software Development, SSH, TCP, TLS, UDP | Tagged: 8846 | Leave a Comment »
Posted by jpluimers on 2026/01/05
At the time of writing (during the Covid-19 Pandemic) the [Wayback/Archive] Product Comparison – GL.iNet contains the below products.
I got 3 of them (2 are variations of the same model) and their quality/price ratio is great, even with the prices that risen during the 2020-onwards global chip shortage.
Posted in Ethernet, GL-AR300M, GL.iNet, GL.iNET GL-SFT1200, Hardware, Network-and-equipment, Power User | Leave a Comment »
Posted by jpluimers on 2025/12/26
TL;DR: avoid Digitus AC fans, but use DC case fans with built-in/external temperature controller plus 12V or USB-step-up power supply and optionally fan grilles/meshes.
A while ago, I bought a 7U shallow 19-inch rack cabinet to house some of our network equipment for the offices and other rooms at the top floor: [Wayback/Archive] DIGITUS Professional Network Wall Housing – Soho Wall Cabinet: Amazon.de: Computer & Accessories
Since it was to be mounted in the boiler room, which is on the top floor under a flat roof, it would get warm so I wanted fans installed in it under or over the air vents in the housing (the cabinet is delivered as flat-pack with parts pictured below and requires about half an hour assembly time):
Posted in Hardware, LifeHacker, Network-and-equipment, Power User | Leave a Comment »
The Wiert Corner - irregular stream of stuff 