HA Rules and a Washer That Talks UART

Homelab Highlights for 2026-11-02: self-hosting and homelab notes worth knowing.

[Audio embed placeholder]

The Lead: Proxmox VE 9 high availability: HA rules, fencing and a failover you have actually tested

A walkthrough of how Proxmox VE high availability actually works: the local and cluster resource managers, the watchdog and fencing, adding guests to HA, and the placement rules that replaced HA groups in Proxmox VE 9. It covers node affinity and resource affinity rules, what happens step by step when a node dies, shutdown policies, maintenance mode, and a checklist.

Why it matters: Most home clusters turn HA on before they’re ready — two nodes with no QDevice, or guests on local storage with no replica — and then nothing restarts, or the surviving node fences itself. The post is also explicit that HA is not a backup, and that a clean shutdown tests the shutdown policy, not failover.

Source: dev.to

News Roundup

CloudNativePG on k3s: PostgreSQL That Survives Node Failures

A Nextcloud PostgreSQL database running as a StatefulSet on Longhorn storage threw 500 errors for the ninety seconds it took volumes to reconstruct after a Proxmox host reboot. The replacement is CloudNativePG on k3s, which replicates at the database level: a primary and a replica on different nodes, with the operator promoting the replica when the primary’s node fails. The writeup covers the cluster definition, Barman backups to MinIO with thirty-day retention, and Prometheus metrics.

Why it matters: Failover takes thirty to sixty seconds with connections dropped during the window, and the author alerts on replication lag above five seconds because that is where a failover would lose data. More moving parts than a plain StatefulSet, but faster than waiting on storage reconstruction.

Source: dev.to

Someone Packed 930,000 Wikipedia Articles and Local AI Into an Offline Survival Library

Survival LLM is a free, MIT-licensed offline library combining roughly 930,000 Wikipedia articles with emergency guides from FEMA, the CDC, Ready.gov, MedlinePlus, WikEM, iFixit and wikiHow — about 1.5 million references in total — plus a local AI assistant running on Ollama. The full library is an 8.8 gigabyte download and about 21 gigabytes installed, with a smaller 1.3 gigabyte option that excludes Wikipedia and iFixit. Answers carry citations checked against the documents actually retrieved.

Why it matters: The developer found some models were inventing references to material they had never consulted, so citations are verified against retrieved sources. The project also notes its 22-scenario evaluation used AI judges and is not independent medical or safety validation.

Source: github.com

The best speech recognition you can run at home is absolutely tiny, and it runs on a ten-year-old laptop

XDA’s Dhruv Bhutani tested Parakeet, an Nvidia speech recognition model — the TDT 0.6B v3 version, a 600-million-parameter model taking about 700 megabytes quantized and around 2 gigabytes of RAM — running without a GPU on hardware as old as a ten-year-old laptop. He used a Docker deployment for API and file transcription, and a Mac front end called MacParakeet for dictation, meeting capture, speaker identification and pulling transcripts from web video.

Why it matters: He dictated an entire article with it and reports accurate results even with an accent and minimal performance impact, with everything staying on-device. For anyone wiring voice into Home Assistant, the hardware bar is low enough to matter.

Source: XDA - Self-Hosting

Tool & Software Highlight: Kanzo: A Lightweight Self-Hosted Kanban Board for Humans and AI Agents

Kanzo is a self-hosted Kanban board written in Rust, shipping as a single small executable backed by SQLite with no external database or cloud account, under the AGPL-3.0 license. It runs on Linux, macOS and Raspberry Pi, syncs boards between machines through a private Git repository, and includes keyboard-driven search, image attachments, and export to Markdown or JSON. Its built-in MCP server lets assistants like Claude Code and Codex pick up tasks, move them between columns, and leave progress comments.

Why it matters: The project states plainly that there is no built-in authentication, so the web interface should stay on a trusted network or sit behind a reverse proxy with auth. Installation is a precompiled binary or Cargo.

Source: github.com

