https://freemwiki.com/index.php?action=history&feed=atom&title=Openai%2F6971762b-a4d0-8013-af97-ad0960889ed5 2026-05-05T00:30:54Z Revision history for this page on the wiki MediaWiki 1.43.3 https://freemwiki.com/index.php?title=Openai/6971762b-a4d0-8013-af97-ad0960889ed5&diff=595932&oldid=prev 2026-01-22T05:25:06Z

<p>by freem.ai...</p> <p><b>New page</b></p><div><br /> {{DISPLAYTITLE:Zigbee Network Troubleshooting}}<br /> <br /> &#039;&#039;This conversation was exported from ChatGPT&#039;&#039;&lt;ref&gt;{{cite web|title=Zigbee Network Troubleshooting|url=https://chatgpt.com/share/6971762b-a4d0-8013-af97-ad0960889ed5|publisher=ChatGPT|access-date=2026-01-21}}&lt;/ref&gt;<br /> <br /> == gpt-5 ==<br /> === User: What do you recommend to this person on reddit ===<br /> What do you recommend to this person on reddit<br /> <br /> === Assistant: Here’s what I’d recommend to them—framed in a practical, Reddit-appropriate way: ===<br /> Here’s what I’d recommend to them—framed in a practical, Reddit-appropriate way:<br /> <br /> That Status.BUFFER_FULL (17) error is almost always Zigbee network congestion or coordinator overload, not Home Assistant itself.<br /> <br /> Based on what you described (≈65 Zigbee devices, ZHA, PoE SMLight coordinator), I’d suggest this checklist:<br /> <br /> ===== 1. Don’t reboot HA to “fix” it =====<br /> <br /> Rebooting clears the queue temporarily, but it hides the real issue. If this keeps happening, the Zigbee stack is getting saturated.<br /> <br /> ===== 2. Check Zigbee router vs battery balance (this is the big one) =====<br /> <br /> If too many of those 65 devices are battery-powered, you’ll hit problems.<br /> <br /> Rule of thumb:<br /> * 1 powered Zigbee router for every 6–10 end devices<br /> * Routers = smart plugs, in-wall switches, bulbs (powered)<br /> <br /> If you’re light on routers, add a few Zigbee plugs in problem areas and let the mesh settle overnight.<br /> <br /> ===== 3. Audit automations for message storms =====<br /> <br /> Recently added scripts + motion automations can flood the network.<br /> <br /> Common offenders:<br /> * Motion sensors firing → multiple light calls<br /> * Repeated turn_on commands even when lights are already on<br /> * Loops or automations without debounce<br /> <br /> Fix:<br /> Add conditions like:<br /> * if light is off<br /> * mode: restart or mode: queued (with limits)<br /> * Short delays (even 200–500 ms helps)<br /> <br /> ===== 4. Verify Zigbee channel vs Wi-Fi overlap =====<br /> <br /> If you’re on:<br /> * Zigbee 11 + Wi-Fi channel 1 → ❌ bad<br /> * Zigbee 15/20/25 → usually safer<br /> <br /> Once chosen, don’t change channels unless necessary, and let the mesh heal for 24 hours.<br /> <br /> ===== 5. Update coordinator firmware (but only once) =====<br /> <br /> The SMLight PoE coordinators are solid, but make sure:<br /> * Firmware is current<br /> * No experimental builds<br /> <br /> After updating, leave it alone—constant resets hurt mesh stability.<br /> <br /> ===== 6. Watch ZHA logs before it breaks =====<br /> <br /> When this happens again, look for:<br /> * Message retries<br /> * Delivery failures<br /> * Devices spamming state updates<br /> <br /> That usually points straight to the problematic device or automation.<br /> <br /> ===== 7. Capacity-wise: you’re not “too big” =====<br /> <br /> 65 devices is fine for ZHA if:<br /> * Mesh is healthy<br /> * Enough routers<br /> * Automations are sane<br /> <br /> Most “Zigbee limits” people hit are actually design issues, not hard limits.<br /> <br /> TL;DR:<br /> Add more Zigbee routers, reduce automation spam, don’t rely on HA reboots, and let the mesh stabilize. BUFFER_FULL means “too much too fast,” not “you’re out of capacity.”<br /> <br /> If you want, I can also help them:<br /> * Identify router gaps<br /> * Sanity-check an automation<br /> * Interpret ZHA logs<br /> <br /> That would be my Reddit reply.<br /> <br /> == References ==<br /> &lt;references /&gt;<br /> <br /> <br /> [[Category:ChatGPT Shares]]<br /> [[Category:openai]]</div>

Lukegao