> For the complete documentation index, see [llms.txt](https://portal-integracao.intelbras.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portal-integracao.intelbras.com.br/linha-android/peripheral/doormanager.md).

# DoorManager

Interface Principal de CallBack: `DoorManager`

Path: `com.lamy.peripheral.sdk.asi.DoorManager`

```java
// Construction method, single example

public static DoorManager getInstance()
/**
* Opening lock
*
* @return int 0 means successful, others mean failed and displays error
code
*/
public int openDoor()

/**
* Closing lock
*
* @return int 0 means successful, others mean failed and displays error
code
*/
public int closeDoor()

/**
* Get the open status of the door button
*
* @return 1 indicates open, 0 indicates closed, while others indicate error
codes
*/
public int getDoorStatus()

/**
* Get the open status of the door button
*
* @return 1 indicates open, 0 indicates closed, while others indicate error
codes
*/
public int getDoorButtonStatus()

/**
* Add door lock/button switch monitoring
*
* @param listener listening added
* @return boolean wehther added successfully
*/
public synchronized boolean addListener(DoorStatusChangeListener listener)

/**
* remove door lock/button switch monitoring
*
* @param listener removed listening
* @return boolean whether removed successfully
*/
public synchronized boolean removeListener(DoorStatusChangeListener
listener)
public interface DoorStatusChangeListener {

/**
* Door lock status change callback
* @param status 1 means the door lock for opening, while 0 means the
door lock for closing
*/
void onDoorStatusChange(int status);

/**
* Door button status change callback
* @param status 1 indicates that the door opening button is open, while
0 indicates that the door closing button is closed
*/
void onDoorButtonStatusChange(int status);

}

```


---

# 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://portal-integracao.intelbras.com.br/linha-android/peripheral/doormanager.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.