Vigilynx User Guide

About This Guide

This guide covers VigiLynx™, Veea’s platform for connecting, protecting, and operating every business location, and the two applications that make up its physical-operations side: IoT Pulse and VeeaVision AI.

The IoT Pulse section is a walkthrough of the day-to-day IoT Pulse workflows: creating locations, enrolling devices, reviewing device details, configuring monitoring rules, triaging alerts, and using analytics. The VeeaVision AI section is a walkthrough of the initial setup, configuration and use of VeeaVision AI, from logging in for the first time to configuring cameras, alerts, and storage. The About VigiLynx section at the start explains how the two applications fit together and when to use which one, and the VHM Mobile App section at the end covers working with both from your phone instead of the browser-based Veea Control Center.

Whether you’re setting up a new site or just need a refresher on where something lives, this manual is built to be read top to bottom or jumped into at whatever chapter you need via the Table of Contents below.

Table of Contents

• About VigiLynx™
  • The Two VigiLynx Applications
  • When to Use Which One
• IoT Pulse
• Chapter 1: Application Overview
  • What is IoT Pulse?
  • Accessing IoT Pulse
  • Provisioning IoT Pulse for First-Time Use
  • Where to Find Things
  • Settings and Alerts
• Chapter 2: Home Page
  • What’s on the Page
  • Activity Stream
  • Priority Watchlist
  • Where to Start Each Day
• Chapter 3: Create and Manage Locations
  • Why Create a Location First
  • How to Create a Location
  • Additional Locations Features
  • The Individual Location Page
• Chapter 4: Devices
  • How to Enroll Devices
  • Individual Device Pages
  • Individual Device Home Page & Overview Tab
  • Activity Tab
• Chapter 5: Camera Functionality
  • Opening a Camera’s Device Page
  • Camera Overview Page
  • Video Dashboard
  • Video Evidence
  • Activity, Rules and Data Tabs
  • Edit Device (Camera)
• Chapter 6: Assets
  • Creating a New Asset
• Chapter 7: Rules & Alerts
  • Configure Monitoring Rules
  • What a Rule Consists Of
  • Review, Acknowledge, and Resolve Alerts
  • The Alert Inbox
  • How to Triage an Alert
• Chapter 8: Analytics
  • Analytics Home Page (Overview)
  • Analytics Categories
  • How to Use Analytics Day to Day
• Chapter 9: Qualified Sensors & Peripherals
• Chapter 10: Troubleshooting
• Chapter 11: Glossary
• VeeaVision AI
• Chapter 12: Introduction
  • What is VeeaVision AI?
  • Prerequisites
  • Access Requirements
  • Accessing VeeaVision AI
  • Provisioning VeeaVision AI for First-Time Use
  • Getting Started
• Chapter 13: Interface & Features
  • Understanding the Interface
  • Live Dashboard
  • Live View
  • Alerts
  • Time-Lapses
  • Video Recordings
  • Detection Timeline
  • Red Zone Monitoring
  • People Count
• Chapter 14: Settings
  • Settings Overview
  • Location Configuration
  • Camera Management
  • Notification Configuration
  • Storage Management
  • Cloud Settings
  • Analytics Policy
• Appendix A: Initial Setup Checklist
• VHM Mobile App
  • VHM Mobile App vs. Veea Control Center

About VigiLynx™

VigiLynx™ is Veea’s platform for connecting, protecting, and operating a business location. It brings secure connectivity, cybersecurity, cameras, sensors, incident handling, operating history, and remote management together in one expandable system. Instead of a site that depends on a separate router, firewall, Wi-Fi system, camera recorder, IoT gateway, and remote-access box (each with its own login, vendor, and support number), a VigiLynx site runs as one managed environment with a single policy model and a single service owner.

Figure: A typical site’s disconnected tools versus a VigiLynx site

VigiLynx runs on the VeeaHub, a compact edge platform installed at the location. One VeeaHub handles wired or 5G broadband, managed Wi-Fi, network segmentation, threat controls, sensor and camera services, and local applications. SecureConnect gives every endpoint (payment terminals, staff devices, guests, cameras, and sensors) its own governed security profile, so guests stay isolated from payment systems and unknown devices are held until an operator approves them. As the site grows, additional VeeaHub units mesh into the same managed site, and optional edge AI accelerators can be added when a use case needs heavier on-site inference.

The Two VigiLynx Applications

The physical-operations side of VigiLynx is delivered through two applications. Both run against the same Sites in the Veea Control Center and the VHM Mobile App, and both contribute to the same asset-centered record of what happened at a location, where it happened, and how the team responded.

• IoT Pulse is the operations control room for sensors and assets. It organizes locations, devices, assets, monitoring rules, alerts, and analytics, and turns raw readings (temperature, humidity, door contact, motion, leak, power) into actionable incidents. Cameras appear in IoT Pulse as evidence sources: live preview, snapshots, and short clips that attach to an alert.
• VeeaVision AI is the AI-powered video application. It handles full camera management, live view, recordings and time-lapses, AI detection of people, vehicles, and safety equipment, red zone monitoring, people counting, recording storage (local or cloud), and notifications through email, SMS, megaphones, and strobes.

In short: if the question is about the condition of an asset or a space, start in IoT Pulse. If the question is about what the cameras saw, or how the cameras record and store video, go to VeeaVision AI.

Figure: How IoT Pulse and VeeaVision AI feed the same VigiLynx asset workflow
 

When to Use Which One

