...

{
  "altitude": 2.3687698831781745,
  "battery": 3630,
  "calculatedTimestamp": "2017-12-15T17:06:13.793Z",
  "maxTimestamp": "2017-12-15T17:06:16.793Z",
  "windowCount": 10,
  "deviceName": "bvTiTag",
  "locationId": 1,
  "floorNumber": 1,
  "id": "6253758190942573046",
  "latitude": 26.205612363949143,
  "location": "26.205612,-80.138235",
  "longitude": -80.13823502660985,
  "mac": "01:fa:b5:26:24:cf:b2",
  "projectId": 8,
  "timestamp": "2017-12-15T17:06:16.555687791Z",
  "type": "location",
  "variance": 0,
  "varianceX": 0,
  "varianceY": 0,
  "varianceZ": 0,
  "error":"OK",
  "errorDescription":""
}

Using The Service

Note:  Support for WebSocket connections to Bluzone has been deprecated.  Please use the RemoteConsumer service and bring your own Kinesis or EventHub stream to consume this data.

The following section assumes familiarity with working with WebSockets.  Bluvision has made a sample client available on Github (https://github.com/bluzone/consumer-service).  The sample client will connect to a WebSocket at the provided URL and dump contents to the console.  

Prerequisites

1. WebSocket Client:  A reference implementation can be found here:  https://github.com/bluzone/consumer-service
2. A project on the Bluzone Portal:  https://bluzone.io
3. The Web API Token from the project.
4. The URL to the Location Stream endpoint:  wss://bluzone.io/portal/consumer/location