sending commands still supported 2025?

[migube]

Hello hello I was using teslamateapi in the past, then switched to something else, but since the Jan 2025 changes , a bit confused if sending commands is still supported nowadays?

I re-enabled teslamateApi on my docker to do some quick tests, and while in the past, I was using /api/v1/cars/1/wake_up (or other commands)

now I get a {"code":"PAGE_NOT_FOUND","message":"Page not found"}#

so wondering if still supposed to work or I did something wrong?

http://url:8088/api/v1/cars/1/command still works giving {"enabled_commands":["/command/set_sentry etc... tx !

[tobiasehlert]

@migube, could be that the /api/v1/cars/:CarID/wake_up command has been removed from the TeslaMate application, since that's something that gets sent there and not to the deprecated Owners API. However, does the request get forwarded into the TeslaMate application or does it get stuck somewhere else on the way? Do you get some error indicating something in the TeslaMateApi application-log?

Regards, Tobias

[jlou07]

Hi @tobiasehlert ,

I’ve been using TeslaMate Proxy Api successfully to push wake and commands, but with the new pay-as-you-go model, the costs could double—so I decided to set up my own proxy to handle the new Fleet API/Vehicle Command Protocol directly.

I’m trying to confirm whether I’ve implemented everything correctly the teslamateapi app. By teslamateapi, here are the some commands who are working :

• /api/v1/cars

Here are some POST who are not working :

• /api/v1/cars/1/wake_up
• /api/v1/cars/1/command/charge_port_door_open ...

Some commands succeed without car results, while others fail with an error message about the new protocol. If anyone else is self-hosting or has successfully integrated the new Fleet API, I’d really appreciate any insights or examples. I want to confirm whether my setup is correct or if there are still partial limitations on Tesla’s side.

Thanks in advance!

Jean-Loup