<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>zigbee on toorun.dev</title><link>https://toorun.dev/tags/zigbee/</link><description>Recent content in zigbee on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/zigbee/index.xml" rel="self" type="application/rss+xml"/><item><title>Zigbee for Embedded Linux: Practical Guide, Hardware, and Protocol Comparisons</title><link>https://toorun.dev/posts/zigbee-embedded-linux-practical-guide/</link><pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate><guid>https://toorun.dev/posts/zigbee-embedded-linux-practical-guide/</guid><description>Zigbee for Embedded Linux: Practical Guide, Hardware, and Protocol Comparisons You need battery-powered temperature sensors across a building, a few controllable lights, and an embedded Linux gateway that collects everything locally. Running Linux on every sensor would be excessive. Keeping every sensor connected to Wi-Fi may also cost more energy than the application needs.
Zigbee is a good fit for small, infrequent sensor reports and control commands. Put the Zigbee firmware on a low-power microcontroller, and use Linux for storage, automation, dashboards, and backend connectivity.</description></item></channel></rss>