-
Notifications
You must be signed in to change notification settings - Fork 12
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
Visible Info Before a NodeInfo Arrives #16
Comments
ianmcorvidae
added a commit
to ianmcorvidae/meshtastic-python
that referenced
this issue
May 30, 2024
ianmcorvidae
added a commit
to meshtastic/python
that referenced
this issue
May 30, 2024
Initialize unknown nodes more in line with meshtastic/design#16; show hardware in --nodes
geeksville
pushed a commit
to geeksville/Meshtastic-python
that referenced
this issue
Jun 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we get a packet from a nodenum that is not in the client database we should create starting data in a consistent way, matching the initial setup in the firmware.
The node num is a UInt32 value representing part of the Mac address, with this data we can generate the BLE name, Default Short and Long Name and user.ID
This is the swift method used to create a user from a node num
The text was updated successfully, but these errors were encountered: