文件列表:

Dockerfile (1646, 2019-10-18)
Jenkinsfile (1183, 2019-10-18)
compose (177, 2019-10-18)
config/ (0, 2019-10-18)
config/entrypoint-interface.sh (319, 2019-10-18)
config/entrypoint-worker.sh (140, 2019-10-18)
config/local.env (154, 2019-10-18)
config/nginx/ (0, 2019-10-18)
config/nginx/local.conf (1466, 2019-10-18)
config/nginx/production.conf (2775, 2019-10-18)
config/production.env (161, 2019-10-18)
docker-compose.yml (810, 2019-10-18)
leaves/ (0, 2019-10-18)
leaves/Arduino Leaf/ (0, 2019-10-18)
leaves/Arduino Leaf/Device.cpp (808, 2019-10-18)
leaves/Arduino Leaf/Device.h (2207, 2019-10-18)
leaves/Arduino Leaf/Leaf.cpp (4674, 2019-10-18)
leaves/Arduino Leaf/Leaf.h (1085, 2019-10-18)
leaves/DemoBlinkLeaf/ (0, 2019-10-18)
leaves/DemoBlinkLeaf/DemoBlinkLeaf.ino (3095, 2019-10-18)
leaves/DemoLampLeaf/ (0, 2019-10-18)
leaves/DemoLampLeaf/DemoLampLeaf/ (0, 2019-10-18)
leaves/DemoLampLeaf/DemoLampLeaf/DemoLampLeaf.ino (2387, 2019-10-18)
leaves/DemoLedLeaf/ (0, 2019-10-18)
leaves/DemoLedLeaf/DemoLedLeaf.ino (1871, 2019-10-18)
leaves/DemoTempSensor/ (0, 2019-10-18)
leaves/DemoTempSensor/DemoTempSensor.ino (1999, 2019-10-18)
leaves/Leaf.js (7871, 2019-10-18)
leaves/PyLeaf/ (0, 2019-10-18)
leaves/PyLeaf/PyLeaf.py (10447, 2019-10-18)
leaves/PyLeaf/setup.py (319, 2019-10-18)
local-compose.yml (666, 2019-10-18)
production-compose.yml (1153, 2019-10-18)
requirements.in (246, 2019-10-18)
requirements.txt (1848, 2019-10-18)
run_tests.sh (205, 2019-10-18)
sentinel/ (0, 2019-10-18)
sentinel/.babelrc (34, 2019-10-18)
... ...

