Replies: 13 comments
-
After seeing this, I checked my Drives and don't see any like those you're showing. I'd have expected a few (I've been running 1.19-dev and now latest for a couple weeks). Wonder what the difference is. I moved my car yesterday from one side of the driveway to the other. No drive was recorded for that. Anything unique about your short drives? |
Beta Was this translation helpful? Give feedback.
-
I get the same problem, it loggs small trips in my garage. |
Beta Was this translation helpful? Give feedback.
-
I'd say:
|
Beta Was this translation helpful? Give feedback.
-
These are sensible defaults, but should preferably be configurable from settings page. |
Beta Was this translation helpful? Give feedback.
-
I don't think so, these are really short 4-5 meters trip out of the garage. If it can help narrow it down I am on a S with MCU1 and also using TeslaFi. |
Beta Was this translation helpful? Give feedback.
-
I agree, and also I would say the setting should purely be on the report side not on the data storage side. But if that's the case, maybe just editing the chart personally within grafana is a viable option instead? |
Beta Was this translation helpful? Give feedback.
-
I absolutely agree that this should be implemented purely be on the report side. This requires only minimal adjustments to the queries. |
Beta Was this translation helpful? Give feedback.
-
@fetzu BTW you can simply update your grafana and just add to set a min of 1 km or change to however you feel best. He wasn't exaggerating when @adriankumpf said minimal :) All you need to do is go to grafana, click edit from the drop down of the panel to edit /w admin login.
|
Beta Was this translation helpful? Give feedback.
-
Second point should be doable in Grafana, but what about the first one? I think it's a valid point and as was said before, being able to configure it in the Settings page would be great. |
Beta Was this translation helpful? Give feedback.
-
@Dulanic Thank you for the quick tip, but this does not solve the scope of the problem at all: changing how drives are shown on the dashboard will not refrain these "end destinations" to be recorded and shown in other dashboards such as "Locations" or "Drive stats". I understand I could manually change the settings of each of these dashboards in Grafana to show the data the way I want to; but this is not in any way a permanent solution (ie: that modified dashboard might become obsolete with every release). I am in no way proficient nor comfortable enough to code and implement this, so I don't know what exactly could be done in Grafana or not (user-set settings for example), or if this need to be taken care of upstream. |
Beta Was this translation helpful? Give feedback.
-
So I don't have the time to do much with this.,.. but here is a function that would adjust the drives to a custom rounded minute range,..... @MaxG88 Here is a quick function I made and an example of how to use it.,... this would start times to the nearest 30 minutes. I set the where to show specific examples where it would combine the drives. So I don't think we need to change the data storage method as we can do it on the report side. It's also changeable via the function variable. |
Beta Was this translation helpful? Give feedback.
-
@Dulanic Thanks! Looks interesting, I'll have a look at it some time soon. |
Beta Was this translation helpful? Give feedback.
-
I was about to raise an issue about this and found this thread while searching. Is there an interest to implement this feature? With a bit of guidance, I could perhaps have a look and try to implement it. |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
With the new Streaming API, every single and smallest drive is being recorded (which is great!) but it also records/counts the tiniest drives (for example coming in or out of a garage that has to be opened manually) as a drive entry (and destination). This means that for every coming in or out of garage (for example) will generate a single "0km" drive and essentially render some stats (median distance, top destinations...) null and void in the long run.
Describe the solution you'd like
It would be great to have a setting to "not record" (as in "not really count") drives which are within the same geofence (providing of course they meet other time. or distance-based criteria. This setting could be turned on on either the "settings" page or even within the geofence page; with maybe the time- or distance-based being set/customizable by the user.
It would either not count that data as a drive OR merge that data with the preceding or next drive (provided it started/ended within x time-frame).
Describe alternatives you've considered
Might be possible to filter out this data in Grafana in some way (as in "not show up drives less than x km" for example), but I think the data would still pollute other stats (top destinations, median drive length...)
Additional Context
Example of these "0 km" drives.
Beta Was this translation helpful? Give feedback.
All reactions