myIO

io.github.SmarthomeNinja由 GitHub 帳號 SmarthomeNinja 發布v1.6.2更新於 Nov 15, 2026

讀取並控制myIO智慧家居控制器:供暖、照明、百葉窗和能源。

AI 翻譯由 AI 模型根據下方的原文描述翻譯,可能有誤。

原文描述

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

發布方自己的服務:myIO Documentation

概覽

myIO 的本機 MCP 服務;無需登入;STDIO;102 個工具。

暫無 AI 概覽:以下資訊來自註冊中心條目和服務本身。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 myIO,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

myIO MCP Server

Talk to your home. myIO MCP connects AI assistants such as Claude to a myIO smart home controller, so you can ask the house in plain words how warm the children's room is, what happened today, or to lower the blinds.

myIO is a central home controller developed in Hungary by myIO Smart Home Zrt. It sits on a DIN rail in the distribution cabinet and runs heating and cooling, lighting, blinds, gates and energy in one system, on its own, without the internet. This is a free, open-source Model Context Protocol (MCP) server for it: it runs on your own computer and reaches the controller over your home network, through its HTTP API.

Example

A real conversation in Claude Desktop, translated from Hungarian:

You: How warm is it in the house right now, room by room?

Claude (used myIO-MCP): Right now (20:02), according to the controller:

RoomTemperature
Bedroom23.6 °C
Bedroom bathroom23.3 °C
Study26.0 °C

It is 5.3 °C outside, and the heating flow water is at 32.3 °C. The study is noticeably warmer than the others. Only the upstairs myIO controller is reachable, so I have no data on the ground-floor rooms.

You: Switch on the study lamp and lower the blinds upstairs.

Claude (used myIO-MCP): The study lamp is on, and all 9 upstairs blinds are going down: bedroom (terrace door, east, south), study, walk-in closet, guest bedroom, bathroom, staircase and guest bathroom.

One thing worth knowing: your own "Upstairs blinds DOWN" group does not include the study blind, and there is also a "Study blind down lock" switch. It is off right now, so I lowered the study blind too. If it was left out of the group on purpose, tell me and I'll raise it again.

Quick start (Claude Desktop)

  1. Download myio-mcp.mcpb.
  2. Open it with a double click (or in Claude Desktop: Settings → Extensions).
  3. Enter the controller's address (e.g. http://192.168.1.178), a user name and the password. Then ask.

Create a separate myIO user for the assistant, and choose how far it may go: switch only (state), change settings too (config, the default) or everything (admin). Claude Code and other MCP clients: see Configuration.

Works with every myIO controller: V3 (Arduino Due, firmware 3.12), V4 GIGA and V4 Opta (firmware 4.x). Features that only exist on V4 answer with a clear error on a V3. More: Talk to your home · Downloads · API reference (Hungarian)

Privacy: the MCP server runs locally, but the AI assistant runs on its provider's servers. Your questions, and what it reads to answer them (e.g. temperatures, output names), reach the provider.

Status (1.6.2, 2026-11-15)

1.6.2: works better from outside the home network (port forwarding, DDNS) - when the controller answers a remote read with 503 and Retry-After (it serves heavy requests from other networks at most every few seconds), the server waits and tries again, at most twice; writes are never repeated. Several controllers in the Claude Code plugin (claude-plugin/).

1.6.1: myio_system restarts and updates a Due (3.12+) over the web too - the MYIO_NEW.BIN package is checked against the controller's chip ID before upload, and the answer says whether it was installed, rejected or cannot be installed (no device key).

