Skip to content

Commit 97f29a5

Browse files
committed
Add notes
1 parent ad9b37c commit 97f29a5

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

README.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -381,7 +381,8 @@ docker run -it --rm --name mqtt-subscriber \
381381

382382
The terminal will then be ready to receive events
383383

384-
> **Note:** There is no change on whilst running this command. The on screen output will only respond once you have
384+
> [!NOTE]
385+
> There is no change on whilst running this command. The on screen output will only respond once you have
385386
> completed the next step.
386387

387388
### Start an MQTT Publisher (2️⃣nd Terminal)
@@ -525,7 +526,8 @@ tutorial as we will be provisioning each device separately.
525526
This example provisions an anonymous group of devices. It tells the IoT Agent that a series of devices will be
526527
communicating by sending device measures over the `/ul/4jggokgpepnvsb2uv4s40d59ov` **topic**
527528
528-
> **Note** Measures and commands are sent over different MQTT topics:
529+
> [!NOTE]
530+
> Measures and commands are sent over different MQTT topics:
529531
>
530532
> - _Measures_ are sent on the `/<protocol>/<api-key>/<device-id>/attrs` topic
531533
> - _Commands_ are sent on the `/<api-key>/<device-id>/cmd` topic
@@ -576,7 +578,8 @@ Three types of measurement attributes can be provisioned:
576578
- `static_attributes` are as the name suggests static data about the device (such as relationships) passed on to the
577579
context broker.
578580

579-
> **Note**: in the case where individual `id`s are not required, or aggregated data is sufficient the `attributes` can
581+
> [!NOTE]
582+
> in the case where individual `id`s are not required, or aggregated data is sufficient the `attributes` can
580583
> be defined within the provisioning service rather than individually.
581584
582585
#### 3️⃣ Request:
@@ -635,7 +638,8 @@ The **topic** must be in the following form:
635638
/<protocol>/<api-key>/<device-id>/attrs
636639
```
637640

638-
> **Note** In the [previous tutorial](https://github.com/FIWARE/tutorials.IoT-Agent), when testing HTTP connectivity
641+
> [!NOTE]
642+
> In the [previous tutorial](https://github.com/FIWARE/tutorials.IoT-Agent), when testing HTTP connectivity
639643
> between the Motion Sensor and an IoT Agent, a similar dummy HTTP request was sent to update the `count` value. This
640644
> time the IoT Agent is configured to listen to MQTT topics, and we need to post a dummy message to an MQTT topic.
641645

0 commit comments

Comments
 (0)