> 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/de/benotigen-sie-hilfe/end-of-sale-products-policy-overview/end-of-sale-announcement-for-br34-wireless-glass-break-sensor.md).

# BR34 Glasbruchsensor

Erfahren Sie Details zu den End-of-Sale-Informationen für den drahtlosen BR34-Glasbruchsensor

Verkada kündigt das bevorstehende Verkaufsende des BR34 Wireless Glass Break Sensors in allen Ländern an.

{% hint style="danger" %}
Endgültige Bestellungen für BR34 müssen bis zum **7. Feb. 2025**.
{% endhint %}

## FAQ

### Was bedeutet das?

Ab dem 7. Feb. 2025 werden wir den BR34 Wireless Glass Break Sensor nicht mehr verkaufen. Verkada bietet für ein bestimmtes Produkt in der Regel zehn (10) Jahre lang nach dem Verkaufsende Support an.

### Können Kunden BR34s zurückgeben, die sie gekauft haben?

Kunden können BR34s zurückgeben *innerhalb von 30 Tagen nach dem Kauf zurückgeben*.

## Wichtige Definitionen

* **Ankündigung des Endes des Verkaufs (dieser Artikel)**: Offizielle Mitteilung zum Verkaufsende.
* **Verkaufsenddatum**: Das letzte Datum, an dem das Produkt über Verkada bestellt werden kann.


---

# 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/de/benotigen-sie-hilfe/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.