Safety and security

Recipes for people who must be found, and places that must be watched. Two apps do much of this without any rule: Security Watch turns panic presses, after-hours presence and lost coverage into incidents for guards, and Fall and man-down detection asks the wearer and then tells the guards. The recipes say when to use those and what a rule adds.

A lone worker falls or stops moving

The question: A technician works alone in the plant room at night. If they fall, someone must know within a minute.

1. Give them a tag that reports movement (a MOKO PS101-M badge, or a worn tag the fall detector supports), and bind it to them as a person (People and assets).
2. Turn on Fall detection under System › Config, and set the rest places (their desk, the break room), where lying still is normal.
3. That is enough: the badge asks them, and if they do not answer, Security Watch opens a critical incident and alerts the guards.

What a rule adds: someone outside Omaya.

Part	Setting
Rule watches	The person, or the label Lone workers
Condition	Fall / man-down detected equal to fall, and a second condition or rule for man_down
Actions	SMS to the duty manager: {{entity.name}} may have fallen in {{zone.name}}; Locate badge now, so the position is fresh; Sound badge, so the person can be found by ear

Pitfall. A badge on a desk is a badge that "stopped moving". Rest places are how you keep false alarms down; add each place where the badge is normally put down.

A panic button that escalates

The question: Reception has a panic button. When it is pressed, the guards must know at once, and the manager if nobody responds.

1. Add it under Devices → Panic Buttons — the button, any press, and the people to page — and give it to the person or desk that carries it. It is a rule, so it is listed under Rules too.
2. Security Watch opens a critical incident on every press, sends it to the guards, and re-sends it until someone acknowledges.

For a channel Security Watch does not use, open the panic button as a rule (Open as a rule) and add an action: Telegram to the security group chat, or Webhook into your own control room.

Pitfall. A button that is not set up as a panic button only raises a warning, never escalated. Check Devices → Panic Buttons lists it. The evidence afterwards is Reports → Panic & Incident Response: time to acknowledge, time to attend.

An asset leaves where it belongs

The question: Wheelchairs keep ending up on other floors. Tell the porters when one leaves Level 2.

Part	Setting
Hardware	A tag on each wheelchair, bound to it as an asset; gateways on Level 2 and the floors around it
Rule watches	The label Wheelchairs (the Leaves a place card at the top of Add Rule starts this rule for you)
Condition	Entered / left a place equal to left, with the place set to the Level 2 venue
Repeat at most every	30 minutes (per wheelchair, on a label rule)
Action	Mini app notification to the porters: {{entity.name}} left Level 2, now in {{to_zone_name}}

The other way to say it is a home zone: give each asset its home on the Devices page, and Home Zone Status equal to not_in_home fires for any asset away from its own home, one rule for all of them. Where it went is on its Trail (Watching people and assets).

Pitfall. A tag that goes silent has not left. A flat battery is Device Status offline, a different rule.

Staff covered outside the building

The question: Our technicians visit other sites and drive between them. Their badges go quiet the moment they leave our gateways. Can we still see where they are, and know when they have left a site?

1. Bind each badge to its person (People and assets).
2. Ask your Omaya contact to switch Omaya Scout on for your organisation, with person tags published.
3. Each technician installs Omaya Scout on their own phone and leaves it scouting. Nothing to sign in to.
4. Open Monitor → Scout (phones) after their first trip: each technician should be Covered, with their phone beside their name. Anyone under No phone yet has not installed it, or has not been outside with it yet.
5. Draw a geofence round each site they visit (Space → Location → Map). Their phone-placed positions cross geofences like any GPS position, so Outdoor Activity, GPS Replay and geofence rules see them.

Part	Setting
Rule watches	The geofence Client site A (for any tag)
Condition	Geofence entered / left (GPS) equal to left
Action	In-App Alert to the dispatcher: {{entity.name}} has left {{geofence.name}}

Pitfall. A press of a panic button relayed by a phone does not page anyone: phones are not gateways you installed, so a relayed press is recorded but fires no rule. Outside the building, give a lone worker a tracker with its own SIM, or rely on their phone. A phone set to Battery saver reports every 5 minutes, so its trail is coarse; Live tracking is every 10 seconds.

A vehicle leaves the site

The question: Tell the fleet manager when a van leaves the depot outside working hours.

Part	Setting
Hardware	A GPS tracker in the van, bound to it as an asset
Before the rule	A geofence around the depot (Indoor and outdoor)
Rule watches	The geofence (for any tracker) or the van's tracker
Condition	Geofence entered / left (GPS) equal to left
Between	19:00 → 07:00, and Saturday and Sunday ticked
Action	WhatsApp or SMS to the fleet manager

Someone in a room after hours

The question: Is anyone in the server room, the store or the pharmacy after closing?

Part	Setting
Hardware	A radar (counts people without tags) or a PIR
Rule watches	The zone
Condition	People in Area (radar) greater than 0, or Sensor reading (any field) occupied Becomes 1 for a PIR
Between	Closing to opening (for example 20:00 → 07:00)
Repeat at most every	15 minutes
Action	In-App Alert to the guards, or Mobile app push

Security Watch does this for zones it watches and adds who was there, if they wore a tag. Use the rule for a room Security Watch does not watch, or for an outside channel.

A door left open

The question: The fire door at the loading bay is propped open. Tell someone when it has been open for 10 minutes.

Part	Setting
Hardware	A door contact: the MOKO S01P has one (door_open), as do the Milesight EM300-MCS and most Zigbee contacts through Home Assistant. Check the field name on the device's View panel
Rule watches	The door sensor
Condition	Sensor reading (any field) door_open equal to 1, held for 10 minutes
Repeat at most every	30 minutes
Action	Raise a work order (work type inspection), or In-App Alert to the guards

Keep a log too. A second rule on the same door, door_open Becomes 1, writing a row to a data table (Door openings: door device), gives "how often is this door opened, and when" as a custom report.