# myIO (npm · myio-mcp)

Read and control a myIO smart home controller: heating, lighting, blinds and energy.

- Trust score: 66/100 (medium)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `myio-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/smarthomeninja-myio-mcp/myio-mcp.md), [page](https://verifymcp.io/servers/smarthomeninja-myio-mcp/myio-mcp)

## Channel facts

- Registry: `npm`
- Package: `myio-mcp`
- Version: `1.6.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 17593 tokens (~135/item across 130 items; 102 tools + 28 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 77/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 32% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 104 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the myIO MCP server?

myIO runs locally as an npm package, launched with npx -y myio-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add smarthomeninja-myio-mcp -- npx -y myio-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "smarthomeninja-myio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "myio-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "smarthomeninja-myio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "myio-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add smarthomeninja-myio-mcp -- npx -y myio-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "smarthomeninja-myio-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "myio-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add smarthomeninja-myio-mcp --command npx --arg -y --arg myio-mcp
```

### Hermes

```yaml
mcp_servers:
  smarthomeninja-myio-mcp:
    command: "npx"
    args: ["-y", "myio-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "smarthomeninja-myio-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "myio-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add smarthomeninja-myio-mcp -t stdio -c npx -a -y myio-mcp
```

### Other

```json
{
  "mcpServers": {
    "smarthomeninja-myio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "myio-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 63, +15)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 1.6.1 → 1.6.2

### 2026-11-14 (score 48)

First indexed and scored.

## MCP tools (102)

### `myio_servers` (~57 tokens)

Configured myIO controllers

List the configured controllers (name, URL) with a live check: firmware version, device name, permission level, reachability. Use the name as the `server` argument of the other tools; without it the first controller is used.

### `myio_info` (~134 tokens)

myIO controller info

Identify the controller: serial, firmware version, CPU/board, device name, element counts (RQ relays, SQ inputs, PCAQ PCA channels, SHQ Shelly, SENQ universal sensors), the permission level of this account (0 admin, 1 editor, 2 user), uptime, found I2C expanders and storage health. Call this first: the version decides which features exist (3.12.x = Due, only base features; 4.x = GIGA/Opta, all features).

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_find` (~81 tokens)

Find by name

Search outputs, groups, sensors, inputs and universal sensors by name (accent- and case-insensitive substring, e.g. "nappali"). Returns ids and live state so you can use the right control tool.

Input parameters:

- `query` (string, required): name fragment
- `server` (string): controller name (default 192.168.1.170)

### `myio_list_devices` (~184 tokens)

List myIO outputs

List outputs with id, name, live state and level: relays (1..RQ), FET/PWM channels (101..116, only on old hardware), PCA dimmer channels (2001..2000+PCAQ), groups (501..). Shows roles in braces: thermostat / sun-controlled / mixer / shutter-up / shutter-down / joiner / rgb:<group> / group:<group>, thermostat thresholds, running timers and group members. By default only NAMED elements are listed (unnamed ones are counted); set include_unnamed=true to see all. Use the ids with the control tools.

Input parameters:

- `include_unnamed` (boolean): also list elements without a name (default false)
- `server` (string): controller name (default 192.168.1.170)
- `type` (string): only this type

### `myio_read_sensors` (~174 tokens)

Read myIO sensors

All sensor readings in real units: 1-Wire temperature (ids 1..100, °C), humidity (101..110, %), pulse energy meter (200), SDM630 power/voltage/current per phase (201..209: W, V, A), and on 4.x firmware the universal sensors (usens 0..SENQ: temperature, humidity, dew point, power, energy, CO2 ... from KNX/Modbus/MQTT/Shelly/Script; activator id = 300+id). Invalid/missing sensors read "invalid"; STALE = no fresh value within the failsafe time.

Input parameters:

- `kind` (string): only this kind
- `server` (string): controller name (default 192.168.1.170)

### `myio_get_status` (~202 tokens)

Raw myIO JSON

Fetch a raw JSON endpoint of the controller. Default sens_out.json (live state of all outputs and sensors, minimal fields). Others: d_sens_out.json (with names), f_sens_out.json (all fields), sens_IO.json (+inputs, 4.3.12+/3.12.7+), output.json, relay.json, pca.json, groups.json, prot.json, joiner.json, sensor.json, info.json, usensor.json / shelly.json / link.json / sysdiag.json / flowtrace.json / prog.json / ai.json / alarm.json (4.x, editor level). Keys the account has no permission for are simply absent. Values: temp ×100, hum ×10, thresholds ×10, PCA level 0..255.

Input parameters:

- `endpoint` (string): file name, e.g. sens_out.json
- `server` (string): controller name (default 192.168.1.170)

### `myio_output` (~169 tokens)

Switch or dim any output

One tool for every output type, by id: relay (1..RQ), FET (101..116), group (501..), PCA dimmer (2001..). action: on | off | toggle | level (level needs `level` 0..255 or `percent` 0..100; PCA/FET only). ON on a dimmer = its configured MAX, OFF = MIN. Reads the state back.

Input parameters:

- `action` (string, required)
- `id` (integer, required): element id
- `level` (integer): raw level 0..255 (action=level)
- `percent` (number): level in percent (action=level, when level is not given)
- `server` (string): controller name (default 192.168.1.170)

### `myio_relay_on` (~79 tokens)

Relay ON

Turn ON a relay output. id = relay id 1..RQ (see myio_info / myio_list_devices). The reply shows the state read back from the controller.

Input parameters:

- `id` (integer, required): relay id (1..RQ)
- `server` (string): controller name (default 192.168.1.170)

### `myio_relay_off` (~79 tokens)

Relay OFF

Turn OFF a relay output. id = relay id 1..RQ (see myio_info / myio_list_devices). The reply shows the state read back from the controller.

Input parameters:

- `id` (integer, required): relay id (1..RQ)
- `server` (string): controller name (default 192.168.1.170)

### `myio_relay_toggle` (~81 tokens)

Relay toggle

Toggle (invert) a relay output. id = relay id 1..RQ (see myio_info / myio_list_devices). The reply shows the state read back from the controller.

Input parameters:

- `id` (integer, required): relay id (1..RQ)
- `server` (string): controller name (default 192.168.1.170)

### `myio_pca_on` (~93 tokens)

PCA ON

Turn ON a PCA channel (dimmer / universal output). id = 2001..2000+PCAQ (a 1-based channel number is also accepted). ON = the channel's configured MAX level, OFF = its MIN level.

Input parameters:

- `id` (integer, required): PCA id (2001..)
- `server` (string): controller name (default 192.168.1.170)

### `myio_pca_off` (~93 tokens)

PCA OFF

Turn OFF a PCA channel (dimmer / universal output). id = 2001..2000+PCAQ (a 1-based channel number is also accepted). ON = the channel's configured MAX level, OFF = its MIN level.

Input parameters:

- `id` (integer, required): PCA id (2001..)
- `server` (string): controller name (default 192.168.1.170)

### `myio_pca_toggle` (~92 tokens)

PCA toggle

Toggle a PCA channel (dimmer / universal output). id = 2001..2000+PCAQ (a 1-based channel number is also accepted). ON = the channel's configured MAX level, OFF = its MIN level.

Input parameters:

- `id` (integer, required): PCA id (2001..)
- `server` (string): controller name (default 192.168.1.170)

### `myio_pca_set` (~150 tokens)

PCA level

Set a PCA channel to an exact level. Give either level (raw 0..255, what the controller stores and shows) or percent (0..100, converted to 0..255). If the channel has an auto-off timer, setting it above MIN (re)starts the timer. id = 2001..2000+PCAQ.

Input parameters:

- `id` (integer, required): PCA id (2001..)
- `level` (integer): raw level 0..255
- `percent` (number): level in percent (0..100), used when level is not given
- `server` (string): controller name (default 192.168.1.170)

### `myio_pwm_on` (~78 tokens)

PWM ON

Turn ON a FET/PWM output (legacy hardware only; ids 101..116 - absent on most GIGA/Opta controllers, see myio_list_devices).

Input parameters:

- `id` (integer, required): FET id (101..116)
- `server` (string): controller name (default 192.168.1.170)

### `myio_pwm_off` (~78 tokens)

PWM OFF

Turn OFF a FET/PWM output (legacy hardware only; ids 101..116 - absent on most GIGA/Opta controllers, see myio_list_devices).

Input parameters:

- `id` (integer, required): FET id (101..116)
- `server` (string): controller name (default 192.168.1.170)

### `myio_pwm_toggle` (~77 tokens)

PWM toggle

Toggle a FET/PWM output (legacy hardware only; ids 101..116 - absent on most GIGA/Opta controllers, see myio_list_devices).

Input parameters:

- `id` (integer, required): FET id (101..116)
- `server` (string): controller name (default 192.168.1.170)

### `myio_pwm_set` (~91 tokens)

PWM level

Set a FET/PWM output level: level (raw 0..255) or percent (0..100). Legacy hardware only (ids 101..116).

Input parameters:

- `id` (integer, required): FET id (101..116)
- `level` (integer)
- `percent` (number)
- `server` (string): controller name (default 192.168.1.170)

### `myio_group_on` (~85 tokens)

Group ON

Turn ON all members of a group of outputs. id = 501..520 (1..20 also accepted). Group commands need EDITOR level on most firmware (a plain user cannot switch groups even with member permissions).

Input parameters:

- `id` (integer, required): group id (501..)
- `server` (string): controller name (default 192.168.1.170)

### `myio_group_off` (~85 tokens)

Group OFF

Turn OFF all members of a group of outputs. id = 501..520 (1..20 also accepted). Group commands need EDITOR level on most firmware (a plain user cannot switch groups even with member permissions).

Input parameters:

- `id` (integer, required): group id (501..)
- `server` (string): controller name (default 192.168.1.170)

### `myio_group_toggle` (~101 tokens)

Group toggle

Smart-toggle a group of outputs. id = 501..520 (1..20 also accepted). Group commands need EDITOR level on most firmware (a plain user cannot switch groups even with member permissions). Mixed state: pullUP=1 turns ALL ON, pullUP=0 turns ALL OFF.

Input parameters:

- `id` (integer, required): group id (501..)
- `server` (string): controller name (default 192.168.1.170)

### `myio_send_command` (~195 tokens)

Raw myIO command

Send raw command(s) to the controller, chained with &, e.g. "r_ON=16&r_OFF=5&PCA*2001=128" (PCA level is RAW 0..255). Covers everything in the API reference: thresholds min_temp_ON*<id>=<x10>, names r_descr*<id>=<text>, timers r_timer*<id>=<s>, scene load lo_all=<slot>, button simulation s_hit=<id>, usens*<id>=<x10> etc. Toggle-type config commands (relaysInvert=<id>, PCA_PWM=<id>...) INVERT the flag - read the current value first. Body limit 1024 bytes. The reply lists which outputs changed state.

Input parameters:

- `commands` (string, required): command string, key=value pairs joined with &
- `server` (string): controller name (default 192.168.1.170)

### `myio_inputs` (~114 tokens)

Physical inputs

State of the physical inputs (wall buttons / switches): id (1..SQ), name, pressed/closed now, enabled, NC. Polled state, not events - a short press can be missed. Needs 4.3.12+ or Due 3.12.7+; inputs the account has no permission for are absent.

Input parameters:

- `only_active` (boolean): only inputs that are pressed/closed now
- `server` (string): controller name (default 192.168.1.170)

### `myio_press_button` (~114 tokens)

Simulate a button

Simulate a wall button on input id (1..SQ): kind hit = short press (default), press = long press, release = release after a long press. The controller runs the actions bound to that input (switch/dim/group/scene), exactly like the physical button. The reply lists the outputs that changed.

Input parameters:

- `id` (integer, required): input id (1..SQ)
- `kind` (string)
- `server` (string): controller name (default 192.168.1.170)

### `myio_thermostats` (~109 tokens)

Thermostats

Outputs controlled by a sensor: thermostat zones (relay or PCA switched by a temperature sensor: target = middle of the ON/OFF thresholds, band = their distance, mode heat if ON<OFF else cool, current temperature, heating/idle), humidity-controlled outputs, sun-controlled outputs (sunrise/sunset) and analog mixers. Use the ids with myio_set_thermostat.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_set_thermostat` (~263 tokens)

Set thermostat

Change a thermostat zone: target temperature (°C, keeps the band), band / hysteresis (°C 0.1..10, keeps the middle), or the raw ON/OFF thresholds (°C). Optionally bind the sensor: sensor = 1..100 (1-Wire id), 301.. (universal sensor 300+id), 0 = unbind (editor level). Heating = ON below OFF, cooling = ON above OFF. The controller switches the output itself; the reply reads the zone back.

Input parameters:

- `band` (number): band / hysteresis °C (0.1..10)
- `id` (integer, required): relay id (1..RQ) or PCA id (2001..) of the zone
- `off` (number): OFF threshold °C (raw; use with on)
- `on` (number): ON threshold °C (raw; use with off)
- `sensor` (integer): bind this sensor id (1..100 1-Wire, 301+ usens, 0 = unbind)
- `server` (string): controller name (default 192.168.1.170)
- `target` (number): target °C (-30..100)

### `myio_shutters` (~84 tokens)

Shutters / covers

Shutters, blinds, gates and other UP/DOWN pairs defined as protection pairs on the controller (the two outputs can never be on together): index, name, up and down relay ids, state opening / closing / stopped. Use myio_shutter to move them.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_shutter` (~136 tokens)

Move a shutter

Move a shutter / cover: action open (down off, up on), close (up off, down on) or stop (both off). Identify it by index (from myio_shutters) or by the id of its up relay. The controller enforces the mutual exclusion; the motor runs until its end switch or until you stop it.

Input parameters:

- `action` (string, required)
- `index` (integer): pair index from myio_shutters
- `server` (string): controller name (default 192.168.1.170)
- `up_id` (integer): id of the UP output instead of index

### `myio_rgb` (~87 tokens)

RGB lights

RGB lights = groups whose name starts with "RGB", with R/G/B channels (PCA or FET outputs whose names start with R, G, B). Shows on/off, colour (max-normalised 0..255) and brightness (0..255, the highest channel level).

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_set_rgb` (~152 tokens)

Set RGB light

Control an RGB light (group id from myio_rgb): on/off, colour r,g,b (0..255 each; the brightness is kept unless given), brightness 0..255 (keeps the colour). ON without colour restores the last colour (white at first). The channel levels are written directly (PCA*<id>=<level>) and read back.

Input parameters:

- `b` (integer)
- `brightness` (integer)
- `g` (integer)
- `id` (integer, required): RGB group id (501..)
- `on` (boolean)
- `r` (integer)
- `server` (string): controller name (default 192.168.1.170)

### `myio_usensors` (~128 tokens)

Universal sensors

4.x: the universal sensor slots (0..SENQ): name, type (temperature, humidity, dew point, power, energy, CO2 ...), value, ok / STALE / no value, failsafe time, enabled. Sources: KNX, Modbus, MQTT, Shelly, Script, external HTTP (usens*<id>=). Activator id for thermostats = 300+id. Needs editor level.

Input parameters:

- `include_disabled` (boolean)
- `server` (string): controller name (default 192.168.1.170)

### `myio_set_usens` (~138 tokens)

Write a universal sensor

4.x: push a value into a universal sensor slot (id 0..SENQ) from outside, e.g. a temperature from another system: value in real units (21.5 °C -> stored as 215). Thermostats, Flow, MQTT and logs see it like any sensor. The slot must be enabled; the reply reads it back.

Input parameters:

- `id` (integer, required): usens id (0..SENQ)
- `server` (string): controller name (default 192.168.1.170)
- `value` (number, required): value in real units (one decimal is kept)

### `myio_config_vars` (~106 tokens)

Raw settings variables

The raw settings block of the controller (the JS variables behind the Setup page: energy manager, SDM, dew point, sensor tables, every array). Give `names` to read specific variables, or `prefix` to list those starting with it; without arguments the variable names are listed. Editor/admin level.

Input parameters:

- `names` (array)
- `prefix` (string)
- `server` (string): controller name (default 192.168.1.170)

### `myio_globals` (~117 tokens)

Controller settings

Global settings: device name, controller clock, time zone (+ automatic EU daylight saving time on/off and whether summer time is in force, 3.12.35 / 4.18.9+), location (for sunrise/sunset), today's sunrise/sunset, button timing (hit/press limits), protection cooldown (4.x), sensor polling periods, pulse meter unit, current/boot scene slot, loggers. Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_set_globals` (~303 tokens)

Change controller settings

Change global settings: name, time_zone (hours from UTC; with automatic DST on it is the STANDARD/winter offset, e.g. 1 for Central Europe - changing it moves the clock at once on 3.12.35 / 4.18.9+), auto_dst (true/false: automatic EU daylight saving time, 3.12.35 / 4.18.9+, on by default; stored at once, no save needed), latitude/longitude, hit_time_limit / press_time_limit (ms), prot_cooldown (s, 4.x), temp_timer / hum_timer / mixer_timer (sensor polling s), impulse_per_unit, consumption_unit, sync_time=true (NTP sync now). Only the given fields change. Editor/admin level.

Input parameters:

- `auto_dst` (boolean)
- `consumption_unit` (string)
- `hit_time_limit` (integer)
- `hum_timer` (integer)
- `impulse_per_unit` (integer)
- `latitude` (number)
- `longitude` (number)
- `mixer_timer` (integer)
- `name` (string)
- `press_time_limit` (integer)
- `prot_cooldown` (integer)
- `server` (string): controller name (default 192.168.1.170)
- `sync_time` (boolean)
- `temp_timer` (integer)
- `time_zone` (integer)

### `myio_rename` (~161 tokens)

Rename an element

Set the name (description) of an element. kind: relay (id 1..RQ), pca (2001.. or channel 1..), fet (101..), group (501.. or 1..), input (1..SQ), thermo (1-Wire sensor id 1..100), humidity (channel index 0..), usens (4.x, id 0..SENQ), shelly (4.x), scene (slot 0..). Empty name clears it. Editor level; accents are fine.

Input parameters:

- `id` (integer, required)
- `kind` (string, required)
- `name` (string, required)
- `server` (string): controller name (default 192.168.1.170)

### `myio_output_config` (~136 tokens)

Output configuration

Configuration of outputs (relay, FET, PCA): auto-off timer, turn-on delay, inverted wiring, alarm flag, justOn (a button can only switch it on), PCA min/max level, fade speed, PWM (dimmer) vs switch mode, mixer mode, sensor binding and thresholds. Give id for one output, type for one kind, or nothing for all named ones. Editor/admin level.

Input parameters:

- `id` (integer)
- `include_unnamed` (boolean)
- `server` (string): controller name (default 192.168.1.170)
- `type` (string)

### `myio_set_output_config` (~212 tokens)

Change output configuration

Change an output's configuration (relay 1..RQ, FET 101.., PCA 2001..): timer_s (auto-off, 0 = off), delay_s (turn-on delay), invert, alarm, just_on, and for PCA/FET: min / max level (0..255), fade_speed, pwm (dimmer mode), mixer. Flags are set to the given value (the controller's toggle commands are only sent when the value differs). Editor level.

Input parameters:

- `alarm` (boolean)
- `delay_s` (integer)
- `fade_speed` (integer)
- `id` (integer, required): output id
- `invert` (boolean)
- `just_on` (boolean)
- `max` (integer)
- `min` (integer)
- `mixer` (boolean)
- `pwm` (boolean)
- `server` (string): controller name (default 192.168.1.170)
- `timer_s` (integer)

### `myio_input_config` (~137 tokens)

Input configuration

What the physical inputs (wall buttons) do: enabled, NC contact, hit-block, and the targets of hit (short press), press (long press) and release in the unified id space (relay 1.., FET 101.., group 501.., scene 1000+slot, PCA 2001.., LED strip 3100+). Give id for one input; otherwise the named / bound ones. Editor/admin level.

Input parameters:

- `id` (integer)
- `include_unused` (boolean)
- `server` (string): controller name (default 192.168.1.170)

### `myio_set_input_config` (~170 tokens)

Change input configuration

Change a physical input (1..SQ): enabled, nc (normally closed), hit_block, and the action targets hit / press / release as element ids (0 = none; relay 1.., FET 101.., group 501.., load scene 1000+slot, PCA 2001.., LED strip 3100+). Flags are set to the given value. Editor level.

Input parameters:

- `enabled` (boolean)
- `hit` (integer)
- `hit_block` (boolean)
- `id` (integer, required): input id (1..SQ)
- `nc` (boolean)
- `press` (integer)
- `release` (integer)
- `server` (string): controller name (default 192.168.1.170)

### `myio_structures` (~93 tokens)

Protection pairs, joiners, groups

The structural configuration: protection pairs (two outputs never on together = shutters; index, UP, DOWN, priority), joiner pairs (master switches the slave too; justOn), groups (id 501.., members in the unified id space, pullUp = mixed state toggles to ON). Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_set_protection` (~150 tokens)

Set a protection pair

Define or clear a protection pair (index 0..PQ-1, or omit index: an identical existing pair is reused, otherwise the first free one): up and down = output ids that may never be on together (relay 1.., PCA 2001..); 0/0 clears the pair. priority = the first (UP) element wins when both are requested. A pair makes a shutter for myio_shutters. Editor level.

Input parameters:

- `down` (integer, required)
- `index` (integer)
- `priority` (boolean)
- `server` (string): controller name (default 192.168.1.170)
- `up` (integer, required)

### `myio_set_joiner` (~123 tokens)

Set a joiner pair

Define or clear a joiner pair (index 0..JQ-1, or omit: an identical existing pair is reused, otherwise the first free one): switching master also switches slave (ids in the unified space); 0/0 clears. just_on = the slave only follows switching ON. Editor level.

Input parameters:

- `index` (integer)
- `just_on` (boolean)
- `master` (integer, required)
- `server` (string): controller name (default 192.168.1.170)
- `slave` (integer, required)

### `myio_set_group` (~156 tokens)

Set group members

Set the member list of a group (id 501..): members = output ids (relay 1.., FET 101.., PCA 2001.., fade variants 4001.. allowed), at most groupSize (usually 10); an empty list clears the group. pull_up = when members are mixed, toggle turns ALL ON (false: all OFF). The controller refuses a group that would contain itself. Editor level.

Input parameters:

- `id` (integer, required): group id (501..) or 1..
- `members` (array, required)
- `name` (string)
- `pull_up` (boolean)
- `server` (string): controller name (default 192.168.1.170)

### `myio_scenes` (~91 tokens)

Scenes (configuration slots)

Scene slots: a slot stores a complete configuration snapshot (outputs, groups, protection, inputs, globals ...) that can be loaded by a timer, a button (target 1000+slot) or myio_scene. Shows the slot list with names, the current and the boot slot. Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_scene` (~116 tokens)

Scene action

Scene slots: load (apply slot - this changes outputs and settings), save (store the CURRENT configuration into slot, overwriting it), new (create the next free slot), delete (slot 0 and the boot slot cannot be deleted), set_boot (slot loaded at power-up), rename. Editor level; save/delete are destructive.

Input parameters:

- `action` (string, required)
- `name` (string)
- `server` (string): controller name (default 192.168.1.170)
- `slot` (integer)

### `myio_timers` (~84 tokens)

Timers

Scheduled actions from timer.csv: time (or sunrise/sunset with ± offset), optional month/day, weekday filter (empty = every day), event (relay/FET/group/PCA ON/OFF, load scene, SG-Ready mode) and target. Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_set_timer` (~291 tokens)

Create or change a timer

Create (omit id; an identical existing timer is not duplicated) or change (id) a timer. Time: hour 0..23 + minute 0..59, or sunrise / sunset = "after" | "before" with hour/minute as the offset (max 4 h). Optional month (1..12) and day (1..31) for a one-day timer. days: weekday names ["Mon","Fri"] (omit = every day). event: code or name - 1 load scene (all), 2 relay ON, 3 relay OFF, 4 FET ON, 5 FET OFF, 6 group ON, 7 group OFF, 15 PCA ON, 16 PCA OFF, 8..14/17 load scene parts, 18 SG-Ready mode. param: the target id (relay/FET/group/PCA id, scene slot, SG mode 1..4). Editor level.

Input parameters:

- `day` (integer)
- `days` (array)
- `event` (required)
- `hour` (integer)
- `id` (integer)
- `minute` (integer)
- `month` (integer)
- `param` (integer, required)
- `server` (string): controller name (default 192.168.1.170)
- `sunrise` (string)
- `sunset` (string)

### `myio_delete_timer` (~53 tokens)

Delete a timer

Delete the timer with the given id (from myio_timers). Editor level.

Input parameters:

- `id` (integer, required)
- `server` (string): controller name (default 192.168.1.170)

### `myio_users` (~59 tokens)

User accounts

The user accounts of the controller: slot, login name, level (admin / editor / user). Slot 0 is the admin. Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_user` (~136 tokens)

Manage a user

User accounts (ADMIN level): action new (next free slot), delete (slot, not 0), rename (slot + name), set_password (slot + password; the login name of the slot is used), set_rights (slot + rights admin|editor|user; not slot 0). Changing the account the server itself uses will break the connection.

Input parameters:

- `action` (string, required)
- `name` (string)
- `password` (string)
- `rights` (string)
- `server` (string): controller name (default 192.168.1.170)
- `slot` (integer)

### `myio_permissions` (~101 tokens)

User element permissions

Element permissions of a user slot (4.x): read / write per relay (and FET), hit / press per input - the lists of element ids the user may see / switch. On Due 3.x the map cannot be read (only set with fill/clear and explicit toggles). Admin level reads it too.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)
- `slot` (integer, required)

### `myio_set_permissions` (~166 tokens)

Change user element permissions

Change the element permissions of a user slot (ADMIN). fill = grant everything, clear = revoke everything. Then per list the ids to GRANT or REVOKE: relay_read, relay_write, pca_read, pca_write, fet_read, fet_write (output ids), input_hit, input_press (input ids). On 4.x the current map is read first and only differences are sent; on Due 3.x the firmware toggles are sent as given (each id flips its bit).

Input parameters:

- `clear` (boolean)
- `fill` (boolean)
- `grant` (object)
- `revoke` (object)
- `server` (string): controller name (default 192.168.1.170)
- `slot` (integer, required)

### `myio_flows` (~138 tokens)

Flow rules

The Flow rule engine (GIGA/Opta 4.4+): every rule as WHEN trigger / AND conditions / THEN actions in plain words with element names, its live state (enabled, running, last fired), the 32 global variables with live values and the webhook targets. id = one rule (with its raw JSON for editing); raw=true returns the whole flows.jsn (the format myio_flow_save takes). Editor/admin level.

Input parameters:

- `id` (integer): only this flow id
- `raw` (boolean)
- `server` (string): controller name (default 192.168.1.170)

### `myio_flow_save` (~462 tokens)

Create / change / delete Flow rules

Edit flows.jsn and reload the engine (no restart). Give ONE of: flow (a whole rule object; replaces the rule with the same id or adds it), delete (flow id), variable {id,name,init} / delete_variable, hook {id,name,met,url,body,err,gap} / delete_hook, or file (the complete flows.jsn). The rule is validated against the controller's card rules first; nothing is written on error. dry_run=true only validates. Card format (keys are short): WHEN t=sens{src:thermo|hum|usens, ch|id, op:gt|lt, val x10, hyst x10} | scmp | out{id, dir 0 off/1 on/2 any} | time{min, days} | sun{ev:rise|set, off} | var{id, op, val} | boot; AND t=sens | scmp | out{id, on 0|1} | twin{from, to, days} | var; THEN t=rel|grp{id, act 0 off/1 on/2 toggle} | pca|fet{id, val 0..255} | delay{s|m} | var{id, op:set|inc|dec, val} | log{val} | msg | http{id: webhook slot, val}. days = bitmask bit0=Mon..bit6=Sun (127 = every day); minutes of day for time/twin; temperatures x10 (21.5 °C = 215). Full reference: myio_reference topic=flow. Editor/admin level.

Input parameters:

- `delete` (integer): flow id to delete
- `delete_hook` (integer)
- `delete_variable` (integer)
- `dry_run` (boolean)
- `file`: the complete flows.jsn (replaces everything)
- `flow` (object): {"id":1,"name":"...","en":1,"when":{...},"and":[...],"then":[...]}
- `hook` (object)
- `server` (string): controller name (default 192.168.1.170)
- `variable` (object)

### `myio_flow` (~148 tokens)

Run / switch a Flow rule

Runtime control of the Flow engine (does NOT change flows.jsn): enable / disable a rule until the next reload or restart (use myio_flow_save en=0|1 to make it permanent), fire = run its THEN chain now (WHEN/AND skipped), set_var = set global variable id (1..32) to value (variable triggers are evaluated). The answer shows the outputs that changed and the trace. Editor/admin level.

Input parameters:

- `action` (string, required)
- `id` (integer, required): flow id, or the variable id for set_var
- `server` (string): controller name (default 192.168.1.170)
- `value` (integer)

### `myio_flow_trace` (~103 tokens)

Flow trace

What the Flow engine did recently (newest first): fired, AND failed, actions, delays, errors, webhook results, with seconds ago. since = the tseq of a previous call to get only newer entries (incremental). Also the engine budget statistics. Editor/admin level.

Input parameters:

- `limit` (integer): default 40
- `server` (string): controller name (default 192.168.1.170)
- `since` (integer)

### `myio_webhook_test` (~85 tokens)

Test a webhook

Fire webhook slot 1..8 (as loaded from flows.jsn hooks[]) once, without the gap brake, and report the HTTP result from the trace. GIGA/Opta 4.4.1+. Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)
- `slot` (integer, required)

