So I was checking the tomtom dev docs.
Seems like there are 2 types of API requests.
The charging availability is the non-tile request. So we have 2500 requests per day available.
If you want more request you could consider a extra account with a different API key. As you can set the API key per charging point in Homey.
I have 4 EV points in my Homey, each of them having 2 charging options. But apparently it seems I edited the update interval to 120 seconds. That’s why I got the request limit. I changed the update interval to 300 seconds, so I think it will be fixed now. Thanks for the help !
One Q though: the ‘availability’ trigger is a true/false trigger. If the charge point has 10 outlets, it is only triggered from 9->10 (false) and 10>9 (true).
I would be interested in a availability_count_changed triggers. This would reduce the amount of flows I currently have.
I do understand the reasoning behind true/false.
But I am personally more interested in this app if it provides a change in the available outlets count.
It would also be good if a variable could be set/initialized which reflects the total amount of ports.
It would also be good if the name of the EV charger device is available as a parameter.
Maybe a configurable ‘label’ variable can be set by the user when installing a new EV Charger device? But only if Homey does not have already a feature to use the name of the device in a flow. Not sure. Have not investigated yet…
This way I can use a single flow
WHEN [available_outlet_count IS CHANGED)
THEN Simplelog "Available ports changed for [charger_label]: [available]/[total_ports] ports.