Use the table below to decide which application to open for a given task. Most sites use both: IoT Pulse for sensors and the asset record, and VeeaVision AI whenever the cameras need to do more than supply evidence for an alert.

IoT Pulse

Sensors, assets, locations, monitoring rules, alerts, and analytics.

Chapter 1: Application Overview

What is IoT Pulse?

Like the SecureConnect service, IoT Pulse is part of VigiLynx™. Veea’s VigiLynx solution consists of one compact platform for connectivity, security, cameras, sensors, local services, policy, and remote operations. IoT Pulse organizes operational data around locations, devices, assets, rules, alerts, and analytics. Think of it as the control room for everything your IoT devices are doing - from the moment a device is enrolled to the moment an alert gets resolved.

Accessing IoT Pulse

When logged into the Veea Control Center, first choose the Site you wish to manage. You will see the IoT Pulse application listed in the lefthand navigation pane. Simply click to enter.

Provisioning IoT Pulse for First-Time Use

If your organization hasn't been provisioned for IoT Pulse yet, you'll still see the link for it listed in the lefthand navigation pane. Clicking the link takes you to a request form to sign up for VigiLynx (the combination of IoT Pulse and VeeaVision AI). The form walks you through three quick steps: your contact details (name, company, business email, phone), a few questions about your organization (business type, number of locations, and VeeaHubs per location), and your equipment needs (cameras per location, the best time for a specialist to call you, and the sensor types and quantities you're interested in.

Once you submit the form, you'll land on a summary screen acknowledging your request:
 

Where to Find Things

The left navigation is your map. It provides access to the major work areas, while the main workspace changes based on the location or device you've selected.

Settings and Alerts

At the upper right, there are icons that allow you to:

• Choose your preferred language
• View active alerts
• Access Settings to configure branding, logo, notifications

Chapter 2: Home Page

The Home page is a a single screen that pulls together the status of every location, the most attention-worthy issue right now, and a live feed of what your devices are reporting.

What’s on the Page

At the very top, the Operations Overview banner gives you the one-line version of an overall status (Critical Attention, Attention Needed, or Normal), how many locations are active, how many alerts are currently open, and when the last report came in.

Below that, the page splits into two halves:

• Operational focus - a spotlight card for whichever location most needs your attention (or the one you last viewed). It shows the location name, its status badge, devices watched vs. online, how many need attention, active alert count, and the three most recent readings from that site - plus Open This Location and View All Locations buttons to jump straight in.
• Live location map - a map view with a pin for every location, color-coded by status, and a popup card for whichever one is currently in focus.

Activity Stream

Underneath the map sits the Activity Stream: a running feed of the most recent events across every location, not just the one you're focused on. Each row shows what happened (current draw, energy total, power draw, temperature, humidity, a captured video snapshot, and so on), which location and device it came from, the reading itself, and how long ago it happened. Click View Activity to open the full log.

Priority Watchlist

Below the Activity Stream is the Priority Watchlist: a card for every active location, each showing its status badge (Critical Attention, Attention Needed, or Normal), the most relevant issue or last activity, and its online/alert counts. Filter chips in the top-right (for example, "1 critical," "1 attention," "2 normal") let you see the breakdown without reading every card. An Open Location Directory button takes you to the full list when you need more than the watchlist shows.

Where to Start Each Day

Because Home aggregates everything, it's the natural first stop: scan the Operations Overview banner and Priority Watchlist for anything flagged critical or needing attention, then use Open This Location to drill into the site that needs you most - or check Live Activity if you just want a pulse on what's happening right now.

Chapter 3: Create and Manage Locations

A location is the workspace that groups a hub, devices, assets, monitoring rules, and analytics. Here's why it comes first, and how to set one up.

Why Create a Location First

Create the location first so discovered devices can be enrolled into the correct context. Without a location, there's nowhere for a newly discovered device to “live.”

How to Create a Location

Procedure

1. Navigate to the Locations page (found on the lefthand navigation pane)

2. Select the Create Location button at the upper right.

   
    

3. Enter the VeeaHub serial number. This establishes the Zigbee source and MQTT topic path for the workspace.
4. Enter the location name and choose the location type.
5. Optionally enter address, city, state or region, postal code, and country metadata.
6. Save the location and continue to the Devices & Assets tab to enroll devices or create assets.

Additional Locations Features

At the top, a search bar lets you filter the directory by name, and a summary row gives you three running totals: how many locations match your current search, how many alerts are open across all of them, and how many devices are being watched in total.

Below that sits the locations table, showing:

• Location (with connectivity state)
• Status
• Alerts
• Last Signal (how recently that location reported in).

Locations that need attention show their specific issue in the row - for example, "Local network connectivity unavailable" or "Power level exceeds 75W"

The Map and Map Intelligence Panel

To the right of the table is a live map with a pin for every location, plus a Map Intelligence panel underneath it. Here, IoT Pulse compares active alerts, how fresh each location's signal is, and whatever you've selected on the map, so you can quickly land on the location that might need action. You can also select any location on the map to quickly access it.

The Individual Location Page

Selecting a location from either the locations table or map takes you to its dedicated detail page - everything specific to that one site.

Every location page is organized into four tabs:

• Overview - the location's summary view
• Devices & Assets - every device and asset registered at this location
• Rules & Alerts - monitoring rules and alerts scoped to this location
• Maintenance Schedule - upkeep and service scheduling for this site

Devices & Assets Tab

This is usually where you'll spend the most time. At the top, Add Device and Add Asset buttons let you register a new device at this location, right next to a summary row showing total assets, active alerts, and reachable devices.

You can toggle your device list by “Device View” or “Asset View”. Asset View gives you additional details for each devices including Rules that may be in place.

The device list shows the device name and thumbnail, its type (for example, RTSP Camera), connection protocol, online status, signal quality, and when it was last seen, plus a menu of per-device actions. Devices that haven't been assigned to an asset yet are flagged with an "Unassigned Asset" tag.

Chapter 4: Devices

The Devices page displays every device across all locations in one view.

At the top, an Add Device button lets you register a new device. Below it, the filter bar gives you a search box plus three dropdowns - All Locations, All Status, and All Types with a Clear Filters button to reset everything at once.

The device list itself is grouped by health, and devices needing attention appear first, in a red-tinted section showing exactly what's wrong (for example, "Connectivity Lost"), which location they're at, and how long they've been in that state. Healthy devices follow underneath in a green-tinted section.

Each row shows: device name and thumbnail, location, device type, connection protocol, status, signal quality, and when it was last seen, plus a per-device action menu.

How to Enroll Devices

The Add Device wizard reads configured bridge connections and displays discovered Zigbee candidates. You can enroll devices individually or in bulk.

First, select “Add Device” from the Devices page or from a Location’s Devices & Assets tab.

Next:

1. Confirm the selected bridge/location context at the bottom of the wizard.
2. Review each device card, including manufacturer, model, capability tags, and external/IEEE identifier when available.
3. Select one or more eligible candidates, or use Select devices for bulk enrollment.
4. Devices already enrolled in another location appear disabled with an assistance message and are skipped by bulk enrollment.
5. Choose Enroll Devices, or use the Enroll button on an individual device card.

6. Use Enable Pairing Mode only when the physical device is not already listed.

   

Good Practices to Follow
 

• Confirm that the wizard is opened for the intended location before enrolling devices.
• Use the IEEE/external ID to confirm the physical Zigbee device identity.
• After enrollment, the device should disappear from the eligible list for the current location.

Once devices are enrolled, where do you go to actually see what they're doing? Device detail pages are the answer - they provide the current normalized state, status cards, device metadata, and tabbed access to activity, rules, and data.

Individual Device Pages

Clicking into any device, whether from the global Devices page or a location's Devices & Assets tab, takes you to its detail page: everything known about that one device, organized into four tabs.

• Overview: for live state and summary cards.
• Activity: to inspect state changes, alerts, and operational events.
• Rules: to see monitoring rules tied to the device.
• Data: to inspect the normalized device model and raw telemetry fields.

Individual Device Home Page & Overview Tab

Activity Tab

You can scan the timeline for the state change or event that explains what happened, and when.

Chapter 5: Camera Functionality

Like any other in IoT Pulse, cameras are listed, and organized the same way covered in the Devices chapter. What's different is what you'll find once you open up a camera's device page. Within is a live video feed, on-demand capture controls, and an evidence gallery that other device types don't have. This chapter walks through that camera-specific experience end to end.

Opening a Camera’s Device Page

You reach a camera's device page the same two ways you'd reach any device: from the global Devices page, or from a location's Devices & Assets tab. Each camera row shows its hardware ID, location, device type (RTSP Camera), connection protocol, online status, signal quality, and when it was last seen. Click the row itself to open the device page.

Camera Overview Page

The Overview page is what you land on when you open a camera. At the top, you'll see:

• the camera's hardware ID
• its location and asset assignments
• model and system
• three status cards: Status (Online/Offline), Evidence and Last Verified (how long ago IoT Pulse last confirmed the stream was reachable).
• a live video preview from the camera
• a button to launch the video dashboard showing all camera streams at this Site

Video Dashboard

The Video Dashboard is a full-screen, multi-camera live view for the entire Site. It’s useful for when you want to monitor several cameras side by side rather than one at a time. Each feed in the grid view is labeled with its hardware ID and a LIVE badge (indicating Status), and an Exit button in the top right returns you to the device page.

Further down the Camera Overview Page, you’ll find a Video Evidence section and tabs for Activity, Rules and Data.

Video Evidence

As shown above, a camera's Video Evidence panel is where you can pull footage from the camera on demand or let IoT Pulse do it automatically.

Manual capture lets you click Capture Snapshot to grab a still from the live feed right now, or Save a Clip to record a short clip. The clip length is adjustable via the Clip Duration field next to it.

Scheduled captures can be turned on to have IoT Pulse pull a low-frequency snapshot automatically, which is useful for giving an asset a visual history even when it doesn't have a live stream running constantly. You can set how often a capture is taken (for example, every 60 minutes) and how many to retain (for example, the last 12).

Evidence history appears below the capture controls in the Captures and Clips gallery, showing everything captured so far, each with a timestamp and Export or Delete actions. Use Browse by Date to jump to a specific day rather than scrolling the full history.

Activity, Rules and Data Tabs

The remaining three tabs at the bottom of a camera's device page work the same way they do for any device, but are worth calling out for what they surface on a camera specifically.

Activity Tab

Activity logs capture events as operational evidence. For example, this could be a "Video Snapshot Captured" entry each time a manual or scheduled capture runs, filterable by 24h, 7d, 30d, or all time. A separate Command History section tracks any remote commands sent to the device.

Rules Tab

Rules is split into two halves.

• Alerts with evidence from this camera lists any alert history where this camera's footage was attached, filterable by All, Open, Acknowledged, and Resolved.
• Rules using this camera as evidence lists the monitoring rules configured to attach this camera's footage when they fire. Use Create Rule in the top right to configure a new one. See the Rules & Alerts Chapter for detailed information on rule creation.

Data Tab

The Data Tab shows the camera's normalized device model, its current Status, Telemetry, Events, Health, and Last Sample alongside the raw Normalized JSON (with a Copy/Export option) and a Retained History card. IoT Pulse can reconnect past readings, activity, and raw payloads to this hardware ID even after the device is unenrolled or re-paired.

If you ever need to double-check how a camera's raw data is being interpreted, the Mapping Review screen shows exactly how IoT Pulse translates the camera's raw payload into its canonical model, field by field. It reports how many fields are mapped, need review, or are unmapped, and displays the Raw Payload and Canonical Snapshot side by side so you can compare them directly. Click Save Mapping once you're satisfied the mapping is correct.

Edit Device (Camera)

Click Edit Device from the either the main Devices page or from the Camera’s Overview tab to open the camera's configuration screen.

At the top, you can update the Custom Name, its Location, and the Asset/monitored item it's assigned to, or leave it unassigned.

Below that, the Camera Stream section is where the actual connection lives: choose the Stream Protocol (RTSP or HTTP MJPEG) and enter the Stream URL, toggling Credentials in URL if the username and password are embedded directly in that URL rather than entered separately. An optional Capture URL can be set for a static image address, used for faster still captures than pulling a frame from the live stream.

Further down:

• Username and Password fields are also available if your camera requires them separately from the stream URL.
• Monitoring Role controls how IoT Pulse treats this camera for rule purposes, "Auto by device + asset," lets the system decide based on context.
• Tags let you label the device for search and filtering
• Notes is a free-text field for anything an operator should know.
• Image URL lets you set a thumbnail for the device card, either by path or by uploading your own file.
• Click Save Device to apply your changes.

Chapter 6: Assets

As opposed to individual devices, Assets can be place or an object - for example: a room, a piece of equipment, a storage closet, a refrigeration unit. An asset groups one or more devices under a single named entity so you can monitor and set rules for the real-world thing they're watching, rather than tracking each device separately.

For example, a “Medicine Refrigerator” asset might combine a temperature and humidity sensor with a door sensor and a smart plug, so all three report together under one name and can share a single monitoring rule. For instance, alerting if the temperature drifts out of range while the door has also been open too long.

On the locations page, select an individual location, and you’ll see you can toggle between a list of that location’s devices and assets:

Creating a New Asset

1. From the Locations page, open the location you want to add an asset to.
2. On the Devices & Assets tab, toggle the view to Asset View, then select Add Asset at the upper right.
3. In the Create Monitored Item panel, give the asset a clear name describing what it represents, and optionally set a Type, Notes for other operators, and Tags to make it easier to find later.
4. Under Assign Devices, select the device or devices that belong to this asset. Devices already assigned elsewhere show which location they're tied to, so you can confirm you're not duplicating an assignment.

5. Select Create Asset to save.

   

Once created, the asset appears in Asset View alongside your others, each showing its device count, active rule count, reachability, and overall status. From there, expand the Rules and Devices sections to see what's attached, or use Add Rule and Edit to build a rule scoped to the whole asset or update its details.

Chapter 7: Rules & Alerts

The Rules & Alerts page displays a list of active alerts and allows you to create rules that trigger those alerts.

Select the “Rules & Alerts” section in the lefthand navigation pane.

Configure Monitoring Rules

A rule is how IoT Pulse turns a raw reading into something actionable. You can create a new rule that is scoped to exactly the condition you care about by selecting the “Add Rule” button at the upper right.

Clicking Create Rule launches a six-step guided flow, Target → Compatible Rule → Condition → Schedule → Delivery → Review

What a Rule Consists Of

Rules define which condition IoT Pulse watches, when the rule is active, how often it can fire, and what response should happen. Get the Condition and Schedule right, and the rest is about making sure the right people see the alert when it triggers.

Review, Acknowledge, and Resolve Alerts

When a rule fires, where does that alert go, and how do you work it? This chapter walks through the alert inbox from open to resolved.

The Alert Inbox

The alert inbox is the operator's triage center. It separates active incidents from acknowledged and resolved history, so you always know what still needs attention.

How to Triage an Alert

Procedure

1. Open Rules & Alerts.
2. Use All, Open, Acknowledged, and Resolved filters to narrow the alert list.
3. Select an alert to open the detailed view.
4. Review severity, current state, monitoring rule, timeline, and any media evidence.
5. Acknowledge the alert when investigation starts.
6. Resolve the alert when the incident is complete or the condition has cleared.

Selecting an alert brings up the Alert Details view

Chapter 8: Analytics

The Analytics section shows you what's been happening in your environment over time. A summarized view of device performance allows you to spot compliance issues, stale reporting or unusual trends.

Analytics Home Page (Overview)

Analytics summarize sensor performance over time so operators can spot compliance issues, stale reporting, or unusual trends.

Analytics Categories

As you scroll down the Overview found on the Analytics landing page, you will find categories for:

• Overall Summary
• Location
• Device
• Environment

On the Alerts & Policies tab, you will find Analytics categories for:

• Alert Activity
• Alert Frequency
• Alert Severity
• Alert Category
• Policies Triggered
• Policy Status
• Response Activity
• Recent Actions

Accessing the Alerts & Policies Tab (below)

How to Use Analytics Day to Day

• Use summary cards for current averages and recent changes.
• Review tracked sensor counts to confirm expected devices are reporting.
• Use charts to compare readings across the selected time period.
• Investigate large gaps or flatlines by opening the associated device Activity tab.

Chapter 9: Qualified Sensors & Peripherals

IoT Pulse is designed to be an open platform, with broad support for Zigbee and Wi-Fi devices across multiple manufacturers. The table below lists the devices that have completed qualification testing to date.

Chapter 10: Troubleshooting

Below is a list of issues you may encounter, along with the likely cause and how to address it.

Chapter 11: Glossary

Below are some terms that are referenced throughout this guide:

VeeaVision AI

AI-powered camera monitoring, recording, video analytics, and storage.

Chapter 12: Introduction

Before diving into the settings pages, let's cover what VeeaVision AI actually does, what needs to already be in place, and what you'll need on hand to get started.

What is VeeaVision AI?

Like the SecureConnect service, VeeaVision AI is part of VigiLynx™. Veea’s VigiLynx solution consists of one compact platform for connectivity, security, cameras, sensors, local services, policy, and remote operations.

VeeaVision AI is an intelligent construction site monitoring system. In short, it gives you:

• Real-time video surveillance from multiple cameras
• AI-powered detection (people, vehicles, safety equipment)
• Automated alerts for safety violations
• Video recording and timelapse capabilities
• Multi-language support

Prerequisites

IMPORTANT ASSUMPTION: this guide assumes that:

• The Veea Hub hardware has been physically installed at the site
• Network connectivity has been configured and tested
• Cameras have been installed and are accessible on the network
• The VeeaVision AI application has been deployed and is running

If any of these prerequisites are not met, contact your Veea support team or system administrator before proceeding.

Access Requirements

Here's what you'll need on hand before you start:

• Network access to the Veea Hub
• A web browser (Google Chrome)
• Administrator credentials for the system

Accessing VeeaVision AI

When logged into the Veea Control Center, first choose the Site you wish to manage. You will see the VeeaVision AI application listed in the lefthand navigation pane. Simply click to enter.

You will be presented with the option to choose:

• Remote link: accessing the application from a different network or location
• Local link: accessing the application from a computer within the same network as the Veea Hub.

Provisioning VeeaVision AI for First-Time Use

If your organization hasn't been provisioned for VeeaVision AI yet, you'll still see the link for it listed in the lefthand navigation pane. Clicking the link takes you to a request form to sign up for VigiLynx (the combination of IoT Pulse and VeeaVision AI). The form walks you through three quick steps: your contact details (name, company, business email, phone), a few questions about your organization (business type, number of locations, and VeeaHubs per location), and your equipment needs (cameras per location, the best time for a specialist to call you, and the sensor types and quantities you're interested in.

Once you submit the form, you'll land on a summary screen acknowledging your request:

Getting Started

If you have an existing setup with a Location defined and cameras set up and enrolled, you can proceed to the next section “Interface & Features” to explore all of the functionality and capabilities of your system.

If this is your first time setting up, please proceed to the Settings section to go through all of the setup, camera enrollment and configuration options.

Chapter 13: Interface & Features

Understanding the Interface

The VeeaVision AI interface is organized into the following areas:

Main Navigation (Left Sidebar)

• Live Dashboard
• Live View
• Alerts
• Time-Lapses
• Video Recordings
• Detection Timeline
• Red Zone

Settings Menu (Bottom Left Sidebar)

• Location Configuration
• Camera Management
• Notification Configuration
• Storage Management

Top Navigation Bar (Far Upper Right)

• AI status indicator
• Push to Talk (megaphone)
• Language selection
• Notifications
• Site Location

Live Dashboard

When you enter VeeaVision AI, you arrive at the Live Dashboard.

Here, you’ll see snapshots of your camera feeds, active alerts as well as all of the menu items to the left.

On each camera feed, you can:

• Pin the feed to make it show prominently on your home page dashboard
• Take a snapshot
• Show detection boxes that may be in place

Live View

On the Live View page, you get a full screen real-time view of each camera.

• At the lower left of your feed, there is a drop down selector to switch cameras
• At the lower right, you have buttons for enabling PTZ controls (if supported) or taking a snapshot of the feed

Alerts

On the Alerts Page, you are presented with a list of all active Alerts across the cameras at your Site/location.

These alerts are categorized as:

• Informational (listed in black) - for example, a person was detected entering a zone
• Critical (listed in red) - for example, a person entered at an unauthorized time

As shown above, you can:

• Export a report (as a CSV file) of alerts
• Choose a custom date range for listing and exporting alerts
• Select to view either all alerts, only information alerts or only critical alerts
• View stored recordings showing footage that triggered the critical alerts

Time-Lapses

The Time Lapse page gives you a quick overview of every camera enabled for time-lapse capture, along with the footage that's been generated.

• The snapshot thumbnail on the left shows the latest still image captured for that camera, along with a running count of how many snapshots have been taken so far (for example, "14 Snapshots so far"). You can click on the camera icon to view and scroll through a slide show of each of the images.
• The Standard Time Lapse video compiles all of that camera's snapshots into a single continuous playback, letting you watch the change over the full capture period in one video.
• The Day-by-Day Progress video breaks the same footage into daily segments, making it easier to compare one day's activity or progress against another rather than watching the entire span at once.
• To view either video, click the play icon on its thumbnail. Cameras are listed in the order they were added, and you can scroll down to see additional cameras.

Video Recordings

The Video Recordings page displays all recorded video clips from your cameras, organized in a chronological feed with the most recent recordings at the top.

• Click the play icon on each thumbnail to view the video.
• Below each thumbnail is the name of the camera that captured it, so when multiple cameras have recordings on the same day, you can quickly identify which clip belongs to which camera.

In the top-right corner, two dropdown filters let you narrow down the feed:

• Select Cameras lets you filter the list to show recordings from one or more specific cameras, rather than scrolling through every camera's footage.
• Select Date lets you jump directly to recordings from a particular day, instead of scrolling back through the full history.

Detection Timeline

The Detection Timeline page lets you review a full day's worth of camera activity at a glance, then jump straight to the moments that matter. The date field in the top-right corner controls which day you're viewing. Click it to open the calendar and select a different date.

Colored bars along the timeline indicate when detection events occurred - yellow for Info-level events and red for Critical-level events.

• The video preview shows the selected camera's footage for the point in the timeline you've clicked on. If no clip is available at that moment, the preview will display "No video."
• The playback controls beneath the video let you fine-tune what you see. Play starts and stops playback, with the elapsed time shown next to it.
• The Detections checkboxes (Critical and Info) let you filter which severity of detection events appear on the timeline.
• The View toggle switches the timeline between Detections and Motion Detection modes.
• The Cameras checklist lets you choose which camera's activity is displayed, if more than one is available.
• Click anywhere on the timeline to preview the video from that moment, and use the arrow buttons or the Zoom controls to navigate and adjust the level of detail shown.

Red Zone Monitoring

The Red Zone Monitoring page logs every time someone (or something) enters a restricted area you've defined, giving you a running history of violations across your Site. Each entry lists:

• the zone name
• the event name
• a description of what triggered it
• the date and time it occurred

Two dropdown filters at the top let you narrow the list. Select Date filters entries to a specific date range, and the zone dropdown lets you focus on a single zone rather than viewing violations from every zone at once. The Time column can also be sorted to reorder entries chronologically.

Clicking the play icon in the Actions column opens the recorded clip for that specific violation. The video player shows the exact camera feed at the time of the event, with the defined red zone boundary overlaid on the footage so you can see precisely where the restricted area is and how the violation happened.

The View Site Map button at the upper right opens a floor plan view of your property.

From here, the Select Level dropdown lets you switch between different levels or areas of your site, and the Cameras Placed list on the left shows every camera positioned on that level.

Click a camera name to highlight its location on the map. This is a useful way to understand where a violation occurred relative to the physical layout of your space.

People Count

The People Count Dashboard gives you a real-time summary and analysis of foot traffic across your site. A download icon in the top-right corner lets you export this data for reporting or record-keeping.

The Entries and Exits Trend chart plots traffic over time, with a blue line for entries and a red line for exits. You can toggle the time range using the buttons in the top-right of this panel

The three tables at the bottom break the data down further.

• People Count by Camera shows visible counts, entries, and exits for each individual camera.
• People Count by Zone shows the same metrics organized by the zones you've defined.
• Whitelist/Blacklist Summary tracks activity for recognized individuals or groups you've flagged, separating totals for whitelisted and blacklisted entries.

Chapter 14: Settings

Settings Overview

The Settings section is where all of the initial configuration for your VeeaVision AI system happens. Here’s how to get there and what's inside before we go page by page.

1. Click on the Settings icon at the bottom of the left sidebar.

   

2. The Settings submenu will expand, showing four options:
   • Location Configuration - Set your site location on a map
   • Camera Management - Add and configure cameras
   • Notification Configuration - Set up email, SMS, and audio alerts
   • Storage Management - Configure storage options
   • Cloud Configuration - Manage cloud storage and sync settings
   • Analytics Policy - Review and manage analytics and data usage settings

Each of these setting types gets its own section below As listed above, the sections are in the order in which they should be set up.

Location Configuration

For a new setup, it’s important to start by setting up your Site’s location. The location underpins reporting and location-based features elsewhere in the app.

• In the Address field, type your site address
• The system will provide address suggestions as you type
• (Optional) Click on the map to place the location marker and drag the marker to adjust the exact position if needed
• The map will automatically zoom to your selected location
• The Latitude and Longitude fields will be automatically filled based on your map selection. You can manually adjust these coordinates if needed
• Click the Save Configuration button

Once your location is set, two buttons let you build out the detail behind that map:

• Manage Levels and Floor Plans is where you define the different levels of your site (for example, "Level 1" or "Basement") and upload a floor plan image for each one. Type a level name into the field and click the plus button to add it. Once you've created at least one level, you can select it from the list to upload and configure its floor plan overlay

• Once you've added cameras to your system, the Manage Camera Placement window is where you pin each one to a specific spot on your site's floor plan. Use the Select Level dropdown at the top to choose which level you're working on.Note that this button requires at least one level to be configured first - if none exist yet, you'll see a prompt reminding you to set up your levels and floor plans before placing cameras.

Camera Management

The Camera Management page lists every camera connected to your VeeaVision AI system, along with its RTSP URL, assigned location, time-lapse schedule, and snapshot interval. From here you can add new cameras, edit existing ones, configure red zones, or remove cameras entirely.

Adding a New Camera

*Note that you may add a maximum of 4 cameras to VeeaVision AI at this time.

• Click the “Add Camera” button at the upper right
• A window will appear with camera configuration options

Fill in the camera details

Required fields:

• Camera Name — a unique name to identify this camera
• RTSP URL — the network address of the camera video stream (supports rtsp://, rtsps://, http://, https://)

Optional field:

• Location (a description of where the camera is positioned)

Timelapse configuration:

• Timelapse Days: select days of the week (Mon–Sun) by clicking the day buttons
• Timelapse Start / Timelapse End: set the start and end time for timelapse capture
• Take Picture Every: select an interval from the dropdown (5–60 minutes)

Save the camera

• Click Save to add the camera to your system
• The camera will appear in your camera list

RTSP URL Format
 

The RTSP URL format varies by camera manufacturer. Here are common ones you'll run into:

Hikvision

rtsp://username:password@IP:554/Streaming/Channels/101

Axis

rtsp://username:password@IP:554/axis-media/media.amp

Generic

rtsp://username:password@IP:554/stream1

Important Notes

• Replace username and password with your camera's actual credentials
• Replace IP with your camera's IP address
• The port is typically 554 for RTSP
• Contact your camera manufacturer for the exact stream path

Managing Existing Cameras

From the Camera Management table, you can perform the following actions on each camera:

Edit Camera

• Click the edit button to modify camera settings
• Update camera name, RTSP URL, location, or timelapse settings

Edit Redzone

• Click to open the red zone editor
• Draw zones on the camera view by clicking points
• Add multiple zones with custom names and colors
• Save all zones using the save button

Delete Camera

• Click to remove a camera from the system
• Confirm deletion when prompted

Notification Configuration

The Notification Configuration page lets you set up how VeeaVision AI alerts you and your team when something happens. For example, this could be a detection, an alert, or a red zone violation. This section covers the four ways VeeaVision AI can notify you:

• Email
• SMS (via Twilio)
• Megaphone (audio warnings)
• Strobe/siren (devices for visual and audible alerts)

Email Notification Configuration

Step 1: Click on the Email tab

Step 2: Configure SMTP settings

Required fields:

• SMTP Server: your email provider's SMTP server address
• SMTP Port: usually 587 for TLS or 465 for SSL
• Username: your email address
• Password: your email password or app-specific password
• From Email: email address that will send alerts
• To Email: address that will receive alerts

Optional fields:

• To Supervisor Email: additional email for supervisor notifications

Step 3: Save settings

• Click Save to apply your email configuration

SMS Notification Configuration (Twilio)

Step 1: Click on the SMS tab

Step 2: Configure Twilio settings

Required fields:

• Account SID: your Twilio account SID (from the Twilio console)
• Auth Token: your Twilio authentication token
• From Number: Twilio phone number to send SMS from
• To Number: phone number to receive SMS alerts

Optional fields:

• WhatsApp Number: WhatsApp number for WhatsApp alerts

Step 3: Save settings

• Click Save to apply your SMS configuration

Megaphone Notification Configuration

Step 1: Click on the Megaphone tab

Step 2: Add megaphone devices

• Click Add Megaphone to add a new device
• Configure megaphone name and IP address
• Save the device configuration

Step 3: Manage existing megaphones

• The table displays megaphone name, IP address, and actions
• Edit device settings using the edit button
• Delete devices using the delete button
• Test megaphone using the test button

Strobe/Siren Notification Configuration

Step 1: Click on the Strobe Setup tab

Step 2: Add strobe/siren devices

• Click Add Strobe/Siren to add a new device
• Configure device name and IP address
• Save the device configuration

Step 3: Manage existing devices

• The table displays device name, IP address, and actions
• Edit device settings using the edit button
• Delete devices using the delete button
• Test device using the test button

Storage Management

The Storage Management page lets you monitor and manage where your VeeaVision AI footage and data are stored, both locally and in the cloud. You are able to:

• Configure where and when video recordings and images are stored
• Choose between Cloud storage or AI server local storage
• Monitor the capacity, usage, and health of each storage location, including an SD card when one is installed

Storage mode options:

• Local Storage on the Hub itself
• Cloud: stores data on the cloud
• SD Card (cards up to 256GB are supported)

Storage behavior:

• Without cloud configuration set up or an SD Card inserted, recordings default to being stored locally on the onboard Hub.
• Inserting an SD Card changes the default storage to the SD Card itself
• Whether recordings are stored locally or on an SD card, the system always keeps at least 10GB of storage free. When free space reaches the 10GB threshold, storage use will not go beyond it; instead, the oldest recordings are automatically overwritten to make room for new ones.

Cloud Settings

The Cloud Settings page is where you connect VeeaVision AI to AWS S3 for offsite backup of your recordings.

This page is organized into four sections:

• The Customer / Site section establishes the identity used to build the S3 folder structure for your deployment. Enter the Customer Name and Customer ID, along with the Site Name and Site ID, so recordings from this location are organized correctly within your cloud storage.
• The AWS S3 section holds your connection details for the S3 bucket recordings will upload to. Set the AWS Region and the S3 Bucket name, along with an optional S3 Prefix/Folder if you want recordings organized under a specific subfolder. The AWS Access Key ID and AWS Secret Access Key fields authenticate the connection - note that credentials are stored server-side, and the secret key is never sent back to the browser once saved.
• The DVR Upload Policy section controls how and when recordings get uploaded. With Upload Enabled set to "Enabled," the system records locally first, then uploads completed recordings to S3, keeping a local copy as a fallback. Upload Mode can be set to Auto for automatic uploads. Retention Days sets how many days recordings are kept before being cleared, and Local Buffer Days sets how many days of footage stay stored locally as a safety buffer even after a successful cloud upload.
• The Cloud Status section gives you a live summary of your sync activity: Total Videos known to the system, how many are Cloud Synced, and how many are Pending Upload. Below that, you'll see the result of the last connection test and the last sync attempt, including any skipped or failed uploads.

Three buttons at the bottom let you take action:

• Save Cloud Settings saves your configuration
• Test Cloud Connection verifies that VeeaVision AI can successfully reach your S3 bucket with the credentials provided
• Sync Now triggers an immediate upload rather than waiting for the next scheduled sync.

Analytics Policy

The Analytics Policy page, titled "Site Operations and Triggers," is where you fine-tune the thresholds, durations, and rules that drive VeeaVision AI’s automated detections and alerts. The page is organized into eight sections, each covering a different analytics feature. A Reset to Defaults button in the top-right corner lets you revert all settings back to their original values if needed.

• Notification Settings controls how loud and how long your audio/visual alerts run: Megaphone Repeat Count sets how many times a megaphone announcement repeats, and Strobe Duration sets how long the strobe siren stays active.
• Heat Map controls how often the heat map visualization refreshes, set via the Update Interval field.
• Queue Management helps monitor line-ups or crowding: Maximum Wait Time sets how long someone can wait before being flagged, and Queue Length Threshold sets the number of people in a queue that triggers an alert.
• Idle Staff flags employees who haven't moved in a while, controlled by the Idle Duration Threshold.
• Person Recognition and License Plate Recognition each let you define an Allowed Duration - a time window (From/To) during which recognized people or vehicles are expected to be present. License Plate Recognition also includes a Number of Times Allowed field, limiting how many times a vehicle can enter/exit per day before it's flagged.
• People Count sets the occupancy rules used on the People Count Dashboard: Maximum Occupancy Threshold and Minimum Occupancy Threshold define the acceptable range of people in a space, and Surge Threshold sets how many times the maximum occupancy can be exceeded before it's treated as a surge event.
• People Tracking includes a Stop Duration Threshold, which sets how long tracking can be lost before the system flags it - useful for detecting if someone has stopped moving or left a monitored area unexpectedly.

Below these cards, the Select Required Zones and Cameras section lets you specify which zones and cameras these analytics rules should apply to. Check the boxes next to a zone (such as "front-door") and its associated camera (such as "Tapo-5BCD") to scope the policy to that area.

Once you've adjusted your settings, click Save All Changes in the bottom-right corner to apply them.

Appendix A: Initial Setup Checklist

Use this checklist to make sure initial setup is complete, page by page.

Location Configuration

• Access Location Configuration page
• Enter site address
• Set location on map
• Verify coordinates
• Save configuration

Camera Management

• Access Camera Management page
• Add all cameras
• Configure RTSP URLs for each camera
• Configure timelapse settings (if needed)
• Set up red zones (if needed)
• Save all camera configurations

Notification Configuration

• Access Notification Configuration page
• Configure email settings
• Save email configuration
• Configure SMS settings (if using Twilio)
• Save SMS configuration
• Configure megaphone devices (if applicable)
• Configure strobe/siren devices (if applicable)

Storage Management

• Access Storage Management page
• Select appropriate storage mode
• Configure storage (if using Cloud mode)
• Save storage configuration

Cloud Configuration
☐ Access Cloud Configuration page
☐ Enter Customer Name and Customer ID
☐ Enter Site Name and Site ID
☐ Configure AWS Region and S3 Bucket
☐ Enter AWS Access Key ID and Secret Access Key
☐ Set S3 Prefix/Folder (if needed)
☐ Configure DVR Upload Policy (upload mode, retention days, local buffer days)
☐ Test cloud connection
☐ Save cloud settings

Analytics Policy
☐ Access Analytics Policy page
☐ Configure Notification Settings (megaphone repeat count, strobe duration)
☐ Configure Heat Map update interval
☐ Configure Queue Management thresholds (max wait time, queue length)
☐ Configure Idle Staff duration threshold
☐ Configure Person Recognition allowed duration
☐ Configure License Plate Recognition allowed duration and times allowed
☐ Configure People Count occupancy thresholds (max, min, surge)
☐ Configure People Tracking stop duration threshold
☐ Select required zones and cameras
☐ Click Save all changes

VHM Mobile App

VHM is the Veea mobile app and the on-the-go interface for VigiLynx™. It connects to the same Sites, applications, and data as the Veea Control Center browser interface, with VeeaVision AI and IoT Pulse each one tap away from the home screen. Use it to check on a location from the field, respond to an alert, or enroll a new camera while you are standing next to it.

Selecting Your Site

IoT Pulse in VHM

VeeaVision AI in VHM

Enrolling a Camera by QR Code

VHM Mobile App vs. Veea Control Center

VHM and the Veea Control Center reach the same Sites, applications, and data, so most tasks can be done in either one. The choice usually comes down to where you are and how much screen you need: VHM is your on-the-go interface, and the Control Center is better suited to detailed setup and review at a desk. The one exception is camera enrollment by QR code, which requires VHM.

Rule of thumb: install VHM on the phone of anyone who installs cameras or responds to alerts in the field, and use the Control Center for initial configuration, policy changes, and reviewing history.