### `myio_scripts` (~125 tokens)

Scripts (myIO Script programs)

The program engine (GIGA/Opta 4.10+): every slot (prog/N.txt, 16 on GIGA, 8 on Opta) with name, state (off / RUNNING / ERROR with line:col and message), cycle time, runs, timing, local variables and arrays, plus the 32 global variables and (trace=true) the recent trace. Editor/admin level.

Input parameters:

- `id` (integer)
- `server` (string): controller name (default 192.168.1.170)
- `trace` (boolean)

### `myio_script_get` (~66 tokens)

Read a script

The source code of script slot N (prog/N.txt) and its state. Language reference: myio_reference topic=script. Editor/admin level.

Input parameters:

- `id` (integer, required)
- `server` (string): controller name (default 192.168.1.170)

### `myio_script_save` (~156 tokens)

Write a script

Write the source of script slot N (prog/N.txt) and recompile it on the controller; the answer is the compile result (error with line:col and the source line) and the new state. enabled=true|false rewrites the #enabled directive. The file is the truth (#name, #every 1s, #enabled, #onboot header). Max size: 8 KB on GIGA, 4 KB on Opta. Language reference: myio_reference topic=script. Editor/admin level.

Input parameters:

- `enabled` (boolean)
- `id` (integer, required)
- `server` (string): controller name (default 192.168.1.170)
- `source` (string, required)

