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

# WebInterface

## Installation

Run `npm run webinterface` in `/Code/WebInterface/` to install all the dependencies.

### Server

Run `npm start` for the server.

### Go on With the Angular DevMode

Run `npm run angulardev` to start the DevMode for the WebApp.

## Application

![](/files/-LHgW_60j8pVt27X0GU2)

The web interface consists of two parts, the **device** and the **radio** .

### Device

If there are no devices (sensor boards) connected, you will get to see the following window:

![](/files/-LHgW_62uFmIf-_DI4Hq)

By clicking on the button *Show Device* all \[approved devices] will be listed.

Each **device** is listed with the following information:

* ID
* Manufacturer
* ProductID
* VendorID
* LocationID
* …

![](/files/-LHgW_64yLCohbK_-zAr)

You can get the information of each single **device** to check which type of sensor it is.

![](/files/-LHgW_6631tvCqFQCnli)

Furthermore the *UUID* is assigned when checking the information, if there is none existing.

![](/files/-LHgW_68IQ2xvVB7iR-M)

Generating the *UUID* is marked with a flash message.

The existing **radio module** config is selected in the next stept, which will be sent to the board. After pressing the button *Initialize*, the board is saving the configuration.

![](/files/-LHgW_6AI8pWFRrok786)

### Radio

You can find all the generated RadioHead configurations when selecting **Radio**. They can be edited or also deleted.

![](/files/-LHgW_6CaiXq5x9FRhBe)


---

# 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://linkediot.gitbook.io/linked-iot/en/dokumentation/webinterface.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.