Replies: 1 comment 6 replies
-
As another example, this occurs during the config flow so it does not show any exception. The error message is not very helpful:
The debug level shows the real issue:
|
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I think the exception handling in this integration could be improved, but I don't know how to do it. As an example, if a vehicle command fails, the HA log looks like this:
The real error is logged by the library at debug level. This exception is logged by
websocket_api
and does not explain the issue. Ideally, this should be logged at error level bytesla_custom
, and not throw an exception.A quick improvement is to add a line in teslajsonpy connection.py after line 212:
That will show the error nicely, but it doesn't prevent the exception. Since each command in this component is a thin wrapper around the library, I'd rather not add try/except blocks to each one. Is there some way to add an exception handler to
TeslaCarEntity
in base.py?Beta Was this translation helpful? Give feedback.
All reactions