[Feature Request]: Get details on `nodeTelemetryMap`

[oscgonfer]

Platform

Cross-Platform

Description

Based on #398

An additional very important aspect to consider: meshtastic is measurement first, whereas smartcitizen is sensor first. This means: when we receive a payload from meshtastic, we get the following decoded protobuf:

decoded {
  portnum: TELEMETRY_APP
  payload: "time: 1751476649 environment_metrics {   temperature: 31.63   relative_humidity: 67.63 }"
}

---

decoded {
  portnum: TELEMETRY_APP
  payload: "time: 1751476649 air_quality_metrics {   co2: 747   co2_temperature: 28.4981308   co2_humidity: 75.2849655 }"
}

This means that we do not know what sensor is behind that co2 or temperature. I am not sure this will be something that could be changed in the payload itself, as it would break protobufs.

However, we could consider having a user interface in the onboarding for users to define what the device is sending. For instance, the user could select something similar to the old kit blueprints, which would effectively make a mapping for that device in the components, or if not available, they could select a list of sensors and associate it to the measurements received.

To be discussed further, but important for next week, as we already have the potential issue with different types of co2 sensors, which would be interesting to consider. @timcowlishaw @pral2a

More options come to this particular aspect. We can request this information via admin request package either from phone, BLE or OTA if we know the admin keys. Our platform could send these requests (if not done manually by the user) to populate that map. This would mean handling admin requests and could potentially be linked to #9