Skip to main content

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.

PurposeAddress
IOSignal WebSocketwss://io.iosignal.net/ws
IOSignal Arduino TCPio.iosignal.net:55488
Remocon web appremocon.kr
Remocon WebSocketwss://io.remocon.kr/ws
Remocon Arduino TCPio.remocon.kr:55488
IOSignal Arduino examples, firmware install and board settingshttps://arduino.iosignal.net
Web examples (channel lab, WebRTC, chat)https://lab.iosignal.net

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. To check messaging without a board, use the CLI.