@sethterashima are there plans to add API fields or endpoints to get the new charging schedule?

I've noticed that the existing fields (scheduled_charging_mode, scheduled_charging_start_time_minutes) are being used with the new schedule, but it's not clear how they work and they obviously can't describe the new schedule model.

As is, the Set Scheduled Departure endpoints no longer work on these vehicles.

Actually, it does work, but you end up with additional schedules. So for every API call a new schedule is added.

@sethterashima are there plans to add API fields or endpoints to get the new charging schedule?

I've noticed that the existing fields (scheduled_charging_mode, scheduled_charging_start_time_minutes) are being used with the new schedule, but it's not clear how they work and they obviously can't describe the new schedule model.

@aaronpkahn ?

@sethterashima @patrickdemers6 when I call the vehicle_data endpoint and request charge_schedule_data to view existing schedules, it seems to return general vehicle information with no details about the car's charge schedules. Did I miss an update?

The add_charge_schedule endpoint seems to work fine.

Thank you for your help!

The endpoint seems to add and remove scheduled departures but cabin overheat protection seems to prevent scheduled departure from triggering the charging at the required time.