HACS moves in, dead Macs get jobs, and a wall clock cuts the cord

Homelab Highlights for 2026-10-16: self-hosting and homelab notes worth knowing.

[Audio embed placeholder]

The Lead: HACS is becoming part of Home Assistant

Starting with Home Assistant 2026.11, the HACS community store ships in core as the Marketplace integration. Existing HACS installs are converted in place, and the standalone integration is retired. Frenck confirmed the rollout and emphasized that marketplace content remains unvetted by the project.

Why it matters: HACS has been the unofficial front door for custom cards and integrations. Baking it into core makes the community ecosystem a first-class part of Home Assistant, but also widens the attack surface for unvetted code. The separate Docker container requirement goes away, simplifying setup.

Source: r/homeassistant - Homelab Highlights top (day)

News Roundup

FLODE: Visualize Home Assistant automations as a flow

FLODE is a HACS panel that renders automations and scripts as a flow on a canvas. It uses Home Assistant’s own editors for cards, saves plain YAML, and includes debugging features like trace timelines, run-from-here, and relation views. Optional AI integration uses HA’s own AI task system.

Why it matters: Long automations with nested choose blocks are hard to read in the normal editor. FLODE provides a visual overview without introducing its own data model, so automations remain untouched if the project is removed. It started as a fork of C.A.F.E. but is a full UI rewrite.

Source: github.com

Let’s Encrypt Is Shortening Certificate Lifetimes

Let’s Encrypt announced default certificate lifetimes drop from 90 to 64 days on February 10, 2027, heading to 45 days in 2028. Authorization reuse shrinks from 30 to 10 days. Existing certs remain valid.

Why it matters: Renewal automation that was comfortable becomes mandatory. Homelab operators need to inventory where TLS terminates, verify certbot timers or cron jobs actually run, and test domain validation before renewal day.

Source: Virtualization Howto

Your Docker Backups Might Be Useless When You Need Them Most

A backup dashboard showing green every night doesn’t guarantee a successful restore. Common failures include missing database dumps, live database files copied mid-write, and environment variables not included in the archive.

Why it matters: A backup never restored is a hope, not a plan. The article recommends picking one noncritical app and actually restoring it in isolation to uncover hidden issues before a real failure.

Source: Noted

Tool & Software Highlight: Fregata: Native Frigate for macOS on Apple Silicon

Fregata runs Frigate natively on macOS, targeting the Apple Neural Engine for object detection. In a real test, inference dropped from ~33ms (Docker/GPU) to 2.45ms, with total system CPU around 4%. The GPU handles enrichments like face and license plate recognition.

Why it matters: A dead-screen M1 MacBook Air can become a powerful, low-power NVR node. However, Fregata’s macOS runtime and CoreML detector are proprietary, which is a trust tradeoff for camera software. The Frigate Python core remains open source.

Source: github.com

Community Highlight: Echo Wall Clock now shows Home Assistant timers, no Echo needed

A homelabber reverse-engineered the Echo Wall Clock’s Bluetooth protocol using Claude Code and built a Home Assistant integration. The clock runs fully local, displaying timers from HA without any Amazon cloud dependency. The protocol notes and a Python library are published.

Why it matters: This frees a popular device from Amazon’s ecosystem. The clock uses Bluetooth Classic (not BLE), so ESPHome and Shelly proxies won’t work. The clock is discontinued, making it a scavenger-hunt item. The builder published full protocol notes for others to build on.

Source: xdaforums.com

Sources

Transcript

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

Host A: Home Assistant users have a big change coming: HACS, the Home Assistant Community Store, is being folded into Home Assistant itself. Starting with the 2026.11 release, the community store ships in core as the Marketplace integration. Existing HACS installs get converted in place, and the standalone HACS integration gets retired. So the thing half the community installs on day one stops being a custom component entirely.

HOST B: That’s a big deal, because HACS has always been the unofficial front door. Custom cards, custom integrations, all of it living outside the sanctioned path. Baking it in means the community ecosystem becomes a first-class part of the product. Frenck, one of the Home Assistant leads, confirmed the rollout in the GitHub thread, and when people asked about the trust angle, he said it will be clear to users that marketplace content is not vetted by the project. That caveat matters. There’s real pushback in the thread about running unvetted code from a store button, and someone joked about rats in a marketplace. Fair point, honestly. Convenience always widens the attack surface.

HOST A: The practical detail most people will care about: one commenter asked whether the separate Docker container dance goes away, and Frenck confirmed it is just baked in now, working for everyone regardless of installation method. That tidies up one of the messier corners of a Home Assistant install. There’s a funny thread note too: the migration will not carry existing issues over to the new repo, which one commenter called a very Home Assistant thing to do.

Host A: Staying in Home Assistant for the first feed item, because FLODE showed up this week and it’s a fun one. It’s a HACS-available panel that draws your automations and scripts as an actual flow on a canvas. The clever bit: FLODE has no editor of its own. Click a card and you get Home Assistant’s own trigger, condition, and action forms, the same ones in Settings. Everything saves as plain HA YAML, so if the project ever vanishes, every automation keeps working untouched.

