An online IoT class works like this: a hardware kit is couriered to the student before the term begins, and every session is a live video call in which the tutor and the student build the same circuit at the same time, each at their own desk. Nothing that matters is pre-recorded, and the student ends most sessions holding a piece of hardware that actually does something.
Many parents are surprised that IoT, a subject all about physical hardware, can be taught well online. It can, provided three things are organised properly: the kit, the class size and the camera setup. Here is exactly how it works, start to finish, for a parent who has never sat in on a session.
What arrives before the first class
Before classes begin, the student receives a hardware kit: a microcontroller, breadboard, sensors, wires and components. Everything they need to build alongside the instructor lives on their own desk. No improvising, no missing parts, and no borrowing from a shared cupboard halfway through a build.
Inside a beginner kit
A kit for a student starting between ages 10 and 13 is usually built around an Arduino Uno R3 or an ESP32 development board. A typical contents list looks like this:
- One Arduino Uno R3, or an ESP32 DevKit board if the course covers Wi-Fi from week one, with its USB cable.
- A 400 point solderless breadboard and a bundle of male to male and male to female jumper wires.
- A DHT11 temperature and humidity sensor, an HC-SR04 ultrasonic distance sensor, an LDR and a PIR motion sensor.
- An SG90 micro servo, a buzzer, a handful of LEDs, push buttons, and 220 ohm and 10k ohm resistors.
- A 0.96 inch OLED display or a 16x2 LCD with an I2C backpack, depending on the level.
- Spares: extra jumper wires, extra LEDs, and one spare of whichever sensor the term leans on most.
In India a kit at this level typically costs somewhere between INR 1,500 and INR 3,500 depending on the board and the display. In the UAE the equivalent lands at roughly AED 120 to AED 250. Providers either fold the kit into the programme fee or sell it once at the start, so ask which it is. A kit billed separately three weeks in is a common and avoidable surprise.
How the kit reaches the student
Kits go out by courier a week or so before the first session, with a printed packing list so the family can check the contents on arrival. The first session is then spent unboxing on camera: the tutor holds up each part, names it, and the student finds the matching one in their own box. That sounds trivial. It is not. A student who can tell a resistor from a diode, and who knows which pouch the servo lives in, loses far less time in week six.
What a live session actually contains
Good online IoT teaching is live and interactive, not a library of recorded lectures. A typical session looks like this:
- The instructor shares their screen and a top-down camera on their own workbench.
- Students follow along, building the same circuit in real time.
- Anyone stuck points their webcam at their board so the mentor can spot the issue.
- The session ends with a small challenge to complete and show next week.
In clock terms, a 90 minute session usually breaks into ten minutes reviewing last week's challenge, fifteen minutes introducing the new idea, forty minutes building and coding together, fifteen minutes of debugging whatever went wrong, and ten minutes setting the next task. Groups of younger students run 60 minutes and shorten the debugging block, because attention rather than difficulty is the limiting factor at that age.
The two camera setup
The tutor runs two video feeds: the laptop camera for their face, and a phone or an inexpensive USB document camera mounted over the breadboard. Students watch the wiring go in row by row instead of comparing their half-built circuit against a finished photograph. On the student's side one camera is enough, as long as it can be picked up and pointed at the board without unplugging anything.
Class size, and why it is capped
Hardware teaching does not scale the way a lecture does. A tutor inspecting twenty breadboards through twenty webcams inspects none of them properly. Group sessions are normally capped at six to eight students, with groups of three or four for the youngest learners and one to one for teenagers preparing a competition entry or a school project. If a provider will not tell you the class size for a hardware session, treat the refusal as the answer.
How a tutor spots a wiring fault through a webcam
This is the part parents are most sceptical about, and it is mostly a matter of method. The tutor asks the student to lay the board flat, light it from the side, and hold the camera about a hand's width above it, looking down the rows rather than across them. Most beginner faults are visible in that single view, and they repeat constantly:
- A component with both legs in the same breadboard row, so it is shorted out and does nothing.
- An LED in backwards. The longer leg is the anode and belongs on the resistor side.
- A jumper in the wrong power rail, or a rail that was never bridged to the board's 5V and GND pins.
- No common ground between the microcontroller and an externally powered servo or motor driver.
- A sensor's data pin sitting in a different pin from the one the code declares.
- 5V wired into a 3.3V pin on an ESP32, which is a fault you want caught before anything is powered on.
When the picture is not enough, the tutor moves to the code. The student shares their screen, opens the Serial Monitor at 9600 baud, and adds two or three Serial.println() checkpoints. From there you can tell quickly whether the board is running at all, whether the pin is being read, and whether the value coming back is sensible. That sequence (look at the board, read the serial output, then check the pin numbers against the wiring) clears the large majority of problems in a few minutes.
Video compression smears thin jumper wires into a blur, which is why live video is often the worst way to show a stuck circuit. One still photo taken from directly above the breadboard, with the phone flash off and a lamp to the side, tells a tutor more than five minutes of shaky footage. Teach your child to send the photo first.
Sessions are recorded so students can rewatch any tricky step. This single feature is one of the biggest advantages online learning has over a one-time classroom session.
A term, week by week
A twelve week beginner term taught online follows a fairly settled shape. Pace varies with age, and if you are unsure whether your child is ready to start, our note on the best age to start IoT and coding covers that question properly.
- Weeks 1 and 2: unboxing, naming the parts, installing the Arduino IDE, uploading a first sketch, blinking an LED with pinMode() and digitalWrite().
- Weeks 3 and 4: inputs. Push buttons, pull-up resistors, reading an LDR with analogRead(), printing values to the Serial Monitor.
- Weeks 5 and 6: sensors that speak a protocol. The DHT11 and the HC-SR04, installing a library, and reading one page of a datasheet without panicking.
- Weeks 7 and 8: outputs and timing. Servos, a buzzer, a display, and the move from delay() to millis() so the board can do two things at once.
- Weeks 9 and 10: connectivity, which is where it stops being electronics and becomes IoT. Joining Wi-Fi on an ESP32 and publishing readings to a dashboard over MQTT or to a service such as ThingSpeak.
- Weeks 11 and 12: the term project. The student picks a problem, plans the build, assembles it, and presents it on camera.
Students who want more to build between sessions can work through our list of beginner IoT projects to build at home, most of which use parts already sitting in the standard kit.
What happens when a component fails
Components do fail. Jumper wires break inside the insulation and still look perfect, inexpensive DHT11 modules die, LEDs go if a resistor was forgotten, and servo gears strip when a child holds the arm still against the motor. Assume one or two failures per student per term and judge a provider on how it handles them, not on whether they happen.
Free tools like Tinkercad let students wire and program virtual circuits in a browser, and Wokwi does the same for the ESP32. If a real component breaks or a new one is on the way, learning never stops. Students can even prototype an entire project digitally before touching hardware. The order we work in is simple: check the spares in the kit first, move the student onto the simulator for that session so they are building rather than watching, and dispatch a replacement part the same week.
How projects are assessed
There is no written exam. A project is judged on what the student can build and explain, which in practice comes down to four questions:
- Does it work? The student records a short video of the build running, with the wiring visible in frame.
- Can they explain it? A two minute walkthrough of what each part is doing, in their own words, without a script.
- Did they debug it themselves? Tutors keep notes on who asked for the answer and who asked for a hint.
- Did they change anything? Copying a circuit is week one work. Adding a second sensor, or shifting a threshold and saying why, is the actual skill.
Rather than a percentage, work is placed on a ladder with four rungs: replicate (build what was demonstrated), modify (change one variable and predict the result before running it), combine (join two circuits from earlier weeks into one), and design (start from a problem instead of a diagram). Most beginners reach the combine rung by the end of a first term, and that is a healthy place to be. Parents who want the reasoning behind starting on this board rather than a robotics kit can read our piece on why Arduino makes a good first board for students.
What parents are expected to do, and not do
The practical requirements are small and mostly one-off.
- A laptop or tablet with a webcam and stable internet.
- The starter kit (provided) and a clear desk to work on.
- About 30 minutes of practice between live sessions.
- Administrator access on the laptop for the first session, because the Arduino IDE and the USB serial driver (usually the CH340 driver on clone boards) need installing once.
- A power socket near the desk and a desk lamp. Overhead lighting alone makes a breadboard genuinely hard to read on camera.
What to leave alone
Sit in on the first session and the last one, then stay out of the middle. The most common way a parent slows a child down is by fixing the circuit for them. A wrongly wired board that the student finds and corrects is worth more than a working board that someone else built. The same goes for answering the tutor's questions on your child's behalf while they are still thinking. A silence on a video call feels much longer than it is, and that pause is usually where the learning is happening.
How progress is reported
Reporting on an online programme should be better than a classroom equivalent, because almost everything the student produces is already a file. What you should expect to receive is straightforward: attendance and practice logs, a short written note from the tutor every fourth session covering what was built and what still needs work, a saved copy of each project's code and wiring photograph, and a fifteen minute call with the tutor at the midpoint and again at the end of the term. Ask to see a sample report before you enrol, since the difference between a real one and a template is obvious at a glance.
By the end of a year the student has a portfolio of working builds with video evidence, which counts for far more than a certificate when they enter a competition or start looking at where IoT skills lead after school.
Still weighing it up against in-person learning? Our online vs offline comparison lays out both side by side.
What to do next
If you are considering an online IoT class, do three things before you pay. Ask exactly what is in the kit and who owns it after the term. Ask for the tutor to student ratio in hardware sessions, not the average across all classes. Ask to sit in on a live session, or at least to watch a recording of a real one rather than a promotional edit. Any provider confident in how it teaches will say yes to all three.
Fizon Tech runs online and in-person IoT, robotics and STEM classes for students aged 8 to 22, from offices in Trichy, Tamil Nadu and Dubai. The syllabus, kit list and session format are set out on our IoT and STEM programme for students page, and you can get in touch to book a trial session and watch one run before deciding.
Written by M Khaushalya, Business Lead, India at Fizon Tech. The role covers Fizon Tech's India programmes, working with parents and schools across Tamil Nadu on IoT, robotics and STEM classes for students aged 8 to 22.