I regularly use an i-Blue 747A+ Bluetooth GPS Trip Recorder. It is a GPS data receiver that provides both bluetooth and USB connectivity. It can also store the data for later download, via USB only. I'm not sure the 747A+ is still sold but other brands based on the same MediaTek MTK chipset, and with similar functionality, are available. e.g. the Qstarz GPS Datalogger BT-Q1000XT. These device are quite common. For my use case, the 747A+ provides GPS data via bluetooth to a Netbook running a moving map program (OziExplorer running under Wine). I use a bash script, triggered by udev, to bind the 747A+ to /dev/rfcomm, which is soft linked with the COM port used by OziExplorer. The set up has worked well for many years. My udev script first runs "/usr/bin/hciconfig hci0 up" to ensure the controller is available. It appears /usr/bin/hciconfig can be replaced by echoing commands to bluetoothctl. e.g. " echo -e "trust $MAC\nconnect $MAC\nquit" | bluetoothctl". A workable kludge I guess. However, finding a replacement for the primary command, "/usr/bin/rfcomm bind /dev/rfcomm0 <GPS>", is another story. In an earlier reply Stefan indicated that /usr/bin/rfcomm can also be replaced by 'bluetoothd together with bluetoothctl'. I am not skilled with bluetooth and the bluetoothctl help is pretty sparse but I can't find anything there to set up /dev/rfcomm and bind a device to it. An example would be very helpful. Google failed me as well. The stuff I could find suggests it must now be set up via dbus. But this is not straight forward and one of the bluez devs commented that it would be better for non-experts to try the Python based Blue Dot library. I had a play with the Blue Dot library but it simply throws the exception "AttributeError: module 'socket' has no attribute 'AF_BLUETOOTH'", which is not surprising given the earlier comment that AF_BLUETOOTH was removed from Python on openSUSE. So, in summary, yes there are users of this stuff; there is a workable alternative to at least some of the hcixxx commands; but a replacement for /usr/bin/rfcomm is problematic. Graeme Blackman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org