Before submitting
Hardware
Heltec V3
Connection Type
Serial
Local or Hosted
https://client.meshtastic.org
Firmware Version
2.7.26.54e0d484
Operating System
Ubuntu 24.04.3 LTS
Browser
Chrome 150.0.7871.181
Expected Behavior
At the Node Details popup, click Verify key. Type or paste the device's public key.
Actual Behavior
At the Node Details popup, click Verify key.
The popup is named "Key Verification". The instruction is "Enter the security number shown on W2NJ Mobile BB38's device:"
(1) It is unclear what key is required here, (a) the node public key, (b) the node provate key, or (c) the admin key.
(2) I tried pasting the 51 character public key of the device (base64:thisishowthebase64numberisrepresented123456=" Only the last eleven characters, but not the equal sign, copied into the field.
(3) I tried pasting the 44 character public key. Seven characters, apparently random, appeared.
(4) I tried typing the 51 character public key. Digits only were allowed.
(5) On none of the ten tabs on the device was a secret number shown.
Steps to Reproduce
(1) It is unclear what key is required here, (a) the node public key, (b) the node provate key, or (c) the admin key.
(2) I tried pasting the 51 character public key of the device (base64:thisishowthebase64numberisrepresented123456=" Only the last eleven characters, but not the equal sign, copied into the field.
(3) I tried pasting the 44 character public key. Seven characters, apparently random, appeared.
(4) I tried typing the 51 character public key. Digits only were allowed.
(5) On none of the ten tabs on the device was a secret number shown.
Relevant console output
Screenshots
No response
Additional Context
If the intent is to make this process dependent on reading a number from the device (like BLE pairing), then a key failure on a solar device will require climbing the tower and retrieving the device. Suboptimal.
Before submitting
Hardware
Heltec V3
Connection Type
Serial
Local or Hosted
https://client.meshtastic.org
Firmware Version
2.7.26.54e0d484
Operating System
Ubuntu 24.04.3 LTS
Browser
Chrome 150.0.7871.181
Expected Behavior
At the Node Details popup, click Verify key. Type or paste the device's public key.
Actual Behavior
At the Node Details popup, click Verify key.
The popup is named "Key Verification". The instruction is "Enter the security number shown on W2NJ Mobile BB38's device:"
(1) It is unclear what key is required here, (a) the node public key, (b) the node provate key, or (c) the admin key.
(2) I tried pasting the 51 character public key of the device (base64:thisishowthebase64numberisrepresented123456=" Only the last eleven characters, but not the equal sign, copied into the field.
(3) I tried pasting the 44 character public key. Seven characters, apparently random, appeared.
(4) I tried typing the 51 character public key. Digits only were allowed.
(5) On none of the ten tabs on the device was a secret number shown.
Steps to Reproduce
(1) It is unclear what key is required here, (a) the node public key, (b) the node provate key, or (c) the admin key.
(2) I tried pasting the 51 character public key of the device (base64:thisishowthebase64numberisrepresented123456=" Only the last eleven characters, but not the equal sign, copied into the field.
(3) I tried pasting the 44 character public key. Seven characters, apparently random, appeared.
(4) I tried typing the 51 character public key. Digits only were allowed.
(5) On none of the ten tabs on the device was a secret number shown.
Relevant console output
Screenshots
No response
Additional Context
If the intent is to make this process dependent on reading a number from the device (like BLE pairing), then a key failure on a solar device will require climbing the tower and retrieving the device. Suboptimal.