You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/multicast/multicast.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ This sequence diagram describes the flow from the user to the Chirpstack Applica
29
29
Sending downlink payload
30
30
-------------------------
31
31
32
-
When the multicast-group is created it's possible to send a downlink payload to the group of devices. This is done by navigating to the details-page of the multicast-group, and from here you have to choose a specific port and a payload that you wish to send to the devices in the Multicast-group.
32
+
When the multicast-group is created it's possible to send a downlink payload to the group of devices. This is done by navigating to the detailspage of the multicast-group, and from here you have to choose a specific port and a payload that you wish to send to the devices in the Multicast-group.
33
33
34
34
The downlink payload is sent using Chirpstack which also has the multicast-group with the devices from OS2IoT.
35
35
@@ -38,7 +38,7 @@ Explanation of properties
38
38
39
39
A very short explanation of some of the properties that needs to be fulfilled when creating a multicast-group:
40
40
41
-
**Multicast address:** An address that defines the multicast-group. Has to be a 8-character hex value.
41
+
**Multicast address:** An address that defines the multicast-group. Has to be an 8-character hex value.
42
42
43
43
**Application Session Key:** An application session key used to encrypt the payloads that are send to the multicast-group. Has to be a 32-character hex value.
0 commit comments