From 9f68e07a6dbe9fdf3d3c65ed2c7111d3ebad3065 Mon Sep 17 00:00:00 2001 From: Vlad Stan Date: Wed, 25 Oct 2023 12:36:08 +0300 Subject: [PATCH] Update 107.md --- 107.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/107.md b/107.md index fbf13e7..dc5d166 100644 --- a/107.md +++ b/107.md @@ -42,7 +42,9 @@ A `user` can publish these event kinds: The content of events can be transmitted in clear text (for public data) or as [NIP-59 Gift Wrap](https://github.com/staab/nips/blob/NIP-59/59.md). + ### Configure Device Event (`kind: 30107`) +--- This message is sent by an admin `user` to a `device`. The `device` saves the config locally and then uses it. **Event Content**: @@ -76,8 +78,8 @@ This message is sent by an admin `user` to a `device`. The `device` saves the co ``` - the `d` tag is required, its value MUST be the same as the pubkey of the `device`. - ### Intent Events (`kind: 8000`) +--- Intent Events represent different actions that can be performed on a device. These actions can be triggered by a `user` or by another `device`. The content of the event is a `JSON` array representing the data type and the data value as specified in [NIP-91 Event Kinds](https://github.com/nostr-protocol/nips/blob/iot/91.md#event-kinds) @@ -100,6 +102,7 @@ Example that turns on a device and sets the temperature to `20.9` degrees Celsiu ### Data Events (`kind: 8001 - 8999`) +--- Data Events represent data published by `device`(s). The `kind` of the event and the `content` must follow ths specification from [NIP-91 Event Kinds](https://github.com/nostr-protocol/nips/blob/iot/91.md#event-kinds). > [!NOTE]