<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress.com" -->
<urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"
	xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
	xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"
	xmlns:image="http://www.google.com/schemas/sitemap-image/1.1"
	>
<url><loc>https://scalablehuman.com/2026/07/07/smart-home-troubleshooting-why-the-fix-was-a-queue-not-a-retry/</loc><news:news><news:publication><news:name>Scalable Human Blog</news:name><news:language>en</news:language></news:publication><news:publication_date>2026-07-07T07:15:32+00:00</news:publication_date><news:title>Smart Home Troubleshooting Why the Fix Was a Queue Not a Retry</news:title><news:keywords>Software Engineering, programming, Node-RED, Raspberry PI, Home Automation, Smart Home, Bluetooth LE, HomeKit, BLE Troubleshooting, Command Queue</news:keywords></news:news><image:image><image:loc>https://scalablehuman.com/wp-content/uploads/2026/07/image_1783406933133.png?w=150</image:loc></image:image></url></urlset>
