Monitoring telemetry isn't pushed live; it's synced from Texture on a recurring Inngest cron job (monitoring-texture-sync-cron in apps/web/src/inngest/monitoring/texture-sync.ts), currently dispatched hourly (cron: "0 * * * *"; a code comment there notes the job previously polled every 15 minutes before being consolidated to reduce provider round trips). That means a newly connected device, or a change in a device's readings, can take up to about an hour to show up, not instantly.

TODO(owner, likely engineering): confirm the current end-to-end staleness bound (cron cadence plus any per-property batching inside the same run) and write the full page from apps/web/src/inngest/monitoring/texture-sync.ts. Cover the two "why does this look stale" cases separately: (1) device connection status (PENDING → CONNECTED, discussed in Your first win) and (2) production/telemetry numbers themselves.