Sanity is the platform for structured content. With Sanity you can manage your text, images, and other media with APIs. Sanity Studio an open source headless real-time CMS, that you can customize with JavaScript and React.

Next.js is an increasingly popular solution for creating Jamstack sites using JavaScript and React.

Combining Next.js, Sanity, Github and Vercel bridges the gap between development and operations activities by enforcing automation in building, testing and deployment of applications. In my case I found a starter kit that had the continuous deployment set up already.

Components for experience, projects, education, blog, comments with CMS integration etc.

It made the component development easier as React makes reuse very easy.

Finally code for interacting with the CMS for writing and publishing content, is well designed.

Building this site with React / Next.js and Sanity

The BLE (Bluetooth Low Energy) Beacon is a hardware-unidirectional transmitter, also called a beacon, that cyclically transmits its identifier and various information to all available electronic devices within range. It most often transmits telemetry data e.g. temperature, supply voltage, uptime, GPS coordinates, counter of sent messages, time. For the device to interact with the beacon, it is necessary to have a specific application / software that is able to process the data and notify the user.

The ESP32 development platform has one 2.4 GHz antenna that can be used for WiFi or Bluetooth individually. In addition to Bluetooth 4.2 support, ESP32 also supports BLE. One of the modes that can be used for BLE is the creation of a Beacon.

Depending on the configuration and preset actions, the Android / iOS system user may be automatically notified of the Beacon within range by system notifications.

Software implementations for ESP32 in the Arduino IDE allows you to create the following BLE Beacon profiles:

Apple profile from 2013 designed for indoor navigation, used in Apple centuries, but also in the Grévin wax museum in Prague, for example.


a more popular BLE Beacon profile from Google from 2015, designed for the distribution of telemetry data, but also URL addresses.


Today we will take a closer look at the implementation of the Eddystone profile, specifically the telemetry variant - Eddystone-TLM and Eddystone-URL containing an executable hyperlink.

 plaintext identifier. It can be used for indoor localization, identification of a physical object


Information on Beacone. Battery voltage, system data, sensor data


A URL of up to 18 characters that redirects the device to a web page that runs under SSL (HTTPS). This type of Beacon contains an identifier in the header: Physical Web

The beacon transmits every 100ms
Transmits information about running firmware version, battery voltage (supply voltage), processor temperature, transmission counter, Beacon uptime
After the transmission, the ESP32 sleeps until the next transmission
To obtain information from Beacon on Android devices, we can use the nRF Connect for Mobile application from Nordic Semiconductor ASA. After installing and opening the application, we can scan the surroundings and view the distributed Beaconom data within range.

The beacon transmits every 100ms
Transmits one telemetry information - TX signal power and URL (hypertext link to link shortener with redirection to HTTPS page)
After the transmission, the ESP32 sleeps until the next transmission
The Eddystone-URL profile has also added the ability to open a hyperlink directly in the main report.

For what purposes can a Beacon built on ESP32 be used?

Information about the shop, operation, distribution of opening hours, contacts, link to the e-shop

Information panels on castles, chateaux, museums or open-air museums for each building

Mobile portable Beacon broadcast advertising for operation (thanks to the size it can be placed in a purse or watch [ESP32-PICO-D4])

Beacon in the car - dissemination of information about the VIN number of the vehicle, battery voltage, registration number, mileage

Internal navigation system to improve orientation

Implementation into own application with client-side conversion of distance to Beacon based on received signal power

BLE Beacon - ESP32 - Eddystone TLM / URL

One of the most commonly used TCP based protocols in IoT is the MQTT protocol. This protocol is easy to use. Its strengths are in machine to machine communication (with low data complexity and minimal response). The MQTT protocol recognizes two network entities. 

Information channel that the client subscribes or publishes to. Topics are most often tied to specific data that the client collects e.g. temperature and humidity. As the topic is hierachical, it is possible to customize the topic to a specific location. For example:

apartment / living_room / window_server_temperature.

Topics are case, but also character sensitive (watch out for spaces, backslashes). Another (or even the same) device can subscribe to the topic and perform an action based on the information (values) read.

