DevelopersDocumentation

WifiManager — Socket.IO transport (real-time)

Keon WiFi SDK → WifiManager

WifiManager controls a device over a persistent Socket.IO connection opened directly to the FeelExchangeCenter (FEC) server: commands reach the device in near real time and status is pushed back with low latency. Choose this transport when live, interactive control is required.

When to choose it

• Interactive sessions where the UI reacts to device state in real time.
• Continuous status streams (position, battery, user actions) without polling.

For the simplest one-key setup see FugManager.

Authentication

The WiFi transport needs a registrationToken, obtained with the partner token:

import { getTokenForKeonWiFi } from '@feelrobotics/keon-wifi-sdk';

const { registrationToken, deviceConnectionKey } = await getTokenForKeonWiFi(
  partnerToken,          // feelAppsToken from your backend (Control Plane)
  deviceConnectionKey    // optional: pass the FeelConnect key to target a device
);

getTokenForKeonWiFi throws AuthError on failure. The registration token is a JWT that also encodes which WebSocket server to connect to.

Quick start

import { getTokenForKeonWiFi, WifiManager } from '@feelrobotics/keon-wifi-sdk';

const { registrationToken } = await getTokenForKeonWiFi(
  partnerToken,
  deviceConnectionKey
);

const manager = await WifiManager.connect(partnerToken, registrationToken, {
  // A connection can cover several devices, so status arrives as a list.
  onStatusChange: (statuses) =>
    console.log('battery', statuses[0]?.battery_status),
  onUserAction: (message) => console.log('user action', message),
});
await manager.moveTo(50, 90);
await manager.disconnect();

API

WifiManager.connect(feelAppsToken, registrationToken, callbacks?) returns a RemoteController — the same server-backed interface as FugManager (getStatuses, setIntensity, setStatusInterval, switchToBtMode, resetCredentials, forceStatusReport), on top of the common KeonController interface.

callbacks accepts onStatusChange(statuses) and onUserAction(message).

Notes

• connect() resolves before the socket is actually established; connection and authorization errors are reported to the console rather than rejecting the returned promise. Treat the first onStatusChange as the connectivity signal.
• Statuses accumulate per device (keyed by serial number) as reports arrive; payloads can be partial.
• Protocol-level details (event vocabulary, server topology, OAuth flow) are documented in the Keon WiFi protocol section.

---

← FugManager — REST · Next: BleManager — Web Bluetooth