<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Homeassistant on Linux Café</title>
    <link>https://mrtomlinux.org/tags/homeassistant/</link>
    <description>Recent content in Homeassistant on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Nov 2026 10:49:43 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/homeassistant/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why My Home Assistant Timer Never Fires—and How to Fix It</title>
      <link>https://mrtomlinux.org/post/2026-11-20-why-my-home-assistant-timer-never-firesand-ho/</link>
      <pubDate>Fri, 20 Nov 2026 10:49:43 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-11-20-why-my-home-assistant-timer-never-firesand-ho/</guid>
      <description>&lt;p&gt;If you’ve ever set a timer in Home Assistant and then stared at the clock wondering why nothing happened, you’re not alone.&lt;br&gt;&#xA;The culprit is almost always one of three things:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Time‑zone or daylight‑saving mis‑configurations&lt;/li&gt;&#xA;&lt;li&gt;Timer entity state or YAML syntax errors&lt;/li&gt;&#xA;&lt;li&gt;System clock drift or NTP hiccups&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Below is a practical walk‑through that keeps the technical meat intact while sounding like a coffee‑shop chat between two sysadmins.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h3 id=&#34;1-verify-the-system-clock-and-time-zone&#34;&gt;1. Verify the System Clock and Time Zone&lt;/h3&gt;&#xA;&lt;p&gt;Home Assistant piggybacks on the host’s clock. If that’s off, timers will be mis‑aligned or never fire.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
