OS X support

[sander]

One advantage of sandeepmistry/node-ancs is that the same code works on OS X and on Linux. This allows for developing on an OS X system while testing / deploying on an embedded Linux system. What would it take to add OS X compatibility (possibly through a different BLE library) to ble-ancs?

[robotastic]

It might be possible.. but judging from this thread, it looks like you
can't advertise that you are looking for a service UID in OS X Core
Bluetooth: sandeepmistry/node-ancs#3

The other challenge is that one a Bluetooth adapter gets associated with a
Mac, iOS doesn't seem to want to let you pair with it in the Bluetooth
settings menu. I have been using a VMWare Linux image to do the development
work and a USB BLE dongle on the Linux side.

I will look into, but I am not sure if I will be able to get it working.

On Mon, Oct 26, 2015 at 10:18 AM, Sander Dijkhuis notifications@github.com
wrote:

One advantage of sandeepmistry/node-ancs
https://github.com/sandeepmistry/node-ancs is that the same code works
on OS X and on Linux. This allows for developing on an OS X system while
testing / deploying on an embedded Linux system. What would it take to add
OS X compatibility (possibly through a different BLE library) to ble-ancs?

—
Reply to this email directly or view it on GitHub
#2.

[sander]

Thanks! For the described use case, perhaps including node-ancs’s behaviour could work, i.e. Mac as central and iOS as peripheral, possibly using a previously set up BLE pairing. Only this issue came up that might complicate things: sandeepmistry/node-ancs#9 (ANCS likely filtered out from GATT response to OS X).

The dongle + virtualisation approach sounds good, I’ll try that.