I used to believe computers were predictable (admittedly a very long time ago.

However, my recent endeavour to integrate Reticulum and Meshtastic on a Raspberry Pi Zero 2W has proven to be quite an adventure.

Initially, I discovered that I could send and receive messages from the Raspberry Pi to my Android phone using Reticulum, but not vice versa (they somehow never went through). Detaching the Meshtastic device resolved the issue. Tbh I did see some complaints about USB events on the installation.

Next, I connected the Meshtastic device to a different port on the USB hub, only to find that the Reticulum device was now no longer recognized (the USB port couldn't be opened).

After swapping both the OTG cable and the hub, I tried again, and once more, the Meshtastic Lilygo conflicted with the Heltec RNode. The solution was to relocate the Meshtastic device to another port on the hub (which I have never had problems with before)...

Anyway, good morning to all! #meshtastic #reticulum

Reply to this note

Please Login to reply.

Discussion

GM

I do not believe a meshtastic device can talk to a reticulum device. I could be wrong though.

Love to see you tinkering with this!

They can't. I just figure that'd it'd be cool to have both running on the same machine (on separate frequencies), since they have very different approaches to the mesh idea.

This is a very good read by Reticulum's main developer.

Or, why we need End-to-End Connectivity, not just End-to-End Encryption.

https://unsigned.io/articles/2022_04_02_From_Here_to_There.html