> 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/devices/rooms.md).

# Rooms

As your smart home grows, organizing sensors by room keeps everything easy to find. Instead of scrolling through a flat list, you can group sensors into rooms like Living Room, Kitchen, Garden, and Garage — so you always know where each sensor lives.

In Chirp, rooms are managed through **Settings → Locations**. Think of each location as a room or area of your home. The interface uses the term "Location settings," but throughout this guide we'll call them rooms because that's how most home users think about them.

## Getting to the rooms page

1. Click **Settings** in the sidebar.
2. Click **Locations** (or go directly to `/settings/locations`).

The page title reads **Location settings** with the subtitle "Manage your locations."

## Adding a room

1. Click **Add location** in the top-right corner.
2. In the dialog, enter a name for the room — something that matches how you think about your home: "Living Room," "Kitchen," "Garden," "Garage," "Basement."
3. Click **Save**.

The room appears in the list. If this is your first one, it replaces the empty state message ("You don't have locations yet").

## Editing a room

Each room in the list shows:

* **Name** — An editable text field. Just click it, type a new name, and click away to save.
* **Delete** — Click the trash icon to remove the room (a confirmation dialog appears first).
* **Expand** — Click the chevron to reveal details and sub-rooms.

### Setting a location on the map

When you expand a room, a search/coordinates field appears. You can:

* Type an address or place name to search
* Enter latitude and longitude directly

This places the room on a map, which helps when viewing sensor data spatially (covered in the Home Dashboards section).

## Sub-rooms

Sub-rooms let you add a layer of detail within a room. For example:

| Room   | Sub-rooms                     |
| ------ | ----------------------------- |
| Garden | Greenhouse, Lawn, Raised Beds |
| House  | Upstairs, Downstairs, Attic   |
| Garage | Workshop, Storage             |

**To add a sub-room:**

1. Expand the parent room by clicking the chevron.
2. Click the **+** button that appears below the sub-room list.
3. Enter a name and click **Save**.

Sub-rooms appear nested under their parent. Each can be renamed or deleted independently.

### Showing and hiding sub-rooms

The **Show sub-locations** toggle at the top of the page controls whether sub-rooms are visible. Turn it off for a clean overview of just your main rooms; turn it on to see the full hierarchy.

This toggle is on by default.

## Tips

* **Name rooms like you talk about them.** "Kitchen" is better than "Room 3." Future you will thank present you.
* **Start simple.** You don't need sub-rooms right away. Add them later if your setup gets complex enough to need them.
* **Rooms help everywhere.** Once set up, rooms can be used to organize dashboards, filter sensor data, and group automations (covered in later sections).


---

# 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/devices/rooms.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.