Changes

Change many devices in one pass

Bulk change in the header, in the selection bar or under the arrow next to Change config in the details of one device opens the same dialog. One device or forty, the same rules apply. Nothing is sent to a board before you press Create jobs.

Bulk change covers the basics: firmware, interval, the WiFi signal and the power mode. To change everything on one device, its sensors, pins, options and how often each value is sent, press Change config in its details. The device builder opens with the saved setup, the board stays fixed, and the last step sends the new setup over the air. A board on firmware 0.5.0 or later takes new sensors, other pins or another sleep mode this way without a firmware update. A sensor that needs a newer firmware says so in the builder, and the update goes first in the same job.

1. 1
   Change

   Tick what changes and pick the new value. Choose the verify mode. Firmware and config combine into one pass.
2. 2
   Devices

   Tick the devices, or use Quick pick: All from a template, All with update available, or Clear. From 20 devices on, a filter field helps.
3. 3
   Check & review

   HydroNode checks every device and shows what changes where. Create jobs starts the change for every device that can take it; the others are skipped.

Reading the check

The check runs every rule for every device before anything is created. The box Same for every device shows the change most devices get, for example Send interval 10 min → 5 min. Below it, one row per device and one cell per change. A cell is yellow when a device starts from a different value than most, for example differs from the usual 10 min.

From Queued to Installed

Every device in a change gets one job. The details panel draws it as five steps: Queued, Offered, Download, Verify, Installed. The board always starts the step itself, when it checks in. HydroNode never reaches into your network.

1. 1
   Queued

   The job exists and waits for the board to check in. A sleeping board shows Waiting for check-in with the time of its next round.
2. 2
   Offered

   The reply to the next reading carries the update. The board finishes its round first, so no reading is lost.
3. 3
   Download

   The board checks the signature, then loads the firmware into its free slot and verifies its checksum. An interrupted download resumes where it stopped.
4. 4
   Verify

   The board restarts into the new firmware and checks itself in its first wake cycle. The check after the restart is described in the OTA guide.
5. 5
   Installed

   The check passed. The details show for example "Verified Strict in 41 s", and the saved setup follows the new version.

A config change takes the same path without a download: the board receives the new settings with the reply, keeps its old config, writes the new one, restarts and checks. A change with firmware and config runs the firmware first and the config right after, as one job.

Cancel a job

While a job is Queued, Offered or Waiting for check-in, a Cancel button stands next to its state. Cancelling keeps the board exactly as it is: nothing was downloaded yet. Once the download or the config change started, the job runs to its end, and a failed check rolls it back on its own.

Bulk change can also set the device thresholds of HTTP devices. A LoRaWAN station takes its interval and thresholds with Change config in its drawer, one station at a time: Battery and Power.

What the board does during an update, the check after the restart and the rollback are explained in Over-the-air updates.