### `myio_script` (~117 tokens)

Run / switch / delete a script

Script slot actions: reload (recompile prog/N.txt; id 0 = all), run (run once now, even if disabled), enable / disable (RAM only until reload/restart; persist=true also rewrites #enabled in the file), delete (removes prog/N.txt, needs MYIO_WRITE=config). Editor/admin level.

Input parameters:

- `action` (string, required)
- `id` (integer, required)
- `persist` (boolean)
- `server` (string): controller name (default 192.168.1.170)

### `myio_reference` (~103 tokens)

myIO language / API reference

The controller documentation bundled with this server (Hungarian, the canonical API_REFERENCE.md): topic=script = the complete myIO Script language (directives, syntax, built-in functions, error codes, examples); topic=flow = the Flow engine and the flows.jsn card format; topic=api with query = the API sections whose heading contains the query (without query: the table of contents).

Input parameters:

- `query` (string)
- `topic` (string, required)

### `myio_sysdiag` (~114 tokens)

System diagnostics

Health snapshot of the controller: uptime and last reset cause (watchdog?), main-loop speed and the longest stall, free RAM and its minimum, M4 button core, LAN link / WiFi, every network socket with its peer, outgoing HTTP slots, storage space, login brake counters. Due 3.12 gives a shorter set. raw=true = the JSON. Editor/admin level.

Input parameters:

- `raw` (boolean)
- `server` (string): controller name (default 192.168.1.170)

### `myio_metrics` (~99 tokens)

Prometheus metrics

The /metrics text (Prometheus format: uptime, loop rate, RAM, M4, link, WiFi RSSI, sockets, webhook counters, storage, usens values, 1-Wire temperatures). filter = only lines containing this text. GIGA/Opta 4.4.1+.

Input parameters:

- `filter` (string)
- `server` (string): controller name (default 192.168.1.170)

### `myio_logs` (~143 tokens)

Log files

Which daily CSV logs exist: event log (ev_log/), consumption (c_log/), SDM meter (sdm_log/), per-sensor temperature (t_log_N/), humidity (h_log_N/), universal sensor (u_log_N/). Without kind: the log folders on each volume and the newest event-log days. kind (+channel for temperature/humidity/usens) = every file of that log with size and date. Read one with myio_log. Editor/admin level.

Input parameters:

- `channel` (integer)
- `kind` (string)
- `server` (string): controller name (default 192.168.1.170)

### `myio_log` (~237 tokens)

Read a log

Read one day of a log (default: today's event log) with filters: level (error | info | debug - 4.x event log lines start with E/I/D), contains (text), since / until (HH:MM), tail (last N matching lines, default 150; 0 = all). date = YYYY-MM-DD, YYMMDD, today or yesterday; or give path (e.g. /ev_log/e_261025.csv). vol: q | s (default: the controller's own lookup, internal flash first). Editor/admin level.

Input parameters:

- `channel` (integer)
- `contains` (string)
- `date` (string)
- `kind` (string)
- `level` (string)
- `path` (string)
- `server` (string): controller name (default 192.168.1.170)
- `since` (string)
- `tail` (integer)
- `until` (string)
- `vol` (string): q = internal flash (GIGA/Opta default), s = SD card (the only volume on a Due)

### `myio_files` (~115 tokens)

List files

List a folder on the controller's storage: name, size, date; folders first; free/total space. vol q = internal flash (GIGA/Opta), s = SD card (Due: only s). Editor/admin level.

Input parameters:

- `dir` (string): default /
- `server` (string): controller name (default 192.168.1.170)
- `vol` (string): q = internal flash (GIGA/Opta default), s = SD card (the only volume on a Due)

### `myio_file_read` (~132 tokens)

Read a file

Download a file from the controller. Text files come back as text (truncated at max_bytes, default 64 KB); binary files as size + hex preview, or base64=true for the content (max 512 KB). Editor/admin level.

Input parameters:

- `base64` (boolean)
- `max_bytes` (integer)
- `path` (string, required)
- `server` (string): controller name (default 192.168.1.170)
- `vol` (string): q = internal flash (GIGA/Opta default), s = SD card (the only volume on a Due)

### `myio_file_write` (~187 tokens)

Write a file

Upload a file to the controller (creates or overwrites; the write is not atomic). content = text (UTF-8) or base64 = binary. make_dirs=true creates missing parent folders. System files (network, passwords, licence, cloud keys, web UI folders htm/ js/, slot folders) need MYIO_WRITE=admin. For flows.jsn / prog/N.txt prefer myio_flow_save / myio_script_save (validated + reloaded). Editor/admin level.

Input parameters:

- `base64` (string)
- `content` (string)
- `make_dirs` (boolean)
- `path` (string, required)
- `server` (string): controller name (default 192.168.1.170)
- `vol` (string): q = internal flash (GIGA/Opta default), s = SD card (the only volume on a Due)

### `myio_file_op` (~169 tokens)

Delete / rename / copy files

File operations: delete (a file or an EMPTY folder), mkdir, rename (move within the volume: path -> to), copy (path -> to, folders recursively; on GIGA/Opta also between volumes with to_vol). The controller refuses to delete slot_0, the boot scene slot or a slot a button/timer refers to. System files need MYIO_WRITE=admin. Editor/admin level.

Input parameters:

- `op` (string, required)
- `path` (string, required)
- `server` (string): controller name (default 192.168.1.170)
- `to` (string)
- `to_vol`
- `vol` (string): q = internal flash (GIGA/Opta default), s = SD card (the only volume on a Due)

### `myio_fm_sync` (~108 tokens)

Internal flash -> SD mirror

The QSPI -> SD card configuration mirror (GIGA/Opta 4.4.3+): op status (default), config (mirror the configuration now), web (configuration + web UI folders), adopt (adopt a foreign card: write mirror.tag, then mirror). Needs an SD card and MYIO_WRITE=admin for the actions.

Input parameters:

- `op` (string)
- `server` (string): controller name (default 192.168.1.170)

### `myio_shelly` (~122 tokens)

Shelly devices

Shelly integration (GIGA/Opta 4.1+): every registered Shelly with IP, model, online state, relay state, and its bindings (which myIO output a channel follows, which myIO button an input drives, which universal sensor a metric feeds). scan=true also shows the results of a network scan (start one with myio_shelly_set action=scan). Editor/admin level.

Input parameters:

- `scan` (boolean)
- `server` (string): controller name (default 192.168.1.170)

### `myio_shelly_set` (~379 tokens)

Configure Shelly

Change the Shelly integration; every change is saved (sh_save). action: enable (enabled=true|false), add (ip), add_found (index from the scan), scan (start=true|false), delete / probe / push (device), disable (device, disabled), rename (device, name), poll (device, ms 500..60000), auth (device, user, password), bind_output (device, channel, output_id: the Shelly channel follows that myIO output; 0 = unbind), bind_input (device, channel, button 1..SQ, mode 0 button / 1 toggle / 2 hit-only), bind_sensor (device, slot 0..3, metric 1 temp / 2 hum / 3 power / 4 volt / 5 curr / 6 energy / 7 device temp, channel, usens id; usens 0 = unbind). After input / sensor bindings send action=push so the Shelly calls back. Device = slot number from myio_shelly. Editor/admin level.

Input parameters:

- `action` (string, required)
- `button` (integer)
- `channel` (integer)
- `device` (integer)
- `disabled` (boolean)
- `enabled` (boolean)
- `index` (integer)
- `ip` (string)
- `metric` (integer)
- `mode` (integer)
- `ms` (integer)
- `name` (string)
- `output_id` (integer)
- `password` (string)
- `server` (string): controller name (default 192.168.1.170)
- `slot` (integer)
- `start` (boolean)
- `usens` (integer)
- `user` (string)

### `myio_link` (~101 tokens)

myIO Link (controller to controller)

myIO Link (GIGA/Opta 4.2+): the other myIO controllers this one polls, their online state, the output links (a local output mirrors / drives a remote one) and sensor links (a remote sensor feeds a local universal sensor). scan=true shows network scan results. Editor/admin level.

Input parameters:

- `scan` (boolean)
- `server` (string): controller name (default 192.168.1.170)

### `myio_link_set` (~286 tokens)

Configure myIO Link

Change myIO Link; saved with ml_save. action: add (ip), add_found (index), scan (start), delete / probe / refresh_names (server slot 0..), disable (server, disabled), port / poll / rename / auth (server, port | ms | name | user+password), link (index, local_id, server 1.., remote_id: local output follows the remote one), unlink (index), link_disable (index, disabled), sensor_link (index, remote_id, server 1.., local_usens), sensor_link_disable (index, disabled). Editor/admin level.

Input parameters:

- `action` (string, required)
- `disabled` (boolean)
- `index` (integer)
- `ip` (string)
- `local_id` (integer)
- `local_usens` (integer)
- `ms` (integer)
- `name` (string)
- `password` (string)
- `port` (integer)
- `remote_id` (integer)
- `server` (string): controller name (default 192.168.1.170)
- `server_no` (integer): server number 1.. for link / sensor_link
- `srv` (integer): server slot (0-based, as in myio_link)
- `start` (boolean)
- `user` (string)

### `myio_mqtt` (~110 tokens)

MQTT client

MQTT client settings and live state (GIGA/Opta 4.3+, Due 3.12.31+): broker, connection state, topics, retain/QoS, Home Assistant discovery, publish masks, subscribe/command channel, external sensor bindings (topic + JSON key -> universal sensor, 4.5+). Passwords and TLS keys are never shown. Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_mqtt_set` (~353 tokens)

Configure MQTT

Change the MQTT client. Only the given fields change; on/off fields are desired values (sent only when different). save=true (default) persists and reconnects (MqttSave). Fields: enabled, host, port, user, password, client_id, base_topic, retain, qos 0|1, ha_discovery, economy (4.x), tls (4.x), publish_on_change {buttons, outputs, activators}, periodic {outputs, temperatures, humidity, usens (4.x), sdm} + period_s 5..65000, subscribe, command_channel, command_slot; sensor_binding {slot, topic, key, usens} (4.5+; usens 0 = unbind); rediscover=true refreshes the Home Assistant entities without reconnecting. Editor/admin level.

Input parameters:

- `base_topic` (string)
- `client_id` (string)
- `command_channel` (boolean)
- `command_slot` (integer)
- `economy` (boolean)
- `enabled` (boolean)
- `ha_discovery` (boolean)
- `host` (string)
- `password` (string)
- `period_s` (integer)
- `periodic` (object)
- `port` (integer)
- `publish_on_change` (object)
- `qos` (integer)
- `rediscover` (boolean)
- `retain` (boolean)
- `save` (boolean)
- `sensor_binding` (object)
- `server` (string): controller name (default 192.168.1.170)
- `subscribe` (boolean)
- `tls` (boolean)
- `user` (string)

### `myio_cloud` (~79 tokens)

myIO Cloud

myIO Cloud remote access (GIGA/Opta 4.4+): enabled, connection state, broker, pairing window, paired phone keys (label, user slot, revoked). Credentials and keys are never shown. Admin level on the controller.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_cloud_set` (~139 tokens)

Manage myIO Cloud

myIO Cloud actions (admin): enable (enabled=true|false), pair (user_slot 1.., label: opens a 5-minute pairing window for one phone - show the QR from the web page), pair_stop, revoke (key, revoked=true|false), delete_key (key). Needs MYIO_WRITE=admin.

Input parameters:

- `action` (string, required)
- `enabled` (boolean)
- `key` (integer)
- `label` (string)
- `revoked` (boolean)
- `server` (string): controller name (default 192.168.1.170)
- `user_slot` (integer)

### `myio_sgready` (~93 tokens)

SG-Ready heat pump

SG-Ready heat pump control (GIGA/Opta 4.4.2+, Due 3.12.9+): enabled, current mode (1 inhibit / 2 normal / 3 recommended / 4 forced), K1/K2 contact outputs, utility-lock limit. Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_sgready_set` (~157 tokens)

Set SG-Ready

Change SG-Ready: mode 1..4 (immediate; mode 1 ends automatically after limit_min), enabled, k1 / k2 (output ids: relay 1.. or PCA 2001..; 0 = none; K1 and K2 must differ), limit_min 1..120. Mode is a state change (MYIO_WRITE=state); the others are configuration. Saved immediately (EEPROM).

Input parameters:

- `enabled` (boolean)
- `k1` (integer)
- `k2` (integer)
- `limit_min` (integer)
- `mode` (integer)
- `server` (string): controller name (default 192.168.1.170)

### `myio_alarm` (~121 tokens)

Alarm panel (SIA receiver)

The alarm panel receiver (GIGA/Opta 4.5.8+, SIA DC-09 over TCP/UDP): enabled, listeners, frame counters, troubles (AC, battery, tamper, communication, zone, supervision), per-partition state (disarmed / partial / armed / ALARM) with the last event code, zone and user, and the universal sensor each partition feeds. Monitoring only (no arming). Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_alarm_set` (~228 tokens)

Configure the alarm receiver

Change the SIA receiver (saved with AlarmSave): enabled, tcp, udp, ack_timestamp (desired values), port 1024..49151 (not 80/843), account (max 32), supervision_min 0..1440, partition_sensor {partition 1.., usens (0 = none)}. simulate = a DC-03 test event like "Nri1/BA01" (burglary alarm partition 1 zone 1) - drives the partition state and its usens; reset_counters=true. TCP on/off takes effect after a restart. Editor/admin level.

Input parameters:

- `account` (string)
- `ack_timestamp` (boolean)
- `enabled` (boolean)
- `partition_sensor` (object)
- `port` (integer)
- `reset_counters` (boolean)
- `server` (string): controller name (default 192.168.1.170)
- `simulate` (string)
- `supervision_min` (integer)
- `tcp` (boolean)
- `udp` (boolean)

### `myio_mia` (~113 tokens)

MIA (self-learning heating)

MIA, the self-learning heating layer (GIGA/Opta 4.11+): features (thermal model, window detection, preheating, pause), and per thermostat zone the learned heat/cool rates, dead time, over/undershoot, duty, confidence, window events, preheating plan and result. zone = one relay id. Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)
- `zone` (integer)

