Doors
| Door | I/O device / camera | Badges | People | Tailgates | Devices |
|---|---|---|---|---|---|
| Loading… | |||||
connecting…
NYC* names starting with NYC · *Lobby ending with Lobby · * all doors| Door | I/O device / camera | Badges | People | Tailgates | Devices |
|---|---|---|---|---|---|
| Loading… | |||||
Counts are for today (since midnight). Click a door in the table or the event list to show only that door. The address bar keeps your filter, so you can bookmark a view.
NYC* · *Lobby · blank = all doors| # | Door | Tailgates | Tailgates compared | People | Per 100 |
|---|---|---|---|---|---|
| Loading… | |||||
Pick a door in the table to see all of its tailgates. "Per 100" = tailgates for every 100 people the camera counted, so busy and quiet doors can be compared.
Readings are saved every few minutes (setting env_log_minutes). Limits, delays and the email list are on the Settings page; the sensors themselves are lines in the door file (water / temp). Dashed red lines are the alert limits.
| # | Door name | I/O device | I/O IP | Input | Output | Camera | Camera IP | Delay s | I/O user | I/O password | Camera user | Camera password | Alarm off from | Alarm off to |
|---|
Changes apply as soon as you save, without restarting. The old file is copied to the backups folder first. A blank password keeps the device's current one; a new one applies to every line of that device. Comment lines (#) in the file are not kept. A new device IP also needs the firewall rule (DEPLOYMENT.md). Sensors are lines too: I/O device water (I/O IP sequent:0, Input = the board input, Output = the environment alert relay) or temp (Input blank, Output = the same alert relay, Camera = sensor name, Camera IP = address, blank = 0x44); Door name = the room. One alert output for all sensors. Alarm off from / to: Monday to Friday, 24 h clock (e.g. 07:30 and 09:00); tailgates in that time are logged but the alarm output isn't pulsed and no email is sent. Leave both blank = alarm on 24/7.
| Username | Role | Added | Actions |
|---|