service advertising data now reported as a simple array of bytes, not {type:'Buffer',data:...}

Author: gfwilliams

README.md

@@ -160,7 +160,7 @@ Useful MQTT advertising parts are:
 * `/ble/advertise/DEVICE` - JSON for device's broadcast name, rssi and manufacturer-specific data
 * `/ble/advertise/DEVICE/manufacturer/COMPANY` - Manufacturer-specific data (without leading company code)
 * `/ble/advertise/DEVICE/rssi` - Device signal strength
-* `/ble/advertise/DEVICE/SERVICE` - Raw service data (as JSON)
+* `/ble/advertise/DEVICE/SERVICE` - Raw service data (as a JSON Array of bytes)
 * `/ble/advertise/DEVICE/PRETTY` or `/ble/PRETTY/DEVICE` - Decoded service data. `temp` is the obvious one
 
 To decode the hex-encoded manufacturer-specific data, try:

lib/discovery.js

@@ -102,7 +102,12 @@ function onDiscovery(peripheral) {
         inRange[addr].data[d.uuid].time > Date.now()-60000)
      return;
 
-    mqtt.send("/ble/advertise/"+id+"/"+d.uuid, JSON.stringify(d.data));
+    // Send advertising data as a simple JSON array, eg. "[1,2,3]"
+    var byteData = [];
+    for (var i=0;i<d.data.length;i++)
+      byteData.push(d.data.readUInt8(i));
+    mqtt.send("/ble/advertise/"+id+"/"+d.uuid, JSON.stringify(byteData));
+
     inRange[addr].data[d.uuid] = { payload : d.data, time : Date.now() };
 
     var decoded = attributes.decodeAttribute(d.uuid,d.data);