> For the complete documentation index, see [llms.txt](https://docs.chirpwireless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirpwireless.io/first-steps.md).

# First Steps

Get started with Chirp — what you need and the LoRaWAN setup flow that takes you from unboxing to live sensor data.

Start with one useful job for your home: see a room's temperature, watch a door sensor, or receive a leak alert. This section helps you find your way around Chirp and connect your first sensor. You can also ask the [AI Assistant](/ai-assistant/let-ai-set-it-up.md) to work through the configuration with you.

The hands-on tutorial uses LoRaWAN. If your sensor uses another connection, the [Connectors guide](/connectors.md) shows where to begin.

## What's ahead

| Page                                                                   | What you'll learn                                                                                                                               |
| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| [Finding Your Way Around](/first-steps/finding-your-way-around.md)     | A tour of the interface — where everything is, what each section does, and how to customize your view                                           |
| [Connect Your First Sensor](/first-steps/connect-your-first-sensor.md) | A hands-on LoRaWAN guide: set up your gateway, create an LNS connection, register a sensor, build a room dashboard, and create your first alarm |

## What you'll need

* A Chirp account
* A web browser on your computer, tablet, or phone
* For the hands-on guide: a LoRaWAN gateway and a sensor (like a temperature/humidity sensor) with its Device EUI and AppKey — these usually come printed on the device or its packaging

No hardware yet? The first two pages are still worth reading — they'll help you understand what Chirp can do and how it works before your sensors arrive.

## The LoRaWAN setup flow

Here's what that path looks like:

```
Sign up → Plug in your gateway → Create a connector → Register your sensor → Build a dashboard → Set up an alarm
```

Not every Chirp setup starts with a gateway. This flow is specifically for LoRaWAN sensors. Other connection types begin with the connection itself instead.

Most people have their first LoRaWAN sensor reporting data within 15 minutes. The [Connect Your First Sensor](/first-steps/connect-your-first-sensor.md) guide walks you through every step.

## After your first sensor

Want to connect scripts or trusted tools to Chirp? Create an API key and use the [API](/api.md) — REST over plain HTTPS is all most home setups need.

## Start with an existing camera

Already have a compatible IP camera? Begin with [Lens and Twin](/lens/installing-twin.md). Twin runs at your home, one container for each camera, and connects it to Chirp. You can complete the sensor walkthrough separately.


---

# 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.chirpwireless.io/first-steps.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.