Cloud Dashboard
Monitoring
Monitoring lets you keep an eye on the temperatures in your stores – for example in fridges, freezers or the sales area. Shelly wireless sensors continuously measure temperature and humidity; the dashboard shows the status of all devices and alerts your team by email, SMS or push notification as soon as a threshold is breached or a sensor stops responding.
Note: Monitoring is included in the Pro plan.
All roles from Employee upwards can see the overview under Monitoring in the menu. Admin permissions are required for the settings (connection, alert channels, thresholds).
What you need
- Shelly temperature sensors that are available in Shelly Cloud – we recommend the Shelly BLU H&T ZB (temperature and humidity).
- A Shelly Cloud account in which the sensors are set up (Shelly Smart Control app).
- Your stores in the dashboard. Ideally, name the rooms in the Shelly app after the store's town or city – scango.ch then assigns the sensors automatically.
To use the Shelly BLU H&T ZB with the Shelly Smart Control app, a gateway is required. Compatible gateways include the Shelly BLU Gateway or any Shelly Plus, Pro, Gen3 or Gen4 device (excluding sensors). To use it in a Zigbee network, a compatible Zigbee gateway is required.
Set up monitoring

Open Settings → Organization and select the Monitoring tab. A status at the top shows how far the setup has progressed: Connected, Setup incomplete or Monitoring off.
- Switch on Monitoring enabled.
- Enter your credentials in the Shelly Cloud connection section:
- Server URI: hostname of your Shelly Cloud server, e.g.
shelly-58-eu.shelly.cloud. You will find it in your Shelly Cloud account details. - Authorization Cloud Key: You can find the Cloud Key in the Shelly Smart Control app or on the web under Settings → Home (field "Cloud Key"). Once saved, the key is no longer displayed; to replace it, simply enter a new one.
- History retention (days): how long the temperature history is kept (1–365 days, default 90).
- Server URI: hostname of your Shelly Cloud server, e.g.
- In the Alert channels section, define how your team is notified (see the "Alerts and recipients" section below for details).
- Click Save settings.
- Click Sync devices. The dashboard imports all temperature sensors from your Shelly Cloud. Use the same button later to add new sensors.
- If the Rooms without a store notice appears, a Shelly room could not be assigned to a store. Select the matching store and click Assign.
- Check the thresholds of each sensor in the Temperature sensors section and save them (see next section).
Thresholds and alert delay

In the Temperature sensors section, you define for each sensor when an alert is triggered:
Column | Meaning |
|---|---|
Device | Name of the sensor from Shelly Cloud, with the Shelly room below it. |
Store | Store the sensor belongs to. It determines who is notified in the event of an alert. |
Min °C / Max °C | Lower and upper temperature limit. |
Delay (min) | Alert delay (min): how long the temperature must stay below the minimum or above the maximum before an alert is triggered (5–180 minutes, default 30). |
Suggested | Suggestion for min, max and alert delay based on past readings, with Apply. |
Active | Only active sensors are monitored and trigger alerts. |
Why an alert delay? Fridges and freezers defrost regularly. During defrosting the temperature rises briefly above the normal range and then drops again. The delay prevents every defrost cycle from triggering a false alarm. Devices with long defrost phases need a higher value.
Using suggestions: The dashboard analyses up to 7 days of readings. The suggested thresholds lie ±2 °C around the normal temperature range (excluding defrost peaks). The suggested alert delay is the longest completed defrost phase plus 5 minutes, but at least 30 minutes. For new sensors, Not enough history yet is shown at first.
- Click Apply for a sensor, or use Apply all suggestions to apply the suggestions for all sensors.
- Adjust the values if necessary. Changed rows are marked as Unsaved.
- Save with Save in the respective row or with Save all.
💡 Set up new sensors with generous limits first and apply the suggestions after a few days – they will then be based on real readings.
Alerts and recipients
In the Alert channels section, enable the channels you want:
Channel | Settings |
|---|---|
Send email alerts (free of charge) | Alert email addresses (comma-separated): one or more addresses. |
Send SMS alerts (CHF 0.10 per SMS segment, see below) | Alert phone numbers (comma-separated, E.164): numbers in international format, e.g. |
Send ntfy alerts | Push notifications on phone or desktop via the ntfy app. ntfy topic: name of the channel your team subscribes to in the ntfy app, e.g. |
The recipients entered here are the default for all stores and for sensors without a store. Under Recipients per store you can use Edit to set your own recipients for individual stores. These fully replace the default for that store (email, SMS and ntfy). Reset returns the store to the organization default. Save changes with Save settings.
There are four alert types:
Alert | When | Channels |
|---|---|---|
Device not responding | The sensor is offline. | Email, SMS, ntfy |
Temperature below minimum | The temperature stays below Min °C for longer than the alert delay. | Email, SMS, ntfy |
Temperature above maximum | The temperature stays above Max °C for longer than the alert delay. | Email, SMS, ntfy |
Battery low | The battery has been below 20% for at least 30 minutes. | Email only |
As long as an incident continues and has not been acknowledged, scango.ch sends a reminder every 30 minutes, or once a day for low battery.
SMS costs and budget
SMS alerts cost CHF 0.10 per SMS segment (excl. VAT). A segment holds up to 160 characters, 70 with special characters such as umlauts; longer messages consist of several segments. Each number gets its own SMS. Test SMS are free.
SMS are billed with your subscription:
- With monthly or quarterly invoicing, the SMS of the period just ended appear as a separate line on the next subscription invoice.
- With yearly invoicing, you get a separate invoice for the SMS of past months as soon as they exceed CHF 20. Smaller amounts carry over to the next month; whatever is still open at the renewal appears on the renewal invoice.
The SMS card under Alert channels shows this month's SMS (segments and cost). Under Monthly SMS budget you can optionally set a budget in CHF. When the month's SMS cost reaches 50%, 75% and 100% of the budget, all owners and admins of the organization get one email each. The budget is a warning level, not a limit: alerts keep being sent by SMS above the budget, so no temperature alert gets lost.
Acknowledge an alert
Every alert notification includes an acknowledge link. SMS uses a short link. The acknowledge page shows the device, store and current readings. Acknowledging stops further reminders for that incident – until the sensor has returned to the normal range and goes outside the limits again.
Overview

Under Monitoring in the menu, you see all sensors as cards with the current Temperature, Humidity, Battery, the thresholds and a small temperature chart. A line at the top summarises how many devices are OK, in alert, offline or without data. Use the Store filter to show only the sensors of one store.
Status | Meaning |
|---|---|
OK | The sensor delivers readings within the thresholds. |
Alert | A threshold has been breached, showing since when. |
Offline | The sensor is not responding. |
No data yet | There are no readings for the sensor yet, e.g. right after syncing. |
The page refreshes automatically every 5 minutes. Refresh fetches the latest readings immediately.
Sensor history and alert history

Click History on a device card. The Sensor history dialog shows:
- the temperature history for 24h, 7d, 30d or 90d (as hourly values for longer periods) with the low, high and latest value,
- the Alert history: which alerts were sent in the selected period, through which channels, and whether they have been Acknowledged.
Copy link gives you a direct link to this sensor, for example to send it to a colleague.