dougculnane
commented
1 year ago @ fredericdepuydt thanks for raising this issue. I understand what you propose and it might help but I am not 100% sure it will as the API is a bit special.
I too am "controlling the charging behavior based on the excess energy ". However I use the Go-E charger and openhab binding. This allows me to set the amps supplied to the car with a polling interval of under a minute. I think the charger end of the connection is a better way to control the power supplied.
The Renault API only allows an on / off type control, so it might be better to invest in a amp level of control on your charging system.
Hi
Currently I'm struggling with the Kamereon Quota limit and my configured refresh interval. (Getting a lot of HTTP 429 Errors) Not all my renault data requires the same refresh interval, and even some data I do not require at all.
Currently the Addon refreshes all API endpoints with the same refresh interval:
Could the Renault Addon be split up in separate 'things' for the bridge (API Parameters) and endpoints (Group of Channels per Endpoint) for which you can set different refresh intervals depending on your setup.
So users can themselves select the endpoints they require, and the refresh intervals for each endpoint.
My specific usecase:
I'm controlling the charging behavior based on the excess energy that's available on my solar panels. Both Location, PlugStatus and BatteryLevel are taken in consideration as to whether the car should charge or not.
But I'm currently not doing anything with the HVAC Status for instance. Also the Cockpit information isn't relevant but would be interesting to have on a much slower refresh rate.
Kind regards, Frederic Depuydt