nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 00:45:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 107.md

Browse Source
This commit is contained in:
Vlad Stan 2023-10-25 12:36:08 +03:00 committed by GitHub
parent 05a988973a
commit 9f68e07a6d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
107.md
View File

@ -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]