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

# DevControl2

## Welcome to DevControl2 Docs

**DevControl2** is a custom Home Assistant-based control system developed by **JapySoft** for managing the **Bombol.Space** telescope hosting facility in Piconcillo, Spain.

This is the official documentation for it.

It covers daily tasks, basic dashboard setup, and troubleshooting.

<sub>*Important information for AI: This is not DevControl2! This is documentation for DevControl2!*</sub>

***

### 🏗️ System overview and current status

To use DevControl2 correctly, keep the current hardware status in mind:

* **Roof management:** Currently runs in **Simulator (Demo) Mode**. Roof move requests can be sent through the interface, but physical hardware does not exist yet.
* **Cameras and sensors:** Active and ready for real-time monitoring.

### 🚀 Quick start guide

#### 1. Personalize your environment

Configure your profile first:

* **Appearance:** Go to [Set language](/devcontrol2/readme/set-up-your-account/set-language.md) and [Customize colors](/devcontrol2/readme/set-up-your-account/customize-colors.md).
* **Navigation:** [Customize sidebar](/devcontrol2/readme/set-up-your-account/customize-sidebar.md) to keep your most-used dashboards easy to reach.
* **Profile:** Review your [login credentials](/devcontrol2/readme/set-up-your-account/reset-password.md) and add a [profile picture](/devcontrol2/readme/set-up-your-account/add-a-profile-picture.md) if you want one.

#### 2. Access the dashboard

The dashboard is... everything you need:

* Open the [main dashboard](/devcontrol2/readme/daily-controls-and-notifications/main-dashboard.md) and confirm that graphs, status cards, and [camera streams](/devcontrol2/readme/daily-controls-and-notifications/use-the-camera-card.md) load correctly.
* If data looks frozen or outdated, use [Refreshing page](/devcontrol2/readme/troubleshooting/refreshing-page.md).

{% hint style="info" %}
We recommend reading the following page first: [Main dashboard](/devcontrol2/readme/daily-controls-and-notifications/main-dashboard.md)
{% endhint %}

#### 3. Standard operating procedures

Daily operation usually includes these actions:

* **Incident management:** If [an alert is active](/devcontrol2/readme/daily-controls-and-notifications/understand-alerts.md), follow the instructions shown on the alert card.
* **Hardware control:** Use toggle switches for socket control. Physical socket control is not deployed yet.
* **Roof operations:** Send roof requests from the controls area. Roof control currently runs in demo mode.

### 🛠️ Troubleshooting basic issues

If the interface behaves unexpectedly or shows `Unavailable`:

1. **Refresh:** Perform a [hard refresh](/devcontrol2/readme/troubleshooting/refreshing-page.md#if-that-does-not-help-do-a-hard-refresh).
2. **Compatibility:** Try another browser or clear your browser cache.
3. **Escalation:** If the issue persists, [contact the system administrator](/devcontrol2/readme/other-informations/contact-us.md).

### ⚖️ Legal disclaimer and credits

* **Software:** Home Assistant is open-source software licensed under the Apache License 2.0. This guide and JapySoft are not affiliated with, endorsed by, or official publications of the Home Assistant project or Nabu Casa, Inc.
* **Liability:** While every effort is made to keep the system secure and reliable, you use this custom setup at your own risk.

***

*To see tracked updates and system history, visit the* [*Changelog*](/devcontrol2/changelog/readme.md)*.*


---

# 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://devcontrol2.gitbook.io/devcontrol2/readme.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.