09-23-2013 02:09 PM
Both MetaWatch and BlackBerry 10 support BLE, but as far as i found out there are problems with stack compatabilities with different devices and apperantly there is problem connecting metawatch and Z10 using GATT services, though i still can use SPP to connect. I tried to contact MetaWatch and didn't get any proper response, till few days ago i got one from Bill Geiser:
"we've made a number of attempts at working with RIM over the years & received little, We won't spend any more time on this" (https://twitter.com/billg/status/38176184381696409
"it takes two to tango....we're done with RIM. Sorry. Too many other opportunities to chase."(https://twitter.com/billg/status/38176268724536524
So i'm trying to ask if blackberry can assist me(or any other developer) to resolve the issues :your personal with metawatch team and the one of connectivity between metawatch and Z10
Thank you in advance
09-23-2013 05:56 PM
09-24-2013 01:13 AM
09-24-2013 02:10 AM
Thanks ZogG. That's useful. No reason why there should be a fundamental incompatibility of any sort that I can think of based on that information, but I'll let our development team do some proper exploration of the issue before I jump to any conclusions.
No thanks necessary from you (though it's nice of course!). Let's work through this and see what *result* we can achieve.
All the best
09-24-2013 02:56 AM
By the way, do you have any information on the GATT profiles and services that the watch supports? I don't see anything on their web site beyond the statement that they support Bluetooth 4.0 to suggest that GATT is supported. We can figure this out once we have a watch in our hands but thought you might already know.
When you say you cannot get it to work with GATT, what do you mean exactly? Are you developing an application to work with it?
09-24-2013 03:14 AM
09-24-2013 03:23 AM
Thanks. You're using exactly the right terminology :-)
I don't see any useful information about GATT in the protocol specification unfortunately. Not to worry though. We can find out service UUIDs easily enough. The challenge will come when trying to establish how to use those services. If the UUIDs are 0x8880 and 0x8882 then these are not standard (defined by the Bluetooth SIG) services and therefore only MetaWatch can specify how to use these services.
So first off we'll try to verify what the watch is actually exposing over GATT. Then we may need to try and persuade MetaWatch to talk to us. No idea of the history there but hopefully they'll be open to establishing a dialogue so that we can help one of their customers.
All the best
09-24-2013 09:51 AM
I confess I'm not 100% clear on the problem you've encountered so whilst our developers get equipped and start to look at MetaWatch, let's just make sure I understand:
- I assume you're developing an application. If so what is its status?
- If MetaWatch are using their own services with their own UUIDs you need to connect to those services. See our HeartMonitor application for an example of how to find and connect to a service by UUID: https://github.com/blackberry/Cascades-Community-S
If you have already tried this, can you clarify exactly what is happening and perhaps share some code please?
Also, do you have a Bluetooth developer's kit like the one from Texas Instruments? http://www.ti.com/tool/cc2540dk-mini
Armed with one of these kits you'll be able to verify that what you think are the UUIDs really are those values.
What version of the BlackBerry 10 OS are you developing for? At version 10.0 UUIDs used with the Bluetooth GATT API did not have a prefix of "0x" but later we changed the API so that now this is required. See this conditional code in HeartMonitor:
09-24-2013 10:16 AM
09-24-2013 10:22 AM
OK, thanks. I'm actually wondering whether MetaWatch supports Bluetooth Low Energy. I looked at their developer support forums and they have a forum called "All things BLE (Alpha)" which to me suggests it's an early stage feature that will not be present in a product out of the box. I've ordered one from Amazon anyway so I'll review as soon as I get it, as will our development team.
I'm beginning to suspect that:
- products don't have BT LE out of the box
- there's alpha firmware available that has it, albeit in an alpha state
Anyway.... one way or another we'll figure this out :-)
All the best