> ## 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.

# FAQs

> Frequently asked questions about OWL DMS

## General Questions

<AccordionGroup>
  <Accordion title="What is OWL DMS?">
    OWL DMS (Device Management System) is a web-based platform for managing Duck mesh networks. It provides real-time monitoring, web-based firmware flashing, GPS visualization, and data export capabilities for ClusterDuck Protocol devices.

    Key features:

    * Web-based firmware flashing via USB
    * Real-time message monitoring with WebSocket updates
    * Interactive map visualization with GPS tracking
    * CSV data export for analysis
    * Multi-user support with device assignments
  </Accordion>

  <Accordion title="What are Duck devices?">
    Duck devices are based on the ClusterDuck Protocol, our open-source LoRa mesh network library (made and maintained by OWL). There are three types:

    * **PapaDuck (Gateway)**: Connects to WiFi and sends data to the cloud
    * **MamaDuck (Node)**: Battery-powered sensor devices
    * **DetectorDuck**: Network testing and optimization tool
  </Accordion>

  <Accordion title="Do I need special software to use OWL DMS?">
    No! OWL DMS runs entirely in your web browser. You only need:

    * Google Chrome or Microsoft Edge (for firmware flashing)
    * A modern web browser for monitoring and management
    * No command-line tools or external software required
  </Accordion>
</AccordionGroup>

## Device Setup

<AccordionGroup>
  <Accordion title="How do I flash firmware to a device?">
    1. Navigate to the "Add Device" page
    2. Connect your device via USB
    3. Follow the 4-step wizard:
       * Connect Device
       * Select Device Type (Papa/Mama/Detector)
       * Configure Firmware (WiFi, sensors, intervals)
       * Review & Flash

    See the [Flash Firmware guide](/guides/flash-device) for detailed instructions.
  </Accordion>

  <Accordion title="What browsers support firmware flashing?">
    **Supported:**

    * Google Chrome (version 89+)
    * Microsoft Edge (version 89+)

    **Not Supported:**

    * Firefox
    * Safari

    The flashing feature requires Web Serial API, which is only available in Chrome and Edge.
  </Accordion>

  <Accordion title="How do I register a new device?">
    Devices are registered through the Network Management page:

    1. Go to **Network** page
    2. Click **Add Device**
    3. Enter device name (3-8 characters)
    4. Select device type (PAPA or MAMA)
    5. For MamaDucks, select parent PapaDuck
    6. Add description and location (optional)
    7. Click **Save**

    After registration, flash firmware to the device to configure it.
  </Accordion>

  <Accordion title="What sensors do MamaDucks support?">
    MamaDucks support multiple sensor types:

    * **GPS Location**: Track device coordinates
    * **BMP180**: Temperature and pressure
    * **BMP390**: High-precision temperature and pressure
    * **DHT11**: Temperature and humidity
    * **LED Control**: Visual indicators

    Choose one sensor type per device during firmware flashing.
  </Accordion>
</AccordionGroup>

## Using the Platform

<AccordionGroup>
  <Accordion title="How do I view device messages?">
    Messages appear in multiple places:

    * **Dashboard**: Recent messages table with real-time updates
    * **Map View**: Message feed for selected PapaDuck
    * **Device Detail Page**: Recent messages for specific Mama Duck (last 100)

    All tables support sorting, filtering, and time range selection.
  </Accordion>

  <Accordion title="How do I know if a device is online?">
    A device is considered **online** if it has sent a message within the last 5 minutes.

    Check status in:

    * Network Management page (online/offline badges)
    * Device detail pages
    * Map View device markers
  </Accordion>

  <Accordion title="How do I export data?">
    Use the Data Export page:

    1. Select date range (max 30 days)
    2. Optionally filter by PapaDuck
    3. Click **Search** to preview
    4. Click **Export CSV** to download

    See the [Data Export guide](/guides/data-export) for details.
  </Accordion>

  <Accordion title="Can I see device locations on a map?">
    Yes! The Map View page shows GPS locations for devices with GPS-enabled firmware.

    Requirements:

    * MamaDuck must have GPS firmware flashed
    * Device must have sent GPS coordinates within last 24 hours
    * GPS data appears as markers on the interactive map
  </Accordion>

  <Accordion title="How do I monitor battery status?">
    Battery information appears on MamaDuck device detail pages:

    * Battery percentage
    * Charging status
    * Voltage and temperature (if available)
    * Last updated timestamp

    **Note**: Battery data only appears if a health message was received within the last 2 hours.
  </Accordion>
</AccordionGroup>

## Network Management

