Connecting LC40 to FIWARE IoT

Transcription

1 Connecting LC40 to FIWARE IoT 1. What is FIWARE IoT FIWARE is an open software ecosystem provided by the FIWARE Community (htttp:// FIWARE exposes to developers Data Context elements or entities (JSON objects) with attributes and metadata with a uniform REST API (NGSI9/10). NGSI is now being adopted by more than 60 smartcities worldwide: Orion Context Broker is available at: FIWARE IoT is an opensource software stack aiming to bring Data-level interoperability to the complex salad of standards and protocols in the world of IoT today. FIWARE IoT is able to expose -by means of the Orion Context Broker componentall IoT devices information and commands using the Data Context API (NGSI). Any IoT standard or proprietary protocol can be connected to FIWARE via the IoT- Ultralight2.0/HTTP: Agent components. Currently FIWARE IoT is providing IoT-Agents for:

2 MQTT/TCP: //bit.ly/fiware_iot-ul20 LWM2M/CoAP: SIGFox Cloud: Additionally, any new standard or proprietary protocol might be implemented using this node.js IoT-Agent library: or this C++ library: 2. How to use LC40 with FIWARE LC40 can be integrated with the above-described FIWARE IoT ecosystems using the following IoT-Agent(s): Ultralight2.0/HTTP MQTT/TCP 3 Configuring LC40 with Ultralight2.0/HTTP IoT-Agent 3.1 Intro & Requirements First of all we need a FIWARE Context Broker available: Check FIWARE Context Broker version: GET Content-Type: application/json Fiware-Service: at4tests Fiware-ServicePath: / RESPONSE: 200 OK "orion": "version": "1.1.0", "uptime": "187 d, 5 h, 38 m, 57 s",

3 "git_hash": "d640ce9acf19af26ab649b1292df46e50aaee94e", "compile_time": "Tue May 3 11:56:34 CEST 2016", "compiled_by": "fermin", "compiled_in": "centollo" 3.2 Configuring LC40 to send data to FIWARE IoT TEST 1: CREATING AN IOT SERVICE (OPTIONAL) POST Content-Type: application/json Fiware-Service: e3t4tests Fiware-ServicePath: /e3tservicepath1 PAYLOAD: "services": [ "apikey": "apikey54321", "token": "token12345", "entity_type": "thing", "resource": "/iot/d" ] RESPONSE: 201: Created CHECK SERVICES GET Content-Type: application/json Fiware-Service: at4tests Fiware-ServicePath: /e3tservicepath1 RESPONSE: 200 OK "_id": "5847cfe2cf f7efdc", "subservice": "/e3tservicepath1", "service": "e3t4tests",

4 "type": "thing", "apikey": "apikey54321", "resource": "/iot/d", "internalattributes": [], "attributes": [], "lazy": [], "staticattributes": [], "commands": [], VIEW REGISTERED DEVICES (none now) GET content-type: application/json fiware-service: e3t4tests fiware-servicepath: /e3tservicepath1 RESPONSE: 200 OK "count": 0, "devices": [], TEST 2: REGISTER A HARDWARE DEVICE "int", POST Content-Type: application/json Fiware-Service: at4tests Fiware-ServicePath: /e3tservicepath1 PAYLOAD: "devices": [ "device_id": "LC40P1", "entity_name": "e3tentity_lc40p1", "entity_type": "thing", "protocol": "IoTA-UL", "timezone": "Europe/Madrid", "attributes": [ "object_id": "MD", "name": "mode", "object_id": "CN", "name": "connection", "type":

5 "int", "int", "object_id": "ST", "name": "status", "object_id": "DM", "name": "dimmer", "object_id": "PW", "name": "power", "object_id": "EN", "name": "energy", "object_id": "SW", "name": "switching_on", "type": "object_id": "ST", "name": "switch_on_time", "type": "object_id": "S1", "name": "sensor1", "type": "int" ], "commands": [ "name": "set_status", "type": "command", "value": "[Dev_ID]@set_status %s", "name": "set_dimmer", "type": "command", "value": "[Dev_ID]@set_dimmer %s" ], "static_attributes": [ "name": "att_name", "type": "string", "value": "value" ] ] RESPONSE 201: Created TEST 4: SEND MEASUREMENTS POST Content-Type: text/plain PAYLOAD: MD 1#CN 1#ST 0#DM 100#PW 0#EN 0#SW 0#ST 0#S1 10 RESPONSE: 200: OK (VOID)

6 3.3 Accessing LC40 data at FIWARE Context Broker TEST 5: READ MEASUREMENTS (OPTIONAL) GET Content-Type: application/json Fiware-Service: e3t4tests Fiware-ServicePath: /e3tservicepath1 RESPONSE 200: OK "id": "e3tentity_lc40p1", "type": "thing", "value": " T11:07:06.175Z",, "att_name": "type": "string", "value": "value", "value": " T11:07:06.175Z", "connection": "value": "1", "value": " T11:07:06.118Z", "dimmer": "value": "100", "value": " T11:07:06.132Z"

7 , "energy": "value": "0", "value": " T11:07:06.146Z", "mode": "value": "1", "value": " T11:07:06.106Z", "power": "value": "0", "value": " T11:07:06.139Z", "sensor1": "value": "10", "value": " T11:07:06.175Z", "set_dimmer_result": "type": "commandresult", "value": " ",, "set_dimmer_status": "type": "commandstatus",

8 "value": "UNKNOWN",, "set_status_result": "type": "commandresult", "value": " ",, "set_status_status": "type": "commandstatus", "value": "UNKNOWN",, "status": "value": " ",, "switch_on_time": "value": "0", "value": " T11:07:06.165Z", "switching_on": "value": "0", "value": " T11:07:06.154Z", "set_status": "type": "command", "value": "",, "set_dimmer": "type": "command", "value": "",

9 3.4 Preparing FIWARE IoT to send commands to [Product Name] Not apply 3.5 Sending commands to LC40 from FIWARE IoT Not apply

10 4 Configuring LC40 with MQTT/TCP IoT-Agent 4.1 Intro & Requirements 4.2 Configuring LC40 to send data to FIWARE IoT Not apply 4.3 Accessing LC40 data at FIWARE Context Broker Not apply 4.4 Preparing FIWARE IoT to send commands to LC40 In order to receive commands, the device is subscribed to the following MQTT topic: <apikey>/<deviceid>/cmd where it will receive the command information. In our case: apikey54321/lc40p1/cmd Test 6: Send commands (Request) COMMAND REQUEST Array ( [0] => :44:12 [1] => receive [2] => Mosquitto\Message Object ( [mid] => 0 [topic] => apikey54321/lc40p1/cmd [payload] => LC40P1@set_status status=1 [qos] => 0 [retain] => ) ) 4.5 Sending commands to LC40 from FIWARE IoT Once the command is completed, the device should return the result of the command to the IoTAgent. For MQTT devices, the result should be returned to the following topic: <apikey>/<deviceid>/cmd

11 In our case: apikey54321/lc40p1/cmd Test 6: Send commands Result COMMAND RESPONSE Array ( [0] => :44:12 [1] => receive [2] => Mosquitto\Message Object ( [mid] => 0 [topic] => apikey54321/lc40p1/cmdexe [payload] => LC40P1@set_status status=1 [qos] => 0 [retain] => ) )