### `myio_mia_set` (~264 tokens)

Configure MIA

Change MIA (saved immediately): enabled, features {model, window, preheat, pause} (desired values), window_drop_c 0.1..5, window_min 2..15, window_hold_min 5..240, preheat_max_min 15..240 (4.12+), learn_days 1..6, exclude {relay, excluded} (MIA does not act on that zone), exclude_f3 {relay, excluded} (4.13+), min_on_off {relay, on_min, off_min} (0 = auto, 4.13+), reset_learned (relay id, 0 = all zones). Editor/admin level.

Input parameters:

- `enabled` (boolean)
- `exclude` (object)
- `exclude_f3` (object)
- `features` (object)
- `learn_days` (integer)
- `min_on_off` (object)
- `preheat_max_min` (integer)
- `reset_learned` (integer)
- `server` (string): controller name (default 192.168.1.170)
- `window_drop_c` (number)
- `window_hold_min` (integer)
- `window_min` (integer)

### `myio_ledstrip` (~120 tokens)

LED strips

Addressable LED strips (GIGA/Opta 4.3.4+): enabled, strips per IO pin (LED count, running program), programs (effect, speed, brightness, colours, blend/kill transitions...). prog = one program with the effect list. Event id 3100+100*(IO-1)+program starts/stops a program (buttons, timers, Flow). Editor/admin level.

