Search results

The Apple iPhone Watch app is buggy at times. Have you tried configuring from the watch itself?

Large middle should be supported:

Have you tried EV Watch? It's the only watch app I'm aware of (hard to keep up with the surge in apps) that supports complications that constantly update.

The problem is that the browser doesn't support SNI which allows https to work on virtual hosted sites that use their own certs and custom domain name. If the website is on a hosting service's domain, e.g., xxx.appspot.com, it should still work because hosting services typically install a...

Yep! Thanks for all the feedback and bug reports!

Thanks! Should be fixed in the latest beta drop. For those sitting on the fence, app is on sale for $0.99 through the end of the month.

Yeah, I was thinking for non-pano roof owners I would put in charge state on the large complication which also states whether or not it's plugged in. For the main watch app, I'll probably just remove the picker.

Awesome! new beta version is available which should fix both issues.

Interesting. Mind sharing which iPhone model that is? I'm having trouble re-creating the issue. Thanks. I was able to reproduce this by changing my system accessibility font size to one step smaller than the default (the smallest setting). Workaround for now is to bump this size up a little...

There's some leeway for graphics in the complications. Probably no pulsing/animations though. Will have to play around with it.

Thanks for the report! Should be an easy fix.

1.14 Released expanding on its focus on Apple Watch 3.0 and at-a-glance info: iPhone Today Extension support Expanded complication support: Large modular and Large utilitarian modes for info beyond charge level iPhone independence (after syncing login token info and in presence of wifi) Other...

Hi, So it looks like a clean merge might be a ways off... Until I can figure out how best to cleanly merge and test everything, I put ericwol@'s version in a separate url: Waze for Tesla Incidents It looks like most browsers these days balk at unsecure webpages that use geolocation. To...

Nice! I'll try to take a look asap.

There's a number of server side apps (like VisibleTesla and the aforementioned evtripping) that do this. For the more paranoid, EV Watch on iOS has a beta feature which does this while keeping your MyTesla credentials safely stored on the phone (vs on a 3rd party server).

Lately it seems one possibility is that Tesla's servers are down (which seemed to occur last night...). I've setup a mock Tesla service in order to get basic stuff working before hitting the real Tesla production servers: Tesla API Simulator Otherwise, it' really difficult to help without...

Updated to version 1.13 to work with iOS 10 and watchOS 3.0. EV Watch for Tesla on the App Store Featuring continuously updating complications and crown support for setting charge:

Here's my quick test from an AWS server in eu (Frankfurt) server: First few traceroute hops verify it's going through the EU. 1 ec2-54-93-0-20.eu-central-1.compute.amazonaws.com (54.93.0.20) 1.146 ms ec2-54-93-0-22.eu-central-1.compute.amazonaws.com (54.93.0.22) 1.154 ms...

This probably warrants a little more research. It's highly doubtful 3rd party clients use a proxy server as that defeats lots of the advantages; not having to deal with backend security and scale. Will spin up an EU sever and give it a try...

Which request? If you don't have any vehicles returned by the API, all the commands will fail with a 404.

If the app can't log in, the API won't let you in. They use the same mechanism.

You're also supplying the parameters on the URL. Try putting them in the content body.

Take out that second "?vehicle_id=" and see what happens. That's not valid URL syntax (the first ? designates url parameters....subsequent ones screw things up).

