So, first, the whole team is currently laser focused on some big announcements coming soon. 
Second, the feature that is being discussed in this thread may seem simple at first glance, but as we have played out all the related scenarios across the platform with different types of users (hobbyists, enterprises, everything between) with different types of devices (Photon, P1, Electron, bluz, RedBear Duo, Oak) using different protocols, some hardware made by 
and some not, it has become clear that this feature (1) will be an amazing level-up, and (2) will take multiple sprints worth of work even if the whole team is tackling it together.
Weāve got specs internally and have driven out a lot of the uncertainty. There are plenty of stories in our issue tracker. The broad description of what weāll be building is āsleepy devices as first class citizensā. It will involve making the TTLs on our events meaningful. It will involve paid tiers of historical data usage. It will involve new API endpoints for asynchronously accessing state that changed long after you requested the change. It will involve both event-driven and polling workflows for users to handle the asynchrony.
Weāre definitely excited about these features, and we know you all are going to love them. The current roadmap has us shipping them around October 1. Iām sure I donāt have to tell you that things change, and this is only our current best guess. But there you go folks ā no promises, but a little peek behind the curtain into our roadmap.
from