Input parameters:

- `prog` (integer)
- `server` (string): controller name (default 192.168.1.170)

### `myio_ledstrip_set` (~208 tokens)

Control / configure LED strips

LED strips: event (id 3100+100*(IO-1)+program: run that program on that IO, the same id again stops it - MYIO_WRITE=state), enabled (desired), program edits (prog 1..32 with fields {fx, speed, brightness, intensity, density, length, palette, direction, color1, color2 (0xRRGGBB number), a, b, blend, blend_fx, blend_dir, kill, kill_fx, kill_dir, off_pause}, name) applied live and saved (ls_save); led_count {io 1..8, count} needs a restart. Editor/admin level.

Input parameters:

- `enabled` (boolean)
- `event` (integer)
- `fields` (object)
- `led_count` (object)
- `name` (string)
- `prog` (integer)
- `server` (string): controller name (default 192.168.1.170)

### `myio_network` (~92 tokens)

Network settings

Network configuration and live state (GIGA/Opta 4.x): host name, LAN (DHCP/static, link), WiFi mode (off / STA / AP), STA and AP settings, live addresses, RSSI, which services run on which interface. Passwords are never shown. Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_network_set` (~177 tokens)

Change network settings

DANGEROUS: a wrong value can make the controller unreachable (then only USB serial or the service access point helps). Changes: host, wifi_mode 0 off / 1 STA / 2 AP, sta {ssid, password, dhcp}, ap {ssid, password, channel 1..13}, lan {enabled, dhcp, static_primary}. apply=true saves AND applies now (no restart; the connection may drop), apply=false only saves for the next boot. Needs MYIO_WRITE=admin.

Input parameters:

- `ap` (object)
- `apply` (boolean, required)
- `host` (string)
- `lan` (object)
- `server` (string): controller name (default 192.168.1.170)
- `sta` (object)
- `wifi_mode` (integer)

### `myio_system` (~221 tokens)

Restart / firmware update

Admin actions: restart (soft reboot, ~1 min offline), ota_upload (file = local path of the firmware package the fleet tool made for THIS controller - GIGA/Opta (4.x): MYIO_UPD.BIN, uploaded to the SD card, or internal flash without a card; Due (3.12+): MYIO_NEW.BIN, SD card only, checked before upload: a raw Arduino build or a package made for another controller is refused), ota_apply (the controller installs the uploaded package and restarts; a GIGA/Opta rolls back by itself if the new image fails, a Due keeps its running firmware if the package is rejected), ota_restore (GIGA/Opta only: go back to the previous image). The answer waits for the controller to come back and reports the running version and the outcome. Needs MYIO_WRITE=admin.

Input parameters:

- `action` (string, required)
- `file` (string)
- `server` (string): controller name (default 192.168.1.170)

### `myio_expanders` (~127 tokens)

RS485 expanders

RS485 expander panels on an Opta (4.5+): per address the configured type (Ext16 I/O, Ext-KNX, Ext-DALI, Ext-DMX, Ext-RS485 Modbus), online state, firmware/protocol, last seen, failsafe/standalone rules for losing the master, AUX output modes, Ext16 1-Wire thermometers. addr = one panel (1..). Editor/admin level.

Input parameters:

- `addr` (integer)
- `server` (string): controller name (default 192.168.1.170)

### `myio_expander_set` (~241 tokens)

Configure expanders

Expander settings (Opta 4.5+): failsafe {addr, mode 0 hold / 1 all off / 2 preset / 3 standalone, timeout_s 1..250, master, rules_linked, relink_truth, autosync, thermo_stale, stale_period_s} (saved; sync=true pushes the rules to the panel now), capture_preset (addr: the current outputs become the failsafe preset), aux {addr, pin 0=AUX2 1=AUX3, mode 0 0-10V / 1 LED strip}, onewire_rescan=true, onewire_forget (eeprom id of an OFFLINE sensor), forget_panel (addr of an OFFLINE panel). Editor/admin level.

Input parameters:

- `aux` (object)
- `capture_preset` (integer)
- `failsafe` (object)
- `forget_panel` (integer)
- `onewire_forget` (integer)
- `onewire_rescan` (boolean)
- `server` (string): controller name (default 192.168.1.170)

### `myio_knx` (~108 tokens)

KNX gateway

Ext-KNX gateway on an Opta (4.5+): the group-address table of the selected panel (row, name, group address, direction IN/OUT/SENSOR, DPT, local channel, flags, target universal sensor), the KNXnet/IP tunnelling interface for ETS (4.14+) and the KNX devices found/programmed without ETS. Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_knx_set` (~225 tokens)

