Security / Public Key

First, congratulations to the team that maintains Meshtastic.

I have a small network in the city where I live with some devices in remote locations managed by the LoRa network.

After updating the node that manages the others, this node with the new firmware is no longer allowed to manage the others! Maybe because it generated a new public key?

It would be really cool if there was a way to preserve management when updating devices! Today I was no longer able to change the settings of the remote nodes and I will have to visit all the points.

Thank you very much for everyone’s attention.

There was a breaking change. I know it does not help you now but I keep a device on 2.4 and a device on the old app to update my remote node on 2.4.

I have auto update off on all my devices running meshtastic. I wait or will change only one but never all in case I encounter a breaking change. There is a work-around in their documentation I think, using a flag for legacy admin, but not using an app. Security Configuration | Meshtastic

1 Like

Thank you for your attention.

I will probably keep two devices as administrator.