Findings is the list of things that need a person: controllers that have gone dark, units running beyond their learned normal, zones that never reach temperature. Each one says what was seen, how long it has been active and what it is consistent with.
A finding is a sentence, not a code. "No telemetry received for 26 days, more than 24 hours without a heartbeat. Consistent with a prolonged power or network interruption." Critical or warning, filtered by status and severity, with the fleet's comfort history above the list.
Plain-English findingsWhat was seen, how long it has been active, and the likely cause it is consistent with
Fleet historyThe share of running zones within 1°C of setpoint, measured daily over 30 or 90 days
Sites ranked by comfort heldWeighted by how many zone-hours each site actually ran, with a 30-day sparkline, so a busy site is not outranked by a quiet one
A high bar for anomaliesA unit must run beyond its threshold for six consecutive hours before it becomes a finding; a single excursion is a reason to look, not to send someone
Screens show demo data in Nexus iQ.
Zone runtime, heating and cooling share, typical time to temperature and out-of-hours running, for the whole fleet or one site, over 7, 30 or 90 days. Counted from telemetry, not modelled.
Where the hours goZone-hours by mode, heat, cool, fan, auto and dry, counted at 30-second resolution
Time to temperatureStarts, median, the slowest 10%, and how many never got there
Rooms that rarely reach targetWhich zones, on which controller, and how far short they typically fall
Compressor behaviourStarts per unit per day, median run length, and the share of starts seen in a single poll, reported separately rather than dressed up as a short-cycling figure
Screens show demo data in Nexus iQ.
Book a free demo and we will walk through a live fleet with you.
Book a demo