[APP][PRO] Tesla - Zero emissions. Zero compromises

I installed the beta and turned on telemetry and turned off polling. I then tried to activate the car key via BLE and the Fleet-API and they both failed. Any suggestions?

Hi,

I’m not sure about the reason. But it sounds as ifnyour client_id is not registered yet. Did you proceed the pairing process and added your client_id and client_secret from your Tesla developer account?

I added a short documentation about the Telemetry fields and how to change the configuration (if needed).

And btw… have you already found the new fields provided by Telemetry?

And sorry, totally forgot…

Many thanks for the donations :innocent: :smiling_face_with_sunglasses: :+1:

The support is really great. Especially those users who were not first-time donors :clap:

Hello RonnyW

Thank you very much for the great app, I’ve been using it for quite some time now. I’ve now switched to telemetry and noticed the following.

If you go to the telemetry settings and click on “activate” again, it will be deactivated again. That’s not supposed to happen, is it?

It should do the same like switching on/off in device settings.

But if something goes wrong while activating, the app switches Telemetty off to get back to a stable state. Is an error messages displayed (below the buttons)?

Edit: Found it. Settings got set to “false” for both buttons :sweat_smile: . Thanks for reporting.

1 Like

New test version 4.0.2

  • Fixes some data conversions for Telemetry
  • Fixes Telemetry avtivation button in repair view

@Asterix The activate buttons is fixed now. It’s doing the same like device settings. But it’s just a shortcut from repair view. After changing the car settings (fields), the new config is pushed to the car automatically. A new activation is not needed.

Yes, I added the Client ID and Client Secret months ago and app was working fine with the polling active. But if I enable Telemetry and turn off polling, everything stops working.

Hm, sounds as if the app was not added as car key before.

But I lost the content of your situation :sweat_smile:

So it’s best to start over. Perhapd something changed in your app registration. Please try this to get a new registration.

  • Remove the car key in your car.
  • Start a new repair process,
  • set client_id and client_secret, proceed to oAuth popup (if you did not clear cookies, this will be passed).
    Now the app should have a new certificate and your client_id should be registered at Tesla.
  • Add the car key.

I hope then you got your car key and Telemetry is working.

I keep getting Signed message error: MESSAGEFAULT_ERROR_INCORRECT_EPOCH when running flows. Is this my end?

EDIT: restarted the app and it’s working. It’s happening quite a lot and is always resolved by restarting the app.

Thanks

The command has only a short valid time (20sec). If message delivery takes longer, the message will be rejected. I can’t say what’s wrong in your case, Perhaps the car was not reached in time.

Finally success! Just removing the key didn’t work, so I archived the app in Tesla Developer and created a new. This allowed me to add a new key and complete setup.

Plan to donate to your server fees today. Thanks for your efforts :+1:

1 Like

Hm, never had this issue. Did you move from one Homey to another (other HomeyID)?

But anyway, it worked. Thanks for your support :+1:

Ah I see. My command is to unlock the doors but maybe the wake is taking too long for the unlock to run in time. I’ll try and run a separate wake command prior.

Thanks

That should bot be an issue. The app sends wake command before door open command if car is offline. You can activate this automatic in device settings.

Perhaps the car is temporarily offline (sporadic LTE disconnects).

Maybe. It’s very consistent. It fails with that issue so I restart the app on Homey and run it again and it works. Happens all the time for some reason.

Ol, then pleae check the settings for ‘wake up if needed’ in command section.

It that doesn’t work, please check which condition could be the reason, which command, a flow, perhaps parallel commands where where the app could try to wake up parallel.

A common reason would be good to find.

Ha! Hadn’t considered that. I did the CM4 mod to increase my RAM!

But then you have the same HomeyID. But whatever, as long as it works now :grinning_face_with_smiling_eyes: