> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-br34-wireless-glass-break-sensor.md).

# BR34 Glass Break Sensor

Learn details about the end-of-sale information for the BR34 Wireless Glass Break Sensor

Verkada is announcing the upcoming end-of-sale of the BR34 Wireless Glass Break Sensor in all countries.

{% hint style="danger" %}
Final orders for BR34 must be received by **Feb 7, 2025**.
{% endhint %}

## FAQ

### What does this mean?

As of Feb 7, 2025, we will no longer sell the BR34 Wireless Glass Break Sensor. Verkada typically provides support for a given product for a period of ten (10) years after the end-of-sale date.

### Can customers return BR34s that they purchased?

Customers may return BR34s *within 30 days of purchase*.

## Key definitions

* **End-of-Sale Announcement (this article)**: Official End-of-Sales notice.
* **End-of-Sale Date**: The last date to order the product through Verkada.


---

# 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.verkada.com/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-br34-wireless-glass-break-sensor.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.