App nor octopus IO not waking up model 3

[Flatchat]

Yup, similar problems here since the latest firmware update and Tessie isn't always recording drives (basically showing car as offline).

 

[Wybrook]

Same here. Never had a problem with Octopus charging until the last two nights. It started some charge periods, but not others, end result was it took two nights to do what it should have done in one. Not normally a problem, but I need to get to 100% on Saturday morning for a long drive, and I don't want to wake up and discover it has failed so will be reverting to manual control.

 

[Js1977]

Just went to update my watch app and found this..

 

[bainsy]

Do we know if this issue has been resolved?

IO still won’t start the charge for me, anyone else?

 

[Zilla91]

It worked for me last night following it failing to charge the night before

 

[bainsy]

It worked for me last night following it failing to charge the night before

Do you have your car set on a schedule? I have done today I’m wondering whether I take that off and see what happens

 

[Zilla91]

No schedules on the car or charger, just using it as instructed by Octopus

 

[debrooker]

Been going through this pain alot over the last few days, IO not waking the car. I'm forever doing Bump charge tests.

 

[andylaight]

Mine has started this now, app seems terrible since recent updates, car stays unwoken on the Tesla app, and third party apps (tessie/watchfortesla) don’t work at all

 

[Cloggie]

Not working for me using Tessie to start the charge at 23:30 and stop at 05:30. The car doesn't seem to be waking up

 

[MrBadger]

Lots of breaking API changes of late. If the API consumer is not being actively maintained, then it is likely to fall foul of these changes.

The joys of accessing an unofficial API. Things can break without warning. Let’s see what the official API brings and how much it will cost to access.

Whether it is the cause of all of the above is unknown, but for less activity maintained services, quite possibly.

 

[NewbieT]

Could be the same issue as the connectivity thread. If the car drops off the mobile network temporarily it won’t receive the SMS to wake up.

 

[Zilla91]

Lots of breaking API changes of late. If the API consumer is not being actively maintained, then it is likely to fall foul of these changes.

The joys of accessing an unofficial API. Things can break without warning. Let’s see what the official API brings and how much it will cost to access.

Whether it is the cause of all of the above is unknown, but for less activity maintained services, quite possibly.

Nothing to do with the API, it’s all to do with connectivity to wake the car up. Once the car is awake everything works fine

 

[MrBadger]

and third party apps (tessie/watchfortesla) don’t work at all

Very possibly API changes.

Post in thread 'Model S REST API'
Model S REST API

 

[Js1977]

and third party apps (tessie/watchfortesla) don’t work at all

watch for tesla and stats both working fine here

 

[timnd]

I'm not having any real issues waking my M3 using the app - Octopus IO seems to be completely broken though.

The car starts charging at 23:30 as soon as my Podpoint is enabled (via homeassistant automation). IO will notice and stop the car from charging if not in a slot, but is then unable to start the car charging again at the start of the next slot.

The only way to get reliable charging at the moment is to switch off the IO smart charging altogether...

 

[Ikin]

I'm not having any real issues waking my M3 using the app - Octopus IO seems to be completely broken though.

The car starts charging at 23:30 as soon as my Podpoint is enabled (via homeassistant automation). IO will notice and stop the car from charging if not in a slot, but is then unable to start the car charging again at the start of the next slot.

The only way to get reliable charging at the moment is to switch off the IO smart charging altogether...

Seems to be a widespread issue. I started this thread, thought it was solved with the last software update but alas I am back where it started with IO useless! Anybody had success via a service request to Tesla?

 

[Js1977]

I am back where it started with IO useless! Anybody had success via a service request to Tesla?

I wouldn't go mentioning anything to do with IO to the service guys tbh...Just go with the car not waking up plain and simple

 

[Jason71]

Seems to be a widespread issue. I started this thread, thought it was solved with the last software update but alas I am back where it started with IO useless! Anybody had success via a service request to Tesla?

I am using Tessie and IO and I have experienced no issues as described above so the question is why are some people.
Waking the car was traditionally done via an SMS message. I assume that has not changed?
There was an issue in the past to do with waking that was down to a Spanish mobile network changing a protocol and the SMS to wake the cars was no longer working. No one ( including Tesla) could figure out why some cars ( including UK ones not just Spanish ones) weren't working and others were fine. it was not until the community twigged that those with a dutch eSIM were OK and those with a Spanish one were not that the issue was solved. And we only knew that based on the nationality of the averts we were getting on the youtube app

So the question is what is different about the cars that work and those that don't?
can we try to find anything common?
could it be the eSim version again? or the age? or model or submodel?

I am
MYLR late 2022
Tessie
OctopusIO

No connectivity issues at all so far
I don't know how to find out anything about the eSim is there a way to tell anything about it like what nationality it is or network it is on?

 

[Pink Duck]

I connected my S to IOG early this morning and that all succeeded nicely, using the v4.7.0 APK though with auto-update off.