Edit the KNX table

Edit the Ext-KNX group-address table (the panel stores it; save=true (default) commits with KnxSave). panel = select another Ext-KNX panel first. rows: [{row 0..47, ga "main/middle/sub" ("" deletes the row), dir 0 none / 1 IN / 2 OUT / 3 SENSOR, dpt 1 bool / 2 percent / 3 float, local 0..15 (panel channel), target usens (SENSOR rows), invert, init_read (desired values), name (max 20, saved at once, 4.15+)}]. tunnel = enable/disable the ETS interface (4.14+), drop_tunnel=true closes the active ETS connection. Editor/admin level.

Input parameters:

- `drop_tunnel` (boolean)
- `panel` (integer)
- `rows` (array)
- `save` (boolean)
- `server` (string): controller name (default 192.168.1.170)
- `tunnel` (boolean)

### `myio_knx_device` (~146 tokens)

KNX devices (without ETS)

KNX device operations over the Ext-KNX panel (Opta 4.14+): scan (who is on the line, ~2 s), add (address a.l.d to the list), ping / info / delete / rename (index from myio_knx), program (address: writes the individual address into the ONE device whose programming button is pressed - needs MYIO_WRITE=admin). The answer waits for the result.

Input parameters:

- `action` (string, required)
- `address` (string)
- `index` (integer)
- `name` (string)
- `server` (string): controller name (default 192.168.1.170)

