Devices

Find a device and see its state

Six tiles sit above the list. Click one to show only those devices, click it again or click Sensors to show all. The active filter also appears as a chip next to the search, where its × removes it.

The search looks at the name, the chip family, the firmware version and the template name. Type custom to find devices without a template. Group sorts the list by template (the default), by chip family, by status, or not at all. Every group has a Select group button. Columns turns the optional columns on and off and has Compact rows for long lists. The browser remembers your choice.

Tick devices to select them. A bar appears at the bottom with Update firmware, which goes straight to the check for the latest firmware, and Bulk change… for everything else. The checkbox in the header selects every device the filter shows. On a phone each device is a card with the same facts, and the list never scrolls sideways.

The gear next to Columns opens Fleet settings with your Default verify mode. It appears once you own at least one sensor.

What each device is doing right now

The Live state column combines the open job, the monitoring status and what the board last reported. States that are happening right now pulse. A download shows a progress bar.

The Jobs running tile counts Queued, Offered, Waiting for check-in, Downloading, Restarting, Applying and both Verifying states. Healthy, Delayed and Offline follow the same rule as Sensor Monitoring.

What the board runs and what it can take

The version comes from the board itself. It reports it with every reading, together with its config revision (r14), restarts, WiFi signal and sensors that failed to read. The hint below the version says what the device can take.

The Config column shows the config revision. It counts up with every flash and every config change, so r15 after r14 means the board took the new settings. The chip drifted marks a device that came from a template but was changed on its own since.

One device, everything about it

Click a row to open its details on the right. The address bar gets ?device=…, so you can bookmark or share the view. Esc, the close button, a click next to the panel or the back button closes it.

1. 1
   State

   The live state in large type with time since the last contact, a sentence that explains it and the five job steps from Queued to Installed.
2. 2
   Problems

   What the device reported going wrong, in plain words: a power drop or crash that restarted it, WiFi that rejected the password or was not found, a sensor that does not answer (with the pins of its saved setup to check), and a round that keeps it awake far longer than its setup needs. Firmware 0.6.0 and later also report how long the last round was awake.
3. 3
   Actions

   Update to the latest firmware, Change config or Reflash via USB. The first button reads Up to date, Needs USB reflash, Config only or Job running when an update is not possible, and its tooltip says why. Change config opens the device builder for this device; the arrow next to it offers Bulk change instead. When the device takes no config, the reason stands under the buttons.
4. 4
   Facts

   Firmware, config revision, last and next contact, battery, signal (dBm, Ethernet, or RSSI and SNR for LoRaWAN), verify mode and template. Click Verify mode to choose Account default, Strict or Lenient for this device.
5. 5
   Error rate

   Refused readings, missed rounds, refused commands, failed or rolled back updates and restarts, each for 24 hours and 7 days with a trend line.
6. 6
   Device setup

   What the device builder put on the board: sensors with bus, pins and values, outputs, and how it reports. Marked "differs from template" when it drifted.
7. 7
   Jobs

   The last ten jobs with who started them, the verify mode, the result and the reason.
8. 8
   Console

   The last twelve lines of the Device Console, live. Open console jumps to the full console on the sensor page.