[ardevd]

@ardevd Great job with this app!
Question 1: Battery Health says 81%. What does this mean and is that a concern at all?
Question 2: Can we use this to see what veriosn software the car has to know if it is current?

Answer 1: There's a reason why the battery health setting is now disabled by default. After the H264 update the health value is way off. Don't pay attention to it for now. Hopefully it will be corrected by JLR in the future.

Answer 2: The API does report TCU versions but not in the same format as we've come to relate to.

 

[ardevd]

Just upgraded to 1.3.4 and the estimated range is way off on the charging display but correct (agrees with Jaguar app and car) on the dashboard display.
Dashboard says 246 miles. Charging display says 397 miles (I wish). Switching to the charging display sometimes pops up saying it can't get current status but the dashboard doesn't have that problem.

Thanks for reporting this! I refactored the charging screen for 1.3.4 and I guess there was a miles/km bug that creeped in. I'll take care of it asap.

 

[Kenny Is Awesome]

Answer 1: There's a reason why the battery health setting is now disabled by default. After the H264 update the health value is way off. Don't pay attention to it for now. Hopefully it will be corrected by JLR in the future.

Answe 2: The API does report TCU versions but not in the same format as we've come to relate to.

Awesome. What version TCU should we be looking for right now in the US to see if the car is current?

Again great job with the App!

 

[ardevd]

Awesome. What version TCU should we be looking for right now in the US to see if the car is current?

Again great job with the App!

Unfortunately, I honestly have no idea. Without some community effort it's unlikely that we will be able to correlate what TCU versions the different API reported values correlate to.

 

[Ayepace]

Awesome. What version TCU should we be looking for right now in the US to see if the car is current?

Again great job with the App!

Many of us in US have TCU 18.2 version as reported in the car's SOTA display (where we can check for updates). If it is at a lower level, you may have to get it updated at a dealership but they don't usually update it without a reported problem. This is supposed to be SOTA updatable, but earlier versions may not have had that feature enabled.

 

[lobster]

Unfortunately, I honestly have no idea. Without some community effort it's unlikely that we will be able to correlate what TCU versions the different API reported values correlate to.

On the WattCat Vehicle Details page, find the TCU Software Version and decode the last 2 Characters as follows:

J8A2-70712-AY = 18.2

J8A2-70712-AX = 17.2

J8A2-70712-AV = 16.2

J8A2-70712-AT = 15.2

J8A2-70712-AS = 14.2

J8A2-70712-AR = 13.2

Cheers, Steve

 

[ardevd]

On the WattCat Vehicle Details page, find the TCU Software Version and decode the last 2 Characters as follows:

J8A2-70712-AY = 18.2

J8A2-70712-AX = 17.2

J8A2-70712-AV = 16.2

J8A2-70712-AT = 15.2

J8A2-70712-AS = 14.2

J8A2-70712-AR = 13.2

Cheers, Steve

That's very useful! Interestingly enough mine shows up as AS. Looking back in my logs I can see that it's been AS since I got the vehicle even though I know I'm on at least 16.2. Wonder why the API does not reflect this. Maybe the API is only showing the version correlating with what the vehicle had when it was delivered.

 

[Ayepace]

That's very useful! Interestingly enough mine shows up as AS. Looking back in my logs I can see that it's been AS since I got the vehicle even though I know I'm on at least 16.2. Wonder why the API does not reflect this. Maybe the API is only showing the version correlating with what the vehicle had when it was delivered.

Likewise, my car reports itself as 18.2 on the software update display, but WattCat's info from API say "AR". It never changed from before when 18.2 was installed late last year. The TCU configure version never changed either.

 

[Kenny Is Awesome]

My Car reports 18.2 but WC shows AS

 

[bruintoo]

Mine doesn't even display which telematics version it's using on the display. It just says No new updates. According to WattCat I have the "AS" version.

 

[PS702]

Neat new feature showing the rank of your average consumption

 

[ardevd]

So, some news and a request for comments.

The next major version of WattCat will focus on integrating route planner functionality. I'm currently working on destination management, adding and deleting destinations. I'll hopefully be able to provide more functionality than what the official route planner app does, including the ability to name a destination. It has always annoyed me how I have to do this through the car Infotainment currently.

