From 80b56485a294fb267992642cd1b0165b66bc8165 Mon Sep 17 00:00:00 2001
From: Vlad Stan <stan.v.vlad@gmail.com>
Date: Tue, 24 Oct 2023 16:28:19 +0300
Subject: [PATCH] Update 107.md

---
 107.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/107.md b/107.md
index 726092e..7c8de00 100644
--- a/107.md
+++ b/107.md
@@ -53,19 +53,21 @@ This message is sent by a `user` to a `device`. The `device` saves the config lo
 ```json
 {
     "type": 0,
-    "admin_pubkeys": [ [<String (optional), admin user public-key>]],
     "name": <String (optional), set a name for the device>,
     "description": <String (optional), device description>,
     "categories":[ <String (optional), device category, such as 'boiler'>],
-    "send_to_pubkeys":[ [<String (optional), user public-key>]],
+    "admin_pubkeys": [ [<String (optional), admin user public-key>]],
+    "publish_to_pubkeys":[ [<String (optional), user public-key>]],
     "intents_from_pubkeys":[ [<String (optional), user public-key>]],
+    "publish_on_change": <Boolean (optional, default `true`), publish event each time a sensor value changes>,
+    "publish_interval": <Integer (optional), publish the sensor value at regular intervals (regardless the value changes or not). The value is in `millisecods`.>
 }
 ```
 
 | Field | Description |
 |---|---|
 | `admin_pubkeys` | List of public keys that are allowed to configure this device.<br>A fresh/blank device will not have this value, so the first received `"type: 0"` should set it.<br/> The `admin_pubkeys` implicitly have the `actions_from_pubkeys` permissions. |
-| `send_to_pubkeys` | List of public keys to which events are published. |
+| `publish_to_pubkeys` | List of public keys to which events are published. |
 | `actions_from_pubkeys` | List of public keys that are allowed to trigger an action on this device.<br/> The `admin_pubkeys` implicitly have the `actions_from_pubkeys` permissions. |
 
 ### Event: Update a `device`