// Quantumancy sensor node — per-device configuration TEMPLATE.
//
// HOW TO USE THIS FILE (there is no provisioning UI in this build — see
// README.md's "Manual configuration" section for the full walkthrough):
//
//   1. Copy this file to `device_config.h` in this same directory:
//        cp device_config.h.example device_config.h
//   2. Edit device_config.h and fill in YOUR OWN values below.
//   3. `device_config.h` is listed in .gitignore — it will not be committed.
//      Never paste real credentials or tokens into this .example file.
//   4. Build and flash as normal (idf.py build flash).
//
// The pairing token comes from the Quantumancy web app: sign in, create a
// device from your account (name + optional sensor-type hint), and the
// backend shows you a raw pairing token EXACTLY ONCE. Copy it straight into
// DEVICE_PAIRING_TOKEN below — the backend only ever stores a hash of it, so
// if you lose it your only recourse is deleting the device and pairing a new
// one.

#pragma once

// --- Wi-Fi station credentials -------------------------------------------
// The device joins this network in station mode (it does not host an AP).
#define DEVICE_WIFI_SSID        "your-wifi-ssid-here"
#define DEVICE_WIFI_PASSWORD    "your-wifi-password-here"

// --- Quantumancy backend ---------------------------------------------------
// Base URL of the backend, NO trailing slash. The firmware appends
// "/api/device/telemetry" itself. Use https:// in any real deployment.
#define DEVICE_BACKEND_BASE_URL "https://your-quantumancy-host.example.com"

// One-time raw pairing token shown by the web app when you create this
// device (POST /api/device). Sent as `Authorization: Bearer <token>` on
// every telemetry POST. Treat it like a password.
#define DEVICE_PAIRING_TOKEN    "paste-your-one-time-pairing-token-here"

// --- Reporting cadence -----------------------------------------------------
// How often (seconds) the telemetry task samples every registered sensor
// driver and POSTs a fresh readings batch. The contract caps 1 req/s
// sustained per device on the backend side — anything >= 2s here is safely
// inside that budget with room for retries.
#define DEVICE_REPORT_INTERVAL_SEC 15