Event types and channels
Every event type IoTFlows watches for, what fires it, its threshold, and the channels it can be delivered through.
An event type is one named condition on one machine, such as Device Offline. There are ten of them, the list is fixed, and every machine carries all ten. You switch them on per machine in Event Notifications, see Set alert rules for a machine.
This page is the lookup. It reproduces the matrix as the modal ships it, so you can check a default or a device restriction without opening a machine.
Event types
The key in the first column is the identifier IoTFlows uses internally. It never appears on screen, but support quotes it, and it is the only unambiguous way to name the two Machine Down rows apart.
| Key | On-screen title | Section | Description on the row | Severity |
|---|---|---|---|---|
aet_downtime_warning | Machine Down | Machine Status | Triggered when asset stops running for specified duration | WARNING |
aet_downtime_critical | Machine Down | Machine Status | Triggered when asset stops running for specified duration | CRITICAL |
aet_machine_up | Machine Up | Machine Status | Get notification once asset is running again | None |
aet_offline_warning | Device Offline | Connectivity | Triggered when the device loses internet or power | None |
aet_shock_critical | Abnormal Shock Detection | Shock Events | Get notification once asset experiences abnormal shocks | None |
aet_health_score_caution | Caution Health Alert | Health Score | Triggered when health score falls below 60% | CAUTION |
aet_health_score_warning | Warning Health Alert | Health Score | Triggered when health score falls below 40% | WARNING |
aet_health_score_critical | Critical Health Alert | Health Score | Triggered when health score falls below 20% | CRITICAL |
aet_temperature_warning | Warning Temperature | Temperature | Triggered when temperature exceeds warning threshold | WARNING |
aet_temperature_critical | Critical Temperature | Temperature | Triggered when temperature exceeds critical threshold | CRITICAL |
Severity is the seriousness IoTFlows assigns the event, drawn as a colored chip reading CAUTION, WARNING or CRITICAL. Where a row has one, the chip replaces the title instead of sitting beside it. That is why the modal shows no visible heading for the two Machine Down rows or the three health rows: you identify them by the chip and the description. The health score behind the last group of three is explained in Monitor machine health and vibration.
Channels
Every event type offers the same six channels, with no exceptions, so this table is a uniform yes. What differs between channels is who they reach and where the setting lives.
| Channel | Column header | Reaches | Scope |
|---|---|---|---|
| The event type's email subscribers | Per person | ||
| Push | PUSH | The event type's push subscribers, on the mobile app | Per person |
| SMS | SMS | The event type's SMS subscribers, who each need a verified phone number | Per person |
| Log | LOG | Nobody. It records the event on the machine's Health tab | The whole machine |
| Work order | WORK ORDER, sub-labeled Maintenance | The maintenance board. The work order arrives unassigned | The whole machine |
| Integrations | INTEGRATIONS, sub-labeled Webhooks | The chat integrations you attach to that row | The whole machine |
Channels by event
| Event | Push | SMS | Log | Work order | Integrations | |
|---|---|---|---|---|---|---|
| Machine Down (warning) | Yes | Yes | Yes | Yes | Yes | Yes |
| Machine Down (critical) | Yes | Yes | Yes | Yes | Yes | Yes |
| Machine Up | Yes, coupled | Yes, coupled | Yes, coupled | Yes | Yes | Yes |
| Device Offline | Yes | Yes | Yes | Yes | Yes | Yes |
| Abnormal Shock Detection | Yes | Yes | Yes | Yes | Yes | Yes |
| Caution Health Alert | Yes | Yes | Yes | Yes | Yes | Yes |
| Warning Health Alert | Yes | Yes | Yes | Yes | Yes | Yes |
| Critical Health Alert | Yes | Yes | Yes | Yes | Yes | Yes |
| Warning Temperature | Yes | Yes | Yes | Yes | Yes | Yes |
| Critical Temperature | Yes | Yes | Yes | Yes | Yes | Yes |
What does "coupled" mean on Machine Up? Switching Machine Down at the warning time off on a channel also switches Machine Up off on that channel, and disables its switch until you turn the warning row back on. The coupling runs one way and off only. Turning the warning row on does not turn Machine Up on.
Turn Log on for every event type you care about, including ones you want no notification for. It costs nobody's attention and it is what makes the event countable later, see Review and dismiss machine events.
You do not need Integrations to get alerts. Email and push work with nothing configured beyond a subscriber list, and an integration is worth creating only once a team is already watching a Slack, Teams or Discord channel, see Send alerts to Slack, Teams, or Discord.
Thresholds and defaults
A threshold is the number the condition is measured against. Six of the ten event types take one you can edit, three show a fixed percentage, and one has none.
| Event | Field label | Unit | Default | Editable | Limits |
|---|---|---|---|---|---|
| Machine Down (warning) | Time threshold | min(s) | The machine's own downtime alert time | Yes | Whole minutes, 0 or more |
| Machine Down (critical) | Time threshold | min(s) | The machine's own downtime alert time | Yes | Whole minutes, 0 or more |
| Machine Up | None | — | — | — | — |
| Device Offline | Time threshold | min(s) | 10 | Yes | Whole minutes, 0 or more |
| Abnormal Shock Detection | Vibration threshold | g | 100 | Yes | 20 to 100, in steps of 1 |
| Caution Health Alert | Threshold | % | 60 | No | Shown for reference, no input |
| Warning Health Alert | Threshold | % | 40 | No | Shown for reference, no input |
| Critical Health Alert | Threshold | % | 20 | No | Shown for reference, no input |
| Warning Temperature | Temperature threshold | °C or °F | 70 °C (158 °F) | Yes | Stored in whole °C, rounded on conversion |
| Critical Temperature | Temperature threshold | °C or °F | 80 °C (176 °F) | Yes | Stored in whole °C, rounded on conversion |
Four details a lookup has to carry:
- The shock threshold is stored on the sensor, not on the rule. Changing it writes to the device, so every reading the device reports afterward is judged against the new number, and the confirmation reads Shock Acceleration Threshold has been changed rather than the Threshold updated every other row shows.
- The two Machine Down defaults come from the machine, not from a constant, so a machine whose downtime alert time has never been set starts both rows at 0.
- The temperature unit is a preference of the browser you are in, not of your account. A colleague opening the same machine may see the other unit.
- Thresholds save on blur. Type the value, then click outside the field and wait for the confirmation.
Critical must be higher than warning. Set a critical temperature below the warning one and a red line reads Critical must be higher than warning. It does not block the save. Both values are written as typed, and the critical alert then fires before the warning alert.
Availability by device
The modal hides the sections the device cannot produce, so two machines in the same organization do not offer the same event types.
| Section | SenseAi | SenseAi Embedded | BeamTracker |
|---|---|---|---|
| Machine Status | Yes | Yes | Yes |
| Connectivity | Yes | Yes | Yes |
| Shock Events | Yes | Yes | No |
| Health Score | Firmware 5 or later | Firmware 5 or later | No |
| Temperature | Firmware 5 or later | Firmware 5 or later | No |
A BeamTracker counts units passing a point rather than reading a machine's own vibration, so it produces no shock, health or temperature reading and its modal is two sections long. A SenseAi below firmware 5 keeps shock but loses health and temperature.
If an event type is missing, check the device before you check anything else. It is the reason far more often than a permission is. To move a machine off firmware below 5, see Get support.
Subscriber lists
Email, push and SMS do not reach "the machine's watchers". Each of those three channels on each of the ten event types carries its own list, so one machine holds thirty independent lists.
A subscriber is one member signed up to one channel on one event type on one machine. Subscribing someone to Machine Down tells them nothing about Device Offline on the same machine.
| Question | Answer |
|---|---|
| Who edits the list | Owners and Administrators, see Roles and permissions |
| What everyone else sees | The same three columns as plain switches, subscribing only themselves |
| What an empty list does | Nothing, silently. The channel is on and the alert reaches nobody |
| Why a member cannot be added to SMS | No verified phone number, listed as No phone number, or listed as Opted Out, see Change your phone number |
| Whether the list follows the person across machines | No. Lists are per machine |
An empty subscriber list is the single most common cause of an alert that should have fired and did not, see Troubleshoot alerts you did not receive.
See also
Post IoTFlows events to an HTTPS URL you control. Add a hosted endpoint under Organization Settings with its URL, description and the signing secret you choose, subscribe it to the events your system acts on, and send each event's real test payload to your URL before you write the handler. The selectable event list is served by IoTFlows and read off the screen, so this page shows how to read it rather than reproducing it.
Symptom, cause and fix for an alert that should have fired and did not. Work the delivery path in order: confirm the event fired by turning Log on and reading the machine's Event Alerts list, then the channel switch on that machine's rule, then that event type's subscriber list, which is empty more often than anything else, and only then the destination. Also covers push that stops after an Android sign-out, SMS to a member with no verified phone number, a chat integration whose webhook was revoked, a rule that fires too often, and an event type the device type does not offer.