Rounds 0-5 of the plan: the February 2026 server fixed, put on tests, extended with the house entities, the configuration layer, automation (Flow rules, myIO Script programs), diagnostics / logs / files, every integration and RS485 expander - and in round 5 the MCP layer: resources, prompts, toolsets, consistent annotations and an optional Streamable HTTP transport.

  • native node:http client (no more curl), one request at a time per controller, Connection: close
  • correct value scales: temperature ×100, humidity ×10, SDM voltage/current ×10, SDM power in W, PCA/FET level raw 0..255
  • every control tool reads the state back and reports what the controller actually did (a command the account has no permission for is silently dropped by the firmware)
  • several controllers in one server (MYIO_SERVERS), every tool takes a server name
  • version gate: V3 (Due 3.12) and V4 (GIGA/Opta 4.x) both supported, 4.x-only features answer with a clear error on a Due
  • entities modelled like the myIO app / Homey / Home Assistant integration: thermostat zones, shutters (protection pairs), RGB groups, wall inputs, universal sensors
  • configuration layer: globals, names, output/input configuration, protection pairs / joiners / groups, scenes, timers, users and permissions - toggle-type settings are read first and only sent when they must change
  • automation: Flow rules described in plain words with element names, validated against the firmware's card rules BEFORE upload (the firmware silently disables a rule with a bad card), saved + reloaded + read back; scripts written, compiled on the controller, compile errors returned with the offending source line; the complete script language reference is a tool (myio_reference)
  • diagnostics: health snapshot (resets, loop stalls, RAM, sockets, WiFi, NTP on a Due), Prometheus metrics, daily logs with level / text / time filters, file manager on internal flash and SD card (system files need MYIO_WRITE=admin)
  • integrations: Shelly, myIO Link, MQTT, myIO Cloud, SG-Ready, alarm panel (SIA), MIA, LED strips, network, restart / web OTA; Opta expanders: failsafe / AUX / 1-Wire, KNX (table, names, ETS interface, device programming), DALI, DMX, Modbus RTU. Toggle-type settings are always given as desired values; passwords, keys and tokens are never returned; a value containing & is refused (the firmware cannot receive it)
  • write level (MYIO_WRITE = state | config | admin) limits what the AI may change
  • MCP layer: resources (myio://<controller>/state ...), four prompts in Hungarian and English that read the controller first, toolsets (MYIO_TOOLSETS) to save context, annotations that follow one rule set, Streamable HTTP for other LAN clients (bearer token)
  • zod input schemas, mock controller + end-to-end tests (npm test, 72 tests), restoring live tests for a bench controller

Tools (102)

ToolToolsetWhat it does
myio_serverscorethe configured controllers with a live check (version, name, permission level)
myio_infocoreserial, firmware version, board, element counts (RQ/SQ/PCAQ/SENQ), permission level, feature flags, expanders, storage health
myio_findcorename search (accent- and case-insensitive) across outputs, groups, sensors, inputs, universal sensors
myio_list_devicescoreoutputs with id, name, live state/level, roles (thermostat, shutter-up/down, rgb:, group: ...), timers, members
myio_read_sensorscoretemperatures (°C), humidity (%), pulse meter, SDM630 power/voltage/current, 4.x universal sensors
myio_get_statuscoreany raw JSON endpoint (sens_out.json, sens_IO.json, info.json, 4.x: usensor.json, sysdiag.json, ...)
myio_outputcoreswitch or dim ANY output by id: action on / off / toggle / level (level 0..255 or percent)
myio_relay_on / _off / _togglelegacyrelay 1..RQ
myio_pca_on / _off / _toggle / myio_pca_setlegacyPCA dimmer channel 2001..2000+PCAQ; set takes level (0..255) or percent (0..100)
myio_pwm_on / _off / _toggle / myio_pwm_setlegacyFET/PWM output 101..116 (legacy hardware only)
myio_group_on / _off / _togglelegacygroup 501.. (editor level needed on the controller)
myio_inputshousewall buttons / switches: state, name, enabled, NC (4.3.12+ / Due 3.12.7+)
myio_press_buttonhousesimulate a button: hit (short), press (long), release - runs the input's bound actions
myio_thermostats / myio_set_thermostathousesensor-controlled zones: target + band (hysteresis), heat/cool, current temperature; set target, band, raw thresholds, bind sensor
myio_shutters / myio_shutterhouseUP/DOWN pairs (protection pairs): opening / closing / stopped; open, close, stop
myio_rgb / myio_set_rgbhouseRGB groups ("RGB..." group with R/G/B channels): on/off, colour, brightness
myio_usensors / myio_set_usenshouse4.x universal sensors (KNX, Modbus, MQTT, Shelly, Script, external): read; push a value from outside
myio_send_commandcoreraw key=value&key=value command string (everything in the API reference); the reply lists the outputs that changed
myio_globals / myio_set_globalsconfigname, clock, time zone, location, sunrise/sunset, button timing, cooldown, sensor polling, pulse meter unit; NTP sync
myio_renameconfigname of a relay / pca / fet / group / input / thermo / humidity / usens / shelly / scene
myio_output_config / myio_set_output_configconfigauto-off timer, delay, inverted, alarm, justOn, PCA min/max, fade speed, PWM / mixer mode
myio_input_config / myio_set_input_configconfigwhat a wall button does: enabled, NC, hit-block, hit / press / release targets
myio_structures / myio_set_protection / myio_set_joiner / myio_set_groupconfigprotection pairs (shutters), joiner pairs, group members and pullUp
myio_scenes / myio_sceneconfigconfiguration slots: list, load, save, new, delete, set_boot, rename
myio_timers / myio_set_timer / myio_delete_timerconfigtimer.csv: time or sunrise/sunset ± offset, date, weekdays, event and target
myio_users / myio_userconfigaccounts: list, new, delete, rename, set_password, set_rights (admin level)
myio_permissions / myio_set_permissionsconfigper-element read/write and hit/press permissions of a user (map readable on 4.x)
myio_config_varsconfigany raw setting variable of the Setup page (energy manager, SDM, dew point ...)
myio_flowsautomationFlow rules (4.4+): WHEN / AND / THEN in plain words with names, live state (enabled, running, last fired), variables, webhooks; raw = flows.jsn
myio_flow_saveautomationadd / replace / delete a rule, a variable or a webhook target, or replace the whole flows.jsn - validated first, then uploaded + reloaded + read back (dry_run)
myio_flowautomationruntime: enable / disable a rule, fire its actions now, set a global variable
myio_flow_trace / myio_webhook_testautomationwhat the engine did (incremental with since); fire a webhook slot and report the HTTP result
myio_scripts / myio_script_getautomationmyIO Script programs (4.10+): state, errors with line:col, timing, locals, arrays, global variables, trace; source of a slot
myio_script_save / myio_scriptautomationwrite + compile a program (compile error with the source line); reload, run once, enable / disable (RAM or persistent), delete
myio_referenceautomationthe bundled firmware documentation: complete script language, Flow card format, any API section
myio_sysdiag / myio_metricsdiaghealth: uptime, last reset cause, loop stalls, RAM, M4 core, LAN/WiFi, sockets, storage, login brake; Prometheus text (4.4.1+)
myio_logs / myio_logdiagdaily CSV logs (event, consumption, SDM, temperature, humidity, usens): list; read one day with level / text / time filters and tail
myio_files / myio_file_read / myio_file_write / myio_file_opdiagstorage (internal flash q, SD card s; a Due has only the SD): list, read (text / binary), write (text / base64, make_dirs), delete / mkdir / rename / copy
myio_fm_syncdiaginternal flash -> SD configuration mirror: status, run, adopt a foreign card (4.4.3+, admin)
myio_shelly / myio_shelly_setintegrationsShelly devices (4.1+): online, state, which myIO output / button / usens each channel is bound to; add, scan, bind, rename, auth, push
myio_link / myio_link_setintegrationsmyIO Link (4.2+): other controllers polled, output and sensor links; add, scan, link, unlink
myio_mqtt / myio_mqtt_setintegrationsMQTT client (4.3+, Due 3.12.31+): broker, state, topics, HA discovery, publish masks, subscribe, external sensor bindings; save + reconnect
myio_cloud / myio_cloud_setintegrationsmyIO Cloud (4.4+): state, pairing window, paired phone keys; enable, pair, revoke, delete (admin)
myio_sgready / myio_sgready_setintegrationsSG-Ready heat pump (4.4.2+, Due 3.12.9+): mode 1..4, K1/K2 outputs, utility-lock limit
myio_alarm / myio_alarm_setintegrationsSIA DC-09 alarm panel receiver (4.5.8+): partitions, troubles, counters; listeners, account, partition -> usens, simulated events
myio_mia / myio_mia_setintegrationsMIA self-learning heating (4.11+): learned zone model, window detection, preheating; features, thresholds, exclusions, reset
myio_ledstrip / myio_ledstrip_setintegrationsWS2812 strips (4.3.4+): strips, programs, effects; run/stop by event id, edit programs live
myio_network / myio_network_setintegrationshost name, LAN, WiFi STA/AP, live addresses, services per interface; change + save or apply (admin, dangerous)
myio_systemintegrationsrestart, web OTA upload / install (GIGA/Opta: MYIO_UPD.BIN + roll back; Due 3.12+: MYIO_NEW.BIN to the SD card, checked for the controller's chip ID before upload), admin - waits for the controller and reports the running version and the outcome
myio_expanders / myio_expander_setexpandersOpta RS485 panels (4.5+): type, online, firmware, failsafe/standalone, AUX mode, Ext16 1-Wire
myio_knx / myio_knx_set / myio_knx_deviceexpandersExt-KNX: group-address table with names, ETS tunnelling interface, devices; edit rows + KnxSave, scan / program addresses (admin)
myio_dali / myio_dali_setexpandersExt-DALI (4.8.6+): endpoints, bindings, desired vs driver parameters, groups; bind, settings, groups, scan, commission (admin)
myio_dmx / myio_dmx_setexpandersExt-DMX (4.9+): fixtures and channel bindings; add, bind, test, blackout
myio_modbus / myio_modbus_setexpandersExt-RS485 Modbus RTU (4.16+): blocks, decoded fields with live values, writer slots, bus; edit tables, presets, raw request, address scan

Element ids are shared by all tools and channels: relays 1..RQ, FET 101..116, groups 501.., PCA 2001..2000+PCAQ (see API_REFERENCE.md chapter 3).

Annotations follow one rule set: read tools are readOnlyHint; a desired-value setter (on / off / level / target / name / a setting) is idempotentHint - calling it twice changes nothing more (an identical protection pair, joiner or timer is reused, not duplicated); toggles, fire / run, button presses and add / new actions are not; tools that can overwrite or delete stored configuration are destructiveHint (switching an output is a reversible state change, not destructive); a tool with several actions is annotated for its most dangerous one. myio_webhook_test is openWorldHint (it calls an outside URL).

Toolsets

The 102 tool descriptions cost context. MYIO_TOOLSETS loads only some groups (the same field is in the Claude Desktop settings):

ToolsetTools
core (always)myio_servers, myio_info, myio_find, myio_list_devices, myio_read_sensors, myio_get_status, myio_output, myio_send_command (8)
legacythe per-type switches from 2026-02: myio_relay_* / myio_pca_* / myio_pwm_* / myio_group_* (14) - myio_output covers them
houseinputs, button simulation, thermostats, shutters, RGB, universal sensors (10)
configsettings, names, output / input configuration, structures, scenes, timers, users, permissions (21)
automationFlow rules, scripts, the language / API reference (10)
diagsysdiag, metrics, logs, files, SD mirror (9)
integrationsShelly, Link, MQTT, Cloud, SG-Ready, alarm, MIA, LED strips, network, restart / OTA (19)
expandersOpta RS485 expanders: Ext16, KNX, DALI, DMX, Modbus (11)

Examples: MYIO_TOOLSETS=house,automation (core + 20), MYIO_TOOLSETS=all,-legacy,-expanders (77). Empty or all = everything (default). Unknown names are reported on stderr; core cannot be switched off. The server instructions tell the model which groups are not loaded, and the prompts only mention tools that are. Resources and prompts do not depend on the toolsets.

Resources

Attachable context - the client reads them without a tool call. <controller> is the URI-safe form of the controller name (Földszint -> foldszint, Ground floor -> ground-floor; printed on stderr at start).

URIContent
myio://<controller>/infoinfo.json + the feature map derived from the firmware version (JSON)
myio://<controller>/statedecoded live state in real units: outputs (level, roles, timers, thermostat thresholds), sensors, inputs, universal sensors (JSON)
myio://<controller>/flows.jsnthe Flow rule file (4.4+)
myio://{controller}/prog/{n}.txttemplate: source of script slot n (4.10+)
myio://{controller}/log/{date}template: one day of the event log, today / yesterday / YYYY-MM-DD / YYMMDD (last 256 KB)
myio://docs/indexcontents of the bundled API reference with the chapter URIs
myio://docs/script / myio://docs/flowthe myIO Script language (10/G) / the Flow card format (10/D)
myio://docs/chapter/<id>one chapter: 1 .. 13, 10-a .. 10-h (Hungarian)
myio://docs/search/{query}template: every section whose heading contains the query (accent-insensitive)

The templates offer completion (controller names, slot numbers, the last seven days).

Prompts

Each prompt reads the controller(s) when it is requested and embeds the data, so the conversation starts with full context (every data block fails on its own: "not available: ..."). Argument language: hu (default) or en; server limits it to one controller.

PromptArgumentsWhat it collects
heating_overviewserver, languagethermostat zones (target, band, current, heating), temperatures and humidity, MIA learned model and today's MIA events, SG-Ready - for every controller
why_not_switchingelement (name or id), server, languagethe output's state and roles, account level, output configuration, thermostat control, protection / joiner / group, timers and scene loads, bound wall buttons, Flow rules and scripts that use it, myIO Link, MQTT control, SG-Ready contacts, today's switching commands for it in the event log. An ambiguous name returns the candidates.
daily_diagnosticsserver, date, languageinfo, sysdiag (resets, RAM, sockets, link / WiFi, NTP), clock vs this computer + time zone / DST, the event log's error and notable lines grouped, RS485 expanders, Flow and script errors - for every controller
new_flow_rulerule (plain words), server, languagethe existing rules, the named outputs and sensors with ids, the 10/D card reference; the model is told to clarify, draft, dry-run (myio_flow_save dry_run=true), explain, and save only after approval

Streamable HTTP (optional)

stdio stays the default. With MYIO_HTTP_PORT the server also answers MCP over Streamable HTTP at /mcp, for other MCP clients on the LAN:

bash
MYIO_HTTP_PORT=8765 MYIO_HTTP_HOST=0.0.0.0 MYIO_HTTP_TOKEN=$(openssl rand -base64 24) \MYIO_BASE_URL=http://192.168.1.178 MYIO_USERNAME=admin MYIO_PASSWORD=... node dist/index.js# client: URL http://<this-machine>:8765/mcp, header  Authorization: Bearer <token>
  • binds to 127.0.0.1 by default; any other address needs MYIO_HTTP_TOKEN (min. 16 characters) or the server refuses to start. On loopback without a token a random one is generated and printed on stderr.
  • every request needs Authorization: Bearer <token> (compared in constant time); sessions are kept in memory (max 16, idle 30 min).
  • all sessions share the controller clients, so the per-controller request queue (and MYIO_MIN_GAP_MS) still protects the firmware.
  • started from a terminal it serves only HTTP; under an MCP client (stdin is a pipe) stdio runs too. MYIO_STDIO=0|1 forces it.
  • plain HTTP: use it inside the home network or behind a TLS reverse proxy / VPN, not on the open internet. On macOS the application firewall may ask to allow incoming connections for node.

Configuration

Environment variables (the Claude Desktop extension asks for them as user config):

VariableMeaning
MYIO_BASE_URLcontroller URL, e.g. http://192.168.1.178 (port 80 by default)
MYIO_USERNAME / MYIO_PASSWORDHTTP Basic auth; the account's permission level limits what the tools can do
MYIO_NAMElabel used in replies (default: the host)
MYIO_SERVERSseveral controllers: JSON array [{"name":"Ground floor","url":"http://192.168.1.178","username":"admin","password":"..."}, ...] - overrides the three above; tools take server: "<name>"
MYIO_WRITEwrite level: state (outputs, thermostat targets, usens, run flows / scripts, SG mode), config (default; also names, timers, scenes, structures, input/output configuration, thermostat sensor binding, Flow / script files, integration settings), admin (also users, permissions, system files, network, Cloud keys, restart / OTA)
MYIO_TOOLSETStool groups to load (see Toolsets), default all
MYIO_HTTP_PORT / MYIO_HTTP_HOST / MYIO_HTTP_TOKEN / MYIO_STDIOoptional Streamable HTTP transport (see above)
MYIO_TIMEOUT_MSHTTP timeout, default 10000
MYIO_MIN_GAP_MSminimum pause between two requests to one controller, default 150 (a Due refuses request bursts)
MYIO_INSECURE_PARSER0 = strict Node HTTP parser (default lenient: the firmware writes its headers by hand)

Claude Desktop

Install myio-mcp.mcpb (Settings → Extensions) and fill in the URL, user and password. To rebuild the bundle:

bash
npm installnpm run pack          # = sync-docs + tsc + mcpb pack . myio-mcp.mcpb

Claude Code / other MCP clients (stdio)

The server is on npm as myio-mcp (Node.js 18 or later), so npx runs it without a checkout:

json
{  "mcpServers": {    "myio": {      "command": "npx",      "args": ["-y", "myio-mcp"],      "env": { "MYIO_BASE_URL": "http://192.168.1.178", "MYIO_USERNAME": "admin", "MYIO_PASSWORD": "..." }    }  }}

Claude Code: claude mcp add myio -e MYIO_BASE_URL=http://192.168.1.178 -e MYIO_USERNAME=admin -e MYIO_PASSWORD=... -- npx -y myio-mcp. From a checkout, use "command": "node" with "args": ["/absolute/path/to/myio-mcp/dist/index.js"] instead.

It is also listed in the official MCP Registry as io.github.SmarthomeNinja/myio-mcp (server.json).

Development

bash
npm installnpm run build         # TypeScript -> dist/npm test              # build + mock controller + end-to-end tests over stdio (node --test)MYIO_BASE_URL=http://192.168.1.56 MYIO_USERNAME=admin MYIO_PASSWORD=... npm run smoke   # read-only check on a real controllernode test/mock_myio.mjs --serve 8111    # standalone mock controller (MOCK_VERSION=3.12.30 for a Due-like one)npm run sync-docs     # copy ../SD_Files/js/lang/HU/API_REFERENCE.md (the canonical reference) into the package; --check only comparesLIVE_SERVERS='[{"name":"Opta","url":"http://192.168.1.60","username":"admin","password":"..."}]' node test/live_mcp5.mjs   # resources + prompts + HTTP, read-only

Layout: src/api.ts (HTTP client + command dispatch), src/model.ts (JSON → devices/sensors, scales, version gate), src/model_auto.ts (Flow validation / description, script state, traces), src/model_diag.ts (sysdiag, logs, files), src/servers.ts (several controllers, URI slugs), src/toolsets.ts (MYIO_TOOLSETS), src/resources.ts, src/prompts.ts, src/docs.ts (the bundled reference), src/http.ts (Streamable HTTP), src/tools/common.ts (read-back, desired-toggle and command helpers), src/tools/basic.ts + house.ts + config.ts + auto.ts + diag.ts + integr.ts + bus.ts (tool families on McpServer), src/index.ts (config + transports), test/mock_myio.mjs (controller mock built from the real d_sens_out.json sample, with an in-memory file system, Flow and Script engines), test/mcp.test.mjs, test/house.test.mjs, test/config.test.mjs, test/auto.test.mjs, test/integr.test.mjs, test/mcp5.test.mjs (resources, prompts, toolsets, annotations, HTTP); test/live_write.mjs, test/live_config.mjs, test/live_auto.mjs and test/live_integr.mjs are restoring live tests for a BENCH controller only; test/live_mcp5.mjs only reads. node test/call.mjs <tool> '<json>' ... calls tools by hand.

Rules the server follows (from the API reference, chapter 12)

  1. One request at a time, Connection: close, no polling faster than 1 s - the controller has 3 listen sockets.
  2. Commands go as POST /info.json body (the GET /command: path does not URL-decode), max 1024 bytes.
  3. The command reply is an HTML/JSON acknowledgement, not the new state: read sens_out.json back.
  4. JSON keys may be missing (permission filtering): never rely on a fixed key set.
  5. Toggle-type config commands (relaysInvert=<id> ...) invert a flag - read first, send only on change.
  6. Fixed point: temperature ×100, humidity/usens/SDM U,I ×10, thresholds ×10, PCA/FET level raw 0..255.

License

MIT, see LICENSE.

來源:README.md,提交 c033493

工具

102

myio_servers

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

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).

輸入參數server

myio_find

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.

輸入參數query必填server

myio_list_devices

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.

輸入參數typeserverinclude_unnamed

myio_read_sensors

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.

輸入參數kindserver

myio_get_status

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.

輸入參數serverendpoint

myio_output

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.

輸入參數id必填levelaction必填serverpercent

myio_relay_on

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.

輸入參數id必填server

myio_relay_off

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.

輸入參數id必填server

myio_relay_toggle

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.

輸入參數id必填server

myio_pca_on

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.

輸入參數id必填server

myio_pca_off

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.

輸入參數id必填server

myio_pca_toggle

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.

輸入參數id必填server

myio_pca_set

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.

輸入參數id必填levelserverpercent

myio_pwm_on

PWM ON

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

輸入參數id必填server

myio_pwm_off

PWM OFF

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

輸入參數id必填server

myio_pwm_toggle

PWM toggle

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

輸入參數id必填server

myio_pwm_set

PWM level

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

輸入參數id必填levelserverpercent

myio_group_on

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).

