You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe there is a limitation that prevents this, but it would be super handy to know on/off events. Right now, I get odometer readings whenever the car turns off. What can't be reasoned out of that data is how long the car was running or what its average speed was. Even simple boolean records of on and off times would help amend this.
In an even more ideal world, all data would get recorded both when the car turns off and on, though I expect this is even more a limitation on Subaru's end. As it stands now, its easy to create a scenario where, on a long journey, the car gets turned off to refuel, then runs another ~300 miles before stopping to refuel again. In that scenario, you would get two reports of low "distance to empty", instead of a more accurate saw tooth shape.
The text was updated successfully, but these errors were encountered:
This is completely due to the limitations in Subaru, if your poll for lights, or location (the acctual locate button) it can trigger an update with ignition = on... but don't get your hopes up also doing it too often might get your account suspended...
What I use to tell the car is likely running is Battery Voltage, I also have a automation if my battery drops to low to remote_start the car so it doesn't die, still doesn't tell you mileage or anything but a better idea if the car is running.
Maybe there is a limitation that prevents this, but it would be super handy to know on/off events. Right now, I get odometer readings whenever the car turns off. What can't be reasoned out of that data is how long the car was running or what its average speed was. Even simple boolean records of on and off times would help amend this.
In an even more ideal world, all data would get recorded both when the car turns off and on, though I expect this is even more a limitation on Subaru's end. As it stands now, its easy to create a scenario where, on a long journey, the car gets turned off to refuel, then runs another ~300 miles before stopping to refuel again. In that scenario, you would get two reports of low "distance to empty", instead of a more accurate saw tooth shape.
The text was updated successfully, but these errors were encountered: