Yup, it looks like the first data gap expanded in the “earlier” direction when you viewed the data the second time. My speculation is that Sense has a whole storage hierarchy for data views:
- Raw data generated at the probe/monitor (1 microsecond resolution for some of the measurements)
- Slightly processed data that is sent back to the mothership that is stored and used for identification and training (who knows how they compress and extract data features - resolution somewhere between 1 microsecond and 1/2 second). But this includes separate data for each house leg, plus phase information.
- Realtime data that is sent to our apps from the mothership when we see the moving waveforms and bubbles - 1/2 sec resolution, some computed realtime (Always On, Other bubbles, some identification bubbles), though some people are also reporting data delays in receiving this data.
- Historic display data that is sent to our apps from the mothership when we either:
- are displaying realtime data, but need some additional history to fill out time window
- go back in time and/or change resolution.
- Identification and summary data - rolled up from the historic display data AFAIK. Used for device displays, trends, usage and export.
What we see on our screen in the Power Meter is typically a hybrid of Realtime data and Historic display data. Seems like there are situations where the Realtime data in the display doesn’t get committed to the Historic display (I think one Sense guy called with the “history timeline”), even though it is there on your screen. Have also heard that one of the challenges in solving this one at Sense is that the slightly processed rawish data from our Senses is just fine at the mothership, but the “historic timeline” has gaps (this is all hints and speculation until Sense formally tells us something).