> For the complete documentation index, see [llms.txt](https://ask.simplehw.eu/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.simplehw.eu/kb/simple-api-6-generation/modes/api-6-mode-independent-information-and-events_15237121/heartbeats.md).

# Heartbeats

Along with uplink messages (events) triggered irregularly (such as sensor-triggered events), you can also receive periodical events that are triggered by time only. We call some of these events **Heartbeats.**

## **Introduction**

Heartbeats are **mode-independent events triggered by time**. There are **3 heartbeats** defined in API 6, Heartbeat 1, Heartbeat 2, and Heartbeat 3. **Heartbeats 1 and 2** are identical yet individual and you can fine-tune their behavior and appended data with a lot of settings. **Heartbeat 3** is used for regular messages with MAC addresses and to control the Stupid modes and its settings are limited compared to HB 1 and 2.

###


---

# 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://ask.simplehw.eu/kb/simple-api-6-generation/modes/api-6-mode-independent-information-and-events_15237121/heartbeats.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.