There is a bug in the meshtastic firmware that sometimes not correctly propagates metadata and resets that in the device.
If we have good node info in the database, e.g., "Freifunk Teufelsberg BOT" (FFTB), do not overwrite the node record in the database with "Meshtastic 9020" (9020) - instead retain the existing value. Also, do not delete position or telemetry data on these records. Just update last heard and update database fields if we have a value. Do not set existing fields to null, never, nowhere.
There is a bug in the meshtastic firmware that sometimes not correctly propagates metadata and resets that in the device.
If we have good node info in the database, e.g., "Freifunk Teufelsberg BOT" (FFTB), do not overwrite the node record in the database with "Meshtastic 9020" (9020) - instead retain the existing value. Also, do not delete position or telemetry data on these records. Just update last heard and update database fields if we have a value. Do not set existing fields to null, never, nowhere.
<!-- github-sync-id:3483601992 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
There is a bug in the meshtastic firmware that sometimes not correctly propagates metadata and resets that in the device.
If we have good node info in the database, e.g., "Freifunk Teufelsberg BOT" (FFTB), do not overwrite the node record in the database with "Meshtastic 9020" (9020) - instead retain the existing value. Also, do not delete position or telemetry data on these records. Just update last heard and update database fields if we have a value. Do not set existing fields to null, never, nowhere.