How to alter "isKeyManuallyVerified"

[roberthadow]

When one of my nodes runs low on power and shuts down, Owner reverts to meshtastic_aaaa and owner_short reverts to aaaa where aaaa is the last four characters of the device MAC address (also AKA). Keys are not lost, but when other devices verfiy keys, the name no longer matches the key. The address becomes untrusted.

Within my own deployment, I'd like to go into each node list and reset "isKeyManuallyVerified". This should be a CLI function. If it already exists, it is not documented.

The Andoid app in its node list indicates whether a node is untrusted. meshtastic --nodes does not include the trust flag.

[ianmcorvidae]

I believe the current only way to manipulate that flag is with the shared-contact interface, which luckily I put up a pull request for the other day: #933

You can see the value of the field using the --show-fields argument that changes which columns are shown by --nodes. The default set of fields is user.longName,user.id,user.shortName,user.hwModel,user.publicKey,user.role,position.latitude,position.longitude,position.altitude,deviceMetrics.batteryLevel,deviceMetrics.channelUtilization,deviceMetrics.airUtilTx,snr,hopsAway,channel,isFavorite,lastHeard,since and isKeyManuallyVerified will add it as a column wherever it's added in the list.

Unrelatedly, however, the loss of the long and short names does not affect other nodes' key verification. They're only looking at the node ID and the key stored for it. If you're seeing communication issues after a reset of this kind, something else is happening.