<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Openwrt on Aada&#39;s Blog</title>
    <link>https://blog.aada.cat/tags/openwrt/</link>
    <description>Recent content in Openwrt on Aada&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 21 Oct 2026 16:45:00 +0200</lastBuildDate>
    <atom:link href="https://blog.aada.cat/tags/openwrt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Publishing DHCP Lease Changes on MQTT</title>
      <link>https://blog.aada.cat/posts/publishing-dhcp-lease-changes-on-mqtt/</link>
      <pubDate>Wed, 21 Oct 2026 16:45:00 +0200</pubDate>
      <guid>https://blog.aada.cat/posts/publishing-dhcp-lease-changes-on-mqtt/</guid>
      <description>&lt;p&gt;Recently I came into the situation that I wanted to automate something based on&#xA;the state of my printer. If I turn it on, a light above it should turn on so&#xA;the tiny screen on it becomes readable. And when the printer turns off again,&#xA;the light should turn off.&#xA;To do this, I needed some way to determine when my printer turns on. Luckily&#xA;it&amp;rsquo;s very reliable at getting DHCP leases and releasing them when it turns off&#xA;again. Additionally, the DHCP server that ships with OpenWRT has a flag to&#xA;accept a script it should run when leases are changed&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
