The meshtastic device does not get named by archy.
Steps to Reproduce
Plug in a meshtastic device to the node.
Expected Behavior
Some kind of integration process happens. For now, name the node to match the device name.
Ultimately, I think we need a story: "new device detected, what would you like to do?"
1)Use this as a new device on your archipelago?
->do you wish to wipe and flash or use as configured?
-->What area do you wish to configure for? (lookup of optimum configuration for that region and program device)
->Rename device "archy-x250-exp"?
rename, announce on network
2)Configure a device to give to a friend?"
->do you wish to wipe and flash or use as configured?
-->What area do you wish to configure for? (lookup of optimum configuration for that region and program device)
->Rename device "???"?
rename, announce on network
3)Configure permissions
Actual Behavior
Device connects and is working, but to the world is "meshtastic 6910" or something. It gets confusing.
Archipelago Version
1.7.99-alpha
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
### Description
The meshtastic device does not get named by archy.
### Steps to Reproduce
Plug in a meshtastic device to the node.
### Expected Behavior
Some kind of integration process happens. For now, name the node to match the device name.
Ultimately, I think we need a story: "new device detected, what would you like to do?"
1)Use this as a new device on your archipelago?
->do you wish to wipe and flash or use as configured?
-->What area do you wish to configure for? (lookup of optimum configuration for that region and program device)
->Rename device "archy-x250-exp"?
rename, announce on network
2)Configure a device to give to a friend?"
->do you wish to wipe and flash or use as configured?
-->What area do you wish to configure for? (lookup of optimum configuration for that region and program device)
->Rename device "???"?
rename, announce on network
3)Configure permissions
### Actual Behavior
Device connects and is working, but to the world is "meshtastic 6910" or something. It gets confusing.
### Archipelago Version
1.7.99-alpha
### Hardware
x86_64 (Intel/AMD)
### Relevant Logs
_No response_
### Screenshots
_No response_
chaum
added the roadmap label 2026-08-31 11:29:24 +00:00
Fixed in maintainer-approved source for the next build: canonical ngit proposal https://gitworkshop.dev/nevent1qqsqkzfan4mfdz3pcp2zqud27k29vq3wfn89cw0t7wjtck3cnwdn94spz3mhxue69uhhyetvv9ujumn8d96zuer9wczngrxp, merged once as 8d388fe780 and mirrored exactly to Gitea. Managed Meshtastic radios receive a local set_owner packet; names now fit the firmware UTF-8 byte limits, the stable local user ID is retained, and an unknown node identity cannot report a rename. Mesh status uses the bounded name. Keep-as-configured naming remains preserved. Eighteen isolated Meshtastic tests pass, including actual PTY packet decoding; the full backend suite has 2,975 passes and no failures. The broader suggested device-provisioning feature is outside the current bugs-first scope. Closing the source bug; no new physical radio run, ISO/OTA installation or firmware deployment is claimed.
Fixed in maintainer-approved source for the next build: canonical ngit proposal https://gitworkshop.dev/nevent1qqsqkzfan4mfdz3pcp2zqud27k29vq3wfn89cw0t7wjtck3cnwdn94spz3mhxue69uhhyetvv9ujumn8d96zuer9wczngrxp, merged once as 8d388fe780016038dd45a046c4ff0f26807dc806 and mirrored exactly to Gitea. Managed Meshtastic radios receive a local set_owner packet; names now fit the firmware UTF-8 byte limits, the stable local user ID is retained, and an unknown node identity cannot report a rename. Mesh status uses the bounded name. Keep-as-configured naming remains preserved. Eighteen isolated Meshtastic tests pass, including actual PTY packet decoding; the full backend suite has 2,975 passes and no failures. The broader suggested device-provisioning feature is outside the current bugs-first scope. Closing the source bug; no new physical radio run, ISO/OTA installation or firmware deployment is claimed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
The meshtastic device does not get named by archy.
Steps to Reproduce
Plug in a meshtastic device to the node.
Expected Behavior
Some kind of integration process happens. For now, name the node to match the device name.
Ultimately, I think we need a story: "new device detected, what would you like to do?"
1)Use this as a new device on your archipelago?
->do you wish to wipe and flash or use as configured?
-->What area do you wish to configure for? (lookup of optimum configuration for that region and program device)
->Rename device "archy-x250-exp"?
rename, announce on network
2)Configure a device to give to a friend?"
->do you wish to wipe and flash or use as configured?
-->What area do you wish to configure for? (lookup of optimum configuration for that region and program device)
->Rename device "???"?
rename, announce on network
3)Configure permissions
Actual Behavior
Device connects and is working, but to the world is "meshtastic 6910" or something. It gets confusing.
Archipelago Version
1.7.99-alpha
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
Fixed in maintainer-approved source for the next build: canonical ngit proposal https://gitworkshop.dev/nevent1qqsqkzfan4mfdz3pcp2zqud27k29vq3wfn89cw0t7wjtck3cnwdn94spz3mhxue69uhhyetvv9ujumn8d96zuer9wczngrxp, merged once as
8d388fe780and mirrored exactly to Gitea. Managed Meshtastic radios receive a local set_owner packet; names now fit the firmware UTF-8 byte limits, the stable local user ID is retained, and an unknown node identity cannot report a rename. Mesh status uses the bounded name. Keep-as-configured naming remains preserved. Eighteen isolated Meshtastic tests pass, including actual PTY packet decoding; the full backend suite has 2,975 passes and no failures. The broader suggested device-provisioning feature is outside the current bugs-first scope. Closing the source bug; no new physical radio run, ISO/OTA installation or firmware deployment is claimed.