DCDevicecamp
Menu

Send a real reading, not just a mockup.

Choose a path, replace the marked credentials and run it. Every example uses TLS and the same telemetry pipeline as production devices.

Pick what you have in front of you.

  1. 01
    Create the destination

    Sign in, create or select a workspace, then add a device.

  2. 02
    Issue a credential

    Choose HTTP for cURL/Python HTTP, or MQTT for Mosquitto, Python MQTT and ESP32. Copy the credential when it is shown; secrets cannot be recovered later.

  3. 03
    Replace the placeholders

    Use the values from Devicecamp for DEVICE_ID, DEVICE_SECRET or the MQTT fields. Never commit the completed file.

  4. 04
    Run and verify

    Start the command or program, then open the device workbench. Temperature and humidity should appear within a few seconds.

One HTTPS request

Requires cURL. Available on macOS, most Linux systems and current Windows versions.

HTTP guide
Run in a terminal
curl -X POST \
  https://api.devicecamp.app/v1/devices/DEVICE_ID/telemetry \
  -H "Authorization: Bearer DEVICE_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"temperature":22.4,"humidity":51}'
Paste the command after replacing DEVICE_ID and DEVICE_SECRET.
Values you must replace
  • DEVICE_ID and its credential
  • Wi-Fi name and password for ESP32
  • Sample sensor reads with your hardware reads
Expected result

The device changes to online and Devicecamp discovers temperature and humidity automatically. If it does not, check the terminal or Serial Monitor first; the examples print transport errors without exposing the secret.

Once the first message works, use these patterns to shape a complete project.

Compare platforms

See where Devicecamp differs before you migrate or start a new build.

Blynk · ThingSpeak · Adafruit IO