> ## Documentation Index
> Fetch the complete documentation index at: https://docs.owlintegrations.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Network Management

> Add, configure, and manage Papa Duck gateways and Mama Duck devices in your mesh network

The Network Management page allows you to configure and monitor all devices in your Duck mesh network, including both Papa Duck gateways and their connected Mama Duck devices.

## Device Hierarchy

OWL DMS uses a two-tier device structure:

<CardGroup cols={2}>
  <Card title="Papa Duck" icon="tower-broadcast">
    Gateway devices that connect to the internet and relay messages to the cloud. Each Papa Duck can support multiple Mama Ducks.
  </Card>

  <Card title="Mama Duck" icon="satellite-dish">
    Mesh network devices that relay messages between end devices and Papa Ducks. Each Mama Duck must be assigned to a parent Papa Duck.
  </Card>
</CardGroup>

## Device Table

The main table displays your Papa Duck devices with expandable rows:

### Table Columns

| Column           | Description                                            |
| ---------------- | ------------------------------------------------------ |
| **Name**         | Device display name (clickable link to device details) |
| **Unique ID**    | Hardware identifier for the device                     |
| **Description**  | Optional device description                            |
| **Location**     | Physical location or deployment area                   |
| **Status**       | Online/Offline (based on messages in last 5 minutes)   |
| **Mama Devices** | Number of connected Mama Duck devices                  |
| **Created**      | Date the device was added to the system                |
| **Actions**      | Edit and delete buttons                                |

### Expandable Rows

Click the expand arrow next to a Papa Duck to view its connected Mama Ducks:

<Steps>
  <Step title="View Mama Ducks">
    Expand a Papa Duck row to see all associated Mama Duck devices
  </Step>

  <Step title="Mama Details">
    Each Mama Duck shows the same information as Papa Ducks (name, ID, description, location, status)
  </Step>

  <Step title="Manage Mama Ducks">
    Click on a Mama Duck name to view its detail page, or use the edit/delete actions
  </Step>
</Steps>

## Adding Devices

### Add Papa Duck

<Steps>
  <Step title="Click Add Device">
    Click the "Add Device" button in the top-right corner
  </Step>

  <Step title="Select Device Type">
    Choose "PAPA" from the device type dropdown
  </Step>

  <Step title="Enter Device Info">
    Fill in the required and optional fields:

    * **Name** (required, 3-8 characters): Short identifier for the device
    * **Description** (optional): Purpose or notes about the device
    * **Location** (optional): Physical location or deployment area
  </Step>

  <Step title="Submit">
    Click "Submit" to create the Papa Duck. The system will generate gateway credentials automatically.
  </Step>
</Steps>

<Info>
  Papa Duck credentials (Device ID and Token) are generated automatically and can be viewed in the device details page.
</Info>

### Add Mama Duck

<Steps>
  <Step title="Click Add Device">
    Click the "Add Device" button
  </Step>

  <Step title="Select Device Type">
    Choose "MAMA" from the device type dropdown
  </Step>

  <Step title="Select Parent Papa">
    Choose which Papa Duck this Mama Duck will connect to (required)
  </Step>

  <Step title="Enter Device Info">
    Fill in the required and optional fields:

    * **Name** (required, 3-8 characters): Short identifier
    * **Parent PAPA** (required): Select the parent Papa Duck
    * **Description** (optional): Purpose or notes
    * **Location** (optional): Physical location
  </Step>

  <Step title="Submit">
    Click "Submit" to create the Mama Duck
  </Step>
</Steps>

<Warning>
  Every Mama Duck must be assigned to a Papa Duck. You cannot create a Mama Duck without first having at least one Papa Duck in your account.
</Warning>

## Editing Devices

Click the edit icon (pencil) next to any device to modify its information:

### Editable Fields

* **Description**: Update the device purpose or notes
* **Location**: Change the deployment location
* **Parent Papa** (Mama Ducks only): Reassign a Mama Duck to a different Papa Duck

<Accordion title="What Cannot Be Changed">
  - Device Name (set during creation)
  - Unique ID (hardware identifier)
  - Device Type (PAPA or MAMA)
  - Gateway credentials (Papa Ducks only)
</Accordion>

## Archiving Devices

Archiving lets you hide Gateways and Nodes you no longer need to see day-to-day — test devices, decommissioned hardware — without deleting them or losing any of their history. Archived devices can be restored at any time.

The Network page has two tabs:

* **Active** — your normal, working device list
* **Archived** — devices you've hidden from view, each with its own search box

### Archiving a Gateway

<Steps>
  <Step title="Open the overflow menu">
    Click the **⋯** menu on a Papa Duck row
  </Step>

  <Step title="Select Archive">
    Choose **Archive**. A confirmation dialog explains that the Gateway will move to Archived and stop appearing in your active network
  </Step>

  <Step title="Confirm">
    Check the box confirming you want to archive the device, then confirm
  </Step>
</Steps>

<Info>
  Archiving a Gateway also archives all of its connected Nodes. You can still restore individual Nodes separately afterward.
</Info>

### Archiving a Node

Open the **⋯** menu on a Mama Duck row and choose **Archive**. This only affects that Node — its parent Gateway stays active.

### Restoring an Archived Device

From the **Archived** tab, open the **⋯** menu on a Gateway or Node and choose **Unarchive**. A confirmation dialog appears; confirm to move the device back to Active.

<Tip>
  Restoring a Gateway only brings back the Nodes that were archived along with it. If you archived a Node individually *before* archiving its Gateway, that Node stays archived — you'll need to restore it separately.
</Tip>

In the Archived tab, a Node whose parent Gateway is still active shows a **Gateway Still Active** badge, so you know it was archived on its own rather than as part of a Gateway archive.

### What Archiving Affects

Once a device is archived, it disappears from:

* The home page device list
* The Gateway selector on the Map page
* The Node dropdown in the Add Device / firmware flash wizard

Nothing is deleted — message history is preserved, and you can still open an archived device directly by its detail page URL.

## Device Status

### Online/Offline Detection

Devices are automatically marked as online or offline based on recent message activity:

<Steps>
  <Step title="Online Status">
    A device is considered **online** if it has sent a message within the last 5 minutes
  </Step>

  <Step title="Offline Status">
    A device is marked **offline** if no messages have been received for more than 5 minutes
  </Step>

  <Step title="Status Indicators">
    * **Green dot**: Device is online
    * **Gray dot**: Device is offline
  </Step>
</Steps>

<Info>
  Device status updates automatically based on real-time message activity from the WebSocket connection.
</Info>

## Viewing Device Details

### Papa Duck Details

Click on a Papa Duck name to view its detail page, which includes:

* Device information (name, ID, description, location)
* Gateway credentials (Device ID and Token for cloud connectivity)
* Last seen timestamp
* Battery status (if available)
* Online/offline status
* Connected Mama Ducks list
* Recent message history

### Mama Duck Details

Click on a Mama Duck name to view its detail page, which shows:

* Device information
* Parent Papa Duck
* Last seen timestamp
* Battery and health metrics
* Online/offline status
* Recent message history
* GPS location history (if equipped)

## Tips

<Tip>
  **Naming convention**: Use descriptive, location-based names for devices (e.g., "PAPA-HQ", "MAMA-FIELD1") to easily identify them in large deployments.
</Tip>

<Tip>
  **Bulk organization**: Use the description and location fields to group devices by project, deployment area, or purpose for easier management.
</Tip>