Feature Request: MeshRank MQTT support #14

New Issue

2026-10-05T01:52:36+02:00

adam commented

2026-10-05 01:52:36 +02:00

In much the same way as your supporting LetsMesh, it would also be great to have support for MeshRank.

The MQTT for LetsMesh operates on a different topic compared to LetsMesh so isn't a drop in replacement, instead needing an alternate topic setup meshrank/uplink/B1829EDBC6C8FFA8F2496C7667B8EB80/{PUBLIC_KEY}/packets

as far as i can see in their notes, that should be all that's needed to support them, but i'm happy to test anything on my system if it helps development.

In much the same way as your supporting LetsMesh, it would also be great to have support for [MeshRank](https://meshrank.net/). The MQTT for LetsMesh operates on a different topic compared to LetsMesh so isn't a drop in replacement, instead needing an alternate topic setup `meshrank/uplink/B1829EDBC6C8FFA8F2496C7667B8EB80/{PUBLIC_KEY}/packets` as far as i can see in their notes, that should be all that's needed to support them, but i'm happy to test anything on my system if it helps development.

adam closed this issue

2026-10-05 01:52:36 +02:00

adam commented

2026-10-05 01:52:37 +02:00

It was a good chance to expand the community coverage too, and now we should be a lot friendlier to other MQTT collectors and be basically sorta parity with mesh2mqtt.

I can see my implementation with packets flowing into the meshrank nursery :)

It was a good chance to expand the community coverage too, and now we should be a lot friendlier to other MQTT collectors and be basically sorta parity with mesh2mqtt. I can see my implementation with packets flowing into the meshrank nursery :)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#14