<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Smart-Meter on Linux Colorado</title><link>https://www.linuxcolorado.com/tags/smart-meter/</link><description>Recent content in Smart-Meter on Linux Colorado</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.linuxcolorado.com/tags/smart-meter/index.xml" rel="self" type="application/rss+xml"/><item><title>My Smart Meter Went Quiet for Ten Days: a 1,094-Day Client Certificate and IEEE 2030.5</title><link>https://www.linuxcolorado.com/post/2026-11-03-smart-meter-cert-expired-home-assistant/</link><pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.linuxcolorado.com/post/2026-11-03-smart-meter-cert-expired-home-assistant/</guid><description>&lt;p&gt;Two sensors in Home Assistant had polled my electricity meter every five seconds for two years. One afternoon they both went &lt;code&gt;unknown&lt;/code&gt; 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.&lt;/p&gt;
&lt;p&gt;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 &lt;code&gt;Command failed (with return code 1)&lt;/code&gt; every five seconds until it ran out of curiosity. This post is the post mortem: how the meter&amp;rsquo;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&amp;rsquo;d check first next time.&lt;/p&gt;</description></item></channel></rss>