輸入參數id必填server

myio_group_off

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).

輸入參數id必填server

myio_group_toggle

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.

輸入參數id必填server

myio_send_command

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.

輸入參數servercommands必填

myio_inputs

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.

輸入參數serveronly_active

myio_press_button

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.

輸入參數id必填kindserver

myio_thermostats

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.

輸入參數server

myio_set_thermostat

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.

輸入參數id必填onoffbandsensorservertarget

myio_shutters

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.

輸入參數server

myio_shutter

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.

輸入參數indexup_idaction必填server

myio_rgb

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).

輸入參數server

myio_set_rgb

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.

輸入參數bgrid必填onserverbrightness

myio_usensors

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.

輸入參數serverinclude_disabled

myio_set_usens

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.

輸入參數id必填value必填server

myio_config_vars

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.

輸入參數namesprefixserver

myio_globals

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.

輸入參數server

myio_set_globals

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.

輸入參數nameserverauto_dstlatitudehum_timerlongitudesync_timetime_zonetemp_timermixer_timerprot_cooldownhit_time_limit另有 3 個

myio_rename

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.

輸入參數id必填kind必填name必填server

myio_output_config

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.

輸入參數idtypeserverinclude_unnamed

myio_set_output_config

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.

輸入參數id必填maxminpwmalarmmixerinvertserverdelay_sjust_ontimer_sfade_speed

