ESP-IDF

The component is configured through Kconfig (idf.py menuconfig or sdkconfig.defaults). Features compile in only when enabled, so you pay for what you use.

DEVICE_STATUS is always registered and has no toggle. Whether a device is alive is not an application concern, and a device that cannot answer it is simply broken.

Feature toggles

Symbol	Default	Purpose
`HYPERWISOR_ENABLE_SYSTEM`	y	Built-in `restart`, `status`, `info` commands
`HYPERWISOR_ENABLE_NTP`	y	SNTP time sync after Wi-Fi up
`HYPERWISOR_ENABLE_HTTP`	y	`hyperwisor_http_get/post` helpers
`HYPERWISOR_ENABLE_WIDGET`	y	Push live values to dashboard widgets
`HYPERWISOR_ENABLE_OTA`	n	OTA via the `OTA_UPDATE` cloud command
`HYPERWISOR_ENABLE_GPIO`	n	Cloud-driven GPIO read/write
`HYPERWISOR_ENABLE_DISPLAY`	n	Backlight control via the board port

Connection settings

CONFIG_HYPERWISOR_WS_HOST="hyperwisor-realtime-secure.onrender.com"
CONFIG_HYPERWISOR_WS_PORT=443
CONFIG_HYPERWISOR_HTTP_BASE_URL="https://hyperwisor.nikolaindustry.workers.dev/functions/v1"

Those are the defaults and point at the live platform. Override them only when self-hosting.

Radio power save

CONFIG_HYPERWISOR_WIFI_PS_NONE=y       # radio always on (mains-powered)
# CONFIG_HYPERWISOR_WIFI_PS_MIN_MODEM=y  # the IDF default
# CONFIG_HYPERWISOR_WIFI_PS_MAX_MODEM=y  # deepest saving

This is a deliberate choice, not a tuning knob. ESP-IDF defaults to MIN_MODEM, which is correct for a battery device and wrong for a mains-powered panel: on a busy 2.4 GHz band the radio misses beacons and the device disassociates (wifi:bcn_timeout), reconnecting every minute or two. Chasing that symptom anywhere above the radio is wasted effort — nothing else matters until the link stops dropping.

Mains-powered device, or a display? Set HYPERWISOR_WIFI_PS_NONE. On a coin cell, leave the default.

Connection behaviour

You do not configure this, but it is worth knowing what the library does when the network misbehaves.

Situation	What happens
Link drops	Backs off 5s, 10s, 20s, 40s, capped at 60s
Jitter	Each retry lands anywhere in a window as wide as the wait itself
Identity rejected	Flat 5s retry, no escalation
Handshake completes	Backoff resets — only `auth_ok` counts as success
Lost keepalive	Three missed ping/pong rounds before the device gives up

The jitter matters as soon as more than one device exists. A fixed interval means every device in the field reconnects in lockstep after a server restart, and that burst keeps the server down. A window that widens with the delay puts the largest spread where the crowd is biggest. Tolerating three lost keepalives rather than one is the same judgement: on the open internet a lost control frame is routine, so a one-strike timeout kills healthy connections.

Board port (optional)

For production boards, provide a hyperwisor_port_t struct of function pointers to integrate with a specific board’s GPIO whitelist, display backlight, or sensor APIs. See hyperwisor_port.h for the full interface.

Next: API reference

The C API across the umbrella header.

Overview

Arduino

ESP-IDF — Configuration

Feature toggles

Connection settings

Radio power save

Connection behaviour

Board port (optional)

Next: API reference