@@ -381,7 +381,8 @@ docker run -it --rm --name mqtt-subscriber \
381
381
382
382
The terminal will then be ready to receive events
383
383
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
385
386
> completed the next step.
386
387
387
388
# ## Start an MQTT Publisher (2️⃣nd Terminal)
@@ -525,7 +526,8 @@ tutorial as we will be provisioning each device separately.
525
526
This example provisions an anonymous group of devices. It tells the IoT Agent that a series of devices will be
526
527
communicating by sending device measures over the `/ul/4jggokgpepnvsb2uv4s40d59ov` **topic**
527
528
528
- > ** Note** Measures and commands are sent over different MQTT topics:
529
+ > [! NOTE]
530
+ > Measures and commands are sent over different MQTT topics:
529
531
>
530
532
> - _Measures_ are sent on the ` /< protocol> /< api-key> /< device-id> /attrs` topic
531
533
> - _Commands_ are sent on the ` /< api-key> /< device-id> /cmd` topic
@@ -576,7 +578,8 @@ Three types of measurement attributes can be provisioned:
576
578
- ` static_attributes ` are as the name suggests static data about the device (such as relationships) passed on to the
577
579
context broker.
578
580
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
580
583
> be defined within the provisioning service rather than individually.
581
584
582
585
#### 3️⃣ Request:
@@ -635,7 +638,8 @@ The **topic** must be in the following form:
635
638
/<protocol>/<api-key>/<device-id>/attrs
636
639
```
637
640
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
639
643
> between the Motion Sensor and an IoT Agent, a similar dummy HTTP request was sent to update the ` count ` value. This
640
644
> time the IoT Agent is configured to listen to MQTT topics, and we need to post a dummy message to an MQTT topic.
641
645
0 commit comments