Temperature readings in Access Assure are event-driven, not collected on a fixed timed interval. Instead, data is sent when something meaningful changes — keeping the platform responsive and efficient. This guide explains how readings flow
through each layer of the system, from the physical device through to the dashboards your team uses.
1. Device and Hub Layer
The hub firmware uses a change-based reporting model. A temperature reading is sent to the backend when either of the following conditions is met:
Significant change detected - The temperature shifts by 0.95 °C or more from the last reported value. This ensures every meaningful environmental change is captured promptly.
Inactivity timeout - If no reading has been sent for 23 hours, a forced report is triggered automatically. This keeps the dashboard graph looking continuous even in stable environments where the temperature barely moves.
Technical note: The 23-hour threshold is stored in firmware as 82,800 seconds. Each sensor's last-reported timestamp is tracked individually, so devices in stable environments are never silently dropped from the graph.
2. Mobile App
The mobile app does not automatically poll for temperature data on a timer. Readings are fetched on demand, in two situations:
When a carer navigates to a service user's profile — the latest sensor readings are loaded immediately.
When the Activity screen is opened — sensor data for that individual is fetched fresh.
Display filter: Readings older than 48 hours are automatically excluded from the mobile view to keep information relevant and current.
3. Web Dashboard
The web dashboard loads temperature trend data on page load and again whenever a different date is selected — not on a recurring background timer. This means the data shown is always a fresh snapshot at the moment of viewing.
4. Analytics and Power BI Dashboards
For commissioners and reporting users, sensor data flows through an analytics pipeline before reaching Power BI. The typical cadence is:
Stage | Frequency | Detail |
Silver layer (micro-batch) | Every 15 minutes | Raw IoT events are processed and structured |
Gold layer (aggregated) | Daily at ~09:30 UTC | Cleaned, enriched data ready for reporting |
Power BI availability | Next day by ~10:00 UTC | End-to-end lag from device event to visible report |
At a Glance — Update Frequency Summary
Layer | When data updates |
Device → Hub → Cloud | On significant change (≥ 0.95 °C), or forced every 23 hours |
Mobile App | On demand — when a carer navigates to a service user or opens the Activity screen |
Web Dashboard | On demand — on page load or when the selected date changes |
Power BI Analytics | Daily batch — typically available by 10:00 UTC the following day |
Questions? If you believe temperature readings are missing or delayed beyond these expected windows, please contact the Access Assure support team. Include the service user ID, device serial, and the date/time range in question.