Okay, dug into the Ecobee APIs.
The good news is that there is data that tells which stage was running (energized) in the 5 minute interval. The bad news is that I’ll have to request an extra object set to get at that data, thus dumping a whole lot more data through the API calls.
Here is the blurb from the API (https://www.ecobee.com/home/developer/api/documentation/v1/objects/ExtendedRuntime.shtml):
The last three 5 minute HVAC Mode reading. These values indicate which stage was energized in the 5 minute interval. Values: heatStage10n, heatStage20n, heatStage30n, heatOff, compressorCoolStage10n, compressorCoolStage20n, compressorCoolOff, compressorHeatStage10n, compressorHeatStage20n, compressorHeatOff, economyCycle.
Let me look at it with fresh eyes, not sure if I’ll be able to do it over this weekend though. I’m really trying to focus on getting my current development branch ready for some Beta testing. I’m very hopeful that this version will clear up the majority of the connectivity (disconnectivity) issues we’ve all had (some worse than others).
My test stub has been running without any failures since the 16th (of Feb). And my full implementation has been running since yesterday (harder to get a true count there since I often cause failures just from the development work).
Could you perhaps put in a feature request in the Issues page on Github for me? Then I’ll remember to come back to this?