The Route planner API is horrible and mixes all sorts of different conventions and even adds a custom binary format into the mix. I literally keep finding new ways they choose to pass the hard coded API credentials in for every new request I look at. It's a bit tedious to work with but I'm getting more familiar with it for every passing day.

I see no reason to have to use two separate apps for vehicle remote control and remote navigation. For JLR, the reason is that they've outsourced everything so they kinda have to separate the functionality into different apps. I don't use the actual routing functionality of the route planner app, I simply want an easy way to search for a destination and send it to the car, and hopefully WattCat can deliver that sometime this summer.

Finally, if anyone have any suggestions on this feature, please do share.

I've also passed along a reminder to the navigation team @ JLR about the fact that we have to constantly sign in to our navigation accounts in the vehicle Infotainment. I'm hoping this gets fixed soon.

 

[Brendon]

So, some news and a request for comments.

The next major version of WattCat will focus on integrating route planner functionality. I'm currently working on destination management, adding and deleting destinations. I'll hopefully be able to provide more functionality than what the official route planner app does, including the ability to name a destination. It has always annoyed me how I have to do this through the car Infotainment currently.

The Route planner API is horrible and mixes all sorts of different conventions and even adds a custom binary format into the mix. I literally keep finding new ways they choose to pass the hard coded API credentials in for every new request I look at. It's a bit tedious to work with but I'm getting more familiar with it for every passing day.

I see no reason to have to use two separate apps for vehicle remote control and remote navigation. For JLR, the reason is that they've outsourced everything so they kinda have to separate the functionality into different apps. I don't use the actual routing functionality of the route planner app, I simply want an easy way to search for a destination and send it to the car, and hopefully WattCat can deliver that sometime this summer.

Finally, if anyone have any suggestions on this feature, please do share.

I've also passed along a reminder to the navigation team @ JLR about the fact that we have to constantly sign in to our navigation accounts in the vehicle Infotainment. I'm hoping this gets fixed soon.

You are my hero.

 

[dernotte]

So, some news and a request for comments.

The next major version of WattCat will focus on integrating route planner functionality. I'm currently working on destination management, adding and deleting destinations.

Hi Ardevd,

Do you plan to update the jlrpy github project as well once you have decoded the route planner API ?

 

[ardevd]

Hi Ardevd,

Do you plan to update the jlrpy github project as well once you have decoded the route planner API ?

Possibly, it doesnt really fit in with jlrpy, since it requires separate credentials, etc. Perhaps I'll make a separate library for it. I havent given it much though yet to be honest.

 

[dernotte]

The method does not fit in the JLR nor Vehicle class, but a RoutePlanner Class, yes...

 

[ardevd]

The method does not fit in the JLR nor Vehicle class, but a RoutePlanner Class, yes...

Hah, possible for sure. I just hate the Jaguar Here API so much right now so it's going to be hard to motive me to refactor jlrpy to accommodate it.

 

[Snowflake]

This app is a real accomplishment. One smart person doing better than teams of others. I'd like to see control of the vehicle's software, like allowing staying at a chosen ride height despite the speed. That's really beyond what an outside facing API would allow, I'm sure. That's probably canbus hacking.

 

[ardevd]

Appreciate the kind words! It's a fun project!

Today's fun (and concerning) fact: When you delete a destination, either from the Here website or the route planner app, the destination isn't actually deleted. It's just marked as deleted but the destination data is still included in the API response data, it's just up to the client to ignore deleted destinations.

However, I did discover how to actually delete destination data. Coming to WattCat sometime soon.

 

[Qtown charger]

Appreciate the kind words! It's a fun project!

Today's fun (and concerning) fact: When you delete a destination, either from the Here website or the route planner app, the destination isn't actually deleted. It's just marked as deleted but the destination data is still included in the API response data, it's just up to the client to ignore deleted destinations.

However, I did discover how to actually delete destination data. Coming to WattCat sometime soon.

Not too concerned. If I'm using the nav system to get me to the nearest brothel, I have bigger problems.