meshtastic-signal-bridge is a headless bridge that relays messages between Meshtastic nodes and a Signal group chat, enabling Meshtastic users to communicate with connected Signal users. The purpose is to facilitate communication between people when cellular/wireless networks are unreliable or disrupted. It also enables offline, “Airplane-mode” communication (except BLE) for privacy conscious individuals.

This project exists to:

• Enable backup communication in times of urgency

• Work with existing community mesh networks and Signal communities

• Be easy enough to run that any ametuer Meshtastic user can get started quickly

The bridge program supports:

• Full 2-way message relay between Meshtastic and Signal

• Commands that can be used by Meshtastic users to get help, change modes, and test their connection to the bridge

• Full onboarding that helps the bridge user set up their bridge quickly and easily

• Informative logging that does not divulge any personal message content

Bridge requirements:

• You must possess a basic understanding of Meshtastic, node configuration, and node placement

• The host system must be in a location that is connectable to a broader, city-wide mesh

• A USB-connected Meshtastic node (e.g. T1000-E)

• A Signal account with a Signal group

Read the Github repo for additional details and instructions.

Github repo

🚨 WEE WOO 🚨: meshtastic-signal-bridge is NOT end-to-end encrypted. Running the bridge will introduce potential vulnerability in the secure communication chain. Run at your own risk. Learn more

Any info on why this wasn't accepted? I couldn't get a reply from anyone. My template didn't ever end up showing up under Statistics > Invalid / Template Errors either.

Edited April 14Apr 14 by ccwod

Did you fill in the form?

You've set privileged=true, that's most likely unnecessarily dangerous for this purpose and would be rejected if there's no good reason.

Registry field seems incorrect too.

Edited April 14Apr 14 by Kilrah

@Kilrah I see. I originally thought Privileged was necessary to access the (required) USB device, but I've just double checked on my host and it seems it is not, so that's something I'll update. What is incorrect about the registry field? Should I not use https://ghcr.io? In any case, I still haven't received admin feedback either way about the template, so I'm wondering if it got overlooked.

51 minutes ago, ccwod said:

Should I not use https://ghcr.io

Should be the full URL, usually the dockerhub page, for ghcr something like

https://github.com/ccwod/meshtastic-signal-bridge/pkgs/container/meshtastic-signal-bridge

Probably not what blocks it but priviledged could have. Communication around this is known to not be great, but a better place to ask about it is probably in the Community Apps thread.