Is there a known bug in the public keys in v. 2.5.6? After updating I can’t get my admin node to configure my other nodes. I’ve deleted node databases, deleted and reflashed firmware, and deleted and reinstalled the app on my phone without any success. I’m running the android version of the app.
Did u upgrade from 2.4 or from another 2.5 version ? (There was a breaking change from 2.4 to 2.5 so previous admin channels no longer work.)
The node I am remote administrating was originally 2.4, but I did an ‘erase and flash’ when I updated it to 2.5.6, and generated a new key for the admin channel after the update. The node I’m using to admin with shipped with 2.5.2 and I erased and flashed to 2.5.6, and loaded the key generated from the target node.
I don’t know if this will help, but in this video Jonathan Bennett mentions firmware v2.5 eliminates the need for separate admin channels for remote node administration. If you do wish to continue using an admin channel, he said something about enabling a legacy setting somewhere. He also said to record your encryption keys before upgrading the firmware because they’ll be needed for the new admin settings. It’s all vague to me because I’ve never used remote admin (yet).
Thanks that did explain some things I wasn’t aware of. Both devices have the same admin key but it still says “public key unauthorized.” Do both devices have to have the exact same public key or just the same public key they had at first contact?
Few things.
You only need to put the public key of the controlling device into the admin key spot on the controlled device. The controlling device admin key can be empty. If you updated firmware with “clean” install you have changed the keys on that device and it will no longer be able to control the device because its public key is different now. If you are on IOS make certain to go to app settings and toggle on “Administration”. Hope this helps.
1 Like