I have a bluetooth device and I'm trying to understand why no BT debug app on my iOS device can find it, and yet my Mac and iPhone settings app can discover and connect to it no problem.
The debug apps I'm using on iOS are BT Low Energy scanners and I'm wondering if it's not that kind of device, is there a way to tell from the below debug?
Connecting to it via mac and running system_profiler SPBluetoothDataType gives:
XRS2 2205:
Address: 84-71-27-05-DB-B8
Major Type: Miscellaneous
Minor Type: Unknown
Services: XRS2 HID, Bluetooth Serial Port, Wireless iAP
Paired: Yes
Configured: Yes
Connected: Yes
Manufacturer: Cambridge Silicon Radio (0x5, 0x27B8)
Bluetooth Core Spec: 3.0
Firmware Version: 0x0400
Vendor ID: 0x0483
Product ID: 0xA026
Class of Device: 0x00 0x00 0x0000
AFH: On
AFH Map: FF43720007FE1CC7F
RSSI: -51
Role: Master
Connection Mode: Sniff Mode
Interval: 250 ms
Host Connectable: No
EDR Supported: Yes
eSCO Supported: Yes
SSP Supported: Yes
Data sheet: https://www.livestock.tru-test.com/sites/default/files/datasheets/XRS2%20Datasheet_0.pdf#product_data_sheets
Bluetooth Low Energy was added to Bluetooth version 4.0. Since your device uses Bluetooth 3.0, it must be a Bluetooth Classic device.
Related
I am running Vmware vm with Ubuntu 18 OS on a Window 10 system. A USB bluetooth device is plug in this Machine. Now I want to control this bluetooth device in Ubuntu 18 VM, but failed.
In Ubuntu VM, I can get bluetooth hardware info through:
# hcitool scan
Scanning ...
70:EF:00:D0:AE:05 ****
3C:CD:57:2C:94:4F ****
14:DE:39:E5:B2:F8 ****
48:01:C5:06:DC:A2 ****
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root#turnbig:~# lshw | grep Blue -C 10
*-usb:1
description: USB hub
product: VMware Virtual USB Hub
vendor: VMware, Inc.
physical id: 2
bus info: usb#2:2
version: 1.00
capabilities: usb-1.10
configuration: driver=hub slots=7 speed=12Mbit/s
*-usb
description: Bluetooth wireless interface
product: Virtual Bluetooth Adapter
vendor: VMware
physical id: 1
bus info: usb#2:2.1
version: 1.00
serial: 000650268328
capabilities: bluetooth usb-2.00
configuration: driver=btusb speed=12Mbit/s
But when i try to connect to other BT devices, it failed with "Device 3C:CD:57:2C:94:4F not available", 3C:CD:57:2C:94:4F is a target bluetooth device to connect:
# bluetooth
bluetooth = on
# bluetoothctl
[NEW] Controller 44:AF:28:F5:2B:D3 ***** [default]
Agent registered
[bluetooth]# info 3C:CD:57:2C:94:4F
Device 3C:CD:57:2C:94:4F not available
[bluetooth]# connect 3C:CD:57:2C:94:4F
Device 3C:CD:57:2C:94:4F not available
I can connect to this BT device through host machine (Window 10)
thanks for any comment.
Question fixed, original solution is post here.
To use a USB bluetooth from VMware guest OS, we can not share bluetooth to guest, we should connect the removeable bluetooth device to guest directly.
I like to use a RaspberryPi to act as HeartRate Sensor and transmit these data via BLTH to other Health/Sport-Apps.
Finally all is working fine with python and bluez I'm able to create a BLTH GATT Server and advertise HR-Data via Service 0x180d.
The last problem is I'm not able to change the Appearance of the BLTH in Generic Access (0x1800). Apprearance is to find here with UUID: 0x2A01.
I tryed to do this the manual way via bluetoothctl:
menu advertise
appearance 833 (for HeartRate)
appearance on
back
advertise on
This will fail with: Failed to register advertisement: org.bluez.Error.Failed
nevermind to which value i change the apperance (also if the value is well known and accepted) it fail the advertisement.
If i switch appearance off it will start advertisment.
Any hint, what do to or what I just missed?
I already updated bluez from 5.50 to 5.54
also used bluez in experimental mode
and using newest raspian os with all updates
Many thanks for help
These are the steps that I used on my Raspberry Pi:
pi#raspberrypi:~ $ bluetoothctl
[bluetooth]# menu advertise
[bluetooth]# clear
[bluetooth]# uuids 0x180D
[bluetooth]# appearance 833
[bluetooth]# name heart_test
[bluetooth]# discoverable on
[bluetooth]# back
[bluetooth]# advertise on
[CHG] Controller 00:02:5B:03:44:07 SupportedInstances: 0x04
[CHG] Controller 00:02:5B:03:44:07 ActiveInstances: 0x01
Advertising object registered
UUID: Heart Rate(0x180D)
Tx Power: off
LocalName: heart_test
Appearance: Heart Rate Belt (0x0341)
Discoverable: on
[bluetooth]#
And it gave me this on me this in the nRF app when I scanned for it:
Many BLE devices have BR/EDR Controller Mode - LE + BR/EDR Host Mode in their Flags. Does this mean that this Device is also a classic Bluetooth device?
BR/EDR is the technical term for what you call bluetooth classic.
With "in their Flags" you probably mean in the advertisement? This would mean that the device at least reports, that it also implements bluetooth classic, yes.
I am using BeagleBone Black and Bluetooth USB dongle V4.0. My dongle is detecting iBeacons with no problems but is there any way to detect mobile phones with bluetooth on. I am using NodeJs and Noble package.
So when I use hcitool lescan it's not finding mobile phone either but with hcitool there is option scan. When I call hcitool scan in terminal I get my mobile as result. Is there any NodeJs package that wraps this option. I have no need to connect to mobile device, I just need to discover it's presence, and see it's MAC address.
If you can see your device with "hcitool scan" and not with "hcitool lescan" it means your phone(or BT stack you use in phone) don't support BLE protocol. Not all BT devices are BLE capable.
Is it possible for the Bluetooth dual-mode device to be discoverable by classic bluetooth at the same time as being pairable with BT LE devices?
It's ok if the device can not operate with both at the same time, but should I switch the chip between those modes really?
I just can not find the answer in the BT 4 Core Specification
Yes, A dual mode device can be discoverable by classic Bluetooth while being connected to a LE device.
The device can also be connected to both classic and LE at the same time (device will time multiplex so as to maintain operations on both Classic and LE simultaneously)