NOTE:
This documentation was written for one of the earlier wovyn devices. The general process and setup is essentially the same, but with just a few minor differences, so don't be surprised if your experience doesn't match perfectly with this documentation.
Connecting a Wovyn sensor to the Internet of Things using a Pico and KRL.
Opening up the sensor, we can see model, serial, and version numbers. Besides its internal sensors, this device has an external temperature probe on a nine foot cable.
Turning over the plastic-shielded printed circuit board, and pulling out the battery pack gives us access to everything we need to proceed.
Configuring the sensor to send its event:
NOTE: You will not see the endpoint split into segments like in the following picture if you are working with the newer wovyn software, rather you will see a single endpoint box where you enter all your information in a single slot. i.e. enter "http://<yourIPaddress>:<yourPort>/sky/event/<yourEci>/<eventID>/<domain>/<type>
Of course the pico identified by the ECI will need a ruleset to receive the event. This is the KRL code that we used initially.
ruleset post_test { meta { shares __testing } global { __testing = { "queries": [ { "name": "__testing" } ], "events": [ { "domain": "post", "type": "test", "attrs": [ "temp", "baro" ] } ] } } rule post_test { select when post test pre { never_used = event:attrs().klog("attrs") } } } |
The rule selected does nothing but log the event attributes. Notice that the ruleset shares a test harness which allows us to easily send a test event from the "Testing" tab of the "My Picos" page.
We used the "Logging" tab to see what happens when the device sends an event.
Notice that several attributes are sent by the device. The first of these are "version", "eventDomain", "eventName", and "emitterGUID". The horizontal scrollbar indicates that there is much more. Capturing and re-formatting all of it, we see that the remaining attributes are named "genericThing", "specificThing", and "property". The following data structure is current as of 1/21/18.
{ "emitterGUID":"5CCF7F2BD537", "eventDomain":"wovyn.emitter", "eventName":"sensorHeartbeat", "genericThing":{ "typeId":"2.1.2", "typeName":"generic.simple.temperature", "healthPercent":56.89, "heartbeatSeconds":10, "data":{ "temperature":[ { "name":"ambient temperature", "transducerGUID":"28E3A5680900008D", "units":"degrees", "temperatureF":75.31, "temperatureC":24.06 } ] } }, "property":{ "name":"Wovyn_2BD537", "description":"Temp1000", "location":{ "description":"Timbuktu", "imageURL":"http://www.wovyn.com/assets/img/wovyn-logo-small.png", "latitude":"16.77078", "longitude":"-3.00819" } }, "specificThing":{ "make":"Wovyn ESProto", "model":"Temp1000", "typeId":"1.1.2.2.1000", "typeName":"enterprise.wovyn.esproto.wtemp.1000", "thingGUID":"5CCF7F2BD537.1", "firmwareVersion":"Wovyn-WTEMP1000-1.14", "transducer":[ { "name":"Maxim DS18B20 Digital Thermometer", "transducerGUID":"28E3A5680900008D", "transducerType":"Maxim Integrated.DS18B20", "units":"degrees", "temperatureC":24.06 } ], "battery":{ "maximumVoltage":3.6, "minimumVoltage":2.7, "currentVoltage":3.21 } }, "version":2 } |
We also tried out the "Reset" option, which apparently forgets only the WiFi hotspot the device uses to send its heartbeat events, but retains the endpoint information.
You may also want to use visual panels to communicate related information, tips or things users need to be aware of. |
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|