<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Posts on Configuring Bits</title><link>https://configuringbits.com/posts/</link><description>Recent content in Posts on Configuring Bits</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://configuringbits.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>An Air-Quality Adventure: ESPHome meets the PMSA003I Sensor</title><link>https://configuringbits.com/posts/2026-05-14-a-high-air-quality-adventure-with-esphome-and-a-pmsa003i-sensor/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://configuringbits.com/posts/2026-05-14-a-high-air-quality-adventure-with-esphome-and-a-pmsa003i-sensor/</guid><description>&lt;p&gt;If you’ve ever tinkered with DIY IoT devices, specifically air quality monitoring, you know that not all sensors are created equal. My recent project, an air quality monitor built on a NodeMCU v2 (ESP8266), taught me a humbling lesson. What should have been a simple plug-and-play integration turned into a “dead as a doornail” scenario involving reverse polarity, almost smoke, and a sensor that refused to speak until it had a 30-second warm-up period.&lt;/p&gt;</description></item><item><title>A Date With the Night</title><link>https://configuringbits.com/posts/date-with-the-night/</link><pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate><guid>https://configuringbits.com/posts/date-with-the-night/</guid><description>&lt;h3 id="late-nights-with-server-upgrades-and-troubleshooting"&gt;Late nights with server upgrades and troubleshooting&lt;/h3&gt;
&lt;p&gt;When your homelab becomes a production server and your users come to expect those services, it’s hard to find a good time for maintenance. In addition to that, when server hardware is being upgraded and parts being swapped out, downtime is a bit more extensive than simply spinning up services on new hardware. That was the situation that I ran into.&lt;/p&gt;
&lt;p&gt;Previous Hardware:&lt;/p&gt;</description></item></channel></rss>