Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Miles Preference #341

Closed
kinteseay opened this issue Jan 4, 2020 · 4 comments
Closed

Miles Preference #341

kinteseay opened this issue Jan 4, 2020 · 4 comments
Labels
kind:bug Something isn't working

Comments

@kinteseay
Copy link

My mileage and degradation views are showing km and my other tabs are showing miles. My preference is miles, but not sure why the others are showing km. I'm not sure when this started happening or if it always happened. My legend shows miles, but the actual value is km.

@kinteseay kinteseay added the kind:bug Something isn't working label Jan 4, 2020
@Tigwin
Copy link

Tigwin commented Jan 4, 2020

change that on the teslamate preference page (not grafana)

@kinteseay
Copy link
Author

kinteseay commented Jan 4, 2020

change that on the teslamate preference page (not grafana)

I have the preference in teslamate preference. What I'm saying is that the result is not consistent between my grafana pages. Some show miles and a couple show km.

After looking some more, it looks like everywhere that references the odometer, it is listed in km (not using my preferences). But on individual drives and range, it is using my preference of miles

@kinteseay
Copy link
Author

Looks like it's working now. I'm not sure what was going on

@lux4rd0
Copy link

lux4rd0 commented Mar 11, 2020

I just noticed this as well - and it's only in one place. If you're on the "Drives" page and the click down into of of the drives by the date link, it seems to be picking up "&var-temp_unit=C&var-length_unit=km" from somewhere even though I have it set to F and mi. Reloading that page with the parameter changes showed it correctly for me. I just haven't dug deeper into where the aliases are being dropped. :)

Edit: it's the same drilling down from the "Trip" page as well... ahhhh - and yeah. See that this is similar to the issue listed here: #431 (I came to this page via a google search...)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants