nanowizz

I ran into that problem when I was querying at 15 second intervals. I got a reject code saying requests too frequent. I backed off to ~30 seconds and now I can go for days with no issues. I just get occasional system crashes with Error 104 and 103 which are network faults. I was able to trap these and restart the code making the API get request again. Just once in a while, the code will get this Error 103 consistently on every request after the restart. So I had to resort to rebooting the system to continue running the program. Fortunately, this can all be done within my Micropython code.

Thank you for the pointers.

I am looking to connect to the developers of the Ecobee API interface. I am having issues with temperature sensor data retrieved through their API interface. Not sure if this is the right place. If not, would highly appreciate a helping hand to point me to the right way. Their we site at developer.ecobee.com provides no link to connect with them except for legal issues. I have an Ecobee Thermostat for my HVAC system and I am developing Micropython code on a Raspberry PICO W to control my ceiling fan to match the fan in my furnace to help distribute the heat in the house. I use the built-in WiFi interface in the PICO W to access the Ecobee API server to monitor the status of my furnace. The Ecobee Thermostat updates the server every 3 minutes. I have succeeded in getting my system working. But I had to resort to various tactics to recover from the many HTTP faults that randomly arises on the API get requests that cause the Micropython system to crash. The most extreme is Exception Error 103 which can turn sticky, meaning the system gets stuck into a state where every API get request crashes with this error. I had to resort to rebooting the whole system to get thing running again. A second issue I have has to do with the values I get when querying the temperature sensors. The temperature values jumps up and down by over 1 degree within seconds. I talked to Ecobee tech support and they directed me to download the data from beestat.io. That data matches the bottom of my jumpy data, but leads it by up to 10 minutes. Ecobee tech support was not able to help with API issues. I have attached a screen shot of my Excel chart showing the data I read from the API and well as data downloaded from beestat.io. Sure like to understand why the data read from the API interface jumps up and down like that.