<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LoRaWAN on LoRaScope — Spectrum &amp; Traffic Analyser</title><link>https://lora.dd.com.au/tags/lorawan/</link><description>Recent content in LoRaWAN on LoRaScope — Spectrum &amp; Traffic Analyser</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 27 Jun 2026 17:54:57 +1000</lastBuildDate><atom:link href="https://lora.dd.com.au/tags/lorawan/index.xml" rel="self" type="application/rss+xml"/><item><title>How I let an AI debug my LoRa network</title><link>https://lora.dd.com.au/blog/2026/06/27/how-i-let-an-ai-debug-my-lora-network/</link><pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate><guid>https://lora.dd.com.au/blog/2026/06/27/how-i-let-an-ai-debug-my-lora-network/</guid><description>&lt;p&gt;I hit a massive run of packet corruption on a live LoRa network. Frames were
arriving mangled, links were flaky, and the usual guesswork — swap the antenna,
move the gateway, twiddle the spreading factor — was getting nowhere. So I
stopped guessing and put an AI agent on the radio.&lt;/p&gt;
&lt;p&gt;This is that session, start to finish. It&amp;rsquo;s also the reason LoRaScope is built
the way it is: not as a screen you stare at, but as an instrument an agent can
drive.&lt;/p&gt;</description></item></channel></rss>