v1.9.0 — August 2026

This release brings dark mode to Monitor and Manager, tools to manage large device fleets, and several new widget options. It also includes broad reliability work: background jobs, command queues and notifications that a single bad record could previously stall now keep running.

New features

Dark mode

Monitor and Manager now have a full dark theme.

• Access: the moon/sun button at the bottom of the side menu.
• Coverage: charts, maps (which switch to a night style automatically), HTML widgets, the AI copilot and floor plans.
• White label: each client's brand colors are preserved.
• Preference: saved per browser, kept after logging out, and applied to the login page too.
• The platform still starts in the light theme.

Bulk device update from CSV

Fix data on many devices at once instead of editing them one by one.

• Access: Manager → Devices → Devices → Add drop-down → Bulk update devices.
• Template: download a CSV with the facility's current devices. Columns: Address, Description, Comments, Latitude, Longitude, IconID, DefaultDashboardID and DefaultViewID.
• Matching: by Address. An empty cell leaves the field unchanged.
• Preview: before applying, every change is shown (current value and new value); afterwards, the result with per-row errors.
• Limit: 1000 devices per file. Latitude and longitude with a decimal comma are accepted.

Installation photo gallery

• Access: Manager → Devices → Devices → edit a device → Images tab.
• Use: upload several images (up to 5 MB each), reorder them by dragging, delete them and view them enlarged.
• Captions: each image has an editable caption.
• Comments: the same tab has a field for installation notes.

Executed actions report

• Access: Manager → Actions → Actions & Scripting → Executed actions button.
• Content: for a date range, each execution with its queued, started and finished times and its log.
• Limits: one-year maximum range and up to 5000 rows, with a notice when the result is truncated.
• Actions list: adds Last execution and Result columns, pages and searches on the server, and lets you select all pages for bulk deletion.
• Execution history is now kept for 30 days (previously 7).

Permanent account deletion

Users can request deletion of their account, as required by GDPR and the app stores.

• Access: Monitor → user profile → Delete my account. Administrators can also do it from Manager → Security → Users → Delete account permanently.
• Impact preview: before confirming, you see the alerts that will be left without recipients, the scheduled reports that will be disabled and the facilities that will be transferred.
• Confirmation: type the account's email.
• Effect: personal data is anonymized and sessions, push notifications and 2FA are revoked. The client's administrators get an email notice.
• Limit: the last administrator of a client cannot be deleted.

Trend line in the metric widget

• Access: Monitor → dashboard in edit mode → metric widget.
• Options: Show trend, Trend style (in the background or below the value) and Trend color.
• Data: uses the dashboard's date range (or the last 24 hours) and only applies to numeric variables.
• It is off by default on each widget.

Pareto and occurrence count in State time summary

• Pareto: bar mode shows each state's percentage plus a cumulative percentage line.
• Show occurrence count: adds how many times each state was entered, in the table (Times column), the tooltip and the pie. On by default.
• Table: now has headers.

Device counters by connectivity

Device count widgets (the Device status donut and the severity counters) add a Group by parameter with Severity and Connectivity options. The single counter lets you choose Online or Offline. The default is still Severity, so existing widgets don't change.

Dual visible + infrared camera

If a device has two cameras (visible and infrared), the image widget shows them side by side automatically, with synchronized time navigation. Single cameras are unchanged.

Data retention up to 5 years

• Access: Manager → client settings → Data retention settings tab.
• Options: from 1 to 5 years.
• Permissions: starting with this release, only the platform administrator can change retention. Other users see the settings as read-only.

Asset Tracking settings per client

• Access: Manager → client settings → Asset Tracking tab.
• Options: Show geozones, Show routes, Show old-dated positions, Allow filtering by assets and Allow filtering by drivers.
• New clients see geozones by default.

Confirmed downlinks on Loriot and ThingPark

• Access: Manager → client settings → Integrations tab.
• Option: Confirmed downlinks. With it, the LoRaWAN network retransmits each command until the device acknowledges it.
• ThingPark: appears as a new integration with this option.
• Off by default.

Device location variables in notifications

They work in opening, closing and escalation notifications. If the device has no position, the facility's is used.

LoRaWAN gateway monitoring

