Verba Plugin profile

UniFi Protect

Handle one natural-language UniFi Protect request for sensors, camera lists, or camera and area snapshot descriptions.

unifi_protect Version 1.0.9
When to use

Best-fit scenarios

Use for camera/scene questions and snapshot descriptions (for example: 'what are my dogs doing in the backyard', 'what does the driveway look like', 'describe the porch camera'), plus Protect sensor status and camera lists. If a request is about viewing/describing a scene, prefer this over unifi_network.

How to call it

Execution guidance

Pass one natural-language Protect request in query. Include the camera or area naturally when needed. This plugin can infer whether the user wants sensor status, a camera list, a specific camera description, or an area description.

Arguments

Input shape

  • query string

    ONE natural-language UniFi Protect request (for example: list my cameras, what is going on in the front yard, describe the doorbell camera, are any doors open).

Settings

Required configuration

  • UNIFI_PROTECT_API_KEY text

    API key used as X-API-KEY header for Protect Integration endpoints.

  • UNIFI_PROTECT_BASE_URL text

    Base URL of your UniFi console (example: https://10.4.20.127).

    Default: https://10.4.20.127
  • VISION_API_BASE text

    OpenAI-compatible base URL for vision (example: http://127.0.0.1:1234).

    Default: http://127.0.0.1:1234
  • VISION_API_KEY text

    Optional. If blank, OPENAI_API_KEY env var will be used if present.

  • VISION_MODEL text

    OpenAI-compatible vision model name (example: qwen2.5-vl-7b-instruct).

    Default: qwen2.5-vl-7b-instruct
Example call

Canonical usage JSON

{
  "function": "unifi_protect",
  "arguments": {
    "query": "ONE natural-language UniFi Protect request (for example: list my cameras, what is going on in the front yard, describe the doorbell camera, are any doors open)."
  }
}