### `myio_dali` (~122 tokens)

DALI gateway

Ext-DALI gateway on an Opta (4.8.6+): panels, the registered endpoints (short address / group / broadcast), the myIO PCA channel each is bound to (dim it with myio_output), last sent and driver-reported level, desired vs driver-read parameters (fade, power-on, failure level, min/max, curve) and group membership. ep = one endpoint. Editor/admin level.

Input parameters:

- `ep` (integer)
- `server` (string): controller name (default 192.168.1.170)

### `myio_dali_set` (~434 tokens)

Configure DALI

DALI registry and driver settings (Opta 4.8.6+; saved automatically). action: bind (ep, pca_id 2001.. or 0), settings (ep, any of fade_time 0..15, fade_rate 0..15, power_on, system_failure, min, max 0..254, curve 0 log / 1 linear; write=true (default) sends them to the driver), groups (ep, group 0..15, member true|false), read (ep: read the driver), identify (ep), add (panel, address 0..63 short / 64..79 group / 80 broadcast), add_all (panel: everything the last scan found), delete (ep), pool (lo, hi PCA ids), auto_bind, scan (panel: find drivers on the bus), abort (panel), commission (panel, mode 0 = re-address ALL / 1 = only unaddressed, start 0..63 - admin), short_address (ep, new 0..63 - admin), reset (ep - admin), panel_config (panel, field 0..6, value). Editor/admin level.

