Firmware SDK Overview

Hyperwisor provides two turnkey firmware libraries for ESP32-class devices. Both handle Wi-Fi provisioning, the realtime connection, and dashboard widget updates behind a simple API — you write device logic, not transport code. Pick the one that matches your toolchain.

Firmware development studio — The Firmware Development Studio — upload versions and push OTA updates to devices in the field.

More boards are on the way. Devices connect over standard IoT protocols — WebSocket, MQTT, or HTTPS — so any board that can speak one of them can already connect; you implement the protocol directly instead of using a drop-in SDK. Planning a different board or mass production? Reach out at support@nikolaindustry.com — we prioritize board support around real production plans.

Arduino vs ESP-IDF

Arduino

For the Arduino IDE. Fastest path to a working device — device.begin() / device.loop() and you’re connected. Rich helpers for widgets, dialogs, database, and onboarding.

ESP-IDF

For Espressif’s native framework. A component you add to idf_component.yml, with Kconfig feature toggles and a board port layer for production builds.

At a glance

	Arduino library	ESP-IDF component
Toolchain	Arduino IDE	ESP-IDF (`idf.py`)
Entry points	`device.begin()` / `device.loop()`	`hyperwisor_init()` / `hyperwisor_start()`
Targets	ESP32	ESP32, S2, S3, C3, C6, P4
Provisioning	Captive setup portal	SoftAP setup page
OTA	Built in	Opt-in (Kconfig)
Device identity	ECDSA P-256 on-chip	ECDSA P-256 on-chip
License	Proprietary (NIKOLAINDUSTRY)	Apache-2.0

What both libraries give you

Wi-Fi provisioning — connect with stored credentials, or fall back to an access-point setup mode on first boot
Realtime communication — a managed connection that auto-reconnects
Dashboard widgets — push live values to widgets by their widget ID
Cloud commands — register handlers for commands sent from a dashboard
OTA updates — push new firmware from the dashboard
Time sync — NTP after the network comes up
On-chip identity — each device generates an ECDSA P-256 keypair in flash and proves who it is before any data flows. The private key never leaves the chip

The one idea to hold on to

Everything a device sends is addressed to a target_id. Inside a command handler, that is the from argument — the dashboard that asked. So a reply, a widget update and a dialog all travel back to wherever the command came from. Hold that and the rest of the API follows: the thing you received from is the thing you send to. Both libraries work this way, with the same command envelope, so a sketch and an ESP-IDF component talk to the dashboard identically.

Pick Arduino

Install and flash your first sketch.

Pick ESP-IDF

Add the component to your project.