> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/release-notes/web/2026/release-15-42-alarm-camera-filters-added.md).

# Release 15.42: Alarm Camera Filters Added

February 13, 2026

Updates to the Solink platform in this release include:

***

## Enhancements

* [**Alarm Motion Zones**](/docs/protect-your-locations-with-alarms/alarm-setup/alarm-motion-zones.md): Added filters to sort for:
  * Indoor and outdoor alarm cameras
  * Standard, Deterrent and Loitering alarm cameras
    * Standard: Traditional video alarms that capture motion in a specified area.
    * Deterrent: Alarm cameras that act as deterrence for trespassers. An onsite speaker must be paired to the camera. Deterrent alarm cameras are currently in beta - please reach out to your Customer Success representative if you are interested in this feature.
    * [Loitering](/docs/protect-your-locations-with-alarms/use-and-configure-alarms/loitering-zones-video-alarms.md): Alarm cameras that capture people or vehicles that loiter in an area for a set period of time. Loitering alarm cameras are currently in beta - please reach out to your Customer Success representative if you are interested in this feature.

## Bug Fixes

* [**Arm / Disarm PIN**](/docs/protect-your-locations-with-alarms/use-and-configure-alarms/arm-disarm-pin.md): Users must first Save the phone number before testing it. Previously, users could test the phone number without saving:\
  ​


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.solink.com/docs/release-notes/web/2026/release-15-42-alarm-camera-filters-added.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.