Appearance
Device SDK (Arduino / ESP32)
The official Autoconnecto Arduino SDK connects an ESP32 to the platform over MQTT (MQTTS / MQTT-over-WSS) with telemetry, shared/client attributes, and dashboard RPC. ESP32 is the architecture listed in the library, and it is the board that has been tested. HTTPS sketches for ESP8266 and Pico W are in the repository and have not been run on those boards. ESP8266 sketches need the ESP8266 Arduino core (they do not build with the ESP32 core alone).
Repository
- GitHub: github.com/autoconnecto/autoconnecto-sdk
- Install: Arduino Library Manager → search AutoconnectoSDK, or clone into
Arduino/libraries/AutoconnectoSDK. PlatformIO:lib_deps = autoconnecto/AutoconnectoSDK.
Example sketches
Each sketch below has a matching dashboard template in the platform Solutions menu. Titles are SDK · <sketch folder> (search Solutions for SDK). Open the Solution to preview with Sample data, or Use it to copy the dashboard into your tenant. See SDK example Solutions.
| Sketch | Transport | Purpose |
|---|---|---|
BasicTelemetry_mqtt / BasicTelemetry_http | MQTT / HTTPS | First telemetry upload |
BasicTelemetry_esp8266 | HTTPS | ESP8266 telemetry, client attributes, shared attributes |
BasicTelemetry_pico_w_http | HTTPS | Pico W telemetry and client attributes |
BasicTelemetry_lte_ppp_mqtt / AllFunctionTest_lte_ppp_mqtt | MQTTS | ESP32 core 3.x PPP. build_opt.h holds only the -D line |
SwitchControl_mqtt / SwitchControl_http | MQTT / HTTPS | Shared attributes + client confirm |
RPCCommands_mqtt / RPCCommands_http | MQTT / HTTPS | Dashboard RPC on MQTT. HTTP sends the same telemetry |
AllFunctionTest_mqtt / AllFunctionTest_http | MQTT / HTTPS | Combined reference |
TelemetryBatch_http / TelemetryBatch_mqtt | HTTPS / MQTT | Batch API, or one MQTT publish per sample at least 1 s apart |
OtaFirmwareUpdate_mqtt / OtaSoftwareUpdate_mqtt | MQTT + HTTPS download | Firmware flash and LittleFS software |
GatewayRelay_http | HTTPS | Gateway → child relay |
Generator_Monitoring_mqtt | MQTT | Generator widget keys |
Machine_Runtime_mqtt | MQTT | Machine fleet current |
FleetSimulator_10_machines_http | HTTPS | Ten-machine HTTP simulator |
WatchdogReconnect_mqtt | MQTT | Reconnect loop |
DeepSleep_http | HTTPS | Deep sleep; set SLEEP_SEC in secrets.h (default 300 in secrets.h.example) |
Integration webhooks (non-Arduino)
For external systems and LoRa network servers, use script samples in the SDK repo:
examples/integrations/ — generic webhook, ChirpStack, and TTN curl/Python examples.
Platform UI
- Solutions — ready dashboards for every SDK example (
SDK · …). Flash the sketch, then open the matching Solution (or Use it into Dashboards). - Device Details → Check connectivity — copy device token, HTTP/MQTT/WS commands, gateway and LoRa notes per device.
- Integrations — LoRaWAN and HTTP integration webhooks, secrets, and mapping (moved from Tenant Settings).
Related
- Device connectivity — all ingress paths (HTTP, MQTT, WS, webhooks, gateway)
- MQTT ingest
- Realtime telemetry flow
