Repository navigation
Feature Request: Custom Bluetooth Name #1243
Description
Change Bluetooth Device Name
Current Config displays "MeshCore - </Device ID/>" where "Meshcore" cannot be removed
Change
Additional Bluetooth Name Field (if possible) so that BT name does not have to be the same as the user identity.
IF </Custom Name/> contains data
THEN BT Name = </Custom Name/>
ELSE BT Name = "Meshcore - </Standard ID/Hex Mash/>"
Reacted by Andreas Kolata, logiczny, Arne Keller, Justin, Yves Blatti, Slava I. Maslennikov, Thibault VINCENT, Ander Punnar and Kyle Boyle
Activity
inversenebula commentedon Dec 19, 2025
Wholeheartedly support this necessary privacy improvement. In some environments it is really not advisable to be announcing the nature of your Bluetooth device to anyone within scanning range. Doing so should be a choice, not forced.
NinjaJake86 commentedon Mar 19, 2026
+1 from me on this, me and my wife both have MeshCore devices and it would be nice to distinguish between the two
basiccode12 commentedon Mar 19, 2026
Im working on a firmware editor and flasher, its still green but this might be a solution for you. https://github.com/basiccode12/MeshCore-Firmware-Editor-and-Flasher
NinjaJake86 commentedon Mar 20, 2026
Looks good! Actually realised that once you set the identity on the app, if you reboot the device and then forget and re add the device it then shows up with the identity in the Bluetooth name so that works fine for me! Thanks though, will take a look at the firmware flasher!
github-actions commentedon Jul 14, 2026
This issue is stale because it has been open for 60 days with no activity. Remove the stale label or add a comment if this issue is still relevant, otherwise this issue will automatically close in 7 days.
ColbyBurkett commentedon Aug 14, 2026
Please continue implementation. Amateur radio operators using the devices under ISM rules would still like to use their call sign in their display name without beaconing their home address and real name to all bluetooth recording equipment in the vacinity. This is a privacy rights concern.
4nd3r commentedon Sep 12, 2026
Adding to this: I have multiple companions with the same key(s) and public name, which effectively makes selecting the correct device in the Bluetooth connection list somewhat difficult. Sure, I can add variations to the name, e.g. ², ³, but it would be much easier if I could set the device name myself, separately from the public name.
Or, alternatively, having the device name, by default, in the form of
MeshCore-<RadioHardwareId>would be totally fine too.recrof commentedon Sep 12, 2026
Just a warning about this approach: it's not recommended. if you have companions in different locations handled by different repeaters - your incoming DMs will be delivered randomly to one that "wins" the ACK race to destination. you won't get recipients DMs delivered to all radios from then on until another flood message gets sent.
netrunnereve commentedon Oct 30, 2026
I wonder if this could be added to the companion cli with something like
set bt_name. This would be a workaround for #1769 as well since if the name is too long you can just override it with whatever you like.By the way I just joined the mesh recently and I'm not comfortable using my device with bluetooth on as it means everyone around me can see my name. I did a quick read of the companion code and this doesn't seem that hard to add, I can try to do it if the maintainers are interested.
netrunnereve commentedon Nov 3, 2026
So I just went ahead and submitted a PR #3754 for this as I want this feature for myself and it was easier than I expected.