8000 Volvo On Call not loading · Issue #3775 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Volvo On Call not loading #3775

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom
Closed
timh77 opened this issue Oct 9, 2016 · 8 comments
Closed

Volvo On Call not loading #3775

timh77 opened this issue Oct 9, 2016 · 8 comments

Comments

@timh77
Copy link
timh77 commented Oct 9, 2016 •
edited by fabaff
Loading

Home Assistant release (hass --version):
0.30.1
Python release (python3 --version):
3.4
Component/platform:
volvooncall
Description of problem:
Doesn't load my car's information
Problem-relevant configuration.yaml entries and steps to reproduce:

device_tracker:
- platform: volvooncall
  username: !secret volvouser
  password: !secret volvopassword

While loading the HASS service I see following in the log. Not sure how to read this, but it seems it can't handle my registration number (JN-959-L).

Traceback (if applicable):

okt 09 12:00:00 raspberrypi hass[30185]: func(*args)
okt 09 12:00:00 raspberrypi hass[30185]: File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/device_tracker/volvooncall.py", line 76, in update
okt 09 12:00:00 raspberrypi hass[30185]: range=status["distanceToEmpty"]))
okt 09 12:00:00 raspberrypi hass[30185]: File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/device_tracker/__init__.py", line 223, in see
okt 09 12:00:00 raspberrypi hass[30185]: dev_id = cv.slug(str(dev_id).lower())
okt 09 12:00:00 raspberrypi hass[30185]: File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/config_validation.py", line 224, in slug
okt 09 12:00:00 raspberrypi hass[30185]: raise vol.Invalid('invalid slug {} (try {})'.format(value, slg))
okt 09 12:00:00 raspberrypi hass[30185]: voluptuous.error.Invalid: invalid slug volvo_jn-959-l (try volvo_jn959l)
@fabaff fabaff changed the title Volvo On Call not Volvo On Call not loading Oct 9, 2016
@molobrakos
Copy link
Contributor
molobrakos commented Oct 9, 2016 •
edited
Loading

Maybe you can try to apply this change which I think might resolve this?
dev...molobrakos:voc
Please let me know if that resolves it for you (which I think it will), and I will create a pull request.

@timh77
Copy link
Author
timh77 commented Oct 9, 2016 •
edited
Loading

Applied the two changes and it worked fine.

{
  "brake_fluid": "Normal",
  "friendly_name": "JN-959-L V60/2016",
  "fuel": 36,
  "gps_accuracy": 0,
  "latitude": XX.XXXXXXXXXXXXXXXX,
  "longitude": X.XXXXXXXXXXXXXXXX,
  "odometer": 19954465,
  "range": 685,
  "service_warning": "Normal",
  "tank_volume": 68,
  "washer_fluid": "Normal"
}

@molobrakos
Copy link
Contributor

Perfect! Also good to know there are other users of this component. (The VOC server actually gives even more information such as engine, lock and window status which the component currently ignores. I didn't add that because it might have to be tested due to not being available on all vehicles.)

@molobrakos molobrakos mentioned this issue Oct 9, 2016
Merged
@timh77
Copy link
Author
timh77 commented Oct 9, 2016

Does it also return any unit of measure? I know in my case it's using the metric system.
And how about the odometer. In my case the current value is 19.954,465 km. Any idea whether it's always 3 decimals?

Anyway, interesting component! 👍

@molobrakos
Copy link
Contributor
molobrakos commented 8000 Oct 9, 2016

You can see all the server output by adding the following to your configuraion.yaml

logger:
  logs:
    homeassistant.components.device_tracker.volvooncall: debug

@molobrakos
Copy link
Contributor

I guess the odometer uses the SI unit for length/distance :-)

@molobrakos
Copy link
Contributor

Closed by #3777

@molobrakos
Copy link
Contributor

If you want/can, would you mind testing the changes (already merged) in #4170 by the way?

@home-assistant home-assistant locked and limited conversation to collaborators Mar 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@molobrakos @timh77
0