Firing history for every alert
An alert's history tab lists every notification, newest first, with the values and the threshold the alert had when it fired. Editing the alert does not change what its history shows.
An alert's history tab lists every notification, newest first, with the values and the threshold the alert had when it fired. Editing the alert does not change what its history shows.
On a computer, with the window narrower than 1280 px, the side menu shows only its icons and leaves the room to the page, while keeping your preference on large screens. The device page arranges its cards to fit the space it has.
When a device reports that it rejects a configuration, it goes back to the last one it applied, and the history shows the change as rejected, with the device's message when it sends one. The send interval accepts 1 minute to 1 day.
The location map on the readings page centers on each position as you step through them, and the dashboard map keeps your zoom when it refreshes.
On the readings page and in the HTML report, each wind direction shows the speed from its own transmission. Before, two transmissions in the same minute shared one speed.
When we schedule maintenance on your device, the unit is notified when it is scheduled, 48 hours before and when it starts. While it lasts, the device switches to maintenance mode and its alerts go quiet.
Rules are drawn as a diagram: conditions flow into a node that requires all or any of them, and the actions branch out from there. Errors show up next to each field as you edit.
An alert notifies you once when it fires and, while it stays triggered, reminds you every 15 minutes for the first hour, every hour up to 6 hours and every 6 hours after that, with at most 20 notifications a day. It also tells you when it recovers.
Each device has its own alerts page, with the last notification of each alert and a switch to turn it on or pause it, one by one or all at once. Alerts are created and edited in a side panel without leaving the page.
The whole app shares the same design for cards, tables and forms. The status of devices and reports shows as a colored dot, and table headers stay in place as you scroll.
The readings page fits on a phone screen: filters stack, the calendar shows a single month and the side menu closes when you tap a link.
When you create, edit, move or delete something, lists update right away, even with filters on. Before, a deleted record could stay in the table until you reloaded the page.
GPS positions without a fix no longer trigger geofence alerts.
Axes fit the actual range of the data, so variables that barely change no longer look like a flat line. A selector under the chart lets you narrow down a stretch and zoom in.
The weather panel on the map shows the forecast for the next 24 hours, the feels-like temperature and the wind, and air quality now includes pollen levels.
Filters, searches, tabs and date ranges are kept in the page address: they survive a reload and can be shared with a link. Searches also ignore accents.
The map in exported HTML reports showed a notice over the streets. It now displays cleanly.
Devices with a camera send photos, which you see on the readings page and in the device's gallery, with an enlarged viewer and download.
Every configuration change to a device is recorded: what changed, who made it and when the device applied it. You can filter it by date, type and author, and it is kept for 3 months.
Wind is shown with arrows and compass points: a compass in the readings table, and a direction and speed table in charts and reports.
The new dashboard is now the only one. Recent records are still under Records.
Exports with many readings no longer fail halfway, and scheduled reports that got stuck in the queue are generated again.
Exported CSV files use the report's number format, so Excel no longer reads 12.96 V as 12,960 V.