Loxone



To begin, enter your email address and choose a password

Physics - Electricity

ENGLISH - Physical basics explained simply voluntary for all who want to refresh their electrical knowledge!
  • Loxone's system solves this problem firstly by having temperature sensors in each room, (they're hidden in the smart light-switches) and secondly by taking remote control of each of your radiator.
  • The Loxone Miniserver is the foundation of all building automation projects from smart homes to commercial projects and beyond. When paired with the Loxone App, all intelligent building functions become clearly and conveniently in view. The Loxone App provides access to lighting, shading, music, security and temperature.
  • Since Loxone is a single manufacturer, that means that the choice is limited to products offered by Loxone. If Loxone ever stops its business or chooses updated standards, older hardware may become obsolete and/or difficult to maintain. De gustibus coloribusque non est disputandum, but choice in terms of style is limited to Loxone devices.

Loxone: Best Workplace for Performers

E-Mail, Teams, CRM, ...

Why Loxone? - Customers and Partners?

Information for potential partners

Loxone Standards & Product Basics

Vorbereitungskurs GERMAN

Installation der Software und Inbetriebnahme des Musterkoffers

Foundation Preparation Course ENGLISH

Installation of Loxone Config and commissioning of the Demo Case

KA´s Config-Peripherietypen

Knowledge Assessment Loxone Eingänge / Ausgänge

KA´s Verkabelung&Installation

Knowledge Assessment zur Loxone Link Technologie

KA´s Übergreifende Funktionen

Loxone
Knowledge Assessment zum Thema Beleuchtung

KA´s Wiring & Installation

Knowledge Assessment for the Loxone Link Technology

KA´s Config-Periphery

Knowledge Assessment for Loxone Inputs and Outputs

KA´s Overlapping Functions

Knowledge Assessment for the World of Lighting

Our API provides programmatic access to loxone, enabling anyone to write innovative applications and utilities on top of our rich database.

What can I do with the API?

Anything you want! The sky is the limit for awesome applications built using our database of guides. We can't wait to see what you come up with!

The API provides access to our guides (step-by-step guides and namespace pages), categories, users, teams, and our reputation badges.

The API responds with JSON by default, but you can also request XML (on some endpoints). For human-palatable formatted json, append ?pretty to the end of any request.

Loxone

If you build on our API, we will support you by maintaining future compatibility. Make sure to version your API calls with 2.0. When we introduce changes that may break existing apps, we will increment the version number.

Getting Started

The best way to get started is to just dive right in! You don't need an app id for most requests, so you can start writing your app right now. Here's an example API call:

Pretty simple! If you want to build an offline tool, an archived collection of oManual files is also available.

HTTP Request Methods

Where possible, we use appropriate HTTP verbs for each action. For a more detailed explanation, check out the full list of HTTP Request Methods.

GET
Retrieve a specific resource.
POST
Create a new resource.
PATCH
Update to a resource, only changing the provided attributes.
PUT
Replace a resource. If the resource doesn't exist, it is created.
DELETE
Delete a resource. This is also used in actions such as un-favoriting and un-completing a guide.

If your HTTP library doesn't support all request methods listed above, perform an HTTP POST request and set the method override header as follows:

Client Errors

Loxone Config

We use HTTP Status Codes to notify the client of any problems that occurred during the request. Each response includes a status code which will tell you if the request succeeded or failed and why.

If the request failed, you'll receive one of seven responses:

Loxone
  1. 400 Bad Request — Invalid JSON in request body.
  2. 401 Unauthorized — Authentication required.
  3. 403 Forbidden — User has insufficient privileges to perform request on specified resource.
  4. 404 Not Found — Resource does not exist.
  5. 405 Method Not Allowed — Unsupported HTTP request method for endpoint.
  6. 409 Conflict — Conflict during save of resource. This is caused by the provided revisionid being different than the current version. The response body is the current version of the resource. See Revisionids.
  7. 422 Unprocessable Entity — Unable to satisfy request due to semantic errors. This is typically caused by missing fields or fields that contain invalid data. Requirements for specific fields are specified for each endpoint. Often, the response body will contain more information about the failure.

Authentication

Loxone Reviews

Authentication through the API is done using authentication tokens which can be retrieved from the Authentication endpoints.

Loxone

Loxone Cz

Here is an example request using curl: