Each site of the remote sites solution has a UPS gateway that reports two UPS units, A and B, and may have cameras. This page explains the UPS profile, the watchdog that notices a silent UPS unit, the UPS page and the Camera page.
Profile: Remote sites · UPS
The UPS gateway reports both units under keys with the unit’s letter. For unit A:
| Key | Label | Unit or values |
|---|---|---|
ups_a_charge | UPS A charge | %, 0 to 100 |
ups_a_voltage | UPS A voltage | V |
ups_a_temp | UPS A temperature | °C |
ups_a_status | UPS A battery status | A status word (below) |
ups_a_alarm | UPS A alarm code | An alarm word (below) |
Unit B uses the same keys with ups_b_. The profile also has lat and lng.
Status and alarm words
The battery status and the alarm code are text keys. The board shows them as coloured words:
ups_*_status | Shown as | Colour |
|---|---|---|
normal | Battery normal | Green |
connected | Battery connected | Green |
floating | Floating charge | Amber |
equalizing | Equalizing charge | Amber |
discharging | Discharging | Amber |
low_battery | Battery low | Amber |
self_test | Self test | Amber |
not_connected | Battery not connected | Red |
fault | Battery fault | Red |
ups_*_alarm | Shown as | Colour |
|---|---|---|
mains | On mains | Green |
battery_fault | Battery fault | Red |
discharging | Battery discharging | Amber |
low_voltage | Battery voltage low | Amber |
almost_empty | Battery almost empty | Red |
overheated | UPS overheated | Red |
supply_fault | Supply fault | Red |
overloaded | UPS overloaded | Red |
bypass_on | Bypass on | Amber |
bypass_fault | Bypass fault | Red |
A word the board does not know shows as Unknown status or Unknown code in amber. If your UPS reports numbers or other words, convert them in the profile’s root flow before they are stored; see Adapting a solution to your devices.
If your UPS speaks SNMP, Hermetry can poll it with the ready UPS template instead; its keys differ (battery.charge, output.source …). See SNMP templates.
Alarm rules
| Type | Severity | Condition | Debounce |
|---|---|---|---|
ups_battery_low | Major | ups_a_charge or ups_b_charge < 25 % (hysteresis 3) | 2 readings to raise, 2 to clear |
ups_fault | Major | Either unit’s status is fault or not_connected | 1 / 1 |
device_offline | Warning | The gateway sent nothing for 600 seconds |
The UPS watchdog
The gateway can stay online while one of its units goes silent. The flow Remote sites: UPS root notices that. It is a profile root for the UPS profile: it replaces the organisation’s root flow for UPS gateways only.
Device messages (Flow input) → Alarm rules → Message type
telemetry → Save telemetry
→ "Carries ups_a_voltage" → Watchdog (5 min, per device)
timeout → Raise alarm ups_a_offline (Warning) "UPS A stopped reporting"
ok → Clear alarm ups_a_offline
→ the same for ups_b_voltage / ups_b_offline
attributes → Save client attributes
rpc_request → System log
otherwise → System log
Errors → System log- A unit that sends no
ups_a_voltage(orups_b_voltage) for 5 minutes raisesups_a_offline(orups_b_offline) as a Warning. The next reading clears it. - The watchdog counts per device, so every UPS gateway has its own timer.
- In a full installation the flow is turned on and bound to the UPS profile. Keep its Save telemetry, Save client attributes and Alarm rules blocks: without them, UPS readings are no longer stored or checked.
To change the silence time, edit the Watchdog blocks. To use the pattern for other equipment, see Counters, statistics and watchdogs and Hosts, the root flow and profile root flows.
The UPS page
The UPS page opens from the UPS units tile of a site page. It finds the site’s UPS gateway through the FEEDS relation. For each unit:
| Card | Shows |
|---|---|
| UPS A charge | A bar: red below 25 %, amber below 50 %, green above |
| UPS A voltage | The voltage with “Updated … ago”: red below 200 V, amber above 245 V |
| UPS A temperature | Blue below 10 °C, green to 35, amber to 45, red above |
| UPS A battery status | The status word, No data without a reading |
| UPS A alarm code | The alarm word |
| UPS A history | Charge and voltage over the board window, on two axes |
| UPS A readings | Charge, temperature and voltage per time stamp, newest first, ten a page, export |
Below them, Alarms of the UPS units lists the gateway’s alarms; a row opens the alarm’s page.
If the page is empty, check that the UPS gateway has a FEEDS relation to the site controller (from the UPS to the controller). See Relations.
The Camera page
The Camera page opens from the Cameras tile of a site page and shows the site’s cameras live.
| Item | Behaviour |
|---|---|
| Which devices | The devices placed in the site’s asset whose profile connects by RTSP or by the supported camera protocol |
| Layout | A fixed grid of 4 video cards (2 × 2). Card n shows the n-th camera of the site, by name. |
| More than four | The count card “Cameras at this site (the first 4 are shown)” tells you; the fifth and later are not shown |
| A slot without a camera, or a camera without live view | Stays empty, with the player’s own text, never an error |
| Start | Never on its own: press play. Each running camera uses camera minutes. |
| Still watching? | Asked every 5 minutes; stops when the card is out of view |
| Higher quality | Offered when the camera has a second usable H.264 stream |
To show a camera on the page:
- Add the camera and turn live view on. See Add a camera or recorder and Live view.
- Place the camera device in the site’s asset. See Placing devices.
- If the camera’s profile was created after the solution was installed, edit the board’s hidden cameras parameter so that it includes that profile.
Watching needs the permission Watch the live picture of a camera and read access to the camera’s device. See Cameras on dashboards and Camera limits and privacy.
A board made from the template keeps the Camera page and its tile, but not the camera cards, because they read a relation. Add Video player cards yourself, bound to each camera’s liveUrl attribute.