Do Not Disturb (DND) Overview#
The Do Not Disturb (DND) service allows passengers to signal to the crew that they should not be disturbed. Airlines can configure exceptions that remain active even when DND is enabled (e.g., meal service, prayer, or other defined events). These exceptions are selectable by the passenger.
When paired, passengers can use their Personal Electronic Device (PED) to turn DND on or off and choose exception items, without needing to access the seatback monitor.
Step 1: Retrieve the DND Service#
The first step in working with DND is to access the DND service object provided by the SDK.
This object acts as the entry point for all interactions related to Do Not Disturb. It exposes properties and functions that allow the application to:
-
Query the current DND status of the paired seat.
-
Update or change the seat’s DND state.
-
Receive notifications when the DND state is modified either by the PED or the seatback monitor.
This ensures developers have a single integration point to handle all DND functionality in their application.
Step 2: Get the Current DND State#
Once the service object is available, the application can retrieve the current DND state of the seat.
This is particularly important after a successful seat pairing, as it ensures that the PED reflects the actual state of the seat.
If the seat is not yet paired, the value will not be available until pairing is complete. Developers should also handle cases where the state may be nil or unavailable, for example, when the pairing status is unknown or disconnected.
By fetching the latest DND state, the application can correctly display whether the seat is currently in DND mode or not, providing the passenger with accurate feedback before they make further changes.
Step 3: Set or Change the DND State#
The DND service allows the PED to actively change the DND state on the seatback system.
Developers can request to enable DND (true) or disable DND (false), depending on passenger preference.
When this action is triggered, the SDK communicates with the seatback system to update the seat’s DND indicator. If the request fails (for example, due to network issues or seat unavailability), an error will be returned so the application can handle it gracefully.
In addition to simple on/off control, the airline may provide exception categories (such as meal service or prayer time). Developers should design their app UI to allow passengers to select these exceptions, ensuring that enabling DND does not block important predefined interactions.
Note: Support for airline-defined exception categories (e.g., meal service, prayer time) is not yet available in the SDK. This functionality is planned for a future release. At present, developers can only enable or disable DND.
Step 4: Handle State Change Events#
The DND state can change not only through the PED but also directly from the seatback monitor. To stay in sync, the application must listen for state change notifications from the SDK.
When such a notification is received, the application should:
-
Fetch the updated DND state from the service.
-
Update the passenger-facing UI accordingly.
This ensures that even if the app is running in the background, disconnected, or if the passenger toggles DND from the seatback, the PED always reflects the latest seat status once active again.
By handling these notifications properly, developers can deliver a seamless and real-time DND experience across PEDs and seatback monitors.
Version 1.0