Devices - Revision history

Scott.Radka: /* 7.1 Device Types */

2019-07-09T01:18:38Z

‎7.1 Device Types

Scott.Radka at 01:18, 9 July 2019

2019-07-09T01:18:04Z

Scott.Radka: Created page with ": ===7.1 Device Types=== The DRMS has has significant enhancements allowing the support of specific smart devices. Currently the DRMS support three different device types: *..."

2019-07-02T02:39:11Z

Created page with ": ===7.1 Device Types=== The DRMS has has significant enhancements allowing the support of specific smart devices. Currently the DRMS support three different device types: *..."

New page

:
===7.1 Device Types===
The DRMS has has significant enhancements allowing the support of specific smart devices. Currently the DRMS support three different device types:
* OpenADR 2.0b and 2.0a compliant devices
* Future Point
* Ambi Climate

'''OpenADR Devices'''These devices follow the OpenADR specification (https://www.openadr.org/specification). The server implements an OpenADR VTN capable of interacting with VENs in both Push and Pull modes over both HTTP and XMPP transports. They support two-way communication with the VTN and are capable of acknowledging the receipt of an event.In the majority of the cases, OpenADR devices will be configured to use the OpenADR Poll service and will poll the VTN at regular intervals.Some OpenADR devices are smart enough to send back reports that the VTN will store for further analysis. '''Future Point Devices'''''''''These devices use the DREDs protocol. Our application connects to them via a set of API endpoints that were created for us on the Future Point / Without Wires cloud service. Since DREDs itself is not an internet based protocol; our application cannot use it directly. '''Ambi Climate Devices'''''''''These devices are controlled via the Ambi Climate cloud service. Ambi Climate has created a set of specific endpoints for our application on their API. We have an authorization token which only grants access to these endpoints. Once per 5 minutes: Ambi Climate also pushes a status update to one of our endpoints. We use this status update to determine which devices can be treated as online, and store the additional information for future use.

Once a device has been created in the system a green dot will appear next to device name. By hovering over the green dot, you will be able to determine the last time the device had communicated with the DRMS. If the dot next to the device name is ever hollow that means that the device is no longer communicating with the DRMS. If this does occur please contact the Demand Response team via the contacts in the ‘Support’ tab.
===7.2 Creating Devices===
When creating a device associated with a site the information that is needed is:
* The devices name
* The Device Type
* The Devices VEN ID
* DRM Capacities at different levels

@@ Line 14: / Line 14: @@
 :These devices are controlled via the Ambi Climate cloud service. Ambi Climate has created a set of specific endpoints for our application on their API. We have an authorization token which only grants access to these endpoints. Once per 5 minutes: Ambi Climate also pushes a status update to one of our endpoints. We use this status update to determine which devices can be treated as online, and store the additional information for future use.
+:
-Once a device has been created in the system a green dot will appear next to device name. By hovering over the green dot, you will be able to determine the last time the device had communicated with the DRMS. If the dot next to the device name is ever hollow that means that the device is no longer communicating with the DRMS. If this does occur please contact the Demand Response team via the contacts in the ‘Support’ tab.
+:Once a device has been created in the system a green dot will appear next to device name. By hovering over the green dot, you will be able to determine the last time the device had communicated with the DRMS. If the dot next to the device name is ever hollow that means that the device is no longer communicating with the DRMS. If this does occur please contact the Demand Response team via the contacts in the ‘Support’ tab.
 =====7.2 Creating Devices=====
 When creating a device associated with a site the information that is needed is:

@@ Line 1: / Line 1: @@
+:
-===7.1 Device Types===
+=====7.1 Device Types=====
 The DRMS has has significant enhancements allowing the support of specific smart devices. Currently the DRMS support three different device types:
 * OpenADR 2.0b and 2.0a compliant devices
 * Future Point
 * Ambi Climate
-−
+:
-'''OpenADR Devices'''These devices follow the OpenADR specification (https://www.openadr.org/specification). The server implements an OpenADR VTN capable of interacting with VENs in both Push and Pull modes over both HTTP and XMPP transports. They support two-way communication with the VTN and are capable of acknowledging the receipt of an event.In the majority of the cases, OpenADR devices will be configured to use the OpenADR Poll service and will poll the VTN at regular intervals.Some OpenADR devices are smart enough to send back reports that the VTN will store for further analysis. '''Future Point Devices'''''''''These devices use the DREDs protocol. Our application connects to them via a set of API endpoints that were created for us on the Future Point / Without Wires cloud service. Since DREDs itself is not an internet based protocol; our application cannot use it directly. '''Ambi Climate Devices'''''''''These devices are controlled via the Ambi Climate cloud service. Ambi Climate has created a set of specific endpoints for our application on their API. We have an authorization token which only grants access to these endpoints. Once per 5 minutes: Ambi Climate also pushes a status update to one of our endpoints. We use this status update to determine which devices can be treated as online, and store the additional information for future use.
+'''OpenADR Devices'''
+:These devices follow the OpenADR specification (https://www.openadr.org/specification). The server implements an OpenADR VTN capable of interacting with VENs in both Push and Pull modes over both HTTP and XMPP transports. They support two-way communication with the VTN and are capable of acknowledging the receipt of an event.In the majority of the cases, OpenADR devices will be configured to use the OpenADR Poll service and will poll the VTN at regular intervals.Some OpenADR devices are smart enough to send back reports that the VTN will store for further analysis.
 Once a device has been created in the system a green dot will appear next to device name. By hovering over the green dot, you will be able to determine the last time the device had communicated with the DRMS. If the dot next to the device name is ever hollow that means that the device is no longer communicating with the DRMS. If this does occur please contact the Demand Response team via the contacts in the ‘Support’ tab.
-===7.2 Creating Devices===
+=====7.2 Creating Devices=====
 When creating a device associated with a site the information that is needed is:
 * The devices name
@@ Line 15: / Line 21: @@
 * The Devices VEN ID
 * DRM Capacities at different levels