myio_input_config

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.

輸入參數idserverinclude_unused

myio_set_input_config

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.

輸入參數id必填nchitpressserverenabledreleasehit_block

myio_structures

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.

輸入參數server

myio_set_protection

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.

輸入參數up必填down必填indexserverpriority

myio_set_joiner

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.

輸入參數indexslave必填master必填serverjust_on

myio_set_group

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.

輸入參數id必填nameservermembers必填pull_up

myio_scenes

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.

輸入參數server

myio_scene

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.

輸入參數nameslotaction必填server

myio_timers

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.

輸入參數server

myio_set_timer

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.

輸入參數iddaydayshourevent必填monthparam必填minuteserversunsetsunrise

myio_delete_timer

Delete a timer

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

輸入參數id必填server

myio_users

User accounts

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

輸入參數server

myio_user

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.

輸入參數nameslotaction必填rightsserverpassword

myio_permissions

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.

輸入參數slot必填server

myio_set_permissions

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).

輸入參數fillslot必填cleargrantrevokeserver

myio_flows

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.

輸入參數idrawserver

myio_flow_save

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.

輸入參數fileflowhookdeleteserverdry_runvariabledelete_hookdelete_variable

myio_flow

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.

輸入參數id必填valueaction必填server

myio_flow_trace

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.

