> 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/ja/toraburushtingu/verkada-ac41-status-led.md).
# AC41 ステータス LED
Verkada AC41 の LED コードの状態について学ぶ
Verkada [AC41 4ドア コントローラー](https://docs.verkada.com/docs/door-controller-ac41-datasheet.pdf) 左上に LED があり、デバイスの状態をひと目で確認できます。
***
## LED ステータス
**オレンジの点灯**—コントローラーはオンになっており、起動中です。
**オレンジの点滅**—コントローラーはファームウェアを更新しています。
**青の点滅**—コントローラーはドアを管理していますが、サーバーに接続できません。Verkada について詳しく見る [必要なネットワーク設定](/access-control/ja/hajimeni/access-control-network-settings.md) は、コントローラーをオンラインにするのに役立ちます。
**青の点灯**—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/access-control/ja/toraburushtingu/verkada-ac41-status-led.md?ask=&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.