<AccordionGroup>
  <Accordion title="What's the difference between PapaDuck and MamaDuck?">
    **PapaDuck (Gateway)**:

    * Connects to WiFi
    * Sends data to cloud
    * Manages multiple MamaDucks
    * Requires power (USB/wall adapter)
    * No sensors

    **MamaDuck (Node)**:

    * Battery powered
    * Collects sensor data
    * Must connect through a PapaDuck
    * Mobile/portable
    * Multiple sensor options
  </Accordion>

  <Accordion title="Can I change which PapaDuck a MamaDuck connects to?">
    Yes! Edit the MamaDuck device:

    1. Go to MamaDuck device detail page
    2. Edit the **Parent PapaDuck** dropdown
    3. Select a different PapaDuck
    4. Click **Save Changes**

    The change takes effect after the device reboots and reconnects.
  </Accordion>

  <Accordion title="How many MamaDucks can one PapaDuck support?">
    There's no hard limit in the platform, but practical limits depend on:

    * Message frequency from each MamaDuck
    * PapaDuck's WiFi connection quality
    * Network congestion

    For most deployments, 10-20 MamaDucks per PapaDuck works well.
  </Accordion>
</AccordionGroup>

## Firmware & Configuration

<AccordionGroup>
  <Accordion title="What is ClusterDuck Protocol (CDP)?">
    The ClusterDuck Protocol is our open-source LoRa mesh network library. Duck devices use CDP to communicate.

    Learn more at the [ClusterDuck Protocol website](https://clusterduckprotocol.org/).
  </Accordion>

  <Accordion title="Can I update firmware on an already-flashed device?">
    Yes! Simply reconnect the device via USB and flash it again through the Add Device page. The new firmware will overwrite the existing configuration.
  </Accordion>

  <Accordion title="What WiFi networks are supported for PapaDuck?">
    **Supported**:

    * 2.4 GHz WiFi networks
    * WPA/WPA2 secured networks
    * Open networks (no password)

    **Not Supported**:

    * 5 GHz WiFi networks
    * Enterprise WiFi (RADIUS authentication)
    * Captive portal networks (hotels, coffee shops)
  </Accordion>

  <Accordion title="How often should devices send data?">
    **GPS Interval**: 5-60 minutes

    * Lower = more frequent updates, higher battery drain
    * Recommended: 15-30 minutes for normal use

    **Sensor Interval**: 30 seconds to 60 minutes

    * Lower = more data points, higher battery drain
    * Recommended: 5 minutes for continuous monitoring
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="My device won't connect to WiFi (PapaDuck)">
    Check:

    * SSID is correct (case-sensitive)
    * Password is correct
    * Network is 2.4 GHz (not 5 GHz)
    * Device is within WiFi range
    * Network doesn't use captive portal

    **Solution**: Reflash the device with correct WiFi credentials.
  </Accordion>

  <Accordion title="Device shows as offline but is powered on">
    A device shows offline if no message received in 5 minutes.

    **For PapaDuck**:

    * Check WiFi connection
    * Check serial monitor for errors
    * Verify internet connectivity

    **For MamaDuck**:

    * Ensure PapaDuck is online
    * Check device is within range
    * Verify sensor configuration
    * Check battery level
  </Accordion>

  <Accordion title="I can't see GPS location on the map">
    GPS locations only appear if:

    * Device has GPS firmware flashed
    * GPS coordinates received within last 24 hours
    * Device has clear view of sky for GPS lock

    Check the device detail page to see if GPS messages are being received.
  </Accordion>

  <Accordion title="Firmware flashing fails">
    Common solutions:

    * Use high-quality USB cable (not charge-only cables)
    * Try different USB port
    * Ensure device has sufficient power
    * Close other programs using the serial port
    * Use Chrome or Edge browser
    * Try a different cable

    See [Flash Firmware Troubleshooting](/guides/flash-device#troubleshooting) for more help.
  </Accordion>

  <Accordion title="Battery drains too quickly">
    To extend battery life:

    * Increase GPS interval (30-60 minutes)
    * Increase sensor reading interval
    * Disable external LED
    * Reduce transmission frequency

    Reconfigure via firmware flashing with adjusted intervals.
  </Accordion>

  <Accordion title="Messages not appearing in dashboard">
    Check:

    * Device is showing as online
    * PapaDuck has WiFi connection
    * Time range filter includes recent data
    * No search filters are active

    Try clicking "Reset Sort & Filters" in the messages table.
  </Accordion>
</AccordionGroup>

## Getting Help

<CardGroup cols={2}>
  <Card title="OWL IoT Discord Community" icon="discord" href="https://discord.gg/9HPQBwhd2E">
    Join our community for support and discussions
  </Card>

  <Card title="Documentation" icon="book" href="/">
    Browse the complete documentation
  </Card>

  <Card title="ClusterDuck Protocol" icon="link" href="https://clusterduckprotocol.org/">
    Learn about the underlying mesh protocol
  </Card>

  <Card title="ClusterDuck Protocol (GitHub)" icon="github" href="https://github.com/ClusterDuck-Protocol/ClusterDuck-Protocol">
    Our open-source LoRa mesh network library.
  </Card>
</CardGroup>