Topics can be used for a number of scenarios from data recording (temperature, humidity) it can also be used to record and distribute current states (light status, thermostat status [ON / OFF]). Subscribed clients always have the up-to-date information on the topic when changes are published.

A service that obtains messages from clients and distributes them to other clients (who subscribed to the relevant topic). Brokers enable communication, ensuring reliable delivery of the latest messages. Clients never communicate directly with each other.

The most common MQTT Broker for personal use (in a LAN network, in a smart home) is Mosquitto. This Broker is one of the most popular, used mainly in home automation systems - Hass.io or Domoticz.

After messages are delivered to all known clients, nothing is retained by the broker. However, if a client publishes a message to a topic with a retain flag set to True, then the message is stored. New clients receive this Last Good Message upon subscription.

The disadvantage of the Broker is that it is a physical device (or software emulated) and so most developers and IoT Engineers reach for a cloud solution, at least for testing purposes. The most famous are Google IoT Cloud, IBM Watson, Azure IoT and IoT Guru Live. These cloud MQTT servers are platform-specific, often require a login, an account link, and are limited to a fixed number of devices, and fixed number of topics.

Often a microcontroller with a simple network stack that allows the device to connect to the Broker. The device sends (publishes) data to the network on the relevant topic. The device can also obtain data from the Broker - by subscribing to the relevant Topic. Hobbyist and Professional Programming of microcontrollers can be done in the Arduino IDE environment. Board support is installed in the environment by importing a package in the board manager. Support can be extended to Espressif based platforms such as the ESP8266 on the development board NodeMCU v3 Lolin and ESP32

IoT device specific client software connects to the MQTT server using a socket connection through WiFi. Libraries are available to connect to the WiFi network and establish HTTP connections.

Using the PubSubClient library, it is possible to connect to MQTT Broker on port 1883 - unsecured port

Using WiFiClientSecure library, it is possible to connect to secure MQTT port 8883 and then send a topic to the Broker or subscribe to one.

The client can also be another user device, such as a computer, which can subscribe using a web based or desktop application. Such a device can also send status updates, and other data to the network e.g. notify that a computer is turned on or the status of connectivity to the Internet.

There are freely available MQTT Brokers that are anonymously usable. After signing up to such a service, a user can send (Publish) the topics they want and also subscribe to topics.

Since free brokers generally do not require authentication, the Broker is shared by all users, it is possible to subscribe to any available topic from another device (with another user's data). Therefore, these broker are not suitable for secure implementations. They are suitable for testing and development purposes and mastering the functionality of communication with MQTT Brokers, and the related message types.

Example for Espressif boards on Anonymous Broker

The first step is to find information about the connection settings for connection with the MQTT Broker. With unencrypted connections, use the standard MQTT protocol 1883 and the MQTT Broker address. Add directives for the compiler (respectively for the preprocessor) to the codes, which, depending on the selected development board, dynamically assigns a linked library, which is used by the given microcontroller.

The source codes for ESP8266 and ESP32 are thus identical and fully transferable between these platforms. The program contains a counter that is incremented (so that the sent value is visibly changed). Data is sent to the topic: esp32 / counter every 10 seconds. The microcontroller also subscribes (but does not have to) subscribe to the same topic. This way you can check if the value in a given topic is changing.

This topic is then accessed by any device that is connected to the Broker and subscribes to esp32 / counter. If the client wants to subscribe to all topics that are available on MQTT Broker, it chooses topic #. The # grid character is similar to that used * in query languages (all).

As this MQTT Broker is public, you can see and modify data in all topics. This poses a safety risk, as temperature-based control systems can be dependent on the MQTT. For this reason, this MQTT Broker is mainly used for testing and development purposes. It is not suitable for use with a household connection to this MQTT Broker, as anyone can read your data or modify it in individual topics.

For testing, confirm that the Broker is fast, the response time is small, at the level of 30 to 50 ms with the processing of received data from the subscribed topic (time measured before the call and after the end of the function).

Al Almaktoum

Blog

Building this site with React / Next.js and Sanity

BLE Beacon - ESP32 - Eddystone TLM / URL

About MQTT and IoT Industries