Not sure if this is just a limitation of the API, but Saturday and today, I received a "car is open" message from Watch for Tesla. I checked the Tesla app and it was not open. However today I figured out that the charger was not latched into the port (and it was probably like this for the last couple days, car was last driven on Friday). This is not a huge deal, but wanted you to be aware of it in case you expected it to show the actual true error. The Tesla app itself showed the correct info about the charge port.
I didn't think to get screenshots before troubleshooting. I checked the logs and saw nothing useful, but there was an error event just around the time of the notification.
Background events:
Request events:
Error
Apple Watch
1/23/23, 9:15 AM: Get data error response body:
Error
Apple Watch
1/21/23, 5:36 PM: Get data error response body:
Error
Apple Watch
1/18/23, 7:16 PM: Get data error response body:
Not sure if this is just a limitation of the API, but Saturday and today, I received a "car is open" message from Watch for Tesla. I checked the Tesla app and it was not open. However today I figured out that the charger was not latched into the port (and it was probably like this for the last couple days, car was last driven on Friday). This is not a huge deal, but wanted you to be aware of it in case you expected it to show the actual true error. The Tesla app itself showed the correct info about the charge port.
I didn't think to get screenshots before troubleshooting. I checked the logs and saw nothing useful, but there was an error event just around the time of the notification.
Background events:
Request events:
Error Apple Watch 1/23/23, 9:15 AM: Get data error response body:
Error Apple Watch 1/21/23, 5:36 PM: Get data error response body:
Error Apple Watch 1/18/23, 7:16 PM: Get data error response body:
Action events:
Bluetooth events: