And I really should have made some tests before my earlier reply. But we all make mistakes sometimes...
I've modified that earlier reply now, to set some facts straight.
This happened to me with one of the two adapters I tried.
OK, yes, but probably not compatible with the variation of bluetooth used in this OpenELEC distro.
I have a similar but not identical keyboard, which also came with a dongle of its own.
(This is a nordic brand, but is in fact a rebranded chinese product, though with Swedish keyboard layout.)
The docs for my keyboard clearly state that the dongle uses Bluetooth 3.0 protocol, which might not be the same version implemented in our OpenELEC variant. This dongle was never recognized on my RPi, though it too works for a PC. Another potential problem with bluetooth adapters is that they're likely to draw fairly high peak current, to achieve proper bluetooth signal strength. So the RPi PSU may need to be a bit stronger than needed for just the RPi.In any case I was able to test my bluetooth keyboard a little with RasPlex anyway, using an ancient Bluetooth adapter I've had for years. (A type made like a huge tooth in transparent blue plastic, so you see the circuit board inside.)
These tests tell me that it's currently a waste of time to try using any bluetooth devices with RasPlex.
The reason is that the PHT program is launched before OpenELEC has reconnected to paired devices, and PHT will only accept input from devices that were well defined during the initialization of PHT. I was able to simulate this by performing the pairing procedure for my keyboard, which still could not be used at that point, as PHT ignored its input. But then I logged in through SSH from a computer and gave the command "killall plexhometheater". That command shuts down the current instance of PHT, but since OpenELEC is still running and is configured to autolaunch PHT, this restarts PHT automatically. And this time the bluetooth keyboard is already connected to OpenELEC during the initialization of PHT, which makes PHT accept input from the keyboard.
This shows that there are two changes needed to completely fix this problem.
1: Somehow ensure that OpenELEC attempts to reconnect paired devices before launching PHT.
2: Somehow ensure that PHT repeats device usage initialization after adding bluetooth devices in the "System Settings" submenu
Note that it will always be necessary to have some other remote or keyboard device (like a USB keyboard) in order to perform original or changed pairing of a Bluetooth keyboard, since no new bluetooth device is ever accepted without such pairing procedure.
At this point I can't think of any more useful tests for this RasPlex version.
Its device usage initialization needs to be recoded for satisfactory use of Bluetooth devices.
Best regards: dlanor
Hi dlanor, after some hours spent last night I've come to the same conclusions as you regarding bluetooth keyboards and rasplex.
I was using a cheap ipazzport bluetooth keyboard from amazon. It paired perfectly well and ctrl+alt+delete worked, as handling that is the purview of the OS and not XBMC, but the keyboard did not work well to control PHT for the reasons you have already described.
I was able to find a patch to XBMC that supposedly rectifies the issue by making XBMC respond to hotplug events however I was unable to ascertain how the patch would fit into OpenELEC as I am unfamiliar with its architecture.
Before I went to sleep I had the idea that it might be possible to set lirc's device to the bluetooth keyboard. The idea being that lirc would be able to handle the delayed start of the bluetooth device and that PHT would work since lirc is always up. Looking into the idea a bit more I found that lirc contains a devinput driver that allows it to read input from a keyboard. I then started trying to figure out how rasplex starts lircd so I could tweak its parameters to use the devinput driver but couldn't find where it is started.
Do you, or does anyone else, have any info that could help me?