A template is a ready flow you copy and adapt. Hermetry’s templates come from the platform and from the ready solutions. Using one is the fastest way to get a correct root flow or a working notification flow.
Where to find templates
- Automation > Templates tab: every host’s templates, each with its host badge, a search box (Search the templates) and Use.
- New flow > Start from: the templates of the host you picked, or An empty flow.
Using a template creates a new flow with the template’s blocks. The new flow is yours: change it, deploy it, delete it. It is not linked to the template.
The templates
| Template | Host | What it does |
|---|---|---|
| Default root flow | IoT | The storage path every root needs: alarm rules, then telemetry and client attributes saved, device requests and other messages logged, errors logged. Start every profile root from it. |
| Water site: alarm notifications | IoT | Every alarm of a tank or a pump station that opens or clears is sent to the organisation’s administrators. |
| Remote sites: alarm notifications | IoT | Every alarm of a site controller or a UPS gateway that opens or clears is sent to the administrators. |
| Remote sites: UPS root | IoT | A root for UPS gateways: the default root’s storage path plus one watchdog per UPS unit; a unit that stops reporting its voltage for five minutes raises a “silent” warning until it reports again. |
| Sensor regions: alarm notifications | IoT | Every threshold, battery or offline alarm of a sensor or weather station that opens or clears is sent to the administrators. |
| Personnel tracking: alarm escalation | IoT | A tracker’s alarm (fall, motionless, SOS, help call, forbidden zone) is sent to the administrators when it opens, when an operator acknowledges it, and when it clears. |
Your organisation may see more templates when other modules are enabled.
How the alarm notification templates work
Device message (types: alarm; profiles: the solution's) → Switch on msg.metadata.alarm.transition
created → Notify (role ADMIN, urgency critical): "Alarm opened on <device>: <title> (<severity>)."
cleared → Notify (role ADMIN, urgency normal): "The alarm on <device> cleared: <title>."
acknowledged → Notify (personnel tracking only)The Notify blocks address the Admin role. Members reached through a role are told in the app, by push and in their linked chat apps, according to their preferences; a role does not reach them by e-mail or SMS. To send mail or SMS, add rows of the kinds address or phone with the addresses and numbers. See Alarm, command and notify blocks.
To adapt one:
- Use the template, then open the Device message block and pick your own device profiles under profiles (empty = every profile).
- Change the recipients, texts and urgency in each Notify block.
- Deploy.
How the UPS root works
The UPS root is a profile root: it replaces the tenant-wide root for the UPS gateway profile. Next to the storage path, for each unit:
Message type = telemetry → Switch "Carries ups_a_voltage" (nempty)
→ Watchdog (5 min, key msg.metadata.deviceId)
timeout → Raise alarm ups_a_offline (warning) "UPS A stopped reporting"
ok → Clear alarm ups_a_offlineUse the same pattern for any device that must report a key regularly. See Counters, statistics and watchdogs and the Flow cookbook.
Templates installed with a solution
When you install a ready solution, its flows are created on the solution’s device profiles (notification flows are stored switched off until you turn them on); the templates above are the same flows, offered for your own profiles. See Install a solution.
The seeded default root
The Default root flow is created and bound tenant-wide automatically when your organisation starts. It does not count toward your plan’s flows. When Hermetry publishes a newer version of it:
- a copy nobody edited takes the new version by itself, as a new version made by System;
- an edited copy is only offered the upgrade, with the list of changes. Applying it is a normal deploy by you.
If you delete the seeded root, it is not created again.
Flows built by modules
Rules-card rules run as flows the rules module builds and keeps. They appear in the list with a Built by badge and the Built by filter (A module (read-only here) or People (ordinary flows)). They are not templates. To change one in the editor, select Detach into an ordinary flow: “After the detach, … no longer changes it: it keeps running as it is, you edit it here like any flow, and it counts against your plan’s flows. This cannot be undone.”
Share your own flows
There is no “save as template”. To reuse a flow, Export it and Import it as a copy, in the same or another organisation. See Versions, testing and rollback.