ricott
commented
11 months ago This is the first time I have heard of this being a problem, but not surprised. A pretty common problem across lots of different Homey apps where refreshing values is based on polling. I have two chargers and thus issue twice the amount of calls to the Easee cloud that you do (assuming you only have one charger?) and still no problems here. Maybe your second integration still is what is adding up to the total so that you are "blocked"? The only thing we see on the screen shots you shared are calls to 124, ie life time energy. This is one of the endpoint that is invoked the least number of times, even if it is one that forces Easee cloud to ping to the charger.
But for sure I know there are thousands of calls made to their cloud services - most don't reach the charger though. I have added a counter to the app. In the Homey mobile app go to settings / Apps / Easee home / settings - here you see a summary since last Homey restart, and stats per endpoint. There will likely be tens of thousands of invocations over time, I have 91k invocations in total since 30th of September (on two chargers).
There are apps like Piggy bank for Homey that controls an Easee charger through the Easee Homey app. The little I have seen in logs from other users tells me that users using this combo of apps issue lots of additional calls to the Easee cloud and the charger. Haven't heard of them being locked out though.
To identify the homey app when calling the Easee cloud the app sets the User-Agent header field to homey-no.easee/<version of the Easee app>. This is what was agreed with the Easee developers in their slack channel, the pyeasee home assistant app does the same.
If this was a common a problem I assume they would reach out to me on the slack channel where we from time to time interact. They know I'm the developer of the Easee homey app and there are not many third party app developers in the slack channel. They have also in the past created tickets for me here on GitHub.
When did the problem start to appear? Is it constant, ie happens all the time? Have you tried disabling one integration and checked if the problem persists?
Can this be changed to something less frequent like once per hour (which would still mean short of 1000 requests/month), or even better, be turned of completely and instead have a flow-card for this?
Of course, most things are possible to change. I fail to see how one API call each 10 minutes can be a problem though. There are other endpoints being invoked 20 times during those 10 minutes. I can post a question in the slack channel and see what they tell me.
rikardlundgren
The Easee cloud freezes and is unable to receive more requests due to excessive polling from this Homey Easee app. I've received logs from Easees dev team showing there is a poll from this app every ten minutes requesting the charger(s) lifetime energy continuously. This means on average 730.5h/month x 6 requests/hour = 4383 requests monthly.
Can this be changed to something less frequent like once per hour (which would still mean short of 1000 requests/month), or even better, be turned of completely and instead have a flow-card for this?
Once the cloud stopped accepting further inputs I'm not able to use even the Easees own android app to give inputs. Only output, data from the charger, is sent back to me.
This also means that the only way to start charging is if you already have set it up to start whenever a car is connected or if you have a physical NFC tag that you have already set up to work locally with the charger. To stop charging you have to use the cars functionality for that.
Last but not least the only way to reset this is to either 1. cut the power to the charger for 2 hours so that it disconnects from the Easee cloud long enough for the cloud to initiate a fresh session once you turn the power on again OR 2. Send a ticket to Easee customer support which they will relay to the dev team to initiate a new session trough the backend.
I have two integrations active to my Easee setup, it's this Homey app and a Monta integration. Look at the log 03 and you will clearly see when the handful number of Monta requests has been sent in. The rest has been confirmed to come from the Homey app.
For info: The support at Easee didn't give me a straight answer on how many requests per unit of time the Easee cloud are supposed to be able to handle and they said that their dev team are working on a potential fix on their side as well.