-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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.
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
[tesla] "IllegalStateException: Expected a boolean but was NUMBER" for seat_heater_left #4509
Comments
Getting the same on Model S P90D same s/w version, although I am sure it was also on previous versions. Also I think the Tesla API is returning a number but the binding expects a boolean. I assume a number between 0-3 to reflect the heater setting? |
I assume the API changes reflect that it's possible to pre heat the seat thru the tesla app. |
|
Just downloaded the latest snahot from here: https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/binding/org.openhab.binding.tesla/2.5.0-SNAPSHOT/ and I can confirm that the issue is now solved! Thanks |
I have also a Tesla S (2015). I replaced the jar file. Unfortunately I still have the error: An exception occurred while parsing data received from the vehicle: 'java.lang.IllegalStateException: Expected a boolean but was NUMBER at line 1 column 464 path $.seat_heater_left' |
I have Tesla Model S85 2014 and currently running on 2018.48.12.1 d6999f5
The openHAB is running on 2.4.0 and the binding is installed thru paper UI (Tesla binding 2.4)
I currently see this error: 2018-12-24 11:02:53.550 [ERROR] [b.binding.tesla.handler.TeslaHandler] - An exception occurred while parsing data received from the vehicle: 'java.lang.IllegalStateException: Expected a boolean but was NUMBER at line 1 column 460 path $.seat_heater_left'
Similar issue was closed here: https://github.com/openhab/openhab2-addons/issues/3261
But for me it seems like the Tesla API is now back with boolean instead of NUMBER.
The text was updated successfully, but these errors were encountered: