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

# Reinicie un controlador de acceso

Aprenda a reiniciar su controlador de acceso Verkada

Si su controlador de acceso deja de responder y no funciona correctamente o [equipo de soporte de Verkada](/command/es/necesitas-ayuda/contact-verkada-support.md) solicita reiniciar el controlador, le recomendamos que reinicie su controlador de acceso.

{% hint style="danger" %}
Debe ser un [administrador de sitio de acceso](/access-control/es/primeros-pasos/roles-and-permissions-for-access-control.md) para el sitio al que pertenece el controlador.
{% endhint %}

{% hint style="warning" %}
Si el controlador muestra un **Sin conexión** estado, reiniciar el controlador a través de Verkada Command no hace nada. Debe desconectar el controlador de acceso y volver a enchufarlo manualmente para reiniciarlo.
{% endhint %}

{% stepper %}
{% step %}
**En Verkada Command, ve a Todos los productos > Dispositivos.**
{% endstep %}

{% step %}
**Seleccione el controlador que desea reiniciar y haga clic en la imagen del controlador a la derecha.**
{% endstep %}

{% step %}
**En la esquina superior derecha, haz clic en Configuración.**
{% endstep %}

{% step %}
**En la Unidad de control de acceso, haga clic en Reiniciar.**

<div align="left" data-with-frame="true"><img src="https://1576776939-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/es/solucion-de-problemas/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.