Sightwise

Sightwise Help

Manuals for everything in Sightwise โ€” the live grid, playback, exporting clips, cameras, users, multi-server sites, the hub, alerts, and the mobile app. Use the search box on the left to jump to a topic.

๐Ÿš€ Getting started

First-run setup

The first time you open a new server it asks you to set it up:

  1. Start a new system โ€” this is your first Sightwise server. Create an administrator username and password.
  2. Add to an existing site โ€” this server joins a site that already has one, so its cameras appear alongside the others. Enter the existing server's address and an admin login on it. (See Multi-server sites.)

Signing in

Sign in with your username and password, or with an access key (the keys live in config.json on the server โ€” there is an admin, a viewer, and a wall key). Use user accounts for people, and keys for shared screens and scripts.

The three pages

  • Server โ€” add cameras, manage users, storage, the site, the hub, backups and updates (admins only).
  • Live โ€” watch live, play back recordings, and export clips.
  • Walls โ€” build and open fixed camera layouts for monitors.

๐Ÿ“บ The live grid & layouts

The Live page shows your cameras in a grid. Drag a camera from the left list into the grid, or drag a whole group. Only the tiles on screen stream, to save bandwidth.

  • Grid size โ€” set columns ร— rows, or leave Auto to grow and shrink with the cameras.
  • Names โ€” toggle the camera name labels.
  • Resize a tile โ€” drag its bottom-right corner. Move โ€” drag the name bar.
  • Full screen a tile โ€” double-click it.
  • Save layout / Save asโ€ฆ โ€” keep a layout to reopen later or Open as wall on a dedicated screen.
  • Hotspots & zoom views โ€” clickable markers that jump to another camera, and saved cropped sub-views, both set up per camera on the Server page.
  • Auto-pause when idle โ€” under โš™ My settings you can have every stream pause after a few minutes of no interaction, to save bandwidth; wall screens never pause. The setting is saved with your account.
On a phone, open the same server and you get the mobile app automatically. See the mobile app.

โฑ๏ธ Playback & the timeline

Below the grid is the timeline. It shows recorded coverage (blue), and โ€” when you run one โ€” motion hits (red). Click the timeline to jump to that moment; the grid switches to playback and every camera on screen plays together, in sync.

Transport

  • โ— LIVE โ€” jump back to live.
  • โฎ / โญ โ€” step to the previous / next recording (skips gaps). While a motion search is active, these step through motion hits instead.
  • โช / โฉ โ€” skip 15 seconds back / forward.
  • โšโš / โ–ถ โ€” pause / play.
  • Speed โ€” 1ร— up to 16ร—.

Finding a time

  • ๐Ÿ“… Calendar โ€” days with footage are underlined; click one to jump there.
  • Span โ€” 1 h / 6 h / 24 h / all footage. You can also scroll over the timeline to zoom around the cursor.

โค“ Clips: export & mosaic

Everything you export or search starts from one selection on the timeline.

  1. Make a selection โ€” drag across the timeline. A highlighted band appears with a readout above it showing start โ†’ end ยท duration.
  2. Fine-tune it โ€” drag either handle to move an edge, or drag the band to slide the whole clip. Press Esc or โœ• to clear it.
  3. Pick an action from the bar that appears under the timeline.
09:12:04 โ†’ 09:15:40 ยท 3m 36s Recorded coverage (blue) Motion hits (red) โŸต drag a handle to resize Playhead โŸถ
The timeline: one selection (with handles and a start โ†’ end ยท duration readout) drives every action.

Actions

  • Export camera โ€” export the one camera chosen in the Camera list for the selected clip.
  • All on screen โ€” one MP4 per on-screen camera on this server.
  • โŠž Mosaic โ€” combine the on-screen cameras into a single grid video.
  • stamp โ€” tick this to burn the timestamp and camera name into the clip (re-encodes, a little slower).

Results appear in one panel with progress and a Save link for each file. On a secure connection you get a "Save asโ€ฆ" dialog; otherwise the browser downloads it.

Click a tile first to "focus" it โ€” it gets an accent outline and is pre-selected in the Camera list. You can still switch cameras in the list at any time.

๐Ÿ”Ž Motion search