# Sentinel IOT [](http://builder.dooher.net/job/sentinel-iot/job/master/) ## Sentinel Hub  **The Sentinel Hub** is the main dashboard which allows the user to visualize and control all of their connected devices. Users can drag and drop arrows between individual **leaves**, which are groups of devices and sensors, in order to create a connection between two or more leaves. This connection can serve different functions including a **subscription** which enables a leaf to routinely update another on its status. Another type of connection is a **conditional connection**, which specifies how one leaf responds to changes in the status of another leaf. ## Sentinel Leaves A **leaf** is a discrete group of one or more devices which interacts with the Sentinel Hub. A leaf consists of a variety of sensors and outputs which can take a variety of forms and data types (see [API Section](#api)). When a leaf sensor updates, it will report to the backend in one of three options: instantly, periodically (e.g. only once a second), or only when requested. ### Arduino Leaves This project will come with a Arduino Library that allows you to easily implement the Leaf API for your Arduino IoT device. See more on the [Arduino](arduino) page. ### Software leaves Leaves can also be software defined rather than existing as a physical device. For example, a user may want to have a leaf which checks the weather from a website and reports it to your thermostat to change the temperature. ## The Sentinel API The Sentinel API enables developers to set up a Sentinel Hub and easily configure and connect leaves. ### WebSockets WebSockets support a more dynamic interface for interacting with leaves. Simply connect to your Sentinel Hub and start sending the messages defined in the **Leaf Messages** section below. ### HTTP Interface A Sentinel Hub contains a REST API to access and change leaves, conditions, devices and options. | Name | HTTP Methods Supported | URL | Notes | Query Parameters | | ---- | ---------------------- | --- | ----- | ---------------- | | List Leaves | GET | https://sentinel.iot/hub_id/leaves/ | None | None | | View Leaf | GET | https://sentinel.iot/hub_id/leaves/uuid | None | None | | List Devices | GET | https://sentinel.iot/hub_id/uuid/devices | None | None | | View Device | GET, POST | https://sentinel.iot/hub_id/leaves/uuid/devices/name | Post only allowed for output devices | value: new value of device (POST only) | | List Conditons | GET | https://sentinel.iot/hub/hub_id/conditions | None | None | | View Conditon | GET, PUT, DELETE | https://sentinel.iot/hub/hub_id/conditions/name | PUT overrides an existing condition or creates one | predicate, action (PUT only; See [Conditions](#conditions) for format) | | List Datastores | GET | https://sentinel.iot/hub/hub_id/datastores | None | None | | View Datastore | GET, PUT, POST, DELETE | https://sentinel.iot/hub/hub_id/datastores/name | None | PUT: name, format
POST/PUT: value | #### REST API Format Examples Conditions: ```JSON { "name": "lamp1_on", "predicate": ["=", ["f7bfd74c-a876-41da-ab37-6c5752e94a25", "rfid"], 3032042781.0], "action": { "action_type": "SET", "target": "b549b7b9-ca65-4552-9e72-3e07dec02568", "device": "left_lamp_on", "format": "bool", "value": true } } ``` Leaves: ```JSON { "uuid": "f7bfd74c-a876-41da-ab37-6c5752e94a25", "name": "RFID Scanner", "model": "rfid01", "api_version": "0.1.0", "is_connected": false, "devices": [ { "name": "rfid", "format": "number", "value": 3032042781.0, "mode": "IN" } ] } ``` Datastores: ```JSON { "name": "is_home", "format": "bool", "value": "false" } ``` ### Leaf Messages These are the messages a leaf will send to a Sentinel Hub. They are JSON messages in the following form. ``` { "type":"[TYPE]", "uuid":"[UUID]", "[ATTR1]":"[ATTR1_VALUE]", "[ATTR2]":"[ATTR2_VALUE]", ... } ``` Only the type and uuid attributes are required, all other attributes are specific to the type of message you are trying to send. Type defines the type of message being sent. UUID is a [unique identifier](https://en.wikipedia.org/wiki/Universally_unique_identifier) for each leaf. | Name | TYPE | Additional Attributes | Description | Required Uses | | ---- | ---- | ---------- | ----------- | ---- | | Name | NAME | name: english name of the node | The name of the device | After receiving a GET_NAME or SET_NAME message | | Config | CONFIG | name: english name of leaf
model: model number of the leaf
api-version: version of api| Configuration of the device. Used to register a leaf with a hub. | After connecting to a hub or receiving a GET_CONFIG message| | Device Status | DEVICE_STATUS | device: name of device
status: status of device | The status for a device will either be it's sensor value (for input devices) or it's current state (for output devices) | After receiving a SET_OUTPUT or GET_DEVICE command | | Unknown Device | UNKNOWN_DEVICE | device: name of unknown device | Used to respond to a request regarding a device that the leaf is not configured to accept | After recieving an invalid SET_OPTION or GET_OPTION command, send one for all devices after getting DEVICE_LIST message | | List Options | OPTION_LIST | device: name of device list is for
options: list of all options and their value types | This command lists all the options available for a particular device. For leaf-wide options, the device will simply be 'leaf' | After receiving a LIST_OPTIONS message | | Invalid Option | INVALID_OPTION | device: name of device
option: name of unknown or invalid option | Used to respond to a request regarding an option that a device does not have | After receiving an invalid SET_OUTPUT or GET_DEVICE command | | Option Update | OPTION | device: name of device
option: name of option
value: current setting of option | Gives the current value of an option for a particular device. For leaf-wide options the device will be "leaf". | After recieving a SET_OPTION or GET_OPTION message | | Invalid Value | INVALID_VALUE | device: name of device
mode: option/device
value: the value that was invalid | Used to respond to a request regarding an improper value for an option or output | After receiving an invalid SET_OUTPUT or SET_OPTION command | | Subscribe | SUBSCRIBE | sub_uuid: uuid of leaf to subscribe to
sub_device: device to subscribe to | Creates a subscription so that whenever a device or leaf is updated, the new status is sent to this leaf | None | | Unsubscribe | UNSUBSCRIBE | sub_uuid: uuid of leaf to unsubscribe from
sub_device: device to unsubscribe from | Removes a subscription so you no longer receive updates from a device | None | | Create Condition | CONDITION_CREATE | name: name of condition to create, predicate: predicate condition has to satisfy, action: what the condition does when the predicate is *true* | Creates a condition, deleting an existing condition with the same name if necessary | None | | Delete Condition | CONDITION_DELETE | name: name of condition to delete | Deletes a condition | None | | Create Datastore | DATASTORE_CREATE | name: name of datastore to create, format: data format of datastore, value: initial value for the datastore | Creates a datastore of a certain data type with an initial value | None | | Get Datastore | DATASTORE_GET | name: name of datastore to get value of | attempt to get the current value of a datastore | None | | Update Datastore | DATASTORE_SET | name: name of datastore to create, value: new value for the datastore | Updates the current value of a datastore | None | | Delete Datastore | DATASTORE_CREATE | name: name of datastore to create, format: data format of datastore, value: initial value for the datastore | Deletes the specified datastore | None | #### Devices This section deals with the various formats through which a device can report or receive data. ##### Device Config When sending a list of devices each element of the list should be in the following format: ``` { "device":"[DEVICE_NAME]", "format":"[FORMAT_TYPE]", "mode":"[IN|OUT]", } ``` The formats are listed below and mode must take the value of either IN or OUT. ##### Status Updates When a device reports its status to a Sentinel Hub it will submit a message that follows the following format. ``` { "type":"DEVICE_STATUS", "uuid":"[UUID]", "device":"[DEVICE_NAME]" "format":"[FORMAT_TYPE]", "value":"[VALUE]", "[ATTR1]":"[ATTR1_VALUE]", "[ATTR2]":"[ATTR2_VALUE]", ... } ``` ##### Data formats These are all of the currently supported data formats for leaf devices. If an unrecognized format is reported, it will default to being interpreted as a String. | Name | JSON Representation | Description | Example | | ---- | ------------------- | ----------- | ------- | | Number | "number" | A number | {
"format":"number",
"value":12345132
} | | Number with Units | "number+units" | A number and some units | {
"format":"number+units",
"value":12345132,
units:"°C"
} | | String | "string" | A text string | {
"format":"string",
"value":132123
} | | Boolean | "bool" | A true/false value (0, 1, true, or false)| {
"format":"bool",
"value":true
} | ##### Options Options are reported to the server in the following manner: ``` { "option":"[OPTION_NAME]", "format":"[DATA_FORMAT]", "value":"[VALUE]", } ``` When you send a list of options, simply send a JSON list containing multiple options in this format. ### Hub Messages These are the messages your leaf must receive and process in order to properly interact with the Sentinel IoT hub it is connected to. The format is as follows: ``` { "type":"[OPTION_NAME]", "[ATTR1]":"[ATTR1_VALUE]", "[ATTR2]":"[ATTR2_VALUE]", ... } ``` | Name | TYPE | Additional Attributes | Description | Required Processing | | ---- | ---- | ---------- | ----------- | ---- | | Set Name | SET_NAME | name: new english name of the node | Changes the default name of the leaf | The leaf should update its name and send a NAME message | | Get Name | GET_NAME | None | Requests the name of the leaf | The leaf should send a NAME message | | Get Configuration | GET_CONFIG | None| Requests configuration of device, usually sent on initial connection. | Send a CONFIG message| | Configuration Complete | CONFIG_COMPLETE | None | Sent when configuration of your leaf is completed | None, though you want to wait until you receive this before sending any messages to the hub | | List Devices | LIST_DEVICES | None | Requests the current status of all sensors (see [Devices](#devices) for the form of each device) | Send a DEVICE_STATUS message for all devices | | Get Device | GET_DEVICE | device: name of device | The status for a device will either be it's sensor value (for input devices) or it's current state (for output devices) | Locate device and send DEVICE_STATUS or UNKNOWN_DEVICE message | | Set Output | SET_OUTPUT | device: name of device
value: new value of output| Changes the output state, if valid, of device | Change the device's output value (or send INVALID_VALUE) and send a DEVICE_STATUS message | | Change Output | CHANGE_OUTPUT | device: name of device
value: new value to add to device's current number | Changes an output device by a certain amount (device must be either a number device or a units device) | Change the device's output value (or send INVALID_VALUE) and send a DEVICE_STATUS message | | List Options | LIST_OPTIONS | device: name of device list is for | This command lists all the options available for a particular device. For leaf-wide options, the device will simply be 'leaf' | Send a OPTION_LIST message | | Get Option | GET_OPTION | device: name of device
option: name of option | Requests the current value of an option for a particular device. For leaf-wide options the device will be "leaf". | Send an OPTION message or a UNKNOWN_DEVICE, UNKNOWN_OPTION | | Set Option | SET_OPTION | device: name of device
option: name of option
value: new setting of option | Changes the current value of an option for a particular device. For leaf-wide options the device will be "leaf". | Change option and send OPTION message if sucessful else send UNKNOWN_DEVICE, UNKNOWN_OPTION, or INVALID_VALUE | | Subscription Update | SUBSCRIPTION_UPDATE | sub_uuid: uuid of leaf you subscribed to
sub_device: name of device you subscribed to
message: message from your subscription (device_status, etc) | None | | Permission Denied | PERMISSION_DENIED | request: request type that was denied,
name/uuid/device (optional): identifier of denied resource | Given when the leaf tries to access something it does not have permission to | None | | Datastore Created | DATASTORE_CREATED | name: name of datastore
format: data format of datastore | Informs the user a datastore has been successfully created | None | | Datastore Deleted | DATASTORE_DELETED | name: name of datastore | Informs the user a datastore has been successfully deleted | None | | Invalid Device | INVALID_DEVICE | leaf: uuid of leaf
device: name of device that couldn't be accessed
reason: reason why it couldn't be accessed | Sent back to a device when it tries to access a device in an invalid way (such as in creating a condition) | None | | Invalid Leaf | INVALID_LEAF | leaf: uuid of leaf that couldn't be accessed
reason: reason why it couldn't be accessed | Sent back to a device when it tries to access a leaf in an invalid way (such as in creating a condition) | None | ## Sentinel Backend The Sentinel Backend processes all of features and interactions defined above. In the current version of Sentinel IoT, the backend is implemented in Django using Django Channels and WebSockets. ### Conditions Conditions in Sentinel have two main components: a predicate and an action. The predicate is the "if" part of the condition; it is some expression that will evaluate to either *true* or *false*. The action is what will happen if the predicate evaluates to *true*. To create a condition, a leaf can send a message as follows: ``` { "type": "CONDITION_CREATE", "name": "[name of condition]", "predicate": [predicate], "action": { "action_type": "[Action Type]", "target": "[Target of action]", "device": "[Device to target]", "value": "[Value to use in action]" } } ``` #### Predicates Predicates are given in [Polish Notation](https://en.wikipedia.org/wiki/Polish_notation) using lists as brackets. ##### Operations An operator predicate can compare two values. These values can either be device values or literals. See below for a few examples. ``` ['[Operator]', ['[Leaf UUID]', '[Device Name']], [Literal or another [uuid, device] pairing]] ``` | Name | Operator | | --------- | ---- | | Equals | = | | Does not equals | != | | Greater than | > | | Less than | < | | Greater than or equal to | >= | | Less than or equal to | <= | Examples: Device and literal: ``` ['=', ['06202ef5-bec3-46d1-b39c-b88910a0ab07', 'sensor_1'], 320212.5] ``` Two devices: ``` ['>', ['06202ef5-bec3-46d1-b39c-b88910a0ab07', 'sensor_1'], ['230025f0-9350-4578-9b95-44cb188e70a3', 'sensor_2']] ``` ##### Connectors You can connect two or more predicates together using the boolean connectors in the table below. These can be nested to an arbitrary depth. The format is as follows:
Binary connector: ``` ['[Connector]', [Predicate1], [Predicate 2]] ``` Unary connector: ``` ['[Connector]', [Predicate]] ``` | Connector | Type | | --------- | ---- | | AND | Binary | | OR | Binary | | XOR | Binary | | NOT | Unary | Examples: Unary: ``` ['NOT', ['>', ['ce505754-341c-48f8-b7f2-2626041df01c', 'sensor_1'], 0]] ``` Binary: ``` ['AND', ['>', ['ce505754-341c-48f8-b7f2-2626041df01c', 'sensor_1'], 0], ['<', ['datastore', '313123'], -123]] ``` Nested: ``` ['NOT', ['XOR', ['>', ['ce505754-341c-48f8-b7f2-2626041df01c', 'sensor_1'], 0], ['<', ['datastore', '313123'], -123]]] ``` #### Actions An action takes the following form: ``` { 'action_type': ['SET' or 'CHANGE'], 'target': [uuid of leaf to perform action on], 'device': [device of leaf to perform action on], 'value': [value to set/change device by] } ``` #### Examples This is a full example of the creation of a conditon: ``` { 'type': 'CONDITION_CREATE', 'uuid': '230025f0-9350-4578-9b95-44cb188e70a3', 'predicate':['AND', ['NOT', ['=', ['ce505754-341c-48f8-b7f2-2626041df01c', 'sensor_1'], 1323112], ['=', ['2a11abdc-be9e-4646-96f5-100ee55211e7', 'sensor_2'], 312312]]], 'action': { 'action_type': 'SET', 'target': '2a11abdc-be9e-4646-96f5-100ee55211e7', 'device': 'output_sensor', 'value': 33790 } } ``` ### Actions Actions specify what happens when a predicate is satisfied. Invalid or mismatched types will again cause the entire condition to be rejected. In addition, if an action targets a device, it must be an output device or the condition will be rejected. Valid actions are as follows: | Action Type | Description | | ------ | ----------- | | SET | Set an output device to a specific output value | | CHANGE | Change a number or unit device to by a specific offset | ### Condition Examples This condition would tell a leaf configured to open a door to open if a valid person scans in on another leaf configured to be a RFID reader. ``` { "type":"CONDITION_CREATE", "name":"open_door", "predicate":['OR', ["=", ["474a3f28-bb3e-478c-b723-1f7eb6b990c3", "rfid"], 303205852], ["=", ["474a3f28-bb3e-478c-b723-1f7eb6b990c3", "rfid"], 303204392]], "action": { "action_type":"SET", "target":"894c2698-0d0d-40cb-ab4d-2abad4d5f287", "device":"door_open", "value":true } } ```

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：