Requirements before starting

• All sensors must be reachable on the network and visible to each other

• All sensors must run the same firmware version

• If a SPIDER is used, it must have the same firmware as the sensors

• Privacy level must be set to 0 during stitching setup (can be raised afterwards)

• All sensors must be recalibrated

• All sensors must be time-synced to the same NTP server

• Minimum 30cm overlap between adjacent sensors

Sensor limits per parent device

Stitching algorithms (FW5.9)

When upgrading an existing multisensor to FW5.9, it keeps the old Floor Stitching algorithm. Change to Space Stitching in the multisensor UI (☰ menu → Mode).

Multisensor tracking algorithms (FW5.9)

Creating a multisensor

1. Go to Settings → Multisensor → +

2. Add each sensor via IP address, MAC address, or launch the Sensor Explorer to scan the network

3. Click two neighboring sensors → click Stitch

4. Floor Stitching: Place at least 3 reference points on the floor in a triangle shape with maximum spread. Points must be on the floor only.

5. Space Stitching: Place at least 5 matching points anywhere in both sensor views (same physical point visible in both images)

6. Click Save → review the stitching quality → stitch all neighboring sensors

7. Click Apply computation

Adding a floor plan (optional)

• Format: PNG only

• Size limit: <1MP and <1MB (single sensor parent) / <100MP and <100MB (SPIDER parent)

• Best workflow: export .dwg → PDF → convert to high-quality PNG via pdf2png.com

• Set the coordinate zero (0,0) point — defaults to top-left

• Set a reference distance using the longest available distance for best accuracy

Maintenance best practices

• Check all sensors show green in the multisensor status after setup

• Verify tracking quality 2–3 months after installation

• If a single sensor's password is changed, you must manually update it in the multisensor settings (Settings → Multisensor → three-dot menu for that sensor → update password)

• Exclusion masks drawn on individual sensors have no effect inside a multisensor — draw exclusion masks at the multisensor level

Common errors

Extension licences in multisensors

Licences are applied to individual sensors, not to the multisensor. For a people attribute to work across the whole multisensor, every child sensor must have a valid licence. Check licensing status in the Multisensor settings.