輸入參數limitsinceserver

myio_webhook_test

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.

輸入參數slot必填server

myio_scripts

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.

輸入參數idtraceserver

myio_script_get

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.

輸入參數id必填server

myio_script_save

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.

輸入參數id必填serversource必填enabled

myio_script

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.

輸入參數id必填action必填serverpersist

myio_reference

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).

輸入參數querytopic必填

myio_sysdiag

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.

輸入參數rawserver

myio_metrics

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+.

輸入參數filterserver

myio_logs

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.

輸入參數kindserverchannel

myio_log

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.

輸入參數voldatekindpathtaillevelsinceuntilserverchannelcontains

myio_files

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.

輸入參數dirvolserver

myio_file_read

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.

輸入參數volpath必填base64servermax_bytes

myio_file_write

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.

輸入參數volpath必填base64servercontentmake_dirs

myio_file_op

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.

輸入參數op必填tovolpath必填serverto_vol

myio_fm_sync

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.

輸入參數opserver

myio_shelly

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.

輸入參數scanserver

myio_shelly_set

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.

輸入參數ipmsmodenameslotuserindexstartusensaction必填buttondevice另有 7 個

myio_mqtt

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.

輸入參數server

myio_mqtt_set

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.

輸入參數qostlshostportsaveuserretainservereconomyenabledpasswordperiod_s另有 10 個

myio_cloud

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.

輸入參數server

myio_cloud_set

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.

輸入參數keylabelaction必填serverenabledrevokeduser_slot

myio_sgready

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.

輸入參數server

myio_sgready_set

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).

輸入參數k1k2modeserverenabledlimit_min

myio_alarm

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.

輸入參數server

myio_alarm_set

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.

輸入參數tcpudpportserveraccountenabledsimulateack_timestampreset_counterssupervision_minpartition_sensor

myio_mia

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.

輸入參數zoneserver

myio_mia_set

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.

輸入參數serverenabledexcludefeaturesexclude_f3learn_daysmin_on_offwindow_minreset_learnedwindow_drop_cpreheat_max_minwindow_hold_min

myio_ledstrip

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.

輸入參數progserver

myio_ledstrip_set

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.

輸入參數nameprogeventfieldsserverenabledled_count

myio_network

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.

輸入參數server

myio_network_set

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.

輸入參數aplanstahostapply必填serverwifi_mode

myio_system

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.

輸入參數fileaction必填server

myio_expanders

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.

輸入參數addrserver

myio_expander_set

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.

輸入參數auxserverfailsafeforget_panelcapture_presetonewire_forgetonewire_rescan

myio_knx

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.

輸入參數server

myio_knx_set

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.

輸入參數rowssavepanelservertunneldrop_tunnel

myio_knx_device

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.

輸入參數nameindexaction必填serveraddress

myio_dali

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.

輸入參數epserver

myio_dali_set

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.

輸入參數ephilomaxminmodecurvefieldgrouppanelstartvalue另有 11 個

myio_dmx

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.

輸入參數server

myio_dmx_set

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.

輸入參數hilotypecountfieldpanelvalueaction必填pca_idserveraddresschannel另有 1 個

myio_modbus

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.

輸入參數panelserver

myio_modbus_set

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.

輸入參數ontobitoffregbaudfromfuncnamesaveblockcount另有 24 個

版本歷史

2
  1. v1.6.2最新Nov 15, 2026
  2. v1.6.1Nov 14, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Myio 整合