Skip to content

Monitoring Alerts ​

Use alerts to learn when conditions at a client site need attention. You can receive alerts on the Fugara dashboard, by email, or both.

Create a probe alert ​

  1. Link the automatic probe to a client in your active company.
  2. Open the client's Overview and choose Probe settings & alerts beside the probe. You can also open Settings & alerts from the client's Monitoring page, or Edit in Probe Fleet.
  3. Under Alerts for this company, choose Add alert.
  4. Give it a recognizable name, such as “Great chamber temperature.”
  5. Choose the measurement and limits or timing condition.
  6. Select the conditions you want to hear about, including Return to normal if wanted.
  7. Choose Dashboard, Email, or both, and select the recipients.
  8. Choose Save alerts.

You need edit access to a linked client to change its company alerts. Probe display and calibration settings can be changed by the probe's owner. Save alerts saves the alert rules separately from Save Probe Settings.

Clear Enabled to pause an alert without removing it. Remove alert, followed by Save alerts, stops future notifications from that rule.

Choose recipients ​

Leave the recipient list unselected to notify all active users in the company. To assign an alert, select one or more company users. Make company-wide clears the selection.

Recipients and delivery channels are set independently for each alert. For example, a chamber temperature alert could appear on everyone's dashboard, while a separate power alert goes to one technician by email.

Temperature, humidity, and pressure ​

Set a low limit, a high limit, or both. Choose Low and High to receive those notifications. Return to normal notifies you after an abnormal reading returns within the limits. A reading exactly at a limit is within the normal range.

Temperature and pressure limits use the probe's saved display unit: °C or °F, and inH2O or mmH2O. Humidity uses percent. If you change the probe's display unit, save that change before editing alert limits. Existing limits convert to the new unit and keep the same meaning.

For example, a temperature alert set to a high limit of 86°F becomes 30°C if you change the probe to Celsius.

Power probe alerts ​

Power probes offer these measurements and conditions:

  • Current and Estimated power: notify on low or high readings, with optional return to normal.
  • Power state: notify when power changes. For power-on, use a high limit of 0. For power-off, use a low limit of 1. Return to normal is the opposite power state.
  • Powered on too long: notify when the probe reports continuous power-on for the chosen number of minutes.
  • Powered during a time-of-day window: notify if power is on between the selected start and end times in the site's timezone. A window of 22:00 to 06:00 covers 10pm through 6am the next morning. The window repeats daily and follows local daylight saving changes.

Create two alerts if you want both a continuous-on duration and a time-of-day window. Turning power off clears either condition. A time-window condition also clears when the window ends.

A gap in probe readings restarts a duration timer that has not yet triggered. An existing duration alert stays active until power-off is confirmed.

Organ left on without input ​

For a linked Organ UI device, open the client's Overview, find Organ Monitoring, and choose Organ left-on alerts.

Set how many minutes the organ may remain powered on without input. Playing or using the organ resets this inactivity period. Ordinary uptime while the organ is being used does not trigger the alert.

Choose Combined organ state, Control power, or Blower power. If control and blower are monitored separately, choose the circuit you want to monitor. Select Return to normal to hear when input resumes or power turns off.

This alert needs current power and activity information from Organ UI. Missing activity information does not count as inactivity, and a lost connection does not clear an existing alert.

Organ UI also offers a standalone left-on alert for sites that do not use Fugara. Avoid enabling the same notification in both places if you only want one copy.

Review dashboard alerts ​

Monitoring alerts appears on your dashboard only when you have at least one dashboard alert. Unread alerts appear first. Choose Mark read to mark an alert as read for your account; other recipients keep their own read status.

Repeated readings in the same abnormal condition do not create repeated alerts. A new alert can occur after the condition returns to normal and becomes abnormal again. Alerts update as the device reports new information, so they may not appear immediately at a limit or time boundary.

Removing a rule does not remove alerts already received. Unlinking the device from every client in your company stops its company alerts.