10 IoT Device Examples and Their Uses
Compare 10 common IoT device examples, understand what each one does, and learn how to choose boards, sensors, and connectivity for a project.
AI may assist drafting, but technical claims are reviewed against cited primary sources. Read our editorial policy.
IoT devices include complete products such as smart thermostats and development platforms such as an ESP32 board. What makes them part of the Internet of Things is the combination of physical sensing or actuation, computing, and a network interface. NIST uses those physical and digital interfaces to define the scope of an IoT device (NIST Cybersecurity for IoT FAQ).
This guide compares ten device examples useful for learning and prototyping. A development board is not a finished product: enclosure, power protection, radio compliance, software maintenance, security, testing, and application-specific approvals remain separate work.
10 IoT device examples at a glance
| Device | Type | Connectivity | Good starting uses | Main tradeoff |
|---|---|---|---|---|
| ESP32 DevKit | Microcontroller board | Wi-Fi, Bluetooth | Low-cost sensor nodes and home prototypes | Third-party board layouts can differ |
| Arduino UNO R4 WiFi | Microcontroller board | Wi-Fi, Bluetooth | Education and shield-based prototypes | Split main processor and wireless module add complexity |
| Arduino Nano 33 IoT | Compact microcontroller board | Wi-Fi, Bluetooth LE | Compact sensors and motion logging | 3.3 V I/O needs care with older accessories |
| Raspberry Pi Pico W | Microcontroller board | Wi-Fi, Bluetooth | Learning, control, and simple connected nodes | Less turnkey networking than a Linux computer |
| Raspberry Pi 5 | Single-board computer | Wi-Fi, Bluetooth, Ethernet | Gateways, dashboards, and computer vision | Higher power and thermal needs |
| Raspberry Pi Zero 2 W | Compact single-board computer | Wi-Fi, Bluetooth | Small gateways and network monitors | Limited memory and ports constrain heavier workloads |
| BBC micro:bit v2 | Educational microcontroller board | Bluetooth, radio | Classroom sensing and interaction | Not intended for demanding gateway workloads |
| Arduino MKR WAN 1310 | LoRaWAN development board | LoRaWAN | Remote low-data sensor prototypes | Requires a compatible regional network and setup |
| Particle Boron | Cellular development kit | Cellular, Bluetooth | Mobile and remote prototypes | Coverage, data service, antenna, and power planning matter |
| Arduino Nicla Sense ME | Sensor board | Bluetooth | Compact environmental and motion sensing | Integrated size costs more and limits physical access |
Connectivity and features vary by revision and software. Confirm the exact board at its official documentation before designing a circuit or buying accessories.
Device vs sensor: what is the difference?
A sensor is the part that observes something: a thermistor, accelerometer, microphone, light sensor, pressure sensor, or similar transducer. A complete IoT device adds computation, software, power, and networking, and may include actuators.
For example, a bare humidity sensor produces an electrical or digital reading. When it is connected to a microcontroller that validates the measurement, sends it over Wi-Fi, accepts authenticated configuration, stores readings during an outage, and reports its own health, it becomes part of an IoT device.
This distinction matters when planning a budget. A board does not automatically include the right sensor, safe power supply, connector, antenna, enclosure, calibration process, or maintenance plan.
1. ESP32 development board
An ESP32 development board combines a microcontroller with Wi-Fi and Bluetooth, making it a common base for room sensors, connected switches, test dashboards, and protocol experiments. Espressif's official DevKitC documentation identifies the development board, module, I/O headers, power options, and getting-started flow (ESP32-DevKitC user guide).
Use it when: the prototype needs wireless connectivity, deterministic microcontroller behavior, and modest local processing.
Watch for: “ESP32 DevKit” is also used for third-party layouts. Check the exact module, USB interface, pin labels, flash configuration, and schematic instead of assuming every board is identical.
2. Arduino UNO R4 WiFi
The UNO R4 WiFi preserves the familiar UNO form while using a Renesas RA4M1 as the main microcontroller and an ESP32-S3 module for Wi-Fi and Bluetooth connectivity. Arduino documents an onboard LED matrix, Qwiic connector, RTC, DAC, and CAN capability on the official board page (Arduino UNO R4 WiFi documentation).
Use it when: a learner benefits from Arduino examples, the UNO physical ecosystem, and visible onboard features.
Watch for: the main processor and wireless module are separate. Confirm which processor owns a peripheral or network task, and account for the board's logic and power requirements before connecting sensors.
3. Arduino Nano 33 IoT
The Nano 33 IoT is a compact Arduino board with Wi-Fi, Bluetooth Low Energy, an inertial measurement unit, and a secure element. Its size suits compact condition monitors and motion experiments (Arduino Nano 33 IoT documentation).
Use it when: small physical size, Arduino tooling, wireless connectivity, and onboard motion sensing are useful.
Watch for: it uses 3.3 V I/O and is not a drop-in electrical replacement for every older 5 V Arduino accessory. Check voltage compatibility before wiring modules.
4. Raspberry Pi Pico W
Raspberry Pi Pico W is a microcontroller board based on the RP2040 family with onboard wireless networking. It can run time-sensitive control loops without a desktop operating system and works well for learning GPIO, sensors, and compact network services. Raspberry Pi provides board documentation, pinout information, and wireless guidance through its official product and documentation pages (Raspberry Pi Pico series documentation).
Use it when: the project needs a low-cost microcontroller, predictable startup, and wireless communication.
Watch for: it does not provide the full Linux software environment of a Raspberry Pi computer. Libraries, TLS memory use, storage, and update mechanisms must fit a microcontroller.
5. Raspberry Pi 5
Raspberry Pi 5 is a Linux single-board computer with Wi-Fi, Bluetooth, Ethernet, USB, display, camera, and high-performance processing options. Official Raspberry Pi material identifies a quad-core Arm Cortex-A76 CPU, wireless networking, and the board's richer I/O platform (Raspberry Pi 5 announcement).
Use it when: a gateway needs Linux packages, multiple services, local dashboards, a database, cameras, or heavier edge processing.
Watch for: power consumption, storage integrity, operating-system maintenance, startup time, and cooling are different from a sleeping microcontroller node. It is often better as a gateway than as every endpoint.
6. Raspberry Pi Zero 2 W
The Zero 2 W is a smaller Linux computer with Wi-Fi and Bluetooth. It fits compact gateways, network monitors, and camera prototypes where Raspberry Pi OS and Linux tooling are more useful than many microcontroller peripherals (Raspberry Pi Zero 2 W product page).
Use it when: physical size and a Linux environment matter more than desktop-class performance.
Watch for: memory, ports, storage, and CPU capacity are limited compared with larger Pi models. Define the services and data retention before choosing it for a gateway.
7. BBC micro:bit v2
The micro:bit v2 is an educational board with an LED display, buttons, motion sensing, temperature-related measurement, a microphone, touch input, radio, and Bluetooth features. The micro:bit foundation explains its integrated sensors and how they behave in learning projects (micro:bit sensors).
Use it when: teaching, fast interactive experiments, and a self-contained board are the priority.
Watch for: classroom convenience does not make it an industrial controller or high-bandwidth gateway. Treat temperature readings and other onboard observations according to the documented sensor implementation and placement.
8. Arduino MKR WAN 1310
The MKR WAN 1310 combines an Arduino microcontroller format with LoRa connectivity for LoRaWAN experiments. Arduino documents its radio module, battery connector, and board resources on the official hardware page (Arduino MKR WAN 1310 documentation).
Use it when: a remote prototype sends small, infrequent sensor messages through an available LoRaWAN network.
Watch for: the device needs the correct regional configuration, gateway or network coverage, keys, payload design, and duty-cycle planning. The LoRa Alliance publishes link-layer and regional specifications because interoperability depends on more than the radio chip (LoRaWAN technical specifications).
9. Particle Boron
Particle Boron is a cellular development platform intended for connected products and prototypes that operate away from local Wi-Fi. A cellular board can combine device hardware with a managed device and data service, depending on the selected platform and plan (Particle Boron documentation).
Use it when: the prototype is mobile or remote and cellular coverage is more realistic than installing a local gateway.
Watch for: verify the exact modem variant, supported region and carrier, antenna requirements, data plan, power peaks, coverage, certification path, and platform lifecycle. “Cellular” is not one globally interchangeable configuration.
10. Arduino Nicla Sense ME
Nicla Sense ME integrates multiple Bosch motion and environmental sensors with Bluetooth Low Energy on a compact board. Arduino's official page describes its sensing functions, microcontroller, and board resources (Arduino Nicla Sense ME documentation).
Use it when: a compact Bluetooth sensor platform is more valuable than assembling several separate breakouts.
Watch for: dense integration can limit connector access and increase replacement cost. Sensor location, heat from electronics, enclosure airflow, calibration, and mounting still influence readings.
ESP32 vs Arduino vs Raspberry Pi
These names describe overlapping ecosystems rather than three equivalent products.
| Choice | What it usually means | Strong fit | Less suitable when |
|---|---|---|---|
| ESP32 development board | Wireless microcontroller platform and Espressif ecosystem | Cost-sensitive connected sensors and embedded control | You need a full Linux application stack |
| Arduino board | Hardware plus a beginner-accessible development ecosystem; capabilities vary by model | Education, rapid hardware experiments, and broad library examples | You assume all Arduino boards have the same voltage, processor, or networking |
| Raspberry Pi Pico W | Raspberry Pi's wireless microcontroller platform | GPIO, control, and MicroPython or C/C++ learning | You need ordinary Linux packages |
| Raspberry Pi computer | Linux single-board computer, such as Pi 5 or Zero 2 W | Gateways, dashboards, cameras, databases, and richer edge software | Battery sleep and instant deterministic startup dominate the design |
Choose the operating model before comparing specifications. A microcontroller normally runs one embedded application; a Linux computer runs an operating system and multiple processes. That difference changes power, storage, updates, security, failure recovery, and maintenance.
Map the use case to the device
| Project need | Start by evaluating | Why |
|---|---|---|
| USB-powered room sensor | ESP32, Pico W, Nano 33 IoT, UNO R4 WiFi | Wireless microcontrollers can read common sensors without a full OS |
| Battery remote soil node | LoRaWAN board or carefully power-managed wireless MCU | Sleep current, radio coverage, and message frequency dominate |
| Cellular asset-tracking prototype | Regional cellular development kit | Mobility and wide-area coverage matter more than local Wi-Fi |
| Camera or local dashboard | Raspberry Pi computer | Linux software and higher processing needs fit an SBC |
| Classroom interaction | micro:bit or beginner Arduino board | Integrated inputs, outputs, and guided materials shorten setup |
| Compact motion/environment experiment | Integrated sensor board such as Nicla Sense ME | Onboard sensors reduce wiring and physical size |
This table is a starting point. Use the IoT Device Finder for a guided hardware profile, the IoT Project Idea Generator for scoped builds, and the IoT Device Comparison to filter 25 boards by connectivity, power, difficulty, and price band.
Seven criteria for choosing an IoT device
1. Physical data and action
List the sensors, actuators, signal types, sample rates, and accuracy needs. Check voltage levels, buses, pin count, timing, and whether a ready-made driver exists.
2. Connectivity ownership
Ask who provides and maintains the Wi-Fi, gateway, SIM, carrier account, Ethernet cable, or LPWAN network. Coverage at the installation point matters more than a protocol logo.
3. Power source and duty cycle
Estimate active, transmit, idle, and sleep time with the complete circuit. A board advertised as low power can still perform poorly with an inefficient regulator, always-on sensor, bright LED, or frequent radio connection.
4. Software environment
Decide whether you need an embedded loop, real-time behavior, MicroPython, Arduino libraries, an RTOS, or Linux services. Also plan provisioning, logs, configuration, updates, and rollback.
5. Security and privacy
NIST's IoT device cybersecurity baseline is a useful requirements prompt covering device identification, configuration, data protection, logical access, software update, cybersecurity-state awareness, and device security (NISTIR 8259A). Tailor the controls to what the device senses or can change.
6. Mechanical and environmental fit
Prototype boards are often open PCBs. Temperature, moisture, dust, vibration, connectors, strain relief, antenna clearance, enclosure material, and service access affect the finished device.
7. Lifecycle and support
Check official documentation, product status, software maintenance, replacement availability, data export, account ownership, and an end-of-life plan. A device is not maintainable merely because the first firmware upload worked.
Common limitations of IoT development boards
- Board variants and clones may change components or pin assignments.
- Product certifications do not automatically cover a modified end product.
- Breadboards and jumper wires are not deployment wiring.
- Development USB power does not model the final supply or battery.
- Example firmware often prioritizes clarity over secure lifecycle management.
- A cloud demo does not prove offline behavior, retention, privacy, or scale.
- Sensor modules may need calibration and application-specific validation.
Use these boards for learning and controlled prototypes. Medical, safety, security, food, traffic, utility, and industrial control applications require qualified design and domain-specific review.
Frequently asked questions
What are five examples of IoT devices?
An ESP32 sensor node, smart thermostat, connected electricity meter, cellular vehicle tracker, and industrial vibration monitor are five examples. Some are development platforms; others are finished systems.
What are ten IoT devices used for?
The ten devices in this guide support sensor nodes, home automation, classroom learning, remote LPWAN experiments, cellular prototypes, gateways, dashboards, motion sensing, and environmental monitoring. Their suitability depends on the complete system.
Is a sensor itself an IoT device?
Usually not. A bare sensor observes a physical quantity. It becomes part of an IoT device when computing, software, power, and networking turn the reading into data that can be exchanged and acted upon.
Is Arduino or Raspberry Pi better for IoT?
Neither is universally better. An Arduino microcontroller board may suit deterministic, lower-power sensor control, while a Raspberry Pi computer may suit Linux applications, gateways, cameras, and local dashboards. Compare specific models and requirements.
What is the easiest IoT board for a beginner?
A board with built-in wireless, official getting-started documentation, compatible voltage levels, and examples for the chosen sensor is usually easiest. ESP32, Arduino UNO R4 WiFi, Nano 33 IoT, Pico W, and micro:bit can all be beginner-friendly in different projects.