Dryad Silvanet Documentation
Get StartedExplore SilvanetPlan a SiteDeploy SilvanetFAQ
  • Dryad Silvanet Documentation
  • Tutorials
    • Get started tutorial (Gen 2)
    • Get started tutorial (Gen 3)
    • Planning tool tutorial
  • Silvanet Suite
    • Explore Silvanet
    • Silvanet Suite (Gen 2)
      • Silvanet Wildfire Sensor (Gen 2)
      • Silvanet Mesh Gateway (Gen 2)
      • Silvanet Border Gateway (Gen 2)
    • Silvanet Suite (Gen 3)
      • Silvanet Wildfire Sensor (Gen 3)
      • Silvanet Mesh Gateway (Gen 3)
      • Silvanet Border Gateway (Gen 3)
    • Silvanet Cloud Platform
    • Silvanet Mesh Network
    • Site Management App
      • User access
      • Dashboard
      • Sites view
      • Site details
        • Device overview
        • Wildfire Sensor data
        • Device info tabs
      • Map view
      • Alert center
      • User Management view
      • User preferences
    • Deployment App
    • Fire detection
  • Site Planning
    • Plan Sites
    • Planning guidelines
      • Deployments stages
      • Scout deployment locations
      • Gateway ratios
      • Gateway ranges
      • Sensor ratios
      • Sensor range
      • Sensor density
    • Coverage planning
      • Planning tool
      • Import KML, KMZ and Shapefiles
      • High density paths
      • Low density areas
      • Connectivity zones
      • Add or move Sensors
      • Export plan
    • Packet editor
  • Silvanet Deployment
    • Deploy Silvanet
    • Deployment guidelines
      • Deployment preparation
      • Border Gateway guidelines
      • Border Gateway scenarios
      • Mesh Gateway guidelines
      • Wildfire Sensor guidelines
    • Deploy Border Gateways (Gen 2/3)
      • Register Border Gateway
      • Mount Border Gateway (Gen 2)
      • Mount Border Gateway (Gen 3)
      • Border Gateway Connectivity Test
    • Deploy Mesh Gateways (Gen 2/3)
      • Register Mesh Gateway
      • Mount Mesh Gateway (Gen 2)
      • Mount Mesh Gateway (Gen 3)
      • Mesh Gateway Connectivity Test
    • Deploy Wildfire Sensors
      • Register Wildfire Sensors
      • Mount Wildfire Sensors
      • Sensor Calibration
      • Sensor normalization
    • Relocate a Silvanet Sensor or Gateway
  • Silvanet API
    • Silvanet API - MQTT Sensor Data Integration
    • Silvanet API - Webhook Integration
  • Silvanet Test Fires
    • Overview
    • Test fire preparation
    • Run test fires
    • Modify fire setups
  • Resources
    • Contact Technical Support
    • Release Notes
    • FAQs
      • General Questions
      • Border Gateway FAQs
      • Mesh Gateway FAQs
      • Wildfire Sensor FAQs
      • Site Management FAQs
      • User Management FAQs
    • Glossary of Terms
    • Status icons
    • Device troubleshooting
    • Firmware updates (FUOTA)
    • Declaration of Conformity (EU)
  • Chandler Burning Index (CBI)
Powered by GitBook

Docs Version

  • Version 4.6.4

Sales Enquiry

  • Contact Dryad Sales

Dryad

  • Dryad.net

© 2025, Dryad Networks GmbH, Eisenbahnstr. 37, 16225 Eberswalde, Germany

On this page
  • Overview
  • Scheduling FUOTA
  • Update times

Was this helpful?

Export as PDF
  1. Resources

Firmware updates (FUOTA)

Dryad updates firmware in Silvanet Devices using FUOTA (Firmware Update Over the Air). Update times vary depending on device energy levels and communication strength between devices.

PreviousDevice troubleshootingNextDeclaration of Conformity (EU)

Last updated 3 months ago

Was this helpful?

About FUOTA

FUOTA is a standard for distributing firmware updates to many devices as the same time in an efficient and secure manner.

The Silvanet Cloud uses which supports FUOTA. Updating Wildfire Sensors use End-to-End 128-bit AES encryption.

Overview

When the firmware needs updating, Dryad Engineering uses FUOTA (Firmware Update Over The Air) to send updates simultaneously to specific Silvanet devices in a Site from the Silvanet Cloud.

FUOTA uses Multicast as it is the most efficient and secure method to update a Site's firmware. During an update, the LoRaWAN Network Protocol is temporarily switched to allow two-way communication. Firmware is then updated using a chunked image transfer (no compression).

Updates are sent in data packets of a restricted size and then are reconstituted in the Silvanet devices before an update is done.

  • Border Gateways: If the firmware in Silvanet Border Gateways require updating, Dryad sends a command for the Silvanet Cloud to update Border Gateways.

  • Mesh Gateways: If the firmware in Mesh Gateways require updating, Dryad sends a command for the Border Gateway(s) to update the Mesh Gateways.

  • Wildfire Sensors: If the firmware in Wildfire Sensors require updating, Dryad sends a command for either Border Gateways or Mesh Gateways to update the Wildfire Sensors.

About updating Border Gateways

When Silvanet Border Gateways require firmware updates, large file transfers are successfully made securely and reliably even with eventual interruptions of power supply and, consequently, sensor operation.

Scheduling FUOTA

The Wildfire Sensors come with a factory install of firmware. If this version of the firmware is not the latest, Dryad engineering checks the current firmware version and updates are scheduled, sometimes during the Calibration phase of the Sensors.

Notifications

Dryad engineering notifies the customer before performing any firmware updates to a Silvanet deployment.

Update times

The update times vary depending on a number of factors.

  • Number and type of Silvanet devices to be updated.

To cope with low power and the various regional regulatory requirements, both the downlink fragment size as well as the periodicity are highly configurable allowing for stretching a FUOTA process to a week or more.

Connectivity strength between the Silvanet Wildfire Sensors and Mesh Gateways or between Mesh/Border Gateways. For more information, see .

Full or charging status of a Silvanet device, which reflects the supercapacitor energy storage levels (high vs low energy storage). For more information, see .

LoRaWAN
Connectivity is not optimal
Charging is not optimal