💡 Unified sensor-inspection timeline with automated correlation highlights

[github-actions[bot]]

Summary

Merge BLE sensor telemetry data (weight, temperature, humidity) with inspection notes, photos, and voice logs into a single chronological hive timeline that automatically highlights correlations between sensor readings and observed conditions. Weather API data overlays provide context even without physical sensors. Industry observers identify this as one of three emerging differentiators in 2026 beekeeping apps.

Market Signal

HiveSense already integrates BLE sensor data alongside inspection logs and is gaining rapid adoption with offline-first architecture. BroodMinder is moving QueenMinder into their mobile Bees App, expanding from pure hardware into decision support. Industry observers identify "unified sensor+inspection timelines" as one of three emerging differentiators in beekeeping apps for 2026, alongside on-device AI voice and local-only privacy modes.

User Signal

Existing idea #86 (sensor-agnostic ingestion) has 3 comments showing sustained interest in sensor integration. The PRD defines telemetry integration as a key architecture pillar (FR35-37). No existing discussion addresses the UX of merging sensor data with inspection records into a single decision-support timeline that highlights automated correlations.

Technical Opportunity

Architecture already defines Pub/Sub topics for telemetry-ingested events and adapter interfaces (ExternalSignal) for external signals. TanStack Query persistent cache can handle time-series sensor data alongside inspection records. The timeline surface can launch with weather API overlays (no hardware needed) and slot in BLE sensor data when the ingestion layer (#86) ships. The domain schema already includes inspections, observations, and media tables — adding a generic timeline_event model unifies these with sensor readings and weather snapshots.

Assessment

Dimension	Score	Rationale
Feasibility	high	Builds on existing schema and adapter patterns; weather overlay needs only OpenWeather API
Impact	high	Creates the decision-context layer that powers recommendations and differentiates from simple inspection logs
Urgency	med	HiveSense momentum means the "unified timeline" UX pattern is becoming table stakes

Adversarial Review

Strongest objection: Requires sensor integration (#86) as a prerequisite. Without sensor data, the timeline is just inspection records with weather overlays — arguably not transformative enough on its own.

Rebuttal: The timeline architecture should be designed sensor-ready from day one, starting with inspection records + weather overlays (available via API, no hardware needed). Sensor data slots in when #86 ships. Even the weather-only version adds decision context no competitor offers in this unified format. The UX pattern also drives adoption of sensor hardware, creating a virtuous loop.

Suggested Next Step

Create a technical spike story defining the timeline data model (events from inspections, sensor readings, weather snapshots) and a wireframe showing the unified per-hive timeline view with correlation highlights.