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.
One Song Wouldn't Play. 231 Files Were Broken. Lidarr's Ogg Tag Writer Was the Culprit.
On September 11, 2026, one song would not play. The client just retried it, in a loop, forever. Not a silence, not an error dialog — a little spinner that never resolved. I’d seen that behavior before, and I’d always blamed the server. This time the server was fine, and the truth was stranger: Lidarr had been quietly corrupting my Ogg Vorbis files for months, nightly, one byte at a time.
The setup is a normal homelab. Music lives on the NAS (.12, ZFS) and is served by Navidrome on .21, which streams the raw file — transcoding is off — to a desktop client called Supersonic. Lidarr 3.1.0.4875, also on .21, manages the library. Somewhere along the way I’d set “Write Metadata to Audio Files” to Sync (writeaudiotags = Sync, scrubaudiotags = True), which means every nightly Refresh Artist rewrites tags and embeds cover art directly into the files themselves.
That setting is the whole story. It turned a metadata tool into a corruption machine.