# microReticulum Updates and Technical Discussion _Build Guides · started by gdane on Sat, May 23, 2026 3:23 PM_ Tags: Question, Discussion, Help --- ## Original post **gdane** · Sat, May 23, 2026 3:23 PM Welcome to the **microReticulum Updates and Technical Discussion** thread. This thread serves as the central place for announcements related to new microReticulum releases, including bug fixes, new features, performance improvements, compatibility changes, and development milestones. In addition to release updates, the thread is open for technical discussion covering topics such as architecture and design decisions, implementation details, integrations, troubleshooting, optimization, deployment experiences, and general development feedback. Whether you are following project progress, testing new releases, integrating microReticulum into your own applications, or contributing ideas and improvements, you are encouraged to participate in the discussion. Note that discussions are expected to remain respectful, constructive, and productive. Offensive, disruptive, or non-constructive posts may be removed in order to maintain a healthy and collaborative community environment. Let's build together! [microReticulum GitHub Repo](https://github.com/attermann/microReticulum) --- ## Reply 1 **gdane** · Sat, May 23, 2026 3:37 PM A quick announcement... I know there has been a lot of interest in `Resource` support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived! I've also added an example project `nomadnet` in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is *extremely* resource-intensive and not embedded-friendly at all, but this is a discussion for another day. Note that `Resource` support is currently only available in the `master` branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play. Cheers! --- ## Reply 2 **daylight-hub** · Sat, May 23, 2026 6:08 PM Is there a way that the microReticulum transport nodes can show up in my network visualization panel on MeshchatX which is connected to a standard RNode? It would be great to confirm that the transport node is indeed up and running. --- ## Reply 3 **Zenith** · Sat, May 23, 2026 6:16 PM **gdane** wrote: > A quick announcement... > > I know there has been a lot of interest in `Resource` support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived! > > I've also added an example project `nomadnet` in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is *extremely* resource-intensive and not embedded-friendly at all, but this is a discussion for another day. > > Note that `Resource` support is currently only available in the `master` branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play. > > Cheers! This is so awesome. Great work Attermann!!! As a side note, for any LXMF implementations in the future that target microControllers where bzip isn't possible - there is compression support signalling with the `SF_COMPRESSION` flag :) https://github.com/markqvist/LXMF/commit/72932eea28074420defd02b6eb3e5e09a126e4ee --- ## Reply 4 **Anonymous** · Sun, May 24, 2026 12:30 AM **daylight-hub** wrote: > Is there a way that the microReticulum transport nodes can show up in my network visualization panel on MeshchatX which is connected to a standard RNode? It would be great to confirm that the transport node is indeed up and running. Not yet, but that has actually been the motivation behind finally getting Resource implemented, so that transport nodes can have a mechanism to share instrumentation with other nodes on the network. I haven't decide if I will implement a NomadNet-type interface, or extend the existing management endpoints already in RNS and recently (partially, wip) implemented in microReticulum. Of course you don't have to wait for me either. You could roll your own firmware based on microReticulum_Firmware, and add in whatever endpoint you like using microReticulum code and the `nomednet` example as a guide. --- ## Reply 5 **Anonymous** · Sun, May 24, 2026 12:31 AM **Zenith** wrote: > **gdane** wrote: > > A quick announcement... > > > > I know there has been a lot of interest in `Resource` support in microReticulum over the past months (even years), and I&#039;m happy to announce that it has finally arrived! > > > > I&#039;ve also added an example project `nomadnet` in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is *extremely* resource-intensive and not embedded-friendly at all, but this is a discussion for another day. > > > > Note that `Resource` support is currently only available in the `master` branch of the microReticulum repo and not in any release (yet). Please treat it as &quot;experimental&quot; for the time being while we work to get more interop testing behind us. In the meantime, feel free to play. > > > > Cheers! > > This is so awesome. Great work Attermann!!! > > As a side note, for any LXMF implementations in the future that target microControllers where bzip isn't possible - there is compression support signalling with the `SF_COMPRESSION` flag :) > > https://github.com/markqvist/LXMF/commit/72932eea28074420defd02b6eb3e5e09a126e4ee Awesome thanks for the heads-up. That would be a really nice addition to NomadNet too. --- ## Reply 6 **Zenith** · Sun, May 24, 2026 12:58 AM That could probably be done too. In the long run, I think it would be very nice to see some type of feature flag happen on the link level, and maybe even options for different compression like zstd. Much like how MTU is negotiated. --- ## Reply 7 **Torlando** · Sun, May 24, 2026 5:03 AM **gdane** wrote: > A quick announcement... > > I know there has been a lot of interest in `Resource` support in microReticulum over the past months (even years), and I'm happy to announce that it has finally arrived! > > I've also added an example project `nomadnet` in the repo that demonstrates a very basic NomadNet client and server. Note however that microReticulum presently does not have support for compressed content, so most pages delivered by standard NomadNet will fail to be received unless compression is disabled. The reason for this omission lies in the compression algorithm bz2 used by RNS which is *extremely* resource-intensive and not embedded-friendly at all, but this is a discussion for another day. > > Note that `Resource` support is currently only available in the `master` branch of the microReticulum repo and not in any release (yet). Please treat it as "experimental" for the time being while we work to get more interop testing behind us. In the meantime, feel free to play. > > Cheers! Awesome! I spent a few cycles in the last few weeks grafting pyxis onto microReticulum 0.3.0, since I had formed it back in December or something, and you had much nicer solutions for several of the problems I had to solve along the way to get it working. Will happily spend a few more using your Resource implementation! --- ## Reply 8 **gdane** · Sat, Jun 6, 2026 4:34 PM New **microReticulum** version 0.4.1 released with several fixes and enhancements. Also new **microReticulum_Firmware** version 1.86.2 released with the latest microReticulum and added features. Notably, this latest firmware release includes support for the new Provisioning system, as well as a single-page HTML RNode management console for managing microReticulum settings and most RNode settings. NOTE: This new provisioning and web console is experimental so use at your own risk. --- ## Reply 9 **gdane** · Sat, Jun 6, 2026 9:31 PM Also announcing a new and very *experimental* feature of microReticulum_Firmware. The latest release version 1.86.2 includes RNode Linux daemons for Raspberry Pi (debian-bookworm) and Luckfox (ubuntu-jammy) that interface directly with SPI-attached LoRa radios (think meshtasticd). I have only tested with an Adafruit RFM95x module wired to a Luckfox Pico so far but will add more example configs as I am able to test new SPI radios. This daemon can run in either traditional RNode Host interface mode (default), or in self-contained transport mode (TNC mode). To use it as a Host interface from Python RNS just define your RNodeInterface as usual but use "port = tcp://localhost" to connect to the rnoded daemon. --- ## Reply 10 **gdane** · Sat, Jun 6, 2026 9:31 PM (duplicate post deleted) --- ## Reply 11 **Anonymous** · Sun, Jun 7, 2026 7:51 AM Is there a way to edit the Nomadnet page? Would be great to customise the name of the Node and page content. --- ## Reply 12 **gdane** · Sun, Jun 7, 2026 6:16 PM **Anonymous** wrote: > Is there a way to edit the Nomadnet page? Would be great to customise the name of the Node and page content. Not through runtime configuration unfortunately. You can easily change in the source though if you're comfortable building it yourself. The site name is currently line 875 in RNode_Firmware.ino, and the page content in all in Pages.h. --- ## Reply 13 **Dio** · Mon, Jun 8, 2026 4:16 AM How do I configure the latest microReticulum_Firmware to enable Transport? I used the rnodeconf --tnc but the serial console says Transport is disabled. It's not clear how the new provisioning system works. --- ## Reply 14 **Anonymous** · Tue, Jun 9, 2026 10:01 PM I would also be very interested in a bit more documentation about how the new features work. <3 --- ## Reply 15 **gdane** · Wed, Jun 10, 2026 8:18 PM **Dio** wrote: > How do I configure the latest microReticulum_Firmware to enable Transport? I used the rnodeconf --tnc but the serial console says Transport is disabled. It's not clear how the new provisioning system works. That should still work the same way it always has using `rnodeconf`. Be sure you're passing all lora parameters when you're enabling TNC mode since those are required to init the radio. Also check the display and be sure it's not complaining about the device being un-provisioned, firmware corrupt, etc. All of those things can happen during installation. If all else fails, provide the device logs from init if you'd like me to take a look. --- ## Reply 16 **gdane** · Wed, Jun 10, 2026 8:20 PM **Anonymous** wrote: > I would also be very interested in a bit more documentation about how the new features work. <3 Baptism by fire unfortunately is all that's available at the moment ;-) --- ## Reply 17 **Anonymous** · Mon, Jun 15, 2026 10:22 PM **gdane** wrote: > **Anonymous** wrote: > > I would also be very interested in a bit more documentation about how the new features work. &lt;3 > > Baptism by fire unfortunately is all that's available at the moment ;-) And it was worth it! Its the first time I finally tried microreticulum, and the new management console is amazing! You really should include some screenshots of all the things you can configure and check out to get people a bit excited :) --- ## Reply 18 **Anonymous** · Mon, Jun 15, 2026 10:41 PM One thing I noticed is that as soon as I set the LoRa interface to AP it would not announce its own nomadnet site. Thats probably not intended, AP mode should only block announce propagation, not your own announces? --- ## Reply 19 **daylight-hub** · Mon, Jun 15, 2026 11:41 PM So, the last microReticulum firmware for the Heltec V4 that I was able to flash using Liam Cottle's RNode flasher was 1.86.1. When I try to flash 1.86.2 or 1.86.3 using the flasher it shows up as missing config. --- ## Reply 20 **Anonymous** · Thu, Jun 18, 2026 5:32 PM @gdane can you maybe help me understand how the remote management feature work? If i connect via nomadnet I can see it recognizes my identity that I put into the remote management field in the web console. But it seems that all I can do there is check its metrics and configurarion, no way to edit anything. Is there a way to also configure the node via reticulum? I didnt find it. --- ## Reply 21 **x2tyfi** · Fri, Jun 19, 2026 3:48 PM @gdane Thanks for the work you're doing on this. Any plans for microReticulum nodes to support `discoverble=yes` so that they appear on maps? I'd love to see the public RNS LoRa network grow over time. But its hard to show growth due to standalone LoRa nodes being invisible. --- ## Reply 22 **gdane** · Fri, Jun 19, 2026 3:53 PM **Anonymous** wrote: > One thing I noticed is that as soon as I set the LoRa interface to AP it would not announce its own nomadnet site. Thats probably not intended, AP mode should only block announce propagation, not your own announces? That's a case I haven't tested, but it *should* behave the same as Python RNS. If you want to DM me some logs I'll take a look. --- ## Reply 23 **gdane** · Fri, Jun 19, 2026 3:57 PM **daylight-hub** wrote: > So, the last microReticulum firmware for the Heltec V4 that I was able to flash using Liam Cottle's RNode flasher was 1.86.1. When I try to flash 1.86.2 or 1.86.3 using the flasher it shows up as missing config. That is odd that you could flash 1.86.1 but not 1.86.3. The amount of spurious out-of-frame logging is much less on rev 3 than on rev 1 so it should be less likely to hose the initial provisioning. I know there's a bit more work I need to do silence all of the spurious logs or move them into KISS framing. I'll make this a point before I release rev 4 and hopefully that will resolve the install issue. BTW, did you try manually provisioning after install with rnodeconf, and if so any trouble with that? --- ## Reply 24 **gdane** · Fri, Jun 19, 2026 4:09 PM **Anonymous** wrote: > @gdane can you maybe help me understand how the remote management feature work? If i connect via nomadnet I can see it recognizes my identity that I put into the remote management field in the web console. But it seems that all I can do there is check its metrics and configurarion, no way to edit anything. Is there a way to also configure the node via reticulum? I didnt find it. Three things to know here: First, the nomadnet page is currently only informational and was intended as more of a placeholder for a legitimate provisioning and monitoring interface. So I don't really plan on extending it. Ultimately I plan to make it just a general page server that will server user-configured content instead of transport node stats. Second, there *is* an existing legitimate provisioning and monitoring interface in the form of a web app. It's available in 1.86.3 but you have to either download it from the repo or run from the public url I have made available [RNode Console](https://attermann.github.io/rnode_console/). This (very experimental) interface exposes both rnodeconf-type config and microReticulum transport node config and metrics, as well as logging. Lastly, the console web app does not yet support configuration over RNS, but it's coming. It's actually in the final phases of testing and refining now. It will also be a feature in 1.86.4 so stay tuned! --- ## Reply 25 **gdane** · Fri, Jun 19, 2026 4:11 PM **x2tyfi** wrote: > @gdane Thanks for the work you're doing on this. Any plans for microReticulum nodes to support `discoverble=yes` so that they appear on maps? > > I'd love to see the public RNS LoRa network grow over time. But its hard to show growth due to standalone LoRa nodes being invisible. It's not on my radar, but it's a good idea. I'll look into the lift required. Likely won't be in the next release but possibly in the following one. --- ## Reply 26 **Anonymous** · Sat, Jun 20, 2026 12:48 PM **gdane** wrote: > **Anonymous** wrote: > > One thing I noticed is that as soon as I set the LoRa interface to AP it would not announce its own nomadnet site. Thats probably not intended, AP mode should only block announce propagation, not your own announces? > > That's a case I haven't tested, but it *should* behave the same as Python RNS. If you want to DM me some logs I'll take a look. Ok, I will. I am a bit unsure when the site is supposed to announce, but I expected at least at bootup? --- ## Reply 27 **Anonymous** · Sat, Jun 20, 2026 1:06 PM **gdane** wrote: > **Anonymous** wrote: > > @gdane can you maybe help me understand how the remote management feature work? If i connect via nomadnet I can see it recognizes my identity that I put into the remote management field in the web console. But it seems that all I can do there is check its metrics and configurarion, no way to edit anything. Is there a way to also configure the node via reticulum? I didnt find it. > > Three things to know here: > > First, the nomadnet page is currently only informational and was intended as more of a placeholder for a legitimate provisioning and monitoring interface. So I don't really plan on extending it. Ultimately I plan to make it just a general page server that will server user-configured content instead of transport node stats. > > Second, there *is* an existing legitimate provisioning and monitoring interface in the form of a web app. It's available in 1.86.3 but you have to either download it from the repo or run from the public url I have made available [RNode Console](https://attermann.github.io/rnode_console/). This (very experimental) interface exposes both rnodeconf-type config and microReticulum transport node config and metrics, as well as logging. > > Lastly, the console web app does not yet support configuration over RNS, but it's coming. It's actually in the final phases of testing and refining now. It will also be a feature in 1.86.4 so stay tuned! Amazing, thank you! I discovered the console. Thats why I was wondering what the "remote management" checkbox was actually doing, and what the identities I could enter for it were for. The nomadnet site needed it set for me to get a look at the mettics, thats why I thought its maybe connected. Management over reticulum would be so nice, happy to wait for it, thank you! ---