2015-06-29, 23:20
Thanks very much to fostersimported for your posting of 2015-06-14 21:58 - very useful.
I've written up a few things that I've discovered through playing around with this just in case they're of use to anyone:
1. It's worth noting that /etc/bluetooth/input.conf contains an IdleTimeout setting, which is commented out by default. It's good for the remote controller battery life to use this since the power consumption is about 100 times less on standby than when connected. In fact when editing this file there should be an example in ~/bluez-4.101/input/input.conf as a result of the tar and patch operations above. Note that the idle timeout before the connection will be disconnected is in seconds, not minutes, so it's probably worth setting something like 'IdleTimeout=600' (600 seconds, i.e. 10 minutes).
2. When trying to pair the remote controls it can be useful to run the bluetooth daemon in foreground - in another ssh session type the following:
3. There are two different Sony PS3 remote controls around, and they appear to require different processes to get them working.
The older ones look like http://www.remotecentral.com/wn000383.jpg and take two AA batteries. The newer ones look like this one on Amazon.com: http://www.amazon.com/Media-Blu-ray-Remo...te+control - they are slightly longer, take two AAA batteries, and have a row of lights to show which device is being controlled (PS3/AMP/TV).
For the the older ones it's sufficient to run 'sudo python ps3_pair.py' as described above.
Whereas the only way I could make one of the newer ones work is by doing the following:
stop and restart bluetooth service (bluetoothd) (not always necessary but it can cure some problems)
Then run:
It will display
Press START and ENTER simultaneously for about five seconds on the PS3 remote - 'PS3' light will start flashing
It will display something like:
Press return - it will then display:
After that, if you run
it should show :
After this the remote control may work, or it may be necessary to do the following:
Press START and ENTER simultaneously for about five seconds on the PS3 remote - 'PS3' light will start flashing
Then type:
(where you replace <device ID> with whatever unique ID was displayed when you ran 'sudo python ps3_pair.py')
After that, if you run
it should show :
And more annoyingly, with the newer remote controls, I found that if you change the batteries you then need to re-run the START + ENTER and 'sudo bluez-test-input connect <device ID>' operation.
And finally, if you get the message
when trying to do any of the above then try stopping and restarting the bluetooth daemon.
I've written up a few things that I've discovered through playing around with this just in case they're of use to anyone:
1. It's worth noting that /etc/bluetooth/input.conf contains an IdleTimeout setting, which is commented out by default. It's good for the remote controller battery life to use this since the power consumption is about 100 times less on standby than when connected. In fact when editing this file there should be an example in ~/bluez-4.101/input/input.conf as a result of the tar and patch operations above. Note that the idle timeout before the connection will be disconnected is in seconds, not minutes, so it's probably worth setting something like 'IdleTimeout=600' (600 seconds, i.e. 10 minutes).
2. When trying to pair the remote controls it can be useful to run the bluetooth daemon in foreground - in another ssh session type the following:
Code:
sudo service bluetooth stop
sudo bluetoothd -n -d
3. There are two different Sony PS3 remote controls around, and they appear to require different processes to get them working.
The older ones look like http://www.remotecentral.com/wn000383.jpg and take two AA batteries. The newer ones look like this one on Amazon.com: http://www.amazon.com/Media-Blu-ray-Remo...te+control - they are slightly longer, take two AAA batteries, and have a row of lights to show which device is being controlled (PS3/AMP/TV).
For the the older ones it's sufficient to run 'sudo python ps3_pair.py' as described above.
Whereas the only way I could make one of the newer ones work is by doing the following:
stop and restart bluetooth service (bluetoothd) (not always necessary but it can cure some problems)
Then run:
Code:
sudo python ps3_pair.py
Code:
Please HOLD the START and ENTER buttons on the PS3 remote.
Searching for devices, please wait...
It will display something like:
Code:
Found:
1: 34:C7:31:04:25:1A [Unknown]
Select the device you wish to add [1]:
Press return - it will then display:
Code:
Registering device... Done
After that, if you run
Code:
/usr/share/doc/bluez/examples/list-devices
Code:
Trusted = 1
After this the remote control may work, or it may be necessary to do the following:
Press START and ENTER simultaneously for about five seconds on the PS3 remote - 'PS3' light will start flashing
Then type:
Code:
sudo bluez-test-input connect <device ID>
After that, if you run
Code:
/usr/share/doc/bluez/examples/list-devices
Code:
Connected = 1
And more annoyingly, with the newer remote controls, I found that if you change the batteries you then need to re-run the START + ENTER and 'sudo bluez-test-input connect <device ID>' operation.
And finally, if you get the message
Code:
dbus.exceptions.DBusException: org.bluez.Error.AlreadyConnected: Already Connected