The node-detail metrics screens crash with IllegalArgumentException: Key "<timestamp>" was already used when a node reports two telemetry or position samples in the same wall-clock second. Several LazyColumns keyed their items on a bare second-resolution timestamp, so same-second samples collide and Compose tears the screen down. Observed on the 2.8.0 internal track (versionCode 29321164); the crash recurs across versions.

🐛 Bug Fixes

• Fixed the duplicate-key crash in the node metrics log lists by giving each LazyColumn item a guaranteed-unique key. The Device, Environment, Power, Air Quality, and Position logs now key on "${time}_$index" (the pattern HostMetricsLog already used) instead of the bare telemetry.time / position.time.
• Fixed the same latent defect in SignalMetrics.LocalStatsEntry (its key was "local_stats_${time}"); it now threads the source-list index so two local-stats samples in the same second can't collide. The sibling PacketEntry keeps its real packet-id key ("packet_${meshPacket.id}").

🛠️ Refactoring & Architecture

• Standardized item keys across the whole feature/node metrics module on two patterns: a real unique id (uuid / packet id) where the list element carries one, and "${time}_$index" for the id-less Telemetry / Position protos. No bare-timestamp keys remain.

Why not a real id everywhere?

The data layer does have a unique id for every one of these lists (each Telemetry is parsed from a MeshLog with a uuid; positions come from a MeshPacket with .id), but those ids are discarded when the rows are mapped to bare protos before reaching the UI state. Threading them through to a single key = { it.uuid } idiom would be a data-model refactor (changing MetricsState's list types and rippling through the use case, charts, and CSV exporters), so it's out of scope for this crash fix and noted as a possible follow-up.

Testing Performed

• ./gradlew spotlessApply spotlessCheck detekt :feature:node:allTests kmpSmokeCompile — all green (722 tests pass; Spotless and detekt clean).
• No test changes: this is a Compose key-stability fix with no behavioral change to the rendered cards or the selection/highlight logic.