My Smart Meter Went Quiet for Ten Days: a 1,094-Day Client Certificate and IEEE 2030.5
Two sensors in Home Assistant had polled my electricity meter every five seconds for two years. One afternoon they both went unknown and stayed that way for ten days before I noticed. Nothing had changed on my side: no update, no restart, no config edit. The meter was still answering other hosts on the LAN. And yet it had quietly stopped talking to me.
The culprit was a client certificate I generated in 2023 with a script that handed it exactly three years of life. When it expired, the meter rejected every poll with a TLS alert, and Home Assistant just logged Command failed (with return code 1) every five seconds until it ran out of curiosity. This post is the post mortem: how the meter’s local IEEE 2030.5 interface actually authenticates, why a cumulative register quietly books ten days of power into a single hour, and what I’d check first next time.
A Valid TLS Cert for a LAN-Only Home Assistant: Traefik, DNS-01, and Split-Horizon DNS
Here’s a puzzle that trips up a lot of homelabbers: you want a publicly-trusted TLS certificate for a service that is only ever reachable on your LAN. No port forwarding, no exposing the box to the internet — but also no browser warnings, no self-signed-cert clicking-through, and no private CA to install on every device.
The specific thing that forced my hand: I wanted to connect Claude.ai’s remote MCP connector to my Home Assistant instance, and that connector flatly refuses plain HTTP. It demands a valid https:// endpoint. My HA is a sealed Green appliance at 192.168.1.18:8123, LAN-only, and I had no intention of exposing it to the world.
The answer is a nice combination of three ideas — a Let’s Encrypt DNS-01 challenge, a wildcard certificate, and split-horizon DNS — wired together with Traefik. This post is the worked example.
Teaching the House to Announce the Mail Truck: A Zero-Shot CLIP Classifier on the Homelab
I wanted my house to say, out loud, “the mail truck is out front” — the moment the USPS truck pulls up, spoken through the same Home Assistant TTS pipeline that runs the rest of the place. Not “a vehicle was detected.” Specifically the mail truck.
The gap between those two sentences is the whole project. My NVR (Frigate) is very good at “there’s a truck in the driveway zone” and completely incapable of “that’s a USPS LLV.” Closing that gap meant adding a small second-stage classifier that looks at the snapshot Frigate already captured and decides what kind of truck it is — running on hardware I already own, with no cloud vision API. It ended up as a zero-shot CLIP classifier, and along the way it picked up a second job I never planned: catching the garbage truck too.