HOST B: And it’s built for debugging, not just pretty pictures. You get Home Assistant’s trace timeline next to the flow, the path a run actually took drawn on the cards, run-from-here on any step, and relations views that surface conflicting automations, self-triggering loops, and missing entities. There’s an optional AI layer through Home Assistant’s own AI task integration, including local Ollama, but the buttons simply don’t exist if no AI task is configured. Full context: FLODE started as a fork of C.A.F.E. by FezVrasta, credited openly in the README, and the developer took some heat in the comments for that until explaining the repo has been around since January with nearly five hundred commits. A full rewrite of the UI is a design fork, not a bug fix, so it holds up. Needs HA 2026.3 or newer.

HOST A: Quick cert alert next. Let’s Encrypt announced on October 7 that default certificate lifetimes drop from 90 days to 64 days on February 10, 2027, heading toward 45 days in 2028, and authorization reuse shrinks from 30 days to 10. Existing certs stay valid, but the writeup over at Virtualization Howto makes the right point: renewal automation that used to be comfortable becomes mandatory. Inventory where TLS actually terminates in the lab, check the certbot timers or cron jobs really run, and test domain validation before renewal day, since a failed challenge defeats the whole schedule.

HOST B: And one more thing to check, from Noted this week. The argument is that a Docker backup dashboard showing green every night proves nothing. Compose files copied without the database, live database files copied mid-write, and environment variables that never made it into the archive are all classic restore failures. The advice worth stealing from the piece: pick one noncritical app and actually restore it somewhere isolated. A backup never restored is a hope, not a plan.

Host B: Tool highlight time, and this one is a solid e-waste rescue story with real numbers behind it. Someone had a base M1 MacBook Air, eight gigs of RAM, whose internal display died. Instead of trashing it, it became a headless homelab node running the arr stack, n8n, Home Assistant with MQTT, and native Jellyfin. The interesting part starts when they added a 4-megapixel camera running full-resolution detection on the main feed.

HOST A: Phase one was Frigate 0.18 in Docker through Colima, with an Apple Silicon GPU detector sidecar because pure CPU detection would melt an 8 gig machine. That got about 33 milliseconds of inference, but it pinned the GPU around the clock on a fanless, closed-lid laptop. Not a great long-term plan for hardware with no fan to save it.

HOST B: Phase two is the project worth knowing: Fregata, which runs Frigate natively on macOS instead of through virtualization layers. Migration pulled configurations over cleanly and downloaded optimized CoreML models on first launch. Inference dropped from about 33 milliseconds to 2.45, a thirteen-times speedup, with the Neural Engine handling detection and detector CPU around one percent. The GPU picks up enrichments like face and license plate recognition, the Media Engine handles decode, and total system CPU idles near four percent. The chassis stays cool to the touch. Here’s the honest caveat, and a commenter flagged it too: the Frigate Python core stays open source, but Fregata’s macOS runtime, the CoreML detector work, and the brand are proprietary. For an NVR watching a home, closed-source camera software is a real tradeoff, not a footnote. It does integrate cleanly with a Dockerized Home Assistant over MQTT, and text-based clip search works out of the box. Worth checking the licensing and trust position before pointing cameras at it.

Host A: Community highlight, and this is exactly the kind of stubbornness this show loves. The Echo Wall Clock is that simple LED-ring clock Amazon sold to show kitchen timers. It only works with an Echo, which is the whole problem. One homelabber had already moved their Echo Show 5s to LineageOS running a kiosk setup, and refused to keep an Alexa device alive just to drive one clock.

HOST B: So the fix: they used Claude Code to reverse-engineer the clock’s Bluetooth protocol and built a Home Assistant integration plus a plugin for their kiosk. The protocol turned out simple, since the clock is basically a display. The controller sets the time and names the timers; the ring lights up, counts down, and pulses when time is up. Pause, resume, cancel, and add-time all work, multiple timers display at once, and nothing on the clock is modified. Completely local.

HOST A: The caveats are useful for anyone tempted. The clock runs on Bluetooth Classic, not BLE, so ESPHome and Shelly Bluetooth proxies will not work; the HA host needs a Classic-capable adapter. A clock talks to one controller at a time, so pairing it disconnects it from any Echo. The builder tested on HA Container on a Raspberry Pi 3B with a single clock and is upfront that other setups are untested. In the comments they were refreshingly honest that Claude did most of the reverse engineering while they played project manager and QA, and they published the full protocol notes and a Python library for anyone building on top. There’s even a web simulator to see what the clock displays without owning one. Reaction in the thread was warm, with people saying it was the last Alexa holdout in their house. One sad detail: the clock is discontinued, so this is a scavenger-hunt device now. Keep an eye on secondhand listings.

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