> 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/access-control/de/fehlerbehebung/access-control-hardware-checks/restart-an-access-controller.md).

# Einen Zutrittscontroller neu starten

Erfahren Sie, wie Sie Ihren Verkada-Zutrittscontroller neu starten

Wenn Ihr Zutrittscontroller nicht mehr reagiert und nicht ordnungsgemäß funktioniert oder [den Verkada-Support](/command/de/benotigen-sie-hilfe/contact-verkada-support.md) Anfragen zum Neustarten des Controllers empfehlen wir, Ihren Zutrittscontroller neu zu starten.

{% hint style="danger" %}
Sie müssen ein [Access-Site-Administrator](/access-control/de/erste-schritte/roles-and-permissions-for-access-control.md) für den Standort, zu dem der Controller gehört.
{% endhint %}

{% hint style="warning" %}
Wenn der Controller einen **Offline** Status anzeigt, bewirkt das Neustarten des Controllers über Verkada Command nichts. Sie müssen den Zutrittscontroller vom Strom trennen und ihn manuell wieder einstecken, um ihn neu zu starten.
{% endhint %}

{% stepper %}
{% step %}
**Gehen Sie in Verkada Command zu Alle Produkte > Geräte.**
{% endstep %}

{% step %}
**Wählen Sie den Controller aus, den Sie neu starten möchten, und klicken Sie rechts auf das Bild des Controllers.**
{% endstep %}

{% step %}
**Klicken Sie oben rechts auf Einstellungen.**
{% endstep %}

{% step %}
**Klicken Sie bei der Access Control Unit auf „Neu starten“.** 

<div align="left" data-with-frame="true"><img src="https://3342059292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-b1225800afbacfd0b3be4dbbf1651ae08ed3a437%2Fa1e99886119e736c5844ddd9930d9e47bed38e00.png?alt=media" alt=""></div>
{% endstep %}
{% endstepper %}


---

# 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/access-control/de/fehlerbehebung/access-control-hardware-checks/restart-an-access-controller.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.