> For the complete documentation index, see [llms.txt](https://wshomedocs.cr-i.tr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wshomedocs.cr-i.tr/readme.md). # Welcome to Smart Home **A modern, open-source Smart Home Automation Platform** designed for seamless device control, modular architecture, and real-time interaction. Smart Home System enables you to: * 🔌 Connect and manage IoT devices with WebSocket support * 🧠 Host your own backend powered by Kotlin & Spring Boot * 🎨 Interact via a beautiful, responsive React-based UI * 🐘 Persist data using PostgreSQL * 🔐 Authenticate users securely with JWT Whether you're a maker, developer, or enthusiast — Smart Home gives you full control over your connected environment.\ Everything runs **locally or in the cloud**, with a **one-line Docker install** and full flexibility. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wshomedocs.cr-i.tr/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.