Product Updates: Customizable Notification Templates & Catching a Stuck Sensor

Two problems, same release: what an alert actually says, and whether the data behind it is even still moving.

Customizable Notification Templates

Email and SMS notification templates can now be customized per solution - the subject line, the body copy, which fields show up and how they’re formatted. For an OEM running ExoSense under its own brand, this is where the wording of an alert stops sounding like a generic platform notice and starts sounding like the OEM’s own product talking. It’s also the groundwork for the custom email domain support that shipped a year later - that release let the sender look like the OEM’s own domain; this one already let the message read like it.

Alongside template customization, this release also added subsystem dashboards in template workflows and condition lifecycle notifications - alerts tied to a condition’s status changing (opened, acknowledged, resolved), not just a threshold tripping.

Catching a Stuck Sensor

A sensor that’s stopped working doesn’t always go offline. Sometimes it keeps transmitting - just the same value, over and over, because the source device or its firmware has frozen. A timeout rule won’t catch that, because data is still arriving on schedule. It just never changes.

The new Repeating Value rule watches for exactly this: a signal sending the same value repeatedly, with three ways to define what counts as “stuck” - a single repeat, a sustained duration at the same value, or a set number of repeats.

A pressure sensor reporting 42.0 PSI all week looks perfectly healthy on a dashboard - right up until someone notices the pump it’s mounted on has been off for three days.

Full release notes: 2024 archive, v2.46.7 and v2.46.3. Rules documentation: Rules - Exosite Documentation.

Want your alerts to sound like your product? Schedule a Demo.