Unlock doors not working

pvprodk commented 3 years ago

The problem

Getting the following error when trying to unlock the car. I know the integration is working, because engine start/stop works fine.

Failure to execute: 500, message='Internal Server Error', url=URL('https://vocapi.wirelesscar.net/customerapi/rest/v3.0/vehicles/*VECHILE-ID*/unlock')

What is version of Home Assistant Core has the issue?

core-2021.2.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

volvooncall

Link to integration documentation on our website

https://www.home-assistant.io/integrations/volvooncall/

Example YAML snippet

# Put your YAML below this line
volvooncall:
  username: MY_USERNAME
  password: MY_PASSWORD

Anything in the logs that might be useful for us?

# Put your logs below this line
Logger: volvooncall.volvooncall
Source: /usr/local/lib/python3.8/site-packages/volvooncall/volvooncall.py:302
First occurred: 21:40:39 (1 occurrences)
Last logged: 21:40:39

Failure to execute: 500, message='Internal Server Error', url=URL('https://vocapi.wirelesscar.net/customerapi/rest/v3.0/vehicles/*VECHILE-ID*/unlock')

probot-home-assistant[bot] commented 3 years ago

volvooncall documentation volvooncall source _{^{(message by IssueLinks)}}

pvprodk commented 3 years ago

I did some research and read elsewhere that the call has been changed to bootunlock instead of unlock, which kind of makes sense when looking at the Volvo On Call app, there the unlock command tells you that the boot has been unlocked and you need to open the boot to unlock the doors. Can we get the integration updated to reflect this behavior?

victorclaessen commented 3 years ago

I found this issue while searching for the same 500 error. I don't use the unlock feature very often, so I only noticed that it wasn't working after this morning's upgrade to version 2021.3.1.

Somewhere during debugging, the error 500 just disappeared. Not sure why, but perhaps it was taken care of by starting the official VOC app somewhere in between testing from HA?

Anyway: I then noticed that the car didn't seem to be unlocking at all, but when I checked by trying to open the trunk it did actually open. So you send this unlock command, you get NO indication whatsoever (neither visually on the car, nor in the API values) that the trunk is unlocked, but for 2 minutes it is really unlocked. In the official VOC app, it will show "trunk unlocked" only if you've unlocked from the official VOC app, which leads me to believe this label is only generated internally/locally in the official VOC app (it just shows "trunk unlocked" for two minutes in the app).

Can you check to see if the car is really not unlocked if you send the unlock command? Otherwise try doing it once with the official VOC app and then I wonder if your error 500 might also disappear afterwards?

github-actions[bot] commented 3 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / core