Possible to use Telemetry with multiple applications?

[jlestel]

I noticed that if a vehicle uses telemetry on an application A, then an application B can't configure its own Telemetry.

Here is the API behavior for application B:

• fleet_telemetry_config CREATE: 1 vehicle updated
• fleet_telemetry_config GET: {"response":{"synced":true,"config":null}}
• fleet_telemetry_config DELETE: 0 vehicle updated

In summary, for application B: the API seems to create the Telemetry, but the config remains null and it is impossible to delete the Telemetry. This is why I deduce that we can only use the Telemetry with one application at a time.

Do you confirm that this is the expected behavior? Are there users who have already encountered the same problem?

[dirkbonhomme]

My own vehicle is active with two applications (although from the same organization). So my understanding is that this should be possible.

[Bre77]

Previously when a second application configured telemetry the first was removed. Now you can have multiple, because my vehicle has both Tessie and Teslemetry working simultaneously.

So I'm not sure about what you're describing because it's not the case on recent vehicle firmwares.

[jlestel]

I had already tried a hard reboot without success yesterday. And the firmware is recent (2024.45.32).

And now I confirm what I said: when Tessie Telemetry is disconnected, my application B Telemetry works normally with the fleet_telemetry_config.

So be careful, it's not because the response of the GET fleet_telemetry_config contains sync: true that it works. You have to check that the config field is not null.

I'll try to activate again Tessie Telemetry to confirm this behavior...

EDIT: I confirm I can't activate the Tessie Telemetry now. So currently, the first one to connect the Telemetry may be the only one eligible(?)

EDIT2: Tessie has finally reconnected their Telemetry. I'll let running and if it continue to work...

EDT3: The Tessie telemetry connection isn't persistent. This corroborates the observations I made on this issue. I've sent an inquiry to Tessie support...

[jlestel]

And here is Tessie's response to my last comment:

Tesla engineering says this is happening because there are too many apps using telemetry on your vehicle. They plan to start working on a fix for this next week.

So, Tesla devs confirm there is indeed a limit to the number of connectable Telemetry.

[ThomasAlxDmy]

Currently we support 3-4 apps in parallel depending on the platforms with some optimization we should be able to get to more.

[jbanyer]

Is there any way to detect that this problem has occurred, ie that the vehicle has rejected the config because it has too many apps configured?

Will this situation fix itself if the user removes another app? Or do we have to re-send the config?

Are there other reasons why the vehicle would reject the config?

We'll need some way to provide the right information to the user. Cheers.

[patrickdemers6]

Will this situation fix itself if the user removes another app? Or do we have to re-send the config?

If another app removes their config, you would be able to send your configuration successfully. It won't magically start to work though.

Are there other reasons why the vehicle would reject the config? The reasons I can think of that a vehicle would reject a config:

• Expired (exp config option)
• Key not on vehicle

We do plan to fix the 3-4 application limit shortly. Keeping this open to track the 3-4 limit fix.

[rawmean]

@patrickdemers6 If that restriction in number of apps connected to the car exist, one would expect that the response to creating a config should indicate this problem and not provide a response that is indistinguishable from the success case.

Can you please at least return a response that indicates this?