Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Documentation issue regarding channel keys #3855

Open
KyleMaas opened this issue May 10, 2024 · 2 comments
Open

[Bug]: Documentation issue regarding channel keys #3855

KyleMaas opened this issue May 10, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@KyleMaas
Copy link

Category

Other

Hardware

Not Applicable

Firmware Version

2.3.6

Description

I'm not sure if this is the correct place to post this, but in the documentation for channel keys on this page:

https://meshtastic.org/docs/configuration/radio/channels/

...it refers to keys as 0, 16, or 32 bytes but doesn't specify how they're supposed to be entered. It has the hex version of the primary default channel ("0x01") right next to a Base64-encoded "AQ==" key but doesn't specify which one you're supposed to use. It took me a bit of trial and error to generate a 32 byte key, because I assumed it was probably hex and saving the channel would fail and not tell me why. Once I figured out I needed to Base64-encode it, everything worked fine, but there's nothing in the interface or the docs as far as I've found which tells you this is the format it expects.

Relevant log output

No response

@garthvh
Copy link
Member

garthvh commented May 11, 2024

The apps are synced up so that you can paste keys between the iOS and android app, not sure any users can really type in base64, not sure how useful it is to put in a warning.

@KyleMaas
Copy link
Author

I did. I wanted to generate my own keys, and was not using the app but the web UI. There was no error message when I used a key that was too long (hex on my first attempt, so more digits). Even just a quick clarification in the docs would have been exceptionally helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants