Versions and verification baseline
The JavaScript documentation on this site targets IOSignal 9.x. The baseline is stated only on this page; individual guides mention a version only for behavior that differs between versions, such as "since 8.0.0".
- Install: guides use
npm install iosignal. npm records the current release as a^9.xrange inpackage.json, and the lockfile pins what was actually installed. A new major version is announced here first. - CDN: there is no lockfile, so URLs pin the major version (
iosignal@9). Existing pages keep working when a new major version is released.
| Component | Baseline | Scope |
|---|---|---|
| IOSignal JavaScript | 9.x (tested 9.12.0; server host 9.13.0; dashboard 9.14.0; connection reply limit 9.19.0) | 2026-11-12: five example builds, four bidirectional/reconnect chat tests, five WebRTC tests. 2026-11-18: 293 public build tests of 9.19.0 |
| iosignal-cli, remocon | 9.x (9.19.0) | 2026-11-18: both CLIs released together from one repository; package tests (iosignal-cli 25, remocon 14). The bundled server is IOSignal 9.19.0. Options differ from the 8.x CLI; check with io-server --version |
| IOSignal Arduino | 9.23.1 | 2026-11-21: the 34 example builds compiled for their boards (development source), and in the public repository 10 representative builds and a sketch using the old remocon:: names. The examples were not run on hardware again. Changes: 9.23.1, 9.23.0, 9.21.0 |
| Remocon Arduino | 9.22.0 (last) | The last version with the device examples; no longer updated. Since 9.23.0 the examples are in IOSignal Arduino. Whether each example was checked on hardware is on its page at arduino.iosignal.net |
| Boho | JS 2.2.1 / Arduino 1.1.0 | Implementation baseline for encryption documentation |
Version numbers: public numbers follow the development version, so numbers can be skipped (9.12.0 follows 9.6.0). iosignal-cli, remocon (npm), IOSignal Arduino and Remocon Arduino are recommended, not required, to use the same number as iosignal; one without changes keeps its previous number (for example iosignal 9.13.0 with iosignal-cli 9.12.0). From 9.0.0 to 9.12.0, iosignal, iosignal-cli and remocon were released together with the same number. Once changes add up, they match again, as iosignal-cli and remocon did at 9.19.0. All 9.x versions can connect to each other, so different numbers work together. Boho keeps its own versions. Arduino Library Manager listings can lag behind the repositories.
Behavior since 7.2.0
- Direct reception emits common
@, then the exact@topicevent. Registering identical processing on both can duplicate execution. Bare@emits once. Direct messages do not reachmessage. subscribe('@topic')andunsubscribe('@topic')throw TypeError. Useon()orlisten()for direct reception.A@topicis a valid subscription to CID A's publications.link()/unlink()scope subscriptions and handlers to their owner while preserving other owners' shared subscriptions.- EMPTY is
(tag)with no payload argument, distinct from explicit null. Older development builds passed null for EMPTY. Tags have a 255-byte UTF-8 limit.
See client API, subscription lifecycle, and payloads. The verification scope describes the current baseline. Physical boards, real capture devices, Safari/iOS, different internet networks, and TURN relay were not tested in this pass.
Changes in 9.19.0
The public version after 9.14.0 (9.15.0–9.18.0 were not published). iosignal-cli and remocon are also 9.19.0. The wire protocol is unchanged, and it connects with every 9.x server and client.
- Server reply limit (client): if the server's first reply (hello) does not arrive within 15 seconds of starting a connection, the client emits
error(no reply from the server in 15 s) and closes the connection. With auto-reconnect it connects to its original address again, so a redirect to a server it cannot reach falls back to the original server. The value isSIZE_LIMIT.SERVER_HELLO_TIMEOUT(15000 ms). Connection and CID lifecycle IOCongSocketaddresses: a numeric IPv4 address such as192.168.0.10:8888works withoutcong://. Before,new URL()threw.host:portandcong://host:portwork as before.BohoAuth.beforeAccept(): a subclass can send a login that passed the key and role checks to another server before it is accepted. By default every login is accepted. Server authentication- Redis key list:
RedisKeyProviderlists device keys withSCANinstead ofKEYS, so a large Redis does not block the server. It falls back toKEYSwhen a client or server cannot useSCAN.RedisServiceallows theSCAN(scan) command. - Peer ping removed:
ping <cid>is gone from the CLIs (iosignal-cli, remocon) and the remocon.kr web CLI.pingis the server ping only and updates its answer on one line. A message that arrives while you type keeps the typed line intact. - remocon CLI location: the remocon repository was merged into the iosignal-cli repository (
packages/remocon). The npm package name and commands are unchanged. remocon CLI - Scope (2026-11-18): 293 public build tests (ESM and CJS). The reply limit and numeric addresses are covered by four unit tests in the development source (a server that never answers, a redirect target that never answers, a server that answers in time, a numeric IPv4 address).
IOSignal Arduino 9.23.1
The messaging API and protocol are the same as 9.23.0, and existing sketches still compile.
- Helper namespace
iosignal: functions and constants ofIOSignalUi.handIOSignalBinding.hare written likeiosignal::formatNameSetting(). Theremocon::name of 9.23.0 stays as an alias of the same namespace (a sketch cannot also includeRemoconUi.hfrom the old Remocon library). - Examples' default server
io.iosignal.net: it wasio.remocon.kr(the same broker). A server saved in the board settings is used first. - The examples' header comments say "device example" instead of "Remocon example".
IOSignal Arduino 9.23.0
The messaging API is unchanged; the examples and helper headers are now in one library.
- Every example in IOSignal: the 22 device examples of Remocon Arduino 9.22.0 are under File → Examples → IOSignal, with the same names. The Remocon library stops at 9.22.0; new examples go to IOSignal only.
- Helper header names:
RemoconUi.h→IOSignalUi.h,RemoconBinding.h→IOSignalBinding.h,RemoconButtons.h→IOSignalButtons.h(classRemoconButtons→IOSignalButtons). Functions and behavior are the same, so only the#includeand class names change. - Dependencies: unchanged (Boho, Crypto, Bounce2). FastLED, U8g2, IRremote and Ethernet are needed only by the examples that use them; install them separately.
- Example site: all Arduino examples are on arduino.iosignal.net (it replaced test.iosignal.net and arduino.remocon.kr). The Wi-Fi hint in
IOSignalConfig.hpoints tohttps://arduino.iosignal.net/wifi/. Web examples are on lab.iosignal.net. - Number: 9.23.0, the same as iosignal (npm) at the time. The previous IOSignal Arduino is 9.21.0; there is no 9.22.0.
IOSignal Arduino 9.21.0
- Reconnect a silent connection: when nothing has arrived for 50 seconds (
pingPeriod) the library sends a PING, and when the server does not answer within 15 seconds it closes the connection and reconnects. A connection that only looks alive (after a router restart, for example) no longer hangs. loop()keeps running while reconnecting:io.loop()used to wait 3 seconds withdelay(). It now tries once every 3 seconds and returns at once (one connection attempt still waits until it ends).- Boho 1.1.0 or later: ESP32 and ESP8266 take the login nonce from the hardware random number generator. Server and protocol are unchanged.
- The
esp01_channel_txrxexample was removed. There are no IOSignal Arduino versions 9.15–9.20.
IOSignal Arduino 9.13.0–9.14.2
Arduino library changes from the same period as JS 9.13.0 and 9.14.0. The messaging API is unchanged.
- Board settings (ESP32, ESP8266, 9.13.0): sketches using
IOSignalConfig.hchange Wi-Fi, server, device key and sketch settings from a browser over USB. Arduino board settings - Anonymous login choice (9.14.1): choosing "connect anonymously" in board settings connects without a key even when the sketch has one.
- Less RAM on UNO (AVR) (9.14.0):
setLog()texts and the redirect address format live in flash. - Example names (9.14.2):
esp8266_channel_txrx→esp_channel_txrx(ESP8266 and ESP32),uno_r4_wifi_channel_receiver_txrx→uno_r4_wifi_channel_txrx. Thepeer_ping_pong,esp32cam(moved to Remocon) andesp01_channel_txrxexamples were removed. - Remocon Arduino 9.14.0–9.14.8, device rules v2: devices announce themselves with
<cid>@$name(name:category) and<cid>@$ui(a button liston,offort=switch4.1). remocon.kr, the Android app and IOSignal Desktop no longer read the device info format of the 9.12.0 examples, so reinstall boards running them. The board settingnameholds$nameasname:category. Button controller examples (button-controller,iris-button-controller,esp01-button-controller) were added. See remocon-arduino for details per version.
Added in 9.14.0
Only iosignal (npm) 9.14.0 was released; iosignal-cli, remocon and the Arduino libraries stay at 9.12.0. The wire protocol and the client API did not change.
- Server dashboard:
new Server({ dashboard })turns on a page (/dashboard) with live charts of the server and its hosts. Choose who may watch: anyone, a token, or an IOSignal login (role or CID). Off by default. Server dashboard, Server API - Host measurements:
host.report(),host.loop(),host.loopStats(),host.counters,host.activity(),host.journal(). Server API - With the dashboard on, a server opened with
portmakes its own HTTP server and serves the page on the same port. Servers without the dashboard behave as before. - Scope (2026-11-14): 293 public build tests (ESM and CJS, including dashboard tests); attached to a live game server and checked every panel and the forgery display in a browser (light and dark).
Added in 9.13.0
Only iosignal (npm) 9.13.0 was released; iosignal-cli, remocon and the Arduino libraries stay at 9.12.0. The wire protocol and the client API did not change.
- Server host
server.host(): runs logic that decides outcomes, such as a game or quiz, inside the server. Each input carries the sender as the server knows it (from.cid), clients cannot send toowntags, andleavearrives when a participant's connection closes. Game logic inside the server, Server API countersinserver.stats()gainhostInbound,hostRejectedandhostDenied.- A server without hosts behaves as before.
- Scope (2026-11-13 to 14): 277 public build tests (ESM and CJS); with 9.13.0 installed from npm, input, sender, forgery blocking and
leavechecked from Node.js (WebSocket and TCP) and the browser bundle; load tests of game servers built on hosts (up to 1,000 watchers). Button input from real phones and Arduino boards was not checked.
Changes in 9.12.0
The public release after 9.6.0 (9.7.0 to 9.11.0 were not published). It is connection-compatible with 9.6.0, and the client API is unchanged.
- Anonymous CID characters: the characters after
?changed from base64url to lowercase Crockford base32 (0-9anda-zwithouti,l,o,u), for example?k3x9. The length is still 4 (8 when short CIDs keep colliding). Check any code that validates anonymous CIDs. remote.site: the Origin host name of a browser connection (''for Node.js, apps and TCP). For display only, never for authorization.nick: an authenticated connection'snickno longer holds a copy of its CID.RedisKeyProvider:addAuthanddelAuthkeep the set of device CIDs in use (sets_cid).- iosignal-cli, remocon 9.12.0: they name their connection with
iam()(iosignal-cli,remocon-cli) on every connection. - IOSignal Arduino 9.6.0 to 9.12.0: adds
unsubscribe(tag)(an empty tag removes every subscription), and a write that cannot be sent closes the connection soloop()reconnects. Overlapping examples (sender/receiver,esp32_channel_txrx,uno_ethernet_duplicate_login) were removed. - Remocon Arduino 9.12.0: type names became
<name>.<major>, such aslight.1andswitch4.1. The device info format changed again in 9.14.0 to the current rules ($name,$ui). The type list is at device types.
Changes in 9.6.0
IOSignal JavaScript 9.6.0 is connection-compatible with 9.0.0. The client's subscription order and call-time checks changed:
- Subscriptions saved by
listen()orlink()are sent after the CID arrives and before thereadyevent. Previously they were sent after ready handlers, so a signal sent at once from a ready handler could get ahead of the client's own subscriptions. subscribe()throwsErrorunless the connection isready(ignored afterdestroy()). To register before connecting, uselisten()orlink().- Calling
listen()inside a ready handler throwsError. Useon()andsubscribe()there. link()subscribes at once only on a ready connection; otherwise when it becomes ready.- Server: per-device delivery policy for owned devices,
server.manager.setDeliveryPolicy(), the'delivery:denied'event and thepolicyDeniedcounter. Per-device delivery policy - iosignal-cli 9.6.0: interactive subscribe commands print an error before
ready.
Changes in 9.0.0
IOSignal JavaScript 9.0.0 is a major release. It separates a connection's role (what it may do) from its quota profile (how much it may send) and removes the quota level table without a compatibility layer: old setting names throw an error that names the replacement. IOSignal Arduino 9.0.0, with the same number, tells the server its receive buffer size when connecting and skips frames larger than the buffer instead of disconnecting (call setRxBuffer() before begin()). IOSignal Arduino 7.0.0 still connects (it ignores the new QUOTA message).
- Key entries use roles and quota names instead of levels:
id.key.cid[.role[.quota]], file rows[id, key, cid, role, quota].id.key.cid.255becomesid.key.cid.admin, andid.key.cid.3becomesid.key.cid. Server authentication - Roles, lowest first:
anonymous,device(default for a login),service,admin.sudorequiresadmin;RedisService(client, minRole)requiresserviceor higher by default. New exports:ROLES,hasRole(remote, role),defaultQuota. - Quota profiles (
quotas:maxMessageBytes,fanout,msgPerSec,bytesPerSec,maxConnections) are always enforced. The 8.x default settings did not enforce quota, so checkanonymousQuotaor the profiles for anonymous clients that send many messages. Server API - Clients read the size limit from
io.quota.maxMessageBytes;io.levelandio.quota.signalSizewere removed. - Every setting is per server, and
serverOptiononly holds defaults that a Server never changes. Renamed:timeout→heartbeatInterval,pingTimeoutGrace→heartbeatGrace,retain.isAvailable→retain.enabled,auth.delay_auth_fail→auth.failDelay. UselogMessages,logStatsandserver.stats()instead ofshowMessage,showMetricandmonitorPeriod. - New server options:
maxPayload,maxBufferedBytes,trustProxy, per-servermembersOnlyandduplicateLogin, and retained-message budgets per owner inretain. An anonymous owner's retained messages expire after it disconnects. - Fixes:
IOCongSocketconnects to IPv6 literal URLs (cong://[::1]:port),X-Forwarded-*headers are trusted only from trusted proxies, and a listen error is emitted as'error'instead of exiting the process. - iosignal-cli 9.0.0:
-t --heartbeat-interval,-m --log-stats <ms>,-s --log-messages,-q --anonymous-quota, and role-based--auth-paramentries. CLI server
Added in 8.1.0
localAuthserver option andLocalKeyProvider: local test authentication without a key list, with the login ID as the CID. Local test logins- iosignal-cli 8.1.0:
io-serveroptions--id-key,--shared-key <key>and--members-only. They need iosignal 8.1.0 or later. close()on a CongSocket-only server no longer waits for a WebSocket server.
Changes in 8.0.0 (Arduino 7.0.0)
IOSignal JavaScript 8.0.0 and IOSignal Arduino 7.0.0 are major releases. Review these changes when upgrading from 7.x.
- The duplicate login default changed from keeping the old connection to replacing it (
keepNew). Restore the previous behavior withduplicateLogin: 'keepOld'. Duplicate logins - The
sudoservice accepts only Boho-authenticated level 255 connections, andRedisServiceaccepts only authenticated connections by default. Unauthenticated lab setups opt out with{ requireAuth: false }(replaced in 9.0 by theadminrole andRedisService(client, minRole)). - Server extensions:
BohoAuthonAuthEventand serviceonRemoteClose(remote). - Anonymous CIDs never reuse a CID that is online. The format (
?+ 4 characters) is unchanged (9.12.0 changed the character set). - IOSignal Arduino 7.0.0: stops instead of reconnecting after
AUTH_CLEARand can print the reason throughsetLog. 6.x cleared the credentials and reconnected as an anonymous client.
Verification scope
Checked on 2026-11-12 against JavaScript 9.12.0. The four chat browser tests were not run this time; their result is from 9.6.0 (2026-11-09). 9.12.0 has no client API changes.
| Target | Result |
|---|---|
| React, Svelte, Vanilla, CDN, WebRTC | Five production builds passed |
| Four chat examples | Two-way messaging and reconnect passed for each |
| WebRTC | Five local browser integration tests passed |
| Documentation JS examples | Server, client, direct topic, and subscription rules checked in Korean and English |
| Arduino hardware and upload | Not verified in this work |
| Real camera and microphone, Safari/iOS, other networks, TURN | Not verified in this work |
Chat tests used a local IOSignal server. WebRTC used Chrome and a virtual capture device on one computer. For the board check sequence, see troubleshooting.