Circuit background

Introduction

Introduction

Inventronix Connect is a platform designed to make it easy to turn your Arduino or ESP32 project into an IoT project - no backend coding required.

What can you do with it?

  • Send data from a WiFi-enabled microcontroller to our server for storage and retrieval
  • Create dashboards to visualise your data in real-time, viewable on desktop or mobile
  • Configure rules and actions based on your data - send commands back to your device, trigger webhooks, or get email notifications

Example Projects

Smart Heating Controller

An ESP32 measures the temperature and humidity of a conservatory, sending data every 10 seconds. Two rules handle the heating automatically:

  • If the average temperature drops below 15°C → send a "turn on heater" command to the device
  • If the average temperature rises above 17°C → send a "turn off heater" command

The dashboard shows real-time gauges, temperature history over 24 hours, and a log of recent rule executions.

Plant Watering Alerts

A soil moisture sensor monitors houseplants. When the average dryness exceeds 90% over 30 minutes, an email notification is sent as a reminder to water the plant.

How it Works (HTTP, not MQTT)

Inventronix Connect uses HTTP instead of MQTT. This makes setup much simpler - no broker configuration, no persistent connections to manage. Your device just makes HTTP requests.

What this means:

  • Device sends data to server: Yes
  • Server sends commands back to device: Yes (on next payload)
  • Multiple devices per project: Yes
  • Device-to-device communication: No
  • Commands received by specific device: No (first to check in gets it)

Commands are delivered in the HTTP response when your device sends its next payload. This means there's a small delay (your polling interval) before a device receives a command.

The Mental Model

Setup (one time, in the web interface)

  • Create a project - this gives you an API key
  • Define a schema - describe the shape of your data (e.g., "temperature is a number between 0-100, heater_on is a boolean")
  • Create actions - what should happen when conditions are met (send email, call webhook, send device command)
  • Create rules - the conditions that trigger your actions (e.g., "if avg temperature in last 5 mins < 15")
  • Build a dashboard - add charts to visualise your data

Runtime (every time your device sends data)

1

What's Next?

  • Quick Start - Get your first payload flowing in 5 minutes
  • Schemas - Learn about data validation and field types
  • Sending Data - API details and Arduino library
  • Dashboards - Build real-time visualisations
  • Rules and Actions - Automate responses to your data
  • Debugging - Troubleshoot when things go wrong