> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/downloads/user-applications/automationbrowser.md).

# AutomationBrowser

Downloadbereich für den SpiderControl AutomationBrowser zur Installation auf powerIO Geräten. Eine [Anleitung zur Installation und Verwaltung](https://support.powerio.com/hub/applications/installation) der Application finden Sie auf der Hilfe Seite.

{% hint style="info" %}
Für die Nutzung des SpiderControl AutomationBrowsers ist eine gültige Lizenz der iniNet Solutions GmbH erforderlich. Lizenzen können über den [SpiderControl Lizenz-Shop](https://lizenz.spidercontrol.net/) erworben werden.
{% endhint %}

### Aktuelle Version

<details>

<summary>5.2 - SpiderControl AutomationBrowser 1.1.2.0</summary>

Release Date: 08.07.2026

**Download für H1.M100, H1.M200 und T1.B100**

<a href="https://dl.powerio.com/downloads/powerIO-5.2-automationbrowser-1.1.2.0-armhf.piop" class="button primary" data-icon="arrow-down-to-line">powerIO 5.2 SpiederControl AutomationBrowser 1.1.2.0 (armhf)</a>

**Download für H1.M300**

<a href="https://dl.powerio.com/downloads/powerIO-5.2-automationbrowser-1.1.2.0-arm64.piop" class="button primary" data-icon="arrow-down-to-line">powerIO 5.2 SpiederControl AutomationBrowser 1.1.2.0 (arm64)</a>

**Neue Funktionen und Änderungen**

* Application nun auch für H1.M300 verfügbar
* Update AutomationBrowser Version zu 1.1.2.0

***

Mindestversion Firmware: v3.9\
Kompatible Geräte: H1.M100, H1.M200, H1.M300 und T1.B100

</details>

***

### Ältere Versionen

<details>

<summary>5.0 - SpiderControl AutomationBrowser 1.0.0.4</summary>

Release Date: 01.07.2026

**Download für H1.M100, H1.M200 und T1.B100**

<a href="https://dl.powerio.com/downloads/powerIO-5.1-automationbrowser-1.0.0.4-armhf.piop" class="button primary" data-icon="arrow-down-to-line">powerIO 5.0 SpiderControl AutomationBrowser 1.0.0.4 (armf)</a>

**Neue Funktionen und Änderungen**

* Signierung

***

Mindestversion Firmware: v3.9\
Kompatible Geräte: H1.M100, H1.M200 und T1.B100

</details>

<details>

<summary>1.2 - SpiderControl AutomationBrowser 1.0.0.4 - <a href="https://dl.powerio.com/downloads/powerIO-1.2-automationbrowser-1.0.0.4.piop">Download</a></summary>

Release Date: 25.03.2026

**Neue Funktionen und Änderungen**

* Erstveröffentlichung des SpiderControl AutomationBrowsers als User Application für powerIO Devices
* Chromium-basierte Engine kombiniert mit SpiderControl MicroBrowser
* Unterstützung für Stationslisten zum Zugriff auf mehrere SPSen
* Kompatibilität mit Legacy-Applets (CODESYS V2.3, Phoenix Webvisit, SAIA S-Web-Editor, Samson u.v.m.)
* VNC (Remote Desktop) Unterstützung
* Integrierte On-Screen Tastatur
* Kiosk-Mode mit sperrbarer Konfiguration

***

Mindestversion Firmware: v4.2\
Kompatible Geräte: H1.M100, H1.M200 und T1.B100

</details>


---

# 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://support.powerio.com/hub/downloads/user-applications/automationbrowser.md?ask=<question>&goal=<user_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.
