v1.9.2 — August 2026

This release focuses on handling alarms from Monitor: alarm pop-ups let operators act without leaving the page, and each alarm keeps its full history. It also adds sensor comparison, LoRaWAN gateway management from Manager and an SMS usage screen.

New features

Alarm pop-ups with direct actions

The pop-up shown in Monitor when an alarm opens now lets you act on it.

• Access: any Monitor screen.
• Buttons: Acknowledge, Silence and View details. View details opens the alarms screen even if the alarm has already been resolved.
• Color: the pop-up uses the severity color, including custom severities. High-severity pop-ups don't close on their own.
• Alarm floods: at most 4 pop-ups are shown, grouped by device, with a summary of the rest.
• Silence: also mutes pop-ups for that device for 10 minutes for the operator who asked.
• Other operators: if someone else acknowledges or silences the alarm, you see a notice on screen.
• Availability: the pop-ups and their colors are available to everyone. The Acknowledge and Silence buttons and the other-operator notice require the alarm lifecycle, available on request; contact support.

Per-alarm event log

• Access: Monitor → Alarms → an alarm's actions → Event log tab.
• Content: every transition of the alarm, with who did it, when and which action.
• Availability: requires the alarm lifecycle, available on request; contact support.

Compare sensors from the map

• Access: Monitor → Maps → Devices → Compare sensors button.
• Use: pick 2 to 4 sensors on the map or in the list, and a variable.
• Periods: 24 hours, 7 days or 30 days.
• Result: a chart with one series per sensor and a table with average, minimum, maximum, latest value and percentage of time within the comfort range.
• Availability: off by default. Enable it per client in Manager → client settings → Maps settings tab → Compare sensors from the map.

LoRaWAN gateways: setup in Manager and map layer

• Access: Manager → client settings → Devices → LoRaWAN Gateways. In Monitor, the LoRaWAN Gateways menu is a read-only view.
• Setup: configure the gateway and locate it by postal address, choosing among the results.
• List: EUI, name, network server, situation, location, coverage and the devices it hears.
• Map: in Monitor → Maps → Devices, the Layers control shows gateways and their coverage. Clicking a gateway shows its location, last activity, RSSI, SNR and the sensors it hears.
• Availability: part of gateway monitoring, which is off by default. Can be enabled per client on request; contact support.

Per-map options and custom menu names

• Access: Manager → client settings → Maps settings tab.
• Per-map options: each Monitor map (facilities, devices and alarms) has an Options button that groups its settings.
• Name in the Monitor menu: changes the name the map uses in the menu and on the Monitor home page. Leave it empty to keep the default name.

SMS usage

A screen to track how many SMS each client sends and how much of its quota is left.

• Access: Manager → [client] → Security → SMS usage.
• Content: messages sent, units used (a long SMS counts as several), contracted quota, percentage used, daily trend, breakdown by facility and failed attempts.
• Alerts: when a threshold is crossed, a banner appears and an email notice is sent. This only works when the client has a quota set.
• Quota: set by the platform administrator.

Improvements

• Intervention records: can store the household contact's name and email. Since this is personal data, it is off by default and enabled per client in Maps settings.
• Shorter SMS: the Google Maps link in SMS messages is shorter, so fewer messages get split in two.
• Timeline widget: better height distribution between the axis and the bars, and a horizontal axis when the historical-widget date format is enabled.
• Orbiwise: cancelling a pending command also removes it from the network server, and a new command replaces the pending one instead of being rejected.
• Parsers: when a decoding script fails, the network server no longer retries the same frame over and over.
• Performance: asset tracking details, facility loading and alarm queries.

API changes

• Last data timestamp: the Device entity adds LastDataDateTime, the time of the last stored data point, distinct from LastActivity (last communication).
• Incremental reads: /api/v2/endpointData/incremental/{seqFrom} and its per-device, per-facility and per-client variants are significantly faster.
• Camera images: DeviceService.GetCameraSnapshot now requires an accessToken and checks permission on the facility. Integrations that called it without a token must now send one.
• New services: SMSUsageService (GetSMSUsage, GetSMSClientQuota, SetSMSClientQuota, EnumSMSUsageDetail) and GET /api/v2/smsUsage?clientID=&period=yyyy-MM; AlarmService.EnumRecentAlarmActivity; DeviceService.EnumSensorComparisonVariables and GetSensorComparison.

Bug fixes

• Alarms: the alarm lifecycle list and the paged actions list returned an error on the first page.
• Severity column: showed the raw multi-language text, and its filter searched inside that text.
• Alert templates: a template with a threshold of 0 could not be created.
• Alarms screen: secondary buttons were not visible and two texts were always in English.
• Notification bell: no longer re-notifies every alarm when switching facility.
• Intervention records: a cost of 0 was saved as "not provided".
• Manager: the image picker showed a duplicate button.
• SMS usage: messages containing the degree symbol were over-counted, the period selector was off by a month in American time zones, and usage was not recorded for clients without a quota.
• Energy and flow metering: the duration of the first sample in each group was miscalculated. This was fixed and the history was recalculated.
• AI Copilot: the AI services returned a 404 error.
• Security: camera and simplified table widgets validate the token format.

Support

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