Prototyping & Education

MQTT for Prototyping & Education

From a first ESP32 project to a classroom lab, MQTT is the quickest way to make things talk. Start on the public shared endpoint, then move to a private broker when it gets real.

No card required

What you can build

Build your first connected project on ConnectMQ

You build the project, ConnectMQ moves the data. Boards and laptops publish readings; a dashboard, a Node-RED flow or a classmate’s script subscribes — no server to set up.

Your boards
ESP32 / Arduinolab/{team}/esp32/temperature
Raspberry Pilab/{team}/pi/sensors
Python scriptslab/{team}/script/out
CLI (mosquitto)lab/{team}/test
ConnectMQ
  • secure WebSockets
  • TLS on 8883
  • QoS 0, 1 and 2
  • retained messages
What you build on top
Class dashboard
Node-RED flows
Grading & data export
Student apps
What you get

Prototyping & Education on ConnectMQ

  • Try the public shared endpoint broker.connectmq.com with any MQTT client
  • Code samples for Python, Node.js, ESP32, Go and the CLI
  • Private broker when public sandboxes are no longer enough
example topic design
lab/team-3/esp32/temperature
lab/team-3/esp32/led/set
From first blink to production

Start small, grow without rewriting

Every step uses standard MQTT, so the same code moves from the public broker to a private one by changing the host, port and credentials.

  1. No sign-up

    Public broker

    • broker.connectmq.com, port 1883
    • Shared: anyone can read the topics
    • Ideal for a first test
  2. Private

    Free plan

    • No card required
    • TLS and your own credentials
    • Up to 5 connections
  3. Production

    Basic or Scale plan

    • Up to 1,000 connections
    • Up to 10,000,000 session minutes a month
    • Same code, new credentials
Real-life example

Students control a lab board from home

A favourite classroom project with MQTT: an ESP32 on the lab bench at school, a Python script on a student’s laptop at home, and ConnectMQ in the middle. No firewall rules at school, no server to set up.

ConnectMQMQTT broker · TLS 8883$ python led.py→ led/set on← led: on← temp: 24.6Student at homePython script · laptopMQTT lablab/+/esp32/#Team 3ESP3224.6 °CSchool labESP32 + LED + sensor · school Wi-Filab/team-3/esp32/led/set {"on":true}lab/team-3/esp32/led/set {"on":true}lab/team-3/esp32/state {"led":true,"temp":24.6}lab/team-3/esp32/state {"led":true,"temp":24.6}Team 3 · nowLED is on — lab at 24.6 °CConnectMQMQTT broker · TLS 8883$ python led.py→ led/set on← led: on← temp: 24.6Student at homePython script · laptopMQTT lablab/+/esp32/#Team 3ESP3224.6 °CSchool labESP32 + LED + sensor · school Wi-Filab/team-3/esp32/led/set {"on":true}lab/team-3/esp32/led/set {"on":true}lab/team-3/esp32/state {"led":true,"temp":24.6}lab/team-3/esp32/state {"led":true,"temp":24.6}Team 3 · nowLED is on — lab at 24.6 °C
  1. 20:15 Student’s laptop at home

    A ten-line Python script publishes a command to the team’s board.

    lab/team-3/esp32/led/set → {"on":true}
  2. 20:15 ESP32 on the lab bench

    Subscribed to its team’s topics: it switches the LED on and publishes its state with the room temperature.

    lab/team-3/esp32/state → {"led":true,"temp":24.6}
  3. 20:15 Student’s script

    Receives the state through ConnectMQ and prints it — the round trip takes well under a second.

  4. 20:16 The whole class

    Every team has its own topics and credentials, so boards and scripts never get in each other’s way.

Start without an account: try the same script on the free public broker broker.connectmq.com:1883, then move the class to a private broker.

Pilot

Run your next lab on ConnectMQ

Start on the public broker with no sign-up, then move the class to a private broker — the Free plan needs no card, Basic gives up to 100 connections, with TLS and its own credentials.