What does your request look like? It sounds like you probably aren't sending parameters (because it sounds like parameterless ones work for you). Here's a curl example sending to my mock endpoint (so i don't need to obfuscate tokens...): Using JSON: curl -XPOST...

Thanks for the offer! But to start, I think the best would be to get code that works against the mock backend to also work with the tesla websocket backend and vice versa. I think poking at the summon interfaces of a remote MS would be asking for trouble..... Fixed this. The other interfaces...

Thanks! Looking at your previous post, it looks like your auth header may not be correct. It should look like: "Authorization: Bearer tokenXYZ" Where tokenXYZ should be replaced by whatever you got from the oauth/token call

It should work although I only tested on the regular api commands and not the auth. Ah, thought I modified the second record slightly but guess I missed some pieces. Eventually I plan to expose the functions to directly modify the underlying model. I'm unfortunately going to be afk for the...

Considering I just got a P replacement, I'm wondering if any P Model Ss have gotten a Q drivetrain? or any P drivetrains have reported issues?

Hi All, Author of the EV Watch and Tesla Waze Website here. Seeing all the difficulties with the API, I'm experimenting with a new project to provide an alternate Tesla API endpoint. The main objectives are to: Avoid having to hit your personal Telsa account and potentially trigger any rate...

Great idea! Will try to incorporate this into a future release, but I'm open to UI ideas. One of the general issues with the Tesla browser is it's poor performance. So for the most part, I try to minimize the amount of necessary interaction.

Updated just now. It's an easy process to update, but I keep it under manual control because I don't have any guarantees that the data source won't suddenly change formats.....

Just had my first drive unit replaced for the milling noise with a P version. (same as above). 22K miles. Noise first noticed around 16k miles. VIN 51xxx

Noticed recently that the google search picks up the https version of the website. Surprisingly, the Tesla browser doesn't support SNI (verified using TLS SNI Test Site: *.sni.velox.ch) and it won't load the https version of the site because the site runs on a shared Ip service (Google App...

In general, yes, if your GET requests for car state (charge, climate, etc..) are working then the commands should work to; they both share the header authorization as well as the vehicle id. The primary difference is that one is POST and one is GET. It's possible there's something else going on...

Those parameters are passed in as normal form/url encoded parameters and not in the header...

It looks like you're getting the same 404 response as your PHP. For CORS, it sends a preflight OPTIONS request to the target url for certain requests to ensure you have access, and the method and headers are all allowed. But I'm, not sure why it's not working for you. Fundamentally, the...

My understanding of what Ingineer posted above is that traffic routing uses Navigon + Inrix data only. This would be like any independent Nav system such as Garmin or Magellan. The center display uses Google Maps and the traffic data on those maps uses Google traffic tiles. When a route is...

Is SSL required? Last I tried it, the https version of the site wasn't working with the tesla browsert.

404 usually means that the vehicle id you're using is incorrect. What happens when you list vehicles? If that works, the proper vehicle id you should use is the "id" field from that response; not the "vehicle_id" field. Does querying for vehicle charge state work? That javascript error you're...

Works for me? Anyone else having issues? No problems with integrating into QuickTesla. The more the merrier! There are some minimal expenses. Part of this was an experiment with using Google's AppEngine/Cloud services vs my traditional hosting which is done on AWS.

4th of July Fire works sale, $0.99: EV Watch for Tesla on the App Store

Should be fixed. Please try again.

Thanks for testing out on iOS 10! Reminds me that I should try it out too!

Latest updated provides a UI refresh as well as improved watch response, 3d touch actions on phone, and improved charge reminder handling. EV Watch for Tesla on the App Store

That that site seem to require SSL. I've noticed that the Tesla browser will reject some lesser secure CAs (e.g. the SSL link doesn't appear green in a desktop browser). In my case, I've a cert from RapidSSL which works fine on the desktop but not in the Tesla browser.

1.09 is out and fixes issues with multi-vehicles and iPads. Also adds a manual check reminder in case iPhone/iPad is not able to access your vehicle due to device restrictions (power/cellular usage).

Fix will be a later version.

Think I found the issue which is likely due to the fact that you have multiple Teslas (lucky u!). Pushing an update to testers now...

Arg, how embarrassing. Does uninstall/reinstall work?

Update is available in the app store. In additional to better complication updates (~every 10 mins), better multi-tesla support, and responsiveness, there's a new beta feature: charge reminders! For security reasons, the checking is done on the device (iPhone/iPad/iPod) itself and for now...