Book Image

Developing IoT Projects with ESP32

By : Vedat Ozan Oner
Book Image

Developing IoT Projects with ESP32

By: Vedat Ozan Oner

Overview of this book

Developing IoT Projects with ESP32 provides end-to-end coverage of secure data communication techniques from sensors to cloud platforms that will help you to develop production-grade IoT solutions by using the ESP32 SoC. You'll learn how to employ ESP32 in your IoT projects by interfacing with different sensors and actuators using different types of serial protocols. This book will show you how some projects require immediate output for end-users, and cover different display technologies as well as examples of driving different types of displays. The book features a dedicated chapter on cybersecurity packed with hands-on examples. As you progress, you'll get to grips with BLE technologies and BLE mesh networking and work on a complete smart home project where all nodes communicate over a BLE mesh. Later chapters will show you how IoT requires cloud connectivity most of the time and remote access to smart devices. You'll also see how cloud platforms and third-party integrations enable endless possibilities for your end-users, such as insights with big data analytics and predictive maintenance to minimize costs. By the end of this book, you'll have developed the skills you need to start using ESP32 in your next wireless IoT project and meet the project's requirements by building effective, efficient, and secure solutions.
Table of Contents (18 chapters)
1
Section 1: Using ESP32
7
Section 2: Local Network Communication
12
Section 3: Cloud Communication

Chapter 10

  1. (d) – MQTT. The MQTT protocol defines a broker as a central element in the architecture, where clients can publish and subscribe to topics. Refer to this link for more information: https://mqtt.org/.
  2. (c) – Only runs on top of UDP. This is not true. CoAP is a service layer protocol so it can run on top of any transport layer. Wikipedia explains this well with examples: https://en.wikipedia.org/wiki/Constrained_Application_Protocol.
  3. (a) – Polling server for status updates. The WebSocket API provides a two-way communication channel between a browser and a server, removing the necessity to poll the server for status updates. See here: https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API.
  4. (b) – Security is an optional feature. On the contrary, most IoT platforms force security at each level of communication.
  5. (c) – A policy file is automatically generated when a thing is created. This is not true. A policy and...