First of all, thank you. I love Beestat and use it daily.
I just recently started playing with the API and writing some custom dashboards to consolidate my three Ecobee thermostats.
I have one Ecobee Premium and two Ecobee Enhanced thermostats. The Premium responds to runtime_thermostat.read API calls with the expected information and works great. Both of the Enhanced units respond with
{
"success": true
"data": []
}
The response is over the same period of time that responds successfully with populated data for the Premium model. The only difference in the API call is the thermostat_id.
I’m assuming it has nothing to do with the Ecobee model. Can anyone give me any pointers on what I’m doing wrong?
This morning I went to copy the API calls I was making and send you a PM…and the JSON returns are no longer empty. Not only that, but they have data for the period that was previously blank.
So, long-story-short, it appears to be working. I’ll report back if I ever see the anomalous behavior again and will try to send you a PM during the period when it is occurring.
Actually, I have another question as I look at it more closely - and maybe this would also explain the empty returns I was seeing previously. I’ve seen mentioned that Beestat queries the Ecobee API every 5 minutes with some other data occurring ~15 minutes as pushes from Ecobee (not sure if that is all still true). Is that true for ALL devices?
I’m seeing two of my thermostats are updated to within about 20 minutes of real-time based on the timestamp in the latest API pull of runtime_thermostat.read.
The same API call with my third thermostat has the latest data lagging behind by nearly 5 hours, however. If there had been a similar large gap (12+ hours) and I was not looking backwards across the day boundary, then I could have missed that my previous empty JSON return was just due to stale data.
If you want to take a look, let me know and I can provide still provide you with one of the serial numbers.