UniFi Watch

UniFi cloud API access is via an API key to api.ui.com (X-API-KEY). Prefer an installed UniFi connector when available; it is owner-scoped and can reach Network inventory. Protect history and sensors often need the unofficial NVR proxy under the same cloud key.

Health and activity reports should only surface significant changes or new issues. Do not repeatedly report standing offlines the user already knows about, or usual backup-WAN high-latency noise, unless those change.

Since-you-left and Protect activity summaries report only what changed. Do not mention unchanged scenes (for example parked vehicles that did not move).

When the user asks where someone or something is on Protect, circle the subject on the snapshot before sending. Unmarked location photos are not acceptable.

UniFi Protect smart-detect may only label generic animal (not dog/cat/pet names). For pet or person location questions, check live Protect frames as well as recent animal or person event thumbnails; subjects can be present without a fresh smart-detect.

When a Protect person, pet, or vehicle is not obvious, send a photo and ask the user to label it. Build a labeled snapshot profile over time rather than guessing from one outfit. Never assume an unlabeled person is the account owner.

UniFi Protect via cloud: official integration snapshots are live-only (GET /protect/integration/v1/cameras/{id}/snapshot, no historical timestamp). Historical activity uses the unofficial NVR API through the same cloud connector key: GET /protect/api/events?start={ms}&end={ms} for motion, smart-detect (person/vehicle/animal), audio, and access; GET /protect/api/events/{id}/thumbnail for event stills. Sensors: GET /protect/api/sensors (temperature often in Celsius under stats.temperature.value).

UniFi Network critical-link watches use the site device list (uplink device name, type wire vs wireless, speed) and client list for named Wi-Fi devices that should stay present. Alert only when a watched switch or AP is offline, its uplink is wrong or meshing when it should be wired, or a watched client is missing.

This bot needs the UniFi cloud API (api.ui.com) and, when available, a UniFi Network connector. Protect event history and sensor reads use the console proxy under the same API key. No marketplace UniFi plugin is packed; the importer must connect their own UniFi API key / connector.