Direct Messaging Key Pair Problem After Configuration Import

[f16flcn]

Hi Community!

I manage a network of around 2-3 dozen Meshtastic devices, configured as clients, repeaters, and routers. These devices are provisioned using a standard configuration files. However, I've noticed the following issue:

Problem with Key Pairs:

When importing the configuration file, the security key pair (private and public) is included in the import file.
As a result, all devices now share the same key pair, causing direct messaging encryption to fail (since all devices use the same keys).
Key Sync Issue:

After upgrading the firmware, even if I generate new keys, the devices do not sync the updated public keys with the network.
I suspect the key synchronization is only triggered when the node name (node ID) changes, but I’m unsure if this is correct or if there’s another trigger for key resync.

Also via the Android App, it does not seem to be possible to set the key pair to blank and reboot the device to generate new keys (as the documentation suggests - maybe only via CLI?).

Questions:
Is there a way to regenerate or resync key pairs across all nodes without:

1. Re-flashing firmware?
   Changing node names (do not believe the Node ID is configurable)?
   Completely re-configuring the devices manually?
   Can I forget the device and will that resync?

2. What triggers key synchronization between nodes, and how can I force a re-sync of public keys for the affected devices (I understand that there a trust implication with this)?

3. Is there a way to modify the configuration import process to exclude the key pairs and allow each device to generate unique keys?

Thank you for any assistance or insights!