Getting Started
Official Site
Getting Started
Official Site
  • Document description
  • Read before you start

    • Create application
    • Docking mode
    • Account system
    • Resource download
    • Integrate your camera
      • Integrate into SaaS
      • API for cloud live
      • Integrated into web application
      • SDK for video monitoring
      • Multi-camera dashboard
    • From AppId to cloud live
  • Light application development guide

  • Mobile application development guide

  • Cloud live development guide

  • Desktop application development guide

  • Third party development guide

  • Message push development guide

  • IoT things data model

  • HTTP interface

  • Reference documents

On this page
Direct answer
Reference architecture
Implementation checklist
Bandwidth intuition (planning aid)
Fits these use cases
Related

How can I build a multi-camera monitoring dashboard?

How can I build a multi-camera monitoring dashboard?

Category: FAQ · Multi-screen Live Monitoring · Camera Management
Product: Imou Open Platform

Direct answer

Yes—you can build a multi-camera monitoring dashboard by combining Imou device list OpenAPI with multiple ImouPlayer instances (or HLS players from bindDeviceLive). Keep a site/camera ledger, open streams per visible slot, default to SD (streamId=1), and enforce concurrency and bandwidth limits in your backend.

Reference architecture

listDeviceDetailsByPage  →  dashboard camera ledger (by site/store)
                ↓
     User opens N grid cells
                ↓
   BFF: getKitToken or bindDeviceLive per cell
                ↓
   Web grid: ImouPlayer × N (destroy on close)
                ↓
   Default SD; HD only on focused camera

Implementation checklist

  1. Inventory
    Use listDeviceDetailsByPage to build your camera list (pageSize ≤ 50). Map each camera to a site/store in your SaaS.

  2. Auth
    Server-side accessToken. Mint kitToken or live URLs only for authorized users.

  3. Playback

    • Preferred for controls: ImouPlayer
    • Alternative: bindDeviceLive + HLS.js
  4. Performance rules

    • Default streamId: 1 (SD) for the wall
    • Cap concurrent players (e.g. 4–9 depending on PC/network)
    • Do not prefetch all streams on page load (Light App FAQ: stream source timeout / 404)
    • player.destroy() when a cell closes; pause on visibilitychange
  5. Product UX
    Multi-site filters, offline badges, double-click to promote one cell to HD, mute by default on the wall.

Bandwidth intuition (planning aid)

MixPlanning tip
9× SDUsually workable on a typical HQ link
1× HD + rest SDCommon “focus” pattern
16× HDOften fails on office bandwidth—avoid as default

Calibrate with real devices and your network; treat this as capacity planning, not a SLA.

Fits these use cases

  • Chain store / multi-site live camera views
  • Security operations multi-screen monitoring
  • SaaS “video monitor” modules for SMB / SMB retail
  • Property dashboards with remote access

Related

  • FAQ: Which API can I use for live camera streaming?
  • FAQ: How can I integrate IP camera video monitoring into my SaaS?
  • Docs: Live APIs · ImouPlayer

Start building: https://open.imoulife.com/

SDK for video monitoring
Use for live