Trying to connect to 2 tags at once

[hardillb]

As mentioned over in the Node-Red side of things, I'm having issues connecting to multiple tags at once.

The second discover never happens. I'm wondering if the discovery phase is shutdown by the connect call. If so I guess the only way to do it is to call discover all, save the list of discovered tags and then connect after a suitable time out period?

var SensorTag = require('sensortag');

SensorTag.discoverByUuid("34b1f7d136b9",function(tag){
    console.log("found " + tag.uuid);
    tag.connect(function(){
        tag.discoverServicesAndCharacteristics(function(){
            tag.notifySimpleKey(function(err){
                console.log(err);
            });
            tag.on('simpleKeyChange', function(left, right){
                console.log("button " + left + " 34b");
            });
        })
    });


});

SensorTag.discoverByUuid('1cba8c20caf3',function(tag){
    console.log("found " + tag.uuid);
    tag.connect(function(){
        tag.discoverServicesAndCharacteristics(function(){
            tag.notifySimpleKey(function(err){
                console.log(err);
            });
            tag.on('simpleKeyChange', function(left, right){
                console.log("button " + left + " 1cb");
            });
        })
       });
});

[sandeepmistry]

@hardillb I can't seem to reproduce locally with 2 CC2650 sensor tags (I only own one CC2540 SensorTag, so can't test with two of those). Tried on my Mac and Raspberry Pi.

As well, a slightly modified version:

var SensorTag = require('sensortag');

var UUID_1 = '68c90b06bc81';
var UUID_2 = '68c90b044580';

SensorTag.discoverByUuid(UUID_1, function(tag1) {
    console.log('1: found ->' + tag1.uuid);

    tag1.connectAndSetUp(function() {
        console.log('1 -> connect and set up');

        tag1.notifySimpleKey(function(err) {
            console.log('1: notifySimpleKey' + (err ? err : 'success'));
        });
    });

    tag1.on('simpleKeyChange', function(left, right) {
        console.log('1: button ->' + right);
    });

    tag1.once('disconnect', function() {
        console.log('1: disconnected');
    });
});

SensorTag.discoverByUuid(UUID_2, function(tag2) {
    console.log('2: found ->' + tag2.uuid);

    tag2.connectAndSetUp(function() {
        console.log('2: connect and set up');

        tag2.notifySimpleKey(function(err) {
            console.log('2: notifySimpleKey' + (err ? err : 'success'));
        });
    });

    tag2.on('simpleKeyChange', function(left, right) {
        console.log('2: button ->' + right);
    });

    tag2.once('disconnect', function() {
        console.log('2: disconnected');
    });
});

Could you please provide debug logs: DEBUG=* node <files>.js

[hardillb]

I still get the same with your code and 2 version 1 SensorTags.

The debug log is here: https://gist.github.com/hardillb/d17331c148128334eae0

[sandeepmistry]

@hardillb any change in behaviour if you swap uuid's/BT address order?

The debug log only shows one discover event. To get more info, you could add some log statements in noble's startScanning and stopScanning methods, to verify stop scanning isn't been called.

[hardillb]

Changing the order doesn't change anything (apart from which tag gets to connect, it's always the first one).

I'll try and find some time later to have a poke lower down the stack

[sandeepmistry]

@hardillb any progress on this?

I'm wondering if something in the Bluetooth stack (hardware, driver, kernel version) doesn't allow for scanning while connected. What adapter and kernel version are you using?

[hardillb]

Sorry, not been in the office long enough to play with this again recently. I'll try and have another look this week.

[hardillb]

This is all running on Fedora Linux 20 with the following

kernel: Linux bagend 3.19.5-100.fc20.x86_64 #1 SMP Mon Apr 20 19:51:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

bluez: 5.18

hardware: Broadcom Corp. BCM20702 Bluetooth 4.0

not had chance to add anything to the code yet

[sandeepmistry]

@hardillb thanks, one thing to try is scan only (no connecting) - something like:

var SensorTag = require('sensortag');

SensorTag.discoverByUuid("34b1f7d136b9",function(tag){
    console.log("found " + tag.uuid);
});

SensorTag.discoverByUuid('1cba8c20caf3',function(tag){
    console.log("found " + tag.uuid);
});

[sandeepmistry]

@hardillb ping ... any progress?

[piekstra]

I am having similar issues trying to connect to a list of CC2650 sensortags at the same time:
Here is a code-snippet (not actually tested but quite similar to my implementation)

var async = require('async');

var devices = [ "68c90b06a104",
                "68c90b043a01",
                "68c90b043a02",
                "68c90b043a03",
                "68c90b043a04"]

var asynchronous = true;
var SensorTag = require('./index');

if (asynchronous) { 
    async.forEach(devices, function(deviceMac, callback) {
      //directly connect to device
      SensorTag.discoverByUuid(deviceMac, function(err) {
        console.log("found " + deviceMac); 
        callback();
      });  
    }, function (err) {
      console.log('All found!');
      process.exit(0);
    }); 
} 

[hardillb]

@sandeepmistry Sorry got side tracked with various things.

I've run the code you suggested and it's discovering both:

$ sudo node test.js
[sudo] password for hardillb: 
found 34b1f7d136b9
found 1cba8c20caf3`

So it looks like it's the connection part

[sandeepmistry]

@hardillb cool, so next step would be trying to connect to both after both are discovered ... please try that out and report back.

[hardillb]

The following code seams to be working:

var SensorTag = require('sensortag');
var tags = [];

SensorTag.discoverByUuid("34b1f7d136b9",function(tag){
    console.log("found " + tag.uuid);
    tags.push(tag);
});

SensorTag.discoverByUuid('1cba8c20caf3',function(tag){
    console.log("found " + tag.uuid);
    tags.push(tag);
});

setTimeout(function(){
   console.log("timer");
   tags.forEach(function(tag){
      tag.connectAndSetUp(function(){
          console.log("connected " + tag);

         tag.notifySimpleKey(function(err) {
            console.log('1: notifySimpleKey' + (err ? err : 'success'));
         });

     });
     tag.on('simpleKeyChange',function(left,right){
        console.log(left + " - " + right);
     });
   })
},5000);

[martin-doyle]

I am having a similar issue.
I have a setup with 3 SensorTags 2650 and once in 3 starts one of the SensorTags is not discovered. What I found is that the discovery with noble and noble-device tests work fine but the peripheral.advertisement.localName is sometimes "undefined".

Then the function "is" does not recognize the device as a SensorTag:

CC2650SensorTag.is = function(peripheral) {
  var localName = peripheral.advertisement.localName;

  return (localName === 'CC2650 SensorTag') ||
          (localName === 'SensorTag 2.0');
};