Boss just bought me one of these ->http://serialio.com/products/adaptors/BlueSnapXP.php

I spent yesterday making it work with my Kubuntu Notebook. Works great, no more getting up in lifts with a cable and my laptop to fix borked Cisco AP's.

Anyway, How do I get this thing going in Maemo? AFAIK there is no hcidtool scan, no rfcommm etc. I would like to use Minicom, as I have gotten this to work with a USB -> Serial Port -> Cisco Cable and it works great.

Thanks for any direction you can give.

I think the bluetooth tools are in the bluez-utils-test package in the diablo tools repository. This is a developer repository. See here:
http://repository.maemo.org/#sdk_debian

You need the diablo/tools distro source for bluez tools:
deb http://repository.maemo.org/ diablo/tools free non-free

From other posts I've read in the past, one is supposed to be using dbus for anything bluetooth related and the bluez tools are deprecated.

You might want to try the ITT wiki for bluetooth stuff as well. I'm new here so I am not too familiar with the available content.

I was doing research for a bluetooth mouse a long time ago and found the familiar bluez tools in this package.

Thanks!! I got those packages and can do a scan, see the device, make the rfcomm0 entry... But trying to connect, I get connection refused. I think because I cannot send the pin code to authenticate.. How do I do that??

Thanks

Ok, got it.. Did not need to send Pin

These are the steps I used to connect to a SerialIO BlueSnapXP. I use this to program Cisco and HP network gear via Console Port.

This works for me.. As always YMMV

I did this on an N810 Diablo

Install minicom --> https://garage.maemo.org/projects/minicom/
Go to http://mulliner.org/nokia770/ -->Install Repository for Diablo
Go to App Manager, install bluez-utils-dist
exit App Manager
Place device in pairing or discovery mode
open X Terminal

Open a new X Terminal Window
In X-Terminal Menu, Windows, New Window
next time all you need to do is:
Open a new Window in X Terminal
I did not have to edit /etc/bluetooth/hcid.conf
I did not have to edit /etc/bluetooth/rfcomm.conf

I hope this helps someone else along the way...