Find movement inside a clip without scrubbing the whole thing.

  1. Make a timeline selection and pick the camera.
  2. Press Motion search. A grid overlay appears on the camera's picture.
  3. Drag a rectangle on the picture to mark the area to watch (or press Whole picture). Drag again to add; start on a marked cell to clear.
  4. Press Search clip. Moments with motion appear as red marks on the timeline and as a list of times.
  5. Step through hits with โฎ / โญ, click a time, or press โ–ถ Play motion only to skip the quiet gaps.

๐ŸŽฅ Cameras & recording

Server โ†’ Cameras

  • Add a camera โ€” enter its RTSP URL(s) and credentials, or use Discover / ONVIF to find cameras on the network. The password is encrypted at rest and never shown back.
  • Recording mode โ€” always, motion-only, or a weekly schedule; set pre/post-event seconds for motion.
  • Motion zones โ€” paint which parts of the frame trigger motion, with per-area sensitivity.
  • Streams โ€” record the main and sub stream so playback and mobile can use the light stream on small tiles.
  • Audio โ€” opt in per camera (off by default).
  • Retention โ€” a maximum age, plus optional tiered rules (keep more for some date ranges).
  • PTZ โ€” pan/tilt/zoom controls on the tile for PTZ cameras, with saved presets and tours that rotate through them server-side.
  • Fisheye dewarp โ€” for a 360ยฐ/panoramic camera, turn on Dewarp on the camera; a button on the tile then cycles Fisheye / 90ยฐ / 180ยฐ / 360ยฐ views of the round image.
  • Storage โ€” spread recording across several drives; Reindex rebuilds the catalog from files on disk.

๐Ÿ“‹ All cameras (inventory)

top nav โ†’ All cameras

A single table of every camera on every server in the site (and, from the hub, across every site). Use it to audit the fleet.

  • Filter by server/site and by status โ€” Disabled, Not recording, Missing model / firmware, or just Problems.
  • Export to Excel or Export CSV โ€” the whole filtered list, for inventory and reporting (no add-ons; the spreadsheet is built in the browser).

๐Ÿ”€ Moving, replacing & re-addressing cameras

Move a camera to another server

On the Server page (or by dragging it in the Live tree), move a camera to another server in the site. Before moving, Sightwise checks the target can actually reach the camera and warns you if not. The camera keeps its id, so its existing recordings stay viewable, and a moved camera's footage on the old server is merged into one continuous timeline. Moving back reuses the original entry.

Replace a camera

Swapping in a new camera? Use take recordings to hand the old camera's archive to the replacement so the history isn't split.

A camera changed IP

Server โ†’ Changed IPsโ€ฆ

When cameras get new addresses (DHCP, a new switch), open Changed IPsโ€ฆ to scan the network and match devices by MAC/serial, or paste a list of old IP, new IP. Sightwise rewrites just the address โ€” the login, port, path and camera id stay, so recordings are kept. Auto-discovery also updates a known camera's address instead of adding a duplicate.

๐Ÿ‘ค Users, roles & permissions

Server โ†’ Users

Roles

  • Admin โ€” everything, including settings and other users.
  • Viewer โ€” watch live, play back, export (within their scope).
  • Wall โ€” a dedicated screen login that resumes its layout automatically and shows nothing before sign-in.

