ScanMyTesla / Tasker Token changed

[rowich]

Just detected that Teslalogger is no longer recording data from Teslalogger and checked the token value. In SMT, I had years ago the typical 8 character code In the Teslalogger settings, it's a new, different code with trailing _1

[rowich]

Communication with Teslalogger und ScanMyTesla works again since I updated ScanMyTesla with the new, changed Token (inkluding _1). The value for "ScanMyTesla last received:" is still empty, no even weird data here

Question still open: Why did the token changed?

[rowich]

At least today after updating to 1.56.0 I realized, that my Taker Token used for ScanMyTesla has again changed. May (I am not using the car currently every day) also after last software update of the car (to 2023.44.30.9)

[rowich]

It happened again (probably after updating to v1.57), and it's again a token with trailing _1. I did not recorded the inital one, but it strongly looks like the same from dec-21

[rowich]

After rebooting Teslalogger, the token is back to the usual value without trailing _1. An additional reboot did not changed it again to the one with _1 for now.

[rowich]

Just getting feedback from the swiss tesla community, that a couple of people seems to have the same issue. One just told me: I stopped using SMT, it's missing now too much data.

[bassmaster187]

I'll check it tonight

[bassmaster187]

fixed in 1.57.1

[rowich]

Thanks for the fix. I am going to observe this during the next days. For now I can confirm that the manual initiated update was successful and the registered token is the usual one without trailing "_1". No token change behaviour after restart and restart-update so far.