System 28621 has received no Main Temperature (v5) or Extended v7 (Solar Radiation) data at any point today — Live Data table is empty for both fields from 00:00 America/Los_Angeles on 2026-07-18, including after sunrise when insolation should be well above zero.
System 111702, using the identical Ambient Weather App Key/App Key/API Key and identical Weather Device configuration (same device, same field mappings), has received v5 and v7 normally all day with no gaps — and has more concurrent extended-parameter writers than 28621 (v8/v11/v12 from IoTaWatt, v9/v10 from a Backup Switch, in addition to the Weather Device import).
Checked and confirmed identical between both systems:
- Ambient Weather API Test button returns valid live data (tempf, solarradiation present) for the shared credentials
- Weather Device settings (API key, App key, device name, Main Temperature enabled, Extended v7 = Solar Radiation) — identical
- Extended Data label/unit/axis config for v7 — identical
v1–v4 on 28621 continue posting normally via my own REST integration (unrelated to this — that data source is separate from the Weather Device import).
No changes were made to 28621’s Weather Device or Extended Data settings before this started. Can you check whether the scheduled Weather Device import job for system 28621 is running?
Thanks — happy to provide anything else that would help track this down.
[EDIT]
“Screenshots attached: last successful v5/v7 data (07/17 23:55 and 20:30) compared to today’s Live Production table showing no data since midnight (07/18 16:30).”
- 07/17/26 23:55 Live Production (Image 2 from just now) — “Last interval before midnight rollover: Temperature = 85.5F, populating normally.”
- 07/17/26 20:30 Extended Data (Image 1 from just now) — “Solar Radiation also populating normally through the evening on 07/17.”
-
07/18/26 16:30 Live Production (your earlier PVO screenshot) — “Today, System 28621: Temperature column showing ‘-’ for every interval, all day.”