Scoping who sees what

  • Camera access โ€” all cameras, or only the ones I pick. Pick individual cameras and/or whole camera groups. A group grant covers every camera in that group, including ones added to it later โ€” the way to manage access at large scale.
  • Time windows โ€” limit live viewing to a weekly schedule and archive playback to a date range or rolling number of days (useful for tenants).
  • Watermark โ€” a tiled identity watermark (the viewer's name across the picture), driven by site-wide opacity/frequency and burned into their exports too.

You can invite a user by link, or set their password directly.

๐Ÿ‘ฅ Sharing layouts

On the Walls/Live page, the ๐Ÿ‘ฅ button on a saved layout opens its sharing window:

  • Add people as Can view or Can edit, and remove them.
  • A layout you received shows who it came from and whether it's view-only.
  • A layout with no owner is visible and editable by everyone โ€” an admin can set an owner to make it private, after which sharing takes effect.

๐Ÿ” Your settings follow you across the site

In a multi-server site, things stay in step across every server so it doesn't matter which one you open:

  • Layouts and user accounts sync between servers (newest change wins; a clashing layout name is kept as "name (from <server>)").
  • Your preferences (like auto-pause) are saved with your account and apply everywhere.
  • Export folder โ€” in Chrome/Edge you can pick a folder once and have clips save straight into it instead of the Downloads prompt.

Sign-in tokens are still per server; your account and settings are what travel.

๐Ÿ–ง Multi-server sites

Several servers in one location form a site and appear together. On the second server choose Add to an existing site during setup, or add siblings later under Server โ†’ Site.

  • Servers in this site โ€” switch between them from the top bar; cameras from all of them show in the list.
  • Move cameras between servers (their existing footage stays viewable on the old server).
  • Settings sync โ€” site name, watermark, saved logins and the update path stay in step across the site.

Cluster: balancing & failover

  • Balance recording โ€” preview a plan that levels load across servers and keeps different angles of a Location on separate servers, then apply it.
  • Failover (opt-in per camera, on its Recording tab) โ€” a backup server keeps a standby copy and takes over if the home server goes down, then hands back when it returns.
  • Tidy leftover copies โ€” remove dead disabled copies whose footage has aged out while the camera is live elsewhere.
  • One continuous timeline โ€” footage split across servers by failover or a move plays back as one timeline; Sightwise streams the remote parts for you.
Failover and cross-server playback should be confirmed on real two-NVR hardware before you rely on them.

โ˜๏ธ Hub & remote access

The hub lets you reach your sites from anywhere โ€” a phone or another location โ€” without opening any ports on the NVRs. Each site dials out to the hub and holds the link open; the hub is the only machine with a public address. A hub is the same Sightwise software in "hub mode": a cloud instance with no cameras that reverse-proxies each site. Each site gets its own web address (e.g. https://25waverly.hub.yourcompany.com) that you use exactly as you would on the LAN.

Site A โ€” NVRs Site B โ€” NVRs Site C โ€” NVRs Hubpublic address ยท no cameras outbound only โ€” no port-forwarding โ†’ ๐Ÿ“ฑ Phone ๐Ÿ’ป PC / wall
Sites dial out to the hub; people reach the hub. No inbound ports are ever opened on a site.

What you need

  • A small cloud server (VPS) with a public IP (1 vCPU / 1 GB is plenty โ€” it stores no video).
  • A domain you can add DNS to, with two records pointing at the VPS: hub.yourcompany.com and the wildcard *.hub.yourcompany.com (the wildcard gives each site its own sub-address).
  • A wildcard HTTPS certificate covering both names (a free Let's Encrypt wildcard via DNS-01 works; Caddy can fetch/renew it automatically).
  • The sites need nothing special โ€” just ordinary outbound internet.

Set it up

  1. Add the two DNS records, then get the wildcard certificate.
  2. Install Sightwise on the VPS in hub mode on port 443 with your cert (Windows: install.ps1 -HubMode -Port 443 -TlsCert โ€ฆ -TlsKey โ€ฆ; Linux: see docs/HUB-LINUX.md). Open https://hub.yourcompany.com and sign in with the hub's admin key (in its config.json).
  3. On the hub's Hub page, Add a site โ€” it shows, once, the hub address, site id and a one-time enrollment key.
  4. On that site's NVR: Server โ†’ Connect to hub, paste the three values, Connect. Within seconds the site turns โ— Online on the hub.
  5. Click Open next to a site to use it over the relay. Bookmark its *.hubโ€ฆ address on the phones/PCs that use it.

On the hub

  • Central sign-on (SSO) โ€” give people one hub account (admin/viewer/wall); one sign-in opens every site they're allowed to, with their hub role as their rights on the site. On the LAN, sites still use their own logins, so a hub/internet outage never blocks local access.
  • Enterprise SSO (OIDC / Entra / Google / Okta) โ€” sign in with your identity provider instead of hub passwords; users are matched by email, and tokens are verified (signature, issuer, audience, expiry, nonce).
  • Per-site access scopes โ€” limit a hub user to certain sites, with an optional per-site role override. Enforced at the relay.
  • Multi-site camera directory โ€” the hub's search box finds a camera across all your sites and jumps to it.
  • Cross-site walls โ€” build and save walls that mix cameras from several sites, then open them as a grid.
Security: the link is outbound from each site (no inbound ports), each site authenticates with its own enrollment key (rotate with New key, cut off with Remove), and every relayed request still passes the site's own login. Full step-by-step with certificate options is in docs/HUB-SETUP.md (Linux in docs/HUB-LINUX.md).

๐Ÿ”” Alerts & notifications

Events โ€” a camera going offline, recording stopping, low disk, a failed backup, the server restarting โ€” become alerts. Each user chooses how they want to hear about each kind.

Your notification settings

Open the ๐Ÿ”” bell (top-right on desktop, the header on mobile) โ†’ Notification settings. For each alert type pick any of:

  • In-app โ€” shows in the bell with an unread count.
  • Email โ€” sent to your address (needs the email account set up, below).
  • Push โ€” a notification on your phone or desktop (press Enable push on this device first).
  • Sound โ€” a chime in the browser.

You can also set a minimum severity and quiet hours. Everything is opt-in โ€” nothing is forced on anyone.

Email account (admins)

Server โ†’ Alerts & email

Enter your SMTP host, port, username, password and From address, then Send test email to confirm it works. This is what email alerts send through.

๐Ÿ“ฑ The mobile app

Open your server's address on a phone and you get the mobile app automatically. Install it from the browser's "Add to Home Screen" for a full-screen, app-like experience and push notifications.

  • Bottom bar โ€” Cameras ยท Alerts ยท Sites ยท Menu.
  • Sites โ€” searchable list; switch between servers.
  • Tap a camera for full screen: live, playback (scrub the timeline), pinch or ยฑ to zoom, PTZ pad and tours, Listen.
  • ๐Ÿ“… jump to a day; โฎ / โญ step recordings.
  • โ‹ฎ menu โ€” Snapshot the current frame to your phone, Export a clip (quick durations), Motion search, quality and info.
  • Alerts โ€” view notifications and Enable push on this device.
  • Menu โ€” server health, a Live-previews toggle, and version.

๐Ÿ’พ Backup & restore

Server โ†’ Backup

  • Save the server's configuration (cameras, users, settings) to a file and restore it later.
  • Schedule automatic backups and keep the last N.

โฌ†๏ธ Software updates & the fleet

From the hub (recommended)

Hub โ†’ Updates

  1. Upload a new sightwise-<version>.zip on the hub's Updates page. It's validated and becomes the published release (the hub keeps the newest few).
  2. Update the hub itself with one click โ€” it swaps in the new version and rolls back automatically if the new one doesn't start.
  3. Update a site, or Update all sites. Each site updates one server at a time (the others first, itself last), waiting for each to come back on the new version and stopping at the first failure.
  4. Automatic โ€” set an hour window per site and Sightwise rolls out behind-version servers on its own, inside that window.

The Fleet table shows every server's version and the job's progress. A site's own Server โ†’ Software updates panel shows the same for that site.

From a network share

Instead of the hub, point each server's update source at a shared folder holding the release zip + latest.json. Updates are checksum-verified with a rollback copy kept. (The share path syncs across a site, so you set it once.)

๐Ÿ“ Audit trail & event log

Server โ†’ Audit, and Server โ†’ Events

  • Audit trail โ€” who did what (sign-ins, exports, camera and user changes). The From column shows how they connected โ€” over the LAN, through the hub (with the public IP when the hub is 0.9.3+), or from a sibling server โ€” plus device, OS and browser.
  • Event log โ€” what happened on the server (cameras up/down, disk, recording, backups) โ€” the same events that feed alerts.
  • Both have a range picker (last 24 hours by default, 7/30 days, all, or a custom range) and export to CSV.

โ“ Troubleshooting

A camera shows "connecting" or black

Check its RTSP URL and credentials on the Server page (use the test button), and that the NVR can reach the camera's IP. Try the sub-stream.

The timeline is empty

The timeline only appears for keys/users that may play back recordings, and only when a camera that records is on screen. Check the camera's recording mode and retention, and that a drive has free space.

I can't export

Exporting needs the export right. Make a timeline selection first โ€” the action bar only appears when a clip is selected.

Email or push isn't arriving

For email, confirm the SMTP account with Send test email. For push, press Enable push on this device in notification settings and allow notifications in the browser; each device enables separately.

Still stuck?

Note your server version (shown top-right) and check the server log. For hub setup, see docs/HUB-SETUP.md.