Thanks for the offer to take quick action on this!
If I may, I would suggest you allow the user to set a time bracket during which the polling frequency slows down. For example, between 11pm and 7am, reduce the API pulls to every several minutes (say 30) instead of every minutes.
This would allow different users to have different times, or no time at all, between which the polling slows down.
Thank you!
I've added in the car_info page toggle switch to enable or disable either the State & Drive logging.
State is Charging, Temperature and other general data being query once every minutes.
Driving is the real time car tracking.
Once you set them both to Off, the system won't try to connect again. If Driving were already in process, then it will continue until it drop connection. Then a car is in idle, that connection drop every 20second or so.
I've wasted WAY too much time trying to get that nice little toggle in there ! Pretty crappy library ! Anyway, that my problem and not giving up when trying to get something working....
There is different kind of data logging... Real time car position, climate, temperature, vehicle state... As far as I know, as long as the CPU is wake up and active for whatever function, doing 2 function at the same time won't cause it to take much more power.
So that mean I need to NOT start streaming until I detect the car start moving, which mean I have to pool the car at certain interval... If I wait too long, you might lose a good part of the beginning of your trip...
So it not just about querying every x number of minutes, it about trying to get the sweet spot that I know if the car is on or off without draining the battery... I got a few idea, but I need to experiment, but it time intensive since I won't really know if the car is really a sleep or not. I would need to have an AMP meter clamp on the 12volt battery to see in real time if itbeing drain or not.. OR wait long time to see my range lower between all my test... Anyway, going to bed now ! GN