Why does the third-party platform experience prolonged wait time when executing one-key takeoff or w

Problem: When the third-party platform uses the dock to execute one-key takeoff or wayline missions, the data consistency of the "Offline Map" and "Custom Flight Area" between the dock and cloud will be checked before each takeoff. If no reply from the cloud to this message, the dock has a timeout logic to wait for around 40 seconds.

Solution: If the third-party doesn't support the "Offline Map" and "Custom Flight Area" functions, developer can reply the following contents to the Obtain offline map protocol (Method: offline_map_get) and Obtain custom flight area file list protocol (Method: flight_areas_get).

Topic: thing/product/{gateway_sn}/requests_reply

Direction: down

Method: flight_areas_get

{
    "bid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx",
    "data": {
        "result": 0
    },
    "method": "flight_areas_get",
    "tid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx",
    "timestamp": 1654070968655
}

Topic: thing/product/{gateway_sn}/requests_reply

Direction: down

Method: offline_map_get

{
    "bid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx",
    "data": {
        "result": 0
    },
    "method": "offline_map_get",
    "tid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx",
    "timestamp": 1654070968655
}