> For the complete documentation index, see [llms.txt](https://docs.mclimate.eu/mclimate-lorawan-devices/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mclimate.eu/mclimate-lorawan-devices/devices/mclimate-open-close-sensor-lorawan/open-close-sensor-lorawan-communication-protocol/notification-blind-time.md).

# Notification Blind Time

{% hint style="info" %}
Default notification blind time changed from 0 minutes to 1 minute for devices with firmware version ≥ 1.3.
{% endhint %}

The Notification Blind Time is used to send the status (open / close) after a certain time. In this time interval, each detected status is counted by the status counter. When the time interval expires, the current status (open / close) and counter are sent to the keep-alive packet.

Notification Blind Time is useful when you are not interested in the events in real-time, but rather want to understand the "final" status of the sensor. E.g. if you install the sensor on a door, there might be a number of opens/closes in a single NBT. The sensor will not send an uplink for every event, but will send the final status of the sensor after NBT interval since the first event.

{% tabs %}
{% tab title="SET" %}

<table data-header-hidden><thead><tr><th width="142"></th><th width="126"></th><th></th></tr></thead><tbody><tr><td><strong>Byte index</strong></td><td><strong>Bit index</strong></td><td><strong>Hex value – Meaning</strong></td></tr><tr><td>0</td><td>-</td><td>1E – The command code.</td></tr><tr><td>1</td><td>-</td><td><p>XX - Notification Blind Time in minutes. </p><p>Default value is 1 minutes.</p></td></tr></tbody></table>

**Example command**, **\[Hex]:** 0x1E0A – The server sets notification blind time to 10 minutes.
{% endtab %}

{% tab title="GET" %}

<table data-header-hidden><thead><tr><th width="133.99999999999997"></th><th width="168"></th><th></th></tr></thead><tbody><tr><td><strong>Byte index</strong></td><td>Sent request</td><td><strong>Received response</strong></td></tr><tr><td>0</td><td>1F – Command code.</td><td>1F - The command code.</td></tr><tr><td>1</td><td></td><td>XX - NBT in minutes.</td></tr></tbody></table>

**Example command: 0x1F**

**Example command sent from server**, **\[Hex]:** 1F;

**Example command response**, **\[Hex]:** 1F0A => NBT = 0A =  10 minutes.
{% endtab %}
{% endtabs %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mclimate.eu/mclimate-lorawan-devices/devices/mclimate-open-close-sensor-lorawan/open-close-sensor-lorawan-communication-protocol/notification-blind-time.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.