rns.recipes

@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.

@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.

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.

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?

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. 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!

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.

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?

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. 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!

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.

For future reference: my understanding of access_point mode was incorrect. It does not only affect announce propagation, it simply blocks all announces, even coming from its own node. Thats how it works in the refernce implementation as well.

**** Announcing major new release of microReticulum ****

Highlights:

• Passive neighbor health detection — Added automatic neighbor-liveness monitoring with targeted probe confirmation for improved route recovery and resilience.
• Expanded remote provisioning and management — Added first-class remote provisioning, grouped configuration commits, remote reboot support, and expanded management metrics.
• Optimized low-bandwidth operation — Added schema caching and compressed provisioning transfers to reduce management traffic, especially for LoRa deployments.
• Improved transport behavior — Added path responsiveness tracking, smarter discovery throttling, replay protection improvements, and filtering of known unresponsive routes.
• Lower memory usage and improved persistence — Migrated additional data structures to microStore and improved allocator usage for constrained embedded systems.
• Enhanced diagnostics and observability — Added transport traffic metrics, RSSI/SNR/Q reporting, neighbor probe metrics, and expanded logging.

Changes, fixes and enhancements are too numerous to mention. See the release notes in the repo for more detail.

microReticulum v0.5.0 Release Notes

**** Also announcing major new release of microReticulum_Firmware ****

Highlights:

• Added WebSocket support for KISS interfaces
• Added RNS transport support in the web console for remote provisioning *
• Expanded provisioning capabilities and metrics
• Reduced remote-management bandwidth usage
• Added native SX1262 board support
• Improved radio reliability and startup behavior
• Reduced firmware footprint through build optimizations

See the release notes in the repo for more detail.

microReticulum_Firmware v1.86.4 Release Notes

• NOTE: Remote management over RNS requires an updated MeshChatX that is not yet publicly available. Stay tuned for an announcement when it is, or see my fork of MeshChatX for a preview.

gdane wrote:

• Added WebSocket support for KISS interfaces

That is actually interesting. Does this mean that rns.js could conceivably use a microreticulum RNode as a Reticulum WebSocket interface? That would bring Reticulum access to a whole new set of client-side web applications.

bergie wrote:

gdane wrote:
> - Added WebSocket support for KISS interfaces

That is actually interesting. Does this mean that rns.js could conceivably use a microreticulum RNode as a Reticulum WebSocket interface? That would bring Reticulum access to a whole new set of client-side web applications.

I'm not familiar with rns.js, but if it implements the same KISS framing over WS that RNS uses over serial, then yes it should work.

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.

I tested this with 1.86.4 and could not reproduce the failure. The web flasher flashed it fine, but it did refuse to "Provision" with the message "Eeprom is already provisioned. You must wipe it to reprovision!" which is expected since it was already provisioned. I tried again after manually erasing the EEPROM and then it did provision fine from the flasher. The "Set Firmware Hash" worked also worked as expected from the flasher.

gdane wrote:

bergie wrote:
> gdane wrote:
> > - Added WebSocket support for KISS interfaces
>
> That is actually interesting. Does this mean that rns.js could conceivably use a microreticulum RNode as a Reticulum WebSocket interface? That would bring Reticulum access to a whole new set of client-side web applications.

I'm not familiar with rns.js, but if it implements the same KISS framing over WS that RNS uses over serial, then yes it should work.

Right now I think it only has a WebSocket interface that treats WS like the regular Reticulum TCP interface. But a WebSocket KISS version ought to be easy to add.

rns.js needs some love anyway.

Hello,

I've been testing this firmware from:

Home -> Microreticulum solar node -> Mobile Rnode

I successfully sent a message Home but unable to open my Home NomadNet site. I was wondering if this firmware is unable to open NomadNet sites and is text message only.

Any help is appreciated.

Anonymous wrote:

Hello,

I've been testing this firmware from:

Home -> Microreticulum solar node -> Mobile Rnode

I successfully sent a message Home but unable to open my Home NomadNet site. I was wondering if this firmware is unable to open NomadNet sites and is text message only.

Any help is appreciated.

I haven't tested the lastest versions, but in general microReticulum is perfectly fine with Nomadnet sites. I had a similar setup working great.

Could be not working for a lot of reasons. What are the rns versions, what LoRa settings do you use? Home <-> Mobile Rnode works fine? What does the setup look in general? What kind of LoRa device are you using?

Anonymous wrote:

Anonymous wrote:
> Hello,
>
> I&#039;ve been testing this firmware from:
>
> Home -&gt; Microreticulum solar node -&gt; Mobile Rnode
>
> I successfully sent a message Home but unable to open my Home NomadNet site. I was wondering if this firmware is unable to open NomadNet sites and is text message only.
>
> Any help is appreciated.

I haven't tested the lastest versions, but in general microReticulum is perfectly fine with Nomadnet sites. I had a similar setup working great.

Could be not working for a lot of reasons. What are the rns versions, what LoRa settings do you use? Home <-> Mobile Rnode works fine? What does the setup look in general? What kind of LoRa device are you using?

Thanks for the reply, I'm thinking it could be the RAK board as its now cutting out every hour or so.
I will test this with a Heltec V4 soon. Good to know that it works with NomadNet sites though.
Thanks

I've just installed the new microreticulum_firmware on a seed xiao esp32s3+sx1262 and exlored via rnode_console, looks great and works fine, also can access the embedded nomanetwork page. however, it doesn't work standalone. As soon as I disconnect it from my laptop and just power it up via usb power supply or batterie, it's off air, no probe destination or nomadnet page reachable anymore. Is that a seed esp32 bug?