Input parameters:

- `action` (string, required)
- `address` (integer)
- `curve` (integer)
- `ep` (integer)
- `fade_rate` (integer)
- `fade_time` (integer)
- `field` (integer)
- `group` (integer)
- `hi` (integer)
- `lo` (integer)
- `max` (integer)
- `member` (boolean)
- `min` (integer)
- `mode` (integer)
- `new_address` (integer)
- `panel` (integer)
- `pca_id` (integer)
- `power_on` (integer)
- `server` (string): controller name (default 192.168.1.170)
- `start` (integer)
- `system_failure` (integer)
- `value` (integer)
- `write` (boolean)

### `myio_dmx` (~91 tokens)

DMX gateway

Ext-DMX gateway on an Opta (4.9+): panels, fixtures (start address, type dimmer/RGB/RGBW/generic, channels) and the myIO PCA channel each DMX channel follows (dim it with myio_output / myio_set_rgb). Editor/admin level.

Input parameters:

- `server` (string): controller name (default 192.168.1.170)

### `myio_dmx_set` (~266 tokens)

Configure DMX

DMX fixtures (Opta 4.9+; saved automatically). action: add (panel, address 1..512, type 0 dimmer / 1 RGB / 2 RGBW / 3 generic), delete (fixture), address (fixture, address), type (fixture, type), channels (fixture, count 1..16 - generic only), bind (fixture, channel 1.., pca_id 2001.. or 0), auto_bind, pool (lo, hi), test (fixture: full on for 1.5 s - state), blackout (panel: all 512 slots to 0 - state), panel_config (panel, field 0..5, value). Editor/admin level.

Input parameters:

- `action` (string, required)
- `address` (integer)
- `channel` (integer)
- `count` (integer)
- `field` (integer)
- `fixture` (integer)
- `hi` (integer)
- `lo` (integer)
- `panel` (integer)
- `pca_id` (integer)
- `server` (string): controller name (default 192.168.1.170)
- `type` (integer)
- `value` (integer)

### `myio_modbus` (~124 tokens)

Modbus RTU master

Ext-RS485 Modbus RTU master on an Opta (4.16+): per panel the bus settings, the poll blocks (slave, function, start register, count, period), the fields decoded from them (type, byte order, scale, target universal sensor) with live values, the writer slots (myIO relay/PCA -> Modbus register), and raw-request / address-scan results. Editor/admin level.

Input parameters:

- `panel` (integer)
- `server` (string): controller name (default 192.168.1.170)

### `myio_modbus_set` (~668 tokens)

Configure / query Modbus

Modbus panel table (Opta 4.16+; the panel saves 8 s after the last change, or save=true now). action: block (panel, index 0..7, slave 1..247, func 1..4, start, count 1..125, period_s, enabled), field (panel, index 0..31, block, offset, dtype 1 u16 / 2 i16 / 3 u32 / 4 i32 / 5 f32 / 6 u64 / 7 i64 / 8 f64 / 9 bit / 10 bool, order 0 ABCD / 1 CDAB / 2 BADC / 3 DCBA, bit, scale -9..9, sf_offset (255 none), target usens, enabled, invert), writer (panel, index 0..15, slave, func 5/6/16, reg, dtype, order, source_pca, off, on, period_s, enabled, invert), delete (panel, table 0 block / 1 field / 2 writer, index), bus (panel, baud code 0 9600 / 1 19200 / 2 38400 / 3 57600 / 4 115200, frame 0 8N1 / 1 8E1 / 2 8O1 / 3 8N2, timeout_ms, retries, gap_ms), name (panel, field_index or writer_index or none for the panel, name), preset (panel, preset id e.g. SDM630), reload (panel), clear (panel - admin), raw (panel, slave, func, reg, count: one request, result shown) and scan (panel, from, to, func, reg: which slave addresses answer). Editor/admin level.

Input parameters:

- `action` (string, required)
- `baud` (integer)
- `bit` (integer)
- `block` (integer)
- `count` (integer)
- `dtype` (integer)
- `enabled` (boolean)
- `field_index` (integer)
- `frame` (integer)
- `from` (integer)
- `func` (integer)
- `gap_ms` (integer)
- `index` (integer)
- `invert` (boolean)
- `name` (string)
- `off` (integer)
- `offset` (integer)
- `on` (integer)
- `order` (integer)
- `panel` (integer, required)
- `period_s` (integer)
- `preset` (string)
- `reg` (integer)
- `retries` (integer)
- `save` (boolean)
- `scale` (integer)
- `server` (string): controller name (default 192.168.1.170)
- `sf_offset` (integer)
- `slave` (integer)
- `source_pca` (boolean)
- `start` (integer)
- `table` (integer)
- `target` (integer)
- `timeout_ms` (integer)
- `to` (integer)
- `writer_index` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/smarthomeninja-myio-mcp/myio-mcp#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 66
- 2026-11-19: 65
- 2026-11-18: 65
- 2026-11-17: 64
- 2026-11-16: 64
- 2026-11-15: 63
- 2026-11-14: 48

## Common questions

### What is the myIO MCP server?

myIO is an MCP server listed in the public MCP registry as io.github.SmarthomeNinja/myio-mcp. Read and control a myIO smart home controller: heating, lighting, blinds and energy. This page covers its npm package (myio-mcp).

### Is the myIO MCP server safe to use?

myIO scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the myIO MCP server expose?

myIO exposes 102 tools: myio_servers, myio_info, myio_find, myio_list_devices, myio_read_sensors, and 97 more. Their descriptions and schemas cost roughly 15,466 tokens of context every time the server is loaded.

### Is the myIO MCP server still maintained?

myIO is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the myIO MCP server under?

myIO declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the myIO MCP server?

VerifyMCP ran 16 checks on myIO, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/myio-mcp
- Socket report: https://socket.dev/npm/package/myio-mcp
- Repository: https://github.com/SmarthomeNinja/myio-mcp
- Website: https://myio.hu/en/
- Changelog RSS feed: https://verifymcp.io/servers/smarthomeninja-myio-mcp/myio-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/smarthomeninja-myio-mcp/myio-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/smarthomeninja-myio-mcp/myio-mcp.json
- HTML version of this page: https://verifymcp.io/servers/smarthomeninja-myio-mcp/myio-mcp