• Access: Monitor → Gateways.
• View: online/offline counters and a table with connectivity, EUI, name, network server, situation, last activity, RSSI, SNR and devices.
• Automatic discovery: gateways that receive uplinks through The Things Network show up automatically as candidates.
• Availability: off by default. Can be enabled per client on request; contact support.

Configuration review assistant

A daily scan that looks for configuration problems before they cause a missed alarm.

• What it checks: alerts without recipients, invalid or bouncing emails, endpoints without data, facilities with incomplete settings, failing parsers, notifications that are not delivered and uplinks from unregistered devices, among others.
• Access: Manager → lightning icon in the top bar, with a count of findings.
• Resolution: findings close on their own once the problem goes away.
• Email digest: optional, sent to the client's administrators only when there is something new.
• Availability: off by default. Available on request; contact support.

Improvements

• Device map at scale: clustering is computed on the server for the visible area and handles on the order of 100,000 devices. If the map cannot load, it now says so.
• Map clustering: all devices are drawn (previously only the first 150), and devices that share a location are grouped into a numbered cluster.
• Map styles: cleaner, with the same style picker in asset tracking, incidents and the map widget.
• Monitor → Endpoints: pages and searches on the server. Each page loads in under half a second for large clients.
• Alerts in Manager: an ID column with copy to clipboard, and select-all-pages for bulk deletion.
• Dashboards: spacing between widgets, and metric and HTML widgets refresh without flickering.
• Performance: device counts, global summary, activity log and drop-downs with long lists.
• Add-ons: the add-ons screen only shows available add-ons, and tabs that depend on an add-on only appear when it is active.
• Translations: the communications chat and the WhatsApp channel are available in all 8 languages.
• Notifications: SMS, voice calls and WhatsApp have a 30-second timeout, so a provider that doesn't respond no longer delays the rest.

API changes

• Position in endpointData: LocationTracker endpoints return Latitude, Longitude and LocationFlags in /api/v2/endpointData (incremental, by query and multiple). These used to be empty.
• New methods: DeviceService.EditDevices (bulk update), ActionService.GetActionExecutionReport, AccountService.GetAccountDeletionImpact and DeleteAccountPermanently, EntityImageService.SetImageCaption and DeviceService.GetDeviceMapClusters.

Bug fixes

• Monitor access: users whose only group was Everyone could not log in.
• Login: with captcha and 2FA both enabled, login was blocked.
• Offline alarms: enabling or shortening a model's offline timeout triggered a burst of retroactive alarms for every inactive device. Also, one faulty device could leave the whole instance without offline alarms.
• Background processing: a single malformed record (a client, a facility, a calendar event, a measurement) could stall the instance's jobs or the ingestion of flow and energy measurements.
• Commands: an unreadable command file blocked the queue, and on MQTT one failed command dropped the rest of the batch.
• LoRaWAN downlinks: on TTN, ThingPark, Loriot and Orbiwise, commands were reported as successful without being verified, and some failures lost the command without a trace.
• Actions: an exception left an action locked until the service restarted. Stuck executions are now released automatically after 60 minutes.
• Notifications: a discarded notification vanished from the queue report; it now shows as discarded. Scheduled reports lost their PDF attachment when the email was retried, and one corrupt scheduled report could stop the others.
• Escalation: could notify the same alarm twice.
• Device Catalog report: counted each facility's virtual weather sensor.
• Map widget: the facility summary counted the virtual sensor; in asset tracking mode it always showed a missing-facility notice, did not reload when the facility changed, and its tooltip could not be closed.
• Maps: the alarm heatmap failed inside a dashboard, and a facility without coordinates broke the facilities map.
• Geozone alerts: only one could be created per endpoint.
• Facilities: incomplete regional settings made the client inaccessible, and an unknown time zone returned an error that didn't say which field was wrong.
• Widgets: the pie chart used a different color for states defined as black, the State time summary legend overflowed its box, and the hexagonal grid was empty when expanded.
• Date picker: choosing a day closed the panel without applying the date.
• Alert templates: applying a template could leave alerts half-created or duplicated, and reprovisioning could set thresholds to 0.
• Shared links: sharing a dashboard or asset tracking view returned an error.
• Security: cross-client access was closed in dashboards, PDF export and alert templates, and login no longer reveals whether an account is disabled.

Support

For questions, contact the Cloud Studio team: contacto@cloud.studio.