Closed nolith closed 2 months ago
todd-herbert
on discord pointed out to some relevant piece of code in the protobuf.
A few things:
-ESSID
suffix (I think it's from X.25 specs) to identify different devices.Can we relax a bit the protobuf requirements for the callsign? In the end it goes into the long name that is 39 bytes
The python api needs to be upgraded to set the ham parameters values properly. There is some overhead on protobufs of a byte or two.
The app has been updated to only allow 6 characters, the size restriction is on the protobufs 8bytes is probably correct for 6 characters
Firmware Version
v2.3.13.83f5ba0
What did you do?
I have a 433Mhz node with Call Sign set to IU5BON, after finding other hamradio nodes with a long name in the format CALLSIGN-ESSID I decided to change mine to IU5BON-9 to better identofy multiple nodes on the same callsign.
The app allowed me to save the configuration but nothing changed.
Expected Behavior
The Call Sign, and node long name should change
Current Behavior
I connected the serial port and this is what I found while sending my modified callsign
So I tested with the CLI
But the device didn't upgrade its config, with
meshtastic --info
I still getOwner: IU5BON (5BON)
.As a last attempt I did
meshtastic --set-owner IU5BON-9
that worked but removed my IsLicensed flag as the iOS App was no longer showing me as an ham. At this point I didmeshtastic --set-ham IU5BON-9
and now everything is ok.Now the iOS app shows the right information but I am afraid of doing any config change from my phone as it may revert/not-work.
Participation
Additional comments
Overall I found very confusing that setting the ham radio mode is not consistent across all the clients.
As another datapoint, a friend of mine did the same stuff on Android and was able to set the nodename as CALLSIGN-15 but he eneded up with a default channel with encryption that was surprising as the default encription key was automatically removed from me using both iOS and the CLI.