How can I change the meshtastic broadcast name?

[ottoxgam]

When I check my packets on meshmap, I'm seeing my messages come through as Node 2840053384, when I have all my info set up as seen in the second screenshot. I poked around local.yaml and found the 2840053384 value listed as the node ID. What ramifications would changing this have?

[KMX415]

Hey @ottoxgam, you caught this at a great time. v0.6.7 just shipped and it fixes exactly what you're seeing.

The reason meshmap shows "Node 2840053384" is your Meshpoint was sending packets but never broadcasting a NodeInfo, so nothing on the mesh ever learned the name to attach to that ID. v0.6.7 adds periodic NodeInfo broadcasts (60s after startup, then every 30 min) and locks the node ID across reboots, so meshmap will pick up your configured long/short name on its own.

cd /opt/meshpoint
sudo git pull origin main
sudo systemctl restart meshpoint

Wait a minute, refresh meshmap. If it doesn't show up, give it the full 30 minutes for the second broadcast.

Don't change the node ID. The number is just an opaque ID, not your name. If you swap it now you'll show up as a brand-new ghost node to anyone who already has you in contacts, and you risk colliding with someone else on the mesh. v0.6.7 will tie your real name to the existing ID for you.

Let me know if it's still showing the raw ID after the second cycle.

[ottoxgam]

Works as intended! It seems to have propagated out on the first cycle!

[KMX415]

Great! Yeah it was really cool to see nodeinfo going out on service restart. It's alive!

[ottoxgam]

Interesting thing of note. After sitting for a while, the meshpoint node is now discovering/listing itself in the node list.

[ottoxgam]

Fantastic! I love it when the timing works out. I had assumed it was something like that, as I didn't see any telemetry or nodeinfo packets seen by my other node! I'll pull the update and test shortly. Thanks so much!

…

On Sun, Apr 26, 2026, 08:29 KMX415 ***@***.***> wrote: Hey @ottoxgam <https://github.com/ottoxgam>, you caught this at a great time. v0.6.7 just shipped and it fixes exactly what you're seeing. The reason meshmap shows "Node 2840053384" is your Meshpoint was sending packets but never broadcasting a NodeInfo, so nothing on the mesh ever learned the name to attach to that ID. v0.6.7 adds periodic NodeInfo broadcasts (60s after startup, then every 30 min) and locks the node ID across reboots, so meshmap will pick up your configured long/short name on its own. cd /opt/meshpoint sudo git pull origin main sudo systemctl restart meshpoint Wait a minute, refresh meshmap. If it doesn't show up, give it the full 30 minutes for the second broadcast. Don't change the node ID. The number is just an opaque ID, not your name. If you swap it now you'll show up as a brand-new ghost node to anyone who already has you in contacts, and you risk colliding with someone else on the mesh. v0.6.7 will tie your real name to the existing ID for you. Let me know if it's still showing the raw ID after the second cycle. — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAVO4TFJ3N4BUBSQDFEJ2L4XYTL5AVCNFSM6AAAAACYF7KPPWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNZRHE2TSMQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AAAVO4UFLBLREMKDV5GCGUD4XYTL5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRXGE4TKOJSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/AAAVO4WOMCKZNWME7RQT4TL4XYTL5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRXGE4TKOJSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>