Public servers and web apps
Public services are intended for learning and temporary experiments. Addresses, quotas, and account features are service policy and may change.
| Purpose | Address |
|---|---|
| IOSignal workbench | test.iosignal.net |
| IOSignal WebSocket | wss://io.iosignal.net/ws |
| IOSignal Arduino TCP | io.iosignal.net:55488 |
| Remocon web app | remocon.kr |
| Remocon WebSocket | wss://io.remocon.kr/ws |
| Remocon Arduino TCP | io.remocon.kr:55488 |
The web controller and board must connect to the same server. Starting on the same router helps with home-channel grouping, but that grouping does not replace user authentication or permissions.
Check the service's current anonymous-access, credential, device-count, message-size, subscriber, and retention policies. Invalid credentials may cause connection rejection. For an independent environment, run your own server. Remocon's account APIs are not automatically included in a generic IOSignal server.
Use HTTPS with public WSS. For local WS and browser access policies, see connection environments. The source-based workbench provides a reproducible alternative to changing public UI menus.