Hey everyone,
I managed to get volvooncall working on Home Assistant however the icon is not showing the right status of the sensor. any idea how to solve this issue?
Thanks is adavance,
André
Hey everyone,
I managed to get volvooncall working on Home Assistant however the icon is not showing the right status of the sensor. any idea how to solve this issue?
Thanks is adavance,
André
Do you mean that it shows the incorrect lock status? In my setup the lock shows “on” when locked and “off” when unlocked. I think it is because the lock has the “assumed_state” attribute that makes it look the way it does with the two lightning bolts. For comparison I also have the Verisure integration enabled and that lock shows up like a slider. Maybe the behavior can be updated in the Volvo On Call component? @molobrakos
It is true that this is because of the component setting the assumed state attribute.
I don’t like the current look of the lock status either. I guess you could propose a change on how locks with assumed state are displayed (open/closed lock icon instead of flash, with active state blue?). Feel free to make a PR for this.
I am not sure removing the assumed_state attribute would be the correct way to go. The communication between HA and the car are two steps via the VOC server and if the car and the VOC server has lost contact, the state reported by the server cannot be trusted I guess.
Thank you both for the reply however I don’t know if mu point is understand well. Underneath you will find my code:
volvo:
control: hidden
name: Volvo
entities:
- sensor.hk388j_fuel
- sensor.hk388j_fuel_2
- sensor.hk388j_odometer
- sensor.hk388j_range
- switch.hk388j_heater
- lock.hk388j_lock
The last is not respond at all, what I mean it show the status While I operate the doors it remains in the same position. The doors cannot be operated whitin the app, only in the Volvo app.
So pushing the doesn’t change a thing. All other are working just fine.
My erro log is:
2017-05-27 21:18:59 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
OSError: [Errno 113] No route to host
2017-05-27 21:19:00 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
OSError: [Errno 113] No route to host
2017-05-27 22:08:45 WARNING (<concurrent.futures.thread.ThreadPoolExecutor object at 0x7faa8353d710>_7) [volvooncall] Failure when communcating with the server: HTTPSConnectionPool(host=‘vocapi.wirelesscar.net’, port=443): Read timed out. (read timeout=30)
2017-05-27 22:08:45 WARNING (<concurrent.futures.thread.ThreadPoolExecutor object at 0x7faa8353d710>_7) [volvooncall] Could not query server: HTTPSConnectionPool(host=‘vocapi.wirelesscar.net’, port=443): Read timed out. (read timeout=30)
2017-05-27 22:08:45 WARNING (<concurrent.futures.thread.ThreadPoolExecutor object at 0x7faa8353d710>_7) [homeassistant.components.volvooncall] Could not query server
2017-05-28 03:01:00 WARNING (<concurrent.futures.thread.ThreadPoolExecutor object at 0x7faa8353d710>_0) [volvooncall] Failure when communcating with the server: HTTPSConnectionPool(host=‘vocapi.wirelesscar.net’, port=443): Read timed out. (read timeout=30)
2017-05-28 03:01:00 WARNING (<concurrent.futures.thread.ThreadPoolExecutor object at 0x7faa8353d710>_0) [volvooncall] Could not query server: HTTPSConnectionPool(host=‘vocapi.wirelesscar.net’, port=443): Read timed out. (read timeout=30)
2017-05-28 03:01:00 WARNING (<concurrent.futures.thread.ThreadPoolExecutor object at 0x7faa8353d710>_0) [homeassistant.components.volvooncall] Could not query server
Thnx in advance,
André
Is this reproducable every time? It seems like you lost connection with the server.
I think you are right but even after a reboot the status remains unchanged, doors open while they are closed. So it looks like that there is no connection although the heater is working properly.
Maybe turning on debug logging would reveal some information about what is wrong.
Try add to your configuration.yaml
logger:
default: info
logs:
volvooncall: debug
homeassistant.components.volvooncall: debug
I did but the log difficult to understand, would you like to help me? And do I need to send it to a privat mail?