<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gpio on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/gpio/</link>
    <description>Recent content in Gpio on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/gpio/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted GPIO Web Control Dashboards: pigpiod vs gpiozero vs libgpiod</title>
      <link>https://www.pistack.xyz/posts/2026-06-07-self-hosted-gpio-web-control-pigpiod-gpiozero-libgpiod/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-07-self-hosted-gpio-web-control-pigpiod-gpiozero-libgpiod/</guid>
      <description>&lt;p&gt;General Purpose Input/Output (GPIO) pins are the bridge between software and the physical world. Whether you&amp;rsquo;re controlling relays, reading sensors, driving motors, or blinking LEDs, your application needs a reliable way to talk to GPIO hardware. When that control needs to happen over a network — a web dashboard toggling lights, a monitoring system reading temperature sensors, or a test automation framework manipulating hardware — you need a GPIO server that exposes pins through a network-accessible API. Three Linux-based open-source frameworks — &lt;strong&gt;pigpiod&lt;/strong&gt;, &lt;strong&gt;gpiozero&lt;/strong&gt;, and &lt;strong&gt;libgpiod&lt;/strong&gt; — each take a different approach to this challenge.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
