Somebody runs a working Microreticulum node?

[cascafico]

I tried to make an Heltec V3 device repeating messages. White LED blinked, but no devices were able to receive from repeater. I made a short survey in local community and it seems nobody had success in make Microreticulum working.

Please, if you have a working Microreticulum, post device models and firmware versions: it would be of great help in solving communications in hilly scenarios.

[attermann]

Hey @cascafico. Apologies for the late reply. Been on hiatus from this project. Many updates have been made in support of RNS 1.0 so I suggest you install the latest 1.85 firmware from this repo and try again. Would love to hear back about your experience.

[cascafico]

I tried as soon as it surfaced here...
Hey: no need to apologies :-)

Scenario:

rnode in rather radio isolated room
tcp & rnode interfaces, transport enabled

microReticulum 1.85 heltecV3 on the roof, only powered

Had a walk with Tlorat3s3; I was able to get announces in Sideband, RSSI values consistent with roof device.

Sadly, every attempt to converse failed.

I'm sorry I was able to perform just empirical test. Hope it could be useful.

[attermann]

Thanks for the feedback. If you get a chance and can capture logs from the serial output on the uR device, that could be very helpful to troubleshoot. I hope to have time to do similar test in the near future.

[slack-t]

I forked this repo and updated the code to support the Heltec Wireless Stick Lite v3 (WSLv3): https://github.com/slack-t/microReticulum_Firmware

if you have the hardware check it out. It wasn't very hard as it's very similar to the Heltec V3 but without the display... I'm too new to this, so I'd appreciate if someone could point me into the right direction to make rnodeconf stop shouting at me that this might be a malicious firmware...

[attermann]

RNode is really fickle (overkill imo) about firmware security. Full support for a new device would require also updating “rnodeconf” to know about the new device and assign product codes, etc. That said, if it’s close enough to a Heltec V3 then I suggest just using that target with whatever changes you need. Also since it’s not one of the few boards that I personally test with, I haven’t added provisioning support to PlatformIO for it yet. You’ll need to add it to the “extra_scripts.py” in the “device _provision” function where you see the case switch for other boards. The values being passed to rnodeconf there (product, model) can be found in defines in the firmware code,

…

On Tue, Mar 24, 2026 at 8:59 AM slack-t ***@***.***> wrote: I forked this repo and updated the code to support the Heltec Wireless Stick Lite v3 (WSLv3): https://github.com/slack-t/microReticulum_Firmware if you have the hardware check it out. It wasn't very hard as it's very similar to the Heltec V3 but without the display... I'm too new to this, so I'd appreciate if someone could point me into the right direction to make rnodeconf stop shouting at me that this might be a malicious firmware... — Reply to this email directly, view it on GitHub <#5?email_source=notifications&email_token=ACXDLGNN5RQJY6S6CWQMH3D4SKPGXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRSHE2DQOJWUZZGKYLTN5XKY43UMF2GKX3DNBQW4Z3FUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16294896>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXDLGKW4QU7OXPUGCLN6F34SKPGXAVCNFSM6AAAAACV6O64FSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMRZGQ4DSNQ> . You are receiving this because you modified the open/close state.Message ID: <attermann/microReticulum_Firmware/repo-discussions/5/comments/16294896@ github.com>