Community Highlight: Local “dumb” Samsung washer monitoring in Home Assistant with ESPHome

A Reddit user going by kralonur built an ESPHome monitor for a Samsung washer that reads the UART communication between the control panel and the main board, rather than estimating the cycle from power draw. Home Assistant gets the program, temperature, spin, rinse, options, displayed time, cycle status and an optional Android notification. The builder captured traffic with a cheap logic analyzer and changed one setting at a time to work out Samsung’s packet format.

Why it matters: It is receive-only, and the builder warns that mains voltage is involved and the interface has not been qualified for isolation. In the comments, a note that the resistor divider is a poor man’s level shifter led the builder to update the README recommending a proper 5-volt to 3.3-volt level shifter and listing the divider’s limits.

Source: r/homeassistant

Sources

Transcript

Host A: Welcome to Homelab Highlights, the show that surfaces practical homelab wins and useful self-hosted tools.

Host A: High availability is the reason a lot of people build a Proxmox cluster in the first place — a node dies at three in the morning and its guests are running again on another node before anyone wakes up. But a walkthrough published yesterday by Charles Hartmann, adapted from his clustering book, makes the point that most home clusters switch HA on before they’re ready for it. Two nodes and no QDevice, or guests whose disks live on local storage with no replica. When a node fails, either nothing restarts, or the surviving node fences itself. And the second trap is worth saying out loud: HA is not a backup. It restarts the guest. It does not undo whatever was wrong with it. Host B: The mechanics are worth understanding first. Every node runs two daemons — a local resource manager that starts and stops HA guests on its own node, and a cluster resource manager, one of which is the active master that decides what runs where and handles fencing. Both lean on a watchdog. While a node is healthy and quorate, its daemons keep resetting the watchdog timer. Lose quorum or lose the daemons, the timer runs out and the node resets itself. That’s fencing — the cluster has to be certain a failed node is truly dead before starting its guests elsewhere, because a second copy writing to shared storage corrupts the disk. Host A: And a warning from the docs that’s easy to skim past: never kill those HA daemons or the watchdog multiplexer by hand, because killing them can reset the node immediately. By default Proxmox uses the kernel’s softdog, which the docs call reliable but not independent of the server’s hardware — a hardware watchdog module is the better option. Now, the part that actually changed in version nine: HA groups are gone, replaced by HA rules. Existing groups migrate to node affinity rules automatically once every node runs nine. Host B: The rules are a nice mental model. Node affinity rules are not strict by default — if the preferred node is down, the guest can run anywhere, unless the rule is made strict, in which case the guest stays stopped rather than landing on the wrong node. Resource affinity is the opposite, strict by default: keep an app and its database together, or keep two DNS servers apart. Rules get checked for conflicts before they apply, and a conflicting rule is disabled until it’s resolved, so the documented advice is to check the rules config after every edit. Hartmann’s checklist item that stings the most: test failover by pulling the power cord on a disposable VM, not a clean shutdown — a clean shutdown tests the shutdown policy, not HA.

Host A: Starting the roundup with a database story out of someone’s actual homelab. This operator’s Nextcloud PostgreSQL ran as a StatefulSet on Longhorn storage, and when the Proxmox host rebooted for a kernel update, the Longhorn volumes took ninety seconds to reconstruct — Nextcloud threw 500 errors the whole time. The fix was CloudNativePG, a Kubernetes operator that manages PostgreSQL replication at the database level instead of the storage level. A primary and a replica run on different nodes, and if the primary’s node dies, the operator promotes the replica. No storage reconstruction in the path. Host B: The writeup on woitzik.dev has the numbers: failover takes thirty to sixty seconds, connections drop during that window, and Nextcloud’s application-level retries cover the gap. Backups run through Barman to a MinIO instance with a thirty-day retention policy, and the operator exposes Prometheus metrics — the author’s Grafana rule alerts if replication lag goes over five seconds, because that’s where a failover would actually lose data. It’s more moving parts than a plain StatefulSet, but for a single-node cluster where a reboot used to mean a ninety-second outage, that seems like the right side of the trade. Host A: [lighter] Here’s one that’s just fun: a project called Survival LLM packs roughly 930,000 Wikipedia articles plus emergency guides from FEMA, the CDC, Ready.gov and iFixit into one offline, searchable library with a local AI assistant on top. It’s an 8.8 gigabyte download, about 21 gigabytes installed, and every answer carries citations checked against the documents actually retrieved — the developer found some models were inventing references to material they’d never consulted. Hopefully nobody ever needs it. Plenty of people will want it sitting on a machine anyway. Host B: Last one before the highlights: over on XDA, Dhruv Bhutani spent time with Parakeet, a small speech recognition model from Nvidia — the version tested is a 600-million-parameter model taking about 700 megabytes quantized and around 2 gigabytes of RAM, transcribing accurately on hardware as old as a ten-year-old laptop. No GPU, no subscription. He ran it through a Mac front end called MacParakeet, dictated an entire article with it, and pulled transcripts from web videos. For anyone wiring voice into Home Assistant, that hardware bar is low enough to matter.

Host B: For the tool highlight, a task manager that fits homelab constraints: Kanzo is a self-hosted Kanban board written in Rust that ships as a single small executable backed by SQLite — no external database, no cloud account, AGPL licensed. It runs on Linux, macOS, and a Raspberry Pi, and boards sync between machines through a private Git repository, a nice fit for anyone who already runs a Git server at home. Host A: The feature that makes it more than another Kanban clone is a built-in MCP server, which lets AI assistants like Claude Code and Codex work directly on the same board — an agent picks up assignments, moves tasks between columns, and leaves progress comments while a human watches in the browser. There’s keyboard-driven search across projects, image attachments, and export to Markdown or JSON. Whether agent-managed boards become a daily habit is an open question, but as an interface between operator and local agent, a shared board is tidy — the agent’s state is visible instead of buried in terminal scrollback. Host B: One caveat the project states plainly: no built-in authentication, so the web interface should stay on a trusted network or sit behind a reverse proxy with auth. Installation is a precompiled binary or Cargo, and for anyone juggling homelab projects across a couple of machines, a board that syncs over Git and costs almost nothing to run is worth a look.

Host A: The community highlight is a washer, and it’s a good one. A Reddit user going by kralonur built an ESPHome monitor for a Samsung washer — instead of the usual smart-plick trick of guessing the cycle from power draw, the device reads the UART communication between the control panel and the main board. Home Assistant gets what the panel actually displays: program, temperature, spin, rinse, options, the time shown, plus cycle status and an optional Android notification. Photos, wiring, and config are on GitHub. Host B: The reverse engineering story is the part worth hearing. The builder captured traffic with a cheap logic analyzer, then changed one setting at a time and compared the bytes to work out Samsung’s packet format — the wiring is standard UART, but the encoding is proprietary. There was a plan to dump the firmware, but Samsung covered the board in resin, and tearing into a working washer destructively to identify the MCU was a line not worth crossing. It’s receive-only, and the builder is upfront that mains voltage is involved and the interface hasn’t been qualified for isolation — anyone not comfortable working safely on mains appliances should stay out. Host A: The comments added real value. One commenter called the voltage divider a poor man’s level shifter — and the builder agreed, updating the README to recommend a proper 5-volt to 3.3-volt shifter and listing the divider’s limits, like back-powering the board when the ESP is off. Others shared their own approaches: one person pointed a camera at a Speed Queen’s panel so Home Assistant reads the indicator lights off the screen, and another stuck with power monitors and Zigbee door sensors on ancient mechanical machines — push notifications, smart-speaker announcements, plus snarky reminders if nobody moves the laundry within an hour. Each one person’s setup, but that last automation might be the best feature in the whole thread.

Host A: That’s Homelab Highlights for Monday. Until next time, happy hosting!