<?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>Async-Rust on Antony Mapfumo</title><link>https://mapfumo.github.io/tags/async-rust/</link><description>Recent content in Async-Rust on Antony Mapfumo</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 11 Jan 2026 13:50:05 +1000</lastBuildDate><atom:link href="https://mapfumo.github.io/tags/async-rust/index.xml" rel="self" type="application/rss+xml"/><item><title>From LoRa Modules to Native LoRaWAN the STM32WL Migration - Wk10</title><link>https://mapfumo.github.io/posts/week-10-from-lora-modules-to-native-lorawan-the-stm32wl-migration/</link><pubDate>Sun, 11 Jan 2026 13:50:05 +1000</pubDate><guid>https://mapfumo.github.io/posts/week-10-from-lora-modules-to-native-lorawan-the-stm32wl-migration/</guid><description>&lt;h2 id="the-challenge">The Challenge&lt;/h2>
&lt;p>For the first 9 weeks of this project, I&amp;rsquo;ve been using RYLR998 LoRa modules - simple AT command modules that handled the radio work while my STM32 focused on sensors. They worked beautifully for point-to-point communication (600m range, 95% success rate), but they had a fundamental limitation:&lt;/p>
&lt;p>&lt;strong>They weren&amp;rsquo;t LoRaWAN.&lt;/strong>&lt;/p>
&lt;p>LoRa (the physical layer) is great for custom networks. But &lt;strong>LoRaWAN&lt;/strong> (the MAC layer protocol) is what you need for:&lt;/p></description></item><item><title>Complete IoT Telemetry Pipeline: From Sensors to Dashboards - Wk7, 8)</title><link>https://mapfumo.github.io/posts/complete-iot-telemetry-pipeline-from-sensors-to-dashboards/</link><pubDate>Sun, 28 Dec 2025 11:42:16 +1000</pubDate><guid>https://mapfumo.github.io/posts/complete-iot-telemetry-pipeline-from-sensors-to-dashboards/</guid><description>&lt;p>Week 7+8 represents &lt;strong>project completion&lt;/strong> at the infrastructure level. This isn&amp;rsquo;t about adding one more feature - it&amp;rsquo;s about building the &lt;strong>complete path from sensor to insight&lt;/strong>.&lt;/p>
&lt;p>After seven weeks:&lt;/p>
&lt;ul>
&lt;li>Week 1-3: Sensors talk via LoRa ✅&lt;/li>
&lt;li>Week 5: Gateway firmware outputs JSON ✅&lt;/li>
&lt;li>Week 6: Async service processes data ✅&lt;/li>
&lt;li>Week 7: Data goes to MQTT and InfluxDB ✅&lt;/li>
&lt;li>Week 8: &lt;strong>Professional dashboards visualize everything&lt;/strong> ✅&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>This is a complete IoT monitoring system.&lt;/strong> From a temperature sensor on a breadboard to a Grafana dashboard refreshing every 10 seconds. All in Rust. All running on real hardware.&lt;/p></description></item><item><title>Async Rust Gateway From Embedded Firmware to Cloud Infrastructure - wk6</title><link>https://mapfumo.github.io/posts/async-rust-gateway-from-embedded-firmware-to-cloud-infrastructure/</link><pubDate>Sun, 21 Dec 2025 10:34:48 +1000</pubDate><guid>https://mapfumo.github.io/posts/async-rust-gateway-from-embedded-firmware-to-cloud-infrastructure/</guid><description>&lt;p>Week 6 marks a fundamental shift in the project. Up through Week 5, everything stayed within the embedded realm - microcontrollers talking to each other over LoRa. Data lived in OLED displays and defmt logs that disappeared when you closed the terminal.&lt;/p>
&lt;p>&lt;strong>Week 6 changes that.&lt;/strong> It&amp;rsquo;s the bridge between embedded and cloud, between constrained systems and abundant infrastructure, between &lt;code>no_std&lt;/code> and &lt;code>std&lt;/code>.&lt;/p>
&lt;p>This is the week I learned &lt;strong>async Rust isn&amp;rsquo;t just about performance - it&amp;rsquo;s about building systems that compose.&lt;/strong>&lt;/p></description></item></channel></rss>