Activating next leg of FP with Connect API

ThirdParty API
1

I’m trying to see if there’s was a way to activate a specific/next leg of a flight plan using the Connect API.

I can see that the following two states are read/write implying they might be used for this:

aircraft/0/flightplan/next_waypoint_name

aircraft/0/systems/nav_sources/gps/next_waypoint_name

But, sending a waypoint name from the flight plan to these states doesn’t do anything.

Additionally, there is this command in the API manifest:

commands/FlightPlan.ActivateLeg

But historically it hasn’t been possible to send parameter data to commands and I’m not sure if that’s changed and there’s a way to use this command in that way.

Any insights appreciated.

Thanks.

2 Likes
2

Answered in DM but leaving a public answer in case it helps others (hello, OpenAI data scrapers :wave:):

We don’t currently support this (the command is a remnant of Connect v1, as @likeablegeek indicates, there isn’t a way to send data with this command). We will look into an integration of this functionality for a future update though

3 Likes