Alan Tse

So the solution is that upon exiting the `async for msg in ws:` loop, you can check the websocket's close reasons including `ws.exception()`. That will contain the `concurrent.futures._base.TimeoutError`.

The wiki section should be open to edits by anyone. The old data should probably be copied from [HA](https://github.com/home-assistant/home-assistant.io/blob/48a817f4f28e8f73088946e60ab0459c53aec30d/source/_integrations/tesla.markdown).

To avoid draining your battery, the component only updates after it detects a car has gone into a non-sleeping state. Give it some time to actually do an update. You...

You need to enable teslajsonpy and read those logs to see why it's failing. As this is access to the raw API interface, I won't be spending much time debugging...

Oh please make sure you understand `vehicle_id` vs `id`. https://tesla-api.timdorr.com/api-basics/vehicles#vehicle_id-vs-id

I'll look at exposing that somewhere, but it shouldn't change so once you find it, it should work indefinitely. This is meant as an advanced feature since HA doesn't allow...

> Could the normal full response be made available as attributes of the location sensor? Or can that already be accessed elsewhere? I don't know what you're asking about with...

Please try the dev branch. The online sensor has attributes for vin, id, and vehicle_id.

> ... is going to be the standard template for just about every call, right? Would be cool if you could just do something like this instead: This is intended...

The component does not do anything command-wise unless you set it. You should review your logbook to see what is being triggered and investigate. Your HA may have an automation...