MooFoo
Posts: 12
Joined: Sun Mar 17, 2013 7:42 pm

Logitech K810 Bluetooth Keyboard

Sun Mar 17, 2013 8:30 pm

Hello folks. Having some trouble getting my bluetooth keyboard to auto pair on reboots, etc. I have tirelessly searched through the RPi forums and google for a solution and have continued to do little more than produce a large bump on my head from all the wall bumping. I deparetly need some help from a more advanced user.

Hardware:
  • IO Gear GBU521 Bluetooth 4.0 USB Dongle
  • Logitech Bluetooth Illuminated Keyboard k810
Installed Packages:
  • bluez
  • bluez-compat
  • blueman
  • bluez-tools
  • bluez-hcidump
I followed the steps found in this solution:
http://forums.linuxmint.com/viewtopic.php?f=42&t=125166

As far as I can tell, there does not seem to be any issues with the Bluetooth USB dongle. The system recognizes it on startup, and also with the hcitool, I am able to see it continuously try to connect to my bluetooth device when it turns on.

Running the following shows the device name and address:

Code: Select all

hcitool scan
Then I run:

Code: Select all

sudo bluez-simple-agent hci0 XX:XX:XX:XX:XX:XX
Which eventually produces:

Code: Select all

Creating device failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
At the same time, I run in a SSH terminal the following:

Code: Select all

sudo hcidump -at
The hcidump tool show that the system is cycling through several attempts to connect, but are denied. The user is never presented with an oportunity to ener a passkey, etc. I see the following (all I could capture from the remote terminal window):

Code: Select all

2013-03-17 15:17:08.180670 < HCI Command: Read Transmit Power Level (0x03|0x002d) plen 3
    handle 11 type 0 (current)
2013-03-17 15:17:08.182124 > HCI Event: Command Complete (0x0e) plen 7
    Read Transmit Power Level (0x03|0x002d) ncmd 1
    status 0x00 handle 11 level 3
2013-03-17 15:17:09.174293 < HCI Command: Read RSSI (0x05|0x0005) plen 2
    handle 11
2013-03-17 15:17:09.175208 > HCI Event: Command Complete (0x0e) plen 7
    Read RSSI (0x05|0x0005) ncmd 1
    status 0x00 handle 11 rssi 0
2013-03-17 15:17:09.177870 < HCI Command: Read Link Quality (0x05|0x0003) plen 2
    handle 11
2013-03-17 15:17:09.179221 > HCI Event: Command Complete (0x0e) plen 7
    Read Link Quality (0x05|0x0003) ncmd 1
    status 0x00 handle 11 lq 255
2013-03-17 15:17:09.182629 < HCI Command: Read Transmit Power Level (0x03|0x002d) plen 3
    handle 11 type 0 (current)
2013-03-17 15:17:09.184227 > HCI Event: Command Complete (0x0e) plen 7
    Read Transmit Power Level (0x03|0x002d) ncmd 1
    status 0x00 handle 11 level 3
2013-03-17 15:17:09.991433 < HCI Command: Disconnect (0x01|0x0006) plen 3
    handle 11 reason 0x13
    Reason: Remote User Terminated Connection
2013-03-17 15:17:09.993269 > HCI Event: Command Status (0x0f) plen 4
    Disconnect (0x01|0x0006) status 0x00 ncmd 1
2013-03-17 15:17:10.075276 > HCI Event: Simple Pairing Complete (0x36) plen 7
    status 0x05 bdaddr 00:1F:20:76:12:8A
    Error: Authentication Failure
2013-03-17 15:17:10.076280 > HCI Event: Auth Complete (0x06) plen 3
    status 0x05 handle 11
    Error: Authentication Failure
2013-03-17 15:17:10.077282 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 11 reason 0x16
    Reason: Connection Terminated by Local Host
Strangely, I can connect the bluetooth keyboard by using the following.

Code: Select all

sudo hidd --search
But it does not pair the device and only starts an input service. After a reboot or keyboard recycle, the keyboard does not reconnect. In that case I see the following in the hcidump tool:

Code: Select all

2013-03-17 15:20:52.770097 > HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
2013-03-17 15:20:52.777090 > HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x04 0x82 0x78 0x00 0x06 0x59 0x83
2013-03-17 15:20:52.777267 < HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
    handle 12 page 1
2013-03-17 15:20:52.779088 > HCI Event: Command Status (0x0f) plen 4
    Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1
2013-03-17 15:20:52.781095 > HCI Event: Link Key Request (0x17) plen 6
    bdaddr 00:1F:20:76:12:8A
2013-03-17 15:20:52.782105 > HCI Event: Read Remote Extended Features (0x23) plen 13
    status 0x00 handle 12 page 1 max 1
    Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
2013-03-17 15:20:52.782289 < HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 00:1F:20:76:12:8A mode 2 clkoffset 0x0000
2013-03-17 15:20:52.784086 > HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
2013-03-17 15:20:52.803083 > HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 00:1F:20:76:12:8A name 'Logitech K810'
2013-03-17 15:20:52.851754 < HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
    bdaddr 00:1F:20:76:12:8A
2013-03-17 15:20:52.853097 > HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 00:1F:20:76:12:8A
2013-03-17 15:20:52.860107 > HCI Event: Link Key Request (0x17) plen 6
    bdaddr 00:1F:20:76:12:8A
2013-03-17 15:20:52.862042 < HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
    bdaddr 00:1F:20:76:12:8A
2013-03-17 15:20:52.863096 > HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 00:1F:20:76:12:8A
2013-03-17 15:20:53.011118 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x13
    Reason: Remote User Terminated Connection
Does any one have any ideas? I would greatly appreciate any ideas since I have now spent several days searching google and trying everything I can find that seems related.

Spid
Posts: 525
Joined: Sat Jan 19, 2013 12:47 pm

Re: Logitech K810 Bluetooth Keyboard

Sun Mar 17, 2013 8:59 pm

These are packages I install, Blueman gives a GUI:

bluez
bluez-firmware
blueman
bluez-utils
bluez-tools

http://www.bluez.org/about
http://packages.debian.org/search?keywords=bluez
I will always assume you are running Raspbian for desktop and Raspbmc for XMBC !

MooFoo
Posts: 12
Joined: Sun Mar 17, 2013 7:42 pm

Re: Logitech K810 Bluetooth Keyboard

Sun Mar 17, 2013 9:03 pm

After making my initial post, I went back to google to find a page I was reading that seemed like it may had been related. I found it, and I can confirm that the below link directly affected my issue.

Looks like there might be a bug in the Bluez kernel. See below links...

Bluetooth Secure Simple Pairing SSP Broken

Code: Select all

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/931860

Code: Select all

http://comments.gmane.org/gmane.linux.bluez.kernel/13171
After reading the above, I executed the following:

Code: Select all

hciconfig hci0 sspmode 0
After that, the guide I was following worked:

Code: Select all

http://forums.linuxmint.com/viewtopic.php?f=42&t=125166
For clarity, I am using the latest Raspbian image, fresh image, all the latest apt-get updates.

I enterred a pass key at the terminal prompt, then entered a pass key on the keyboard, and the devices paired. Looks like the pairing process was getting interupted by the encrypted input stream. Beyond that, I have no clue.

The keyboard is now paired. Works after turning off and back on. Also works after reboot. Now I will try this solution on the RaspBMC box I have running to see if I can reliably switch between the two.
Last edited by MooFoo on Mon Mar 18, 2013 12:07 am, edited 1 time in total.

MooFoo
Posts: 12
Joined: Sun Mar 17, 2013 7:42 pm

Re: Logitech K810 Bluetooth Keyboard

Mon Mar 18, 2013 12:02 am

After my above fix for the keyboard, I was able to get the Microsoft 5000 bluetooth mouse to pair in a snap using blueman. A quick search for a pin code, found 0000, and that works on reboots as well.

Currently having trouble with the DBUS on RaspBMC. Been following this guide, but no luck. The hciconfig tool shows the interface as DOWN still. Keep getting errors on sudo apt-get update && sudo apt-get upgrade. Still researching. Plan to start over with a new RaspBMC image and let it go through the first run with the bluetooth dongle plugged in.

Code: Select all

http://www.ctheroux.com/2012/08/a-step-by-step-guide-to-setup-a-bluetooth-keyboard-and-mouse-on-the-raspberry-pi/

cowbear16
Posts: 1
Joined: Wed Mar 27, 2013 1:40 am

Re: Logitech K810 Bluetooth Keyboard

Wed Mar 27, 2013 1:45 am

Have you tried this:

Code: Select all

sudo l2ping -c 1 XX:XX:XX:XX:XX:XX
The above code will tell you if the designated device is in range. To find the MAC address just use:

Code: Select all

hcitool scan

Hope this helps!

Check out these URLs, which is where I found this information:
http://grefab.blogspot.com/2012/09/am-i ... tooth.html
http://www.dreamgreenhouse.com/projects ... /index.php

lmayorga
Posts: 3
Joined: Fri Jun 07, 2013 11:08 pm

Re: Logitech K810 Bluetooth Keyboard

Sat Jun 08, 2013 2:16 pm

I followed this tutorial from beginning to end http://www.ctheroux.com/2012/08/a-step- ... pberry-pi/ and it worked for me except for the last command :( .

The only explanation i can come up is that Logitech k811 is only compatible with iOS but still don't understand if it's bluetooth it should work because the bluetooth version 3 is supported on both sides.


http://www.raspberrypi.org/phpBB3/viewt ... 5&p=366098


I guess i am looking for a keyboard compatible with my rpi and the mac.

lanwarrior
Posts: 41
Joined: Fri Aug 22, 2014 6:05 am
Location: Somewhere in the you-es-a

Re: Logitech K810 Bluetooth Keyboard

Wed Sep 10, 2014 5:56 am

I tried the solution above, but I couldn't get the K810 to work with my Plugable USB-BT4LE bluetooth dongle.

The problem is, when the "Enter Key:" came out, none of the usual PIN works (0000, 1234). Logitech support website did not mention any PIN.

Also, the Bluetooth GUI in LXDE doesn't start. I can see the "B" Bluetooth icon in the taskbar, though. Bluetooth is also running when I ran "/etc/init.d/bluetooth status".

How did you get it to work?

fruitoftheloom
Posts: 22067
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: Logitech K810 Bluetooth Keyboard

Wed Sep 10, 2014 6:03 am

Is the Bluetooth Dongle recognised correctly ?

Open LXTerminal type lsusb and post output !
Retired disgracefully.....
......to an uncomplicated life !

Rather than negativity think outside the box !

lanwarrior
Posts: 41
Joined: Fri Aug 22, 2014 6:05 am
Location: Somewhere in the you-es-a

Re: Logitech K810 Bluetooth Keyboard

Wed Sep 10, 2014 6:49 am

fruitoftheloom wrote:Is the Bluetooth Dongle recognised correctly ?

Open LXTerminal type lsusb and post output !
Yes it does.

Code: Select all

[email protected] ~ $ lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. 
Bus 001 Device 004: ID 0a5c:21e8 Broadcom Corp. 
Bus 001 Device 013: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
Bus 001 Device 014: ID 05ac:024f Apple, Inc. 
Bus 001 Device 015: ID 046d:c069 Logitech, Inc. M500 Laser Mouse
[email protected] ~ $ sudo /etc/init.d/bluetooth status
[ ok ] bluetooth is running.
[email protected] ~ $ hcitool dev
Devices:
	hci0	00:02:72:D9:FA:3F
[email protected] ~ $ 
I can run "sudo bluez-simple-agent hci0 [K810-mac-address]" and it'll find the keyboard, but it's asking for PIN and there is no such thing for the K810.

When I connect my K810 to my PC, Mac, Android or iOS devices, it will generate a random number (47261, 13421) that I have to enter from the K810 keyboard itself.

I think that is what the GUI app will ask, but unfortunately it won't start in LXDE.

fruitoftheloom
Posts: 22067
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: Logitech K810 Bluetooth Keyboard

Wed Sep 10, 2014 7:22 am

Bus 001 Device 004: ID 0a5c:21e8 Broadcom Corp.

So this I presume is your Bluetooth Dongle, if so the device appears to not be correctly recognised, after Broadcom it should have a model number ;)

I presume this is a model B Pi, if so you may need to use a Mains Powered USB Hub to provide adequate power to the USB Peripherals:

http://elinux.org/RPi_USB_Bluetooth_adapters
Retired disgracefully.....
......to an uncomplicated life !

Rather than negativity think outside the box !

User avatar
DougieLawson
Posts: 37732
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: Logitech K810 Bluetooth Keyboard

Wed Sep 10, 2014 11:12 am

This might help: https://help.ubuntu.com/community/Media ... icTrackpad it's for the same Broadcom BT adapter.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

lanwarrior
Posts: 41
Joined: Fri Aug 22, 2014 6:05 am
Location: Somewhere in the you-es-a

Re: Logitech K810 Bluetooth Keyboard

Wed Sep 10, 2014 3:34 pm

fruitoftheloom wrote:Bus 001 Device 004: ID 0a5c:21e8 Broadcom Corp.

So this I presume is your Bluetooth Dongle, if so the device appears to not be correctly recognised, after Broadcom it should have a model number ;)

I presume this is a model B Pi, if so you may need to use a Mains Powered USB Hub to provide adequate power to the USB Peripherals:

http://elinux.org/RPi_USB_Bluetooth_adapters
This dongle is in the list from the USB Peripherals link you provided. It's actually the reason I bought it.

I think the dongle is recognized by the OS. I execute sudo hcidump -at and when connecting, I can see the BT dongle "talking" to my K810. The exchange is working, but K810 is asking for password (there is an actual prompt on the terminal). I entered 12345 and 00000 (standard BT password), but nothing. I wonder if the BT utilitity / driver is broken in Wheezy?

BTW, also tested this with another BT keyboard, same thing. :(

Code: Select all

[email protected] ~ $ sudo bluez-simple-agent hci0 90:7F:61:8D:C3:91
RequestPinCode (/org/bluez/2107/hci0/dev_90_7F_61_8D_C3_91)
Enter PIN Code: 12345
Creating device failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[email protected] ~ $ 

Code: Select all

[email protected] ~ $ sudo hcidump -at
HCI sniffer - Bluetooth packet analyzer ver 2.4
device: hci0 snap_len: 1028 filter: 0xffffffff
2014-09-10 08:30:52.039651 < HCI Command: Create Connection (0x01|0x0005) plen 13
    bdaddr 90:7F:61:8D:C3:91 ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 
2014-09-10 08:30:52.040853 > HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
2014-09-10 08:30:52.416865 > HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 90:7F:61:8D:C3:91 type ACL encrypt 0x00
2014-09-10 08:30:52.417320 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
    handle 12
2014-09-10 08:30:52.418901 > HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
2014-09-10 08:30:52.458913 > HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
2014-09-10 08:30:52.459229 < HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 90:7F:61:8D:C3:91 mode 2 clkoffset 0x0000
2014-09-10 08:30:52.460898 > HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
2014-09-10 08:30:52.504871 > HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 90:7F:61:8D:C3:91 name 'Bluetooth Keyboard                   '
2014-09-10 08:30:52.505040 < HCI Command: Authentication Requested (0x01|0x0011) plen 2
    handle 12
2014-09-10 08:30:52.506903 > HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
2014-09-10 08:30:52.507921 > HCI Event: Link Key Request (0x17) plen 6
    bdaddr 90:7F:61:8D:C3:91
2014-09-10 08:30:52.511420 < HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
    bdaddr 90:7F:61:8D:C3:91
2014-09-10 08:30:52.512986 > HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 90:7F:61:8D:C3:91
2014-09-10 08:30:52.513885 > HCI Event: PIN Code Request (0x16) plen 6
    bdaddr 90:7F:61:8D:C3:91
2014-09-10 08:31:01.641809 < HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
    bdaddr 90:7F:61:8D:C3:91 len 5 pin '12345'
2014-09-10 08:31:01.645033 > HCI Event: Command Complete (0x0e) plen 10
    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 90:7F:61:8D:C3:91
2014-09-10 08:31:19.087724 < HCI Command: Disconnect (0x01|0x0006) plen 3
    handle 12 reason 0x13
    Reason: Remote User Terminated Connection
2014-09-10 08:31:19.089224 > HCI Event: Command Status (0x0f) plen 4
    Disconnect (0x01|0x0006) status 0x00 ncmd 1
2014-09-10 08:31:19.171218 > HCI Event: Auth Complete (0x06) plen 3
    status 0x16 handle 12
    Error: Connection Terminated by Local Host
2014-09-10 08:31:19.172234 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x16
    Reason: Connection Terminated by Local Host

lanwarrior
Posts: 41
Joined: Fri Aug 22, 2014 6:05 am
Location: Somewhere in the you-es-a

Re: Logitech K810 Bluetooth Keyboard

Sat Sep 13, 2014 6:04 pm

Just a quick update: seems that something is going on with the software in Wheezy, though I cannot confirm. I got another "compatible" bluetooth dongle (as mentioned http://elinux.org/RPi_USB_Bluetooth_adapters) - D-Link DBT-122 and same thing: pairing ANY Bluetooth keyboard ask for a PIN, which I don't have and neither the manufacturer or myself set.

Just for fun, I did a fresh install of OS (update, upgrade, bluez, yada..yada.) and same thing.

I will create a new thread for BT and keyboard in general (not K810) specific and see if anyone have any input. Right now I just want a working BT keyboard.

pixelworlds
Posts: 8
Joined: Wed Nov 05, 2014 10:16 pm

Re: Logitech K810 Bluetooth Keyboard

Thu Nov 13, 2014 1:33 am

I've had an interesting time trying to connect a K810 also.

I've been able to get the bluetooth installed and (seemingly) working - I can even get the keyboard connected using the instructions in this post. However, it never enters anything when I press a key.

I can run

Code: Select all

sudo hcidump -at
and I can see the bluetooth logging a keypress -- but nothing even shows on the screen. This is the hcidump output:

Code: Select all

    Features: 0xbc 0x04 0x82 0x78 0x00 0x06 0x59 0x83
2014-11-13 01:30:51.420684 < HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3
    handle 70 page 1
2014-11-13 01:30:51.425452 > HCI Event: Command Status (0x0f) plen 4
    Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1
2014-11-13 01:30:51.432462 > HCI Event: Read Remote Extended Features (0x23) plen 13
    status 0x00 handle 70 page 1 max 1
    Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
2014-11-13 01:30:51.432647 < HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 00:1F:20:A9:21:02 mode 2 clkoffset 0x0000
2014-11-13 01:30:51.437471 > HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
2014-11-13 01:30:51.607470 > HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x13 bdaddr 00:1F:20:A9:21:02 name ''
    Error: Remote User Terminated Connection
2014-11-13 01:30:51.608473 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 70 reason 0x13
    Reason: Remote User Terminated Connection
Anyone experiencing the same thing?

User avatar
_emanuel_
Posts: 17
Joined: Wed Apr 01, 2015 9:47 pm
Location: bavaria
Contact: Website

Re: Logitech K810 Bluetooth Keyboard

Mon May 04, 2015 8:27 pm


Anathemapth
Posts: 1
Joined: Fri Feb 20, 2015 6:55 am

Re: Logitech K810 Bluetooth Keyboard

Wed Aug 10, 2016 6:04 am

I am having an interesting problem related to this that I am not sure can be addressed. I have built an arcade cabinet where I am using a raspberry pi running mame. It is fully enclosed. I have finally got the Logitech K810 keyboard to bind with it so I can admin the pi without having to open the cabinet up. Problem is the K810 only looks for bt controllers for the first 20 seconds it boots up. When I start up my cabinet, the keyboard is no longer looking for a controller. I tried turning the keyboard on when the cabinet comes up but it is hit or miss to have it looking at the same time the bt stuff is loading. Does bt have a method to look to see if it is bound to a device id currently, and if not, to have it send something out to force the keyboard to connect?

Sorry if this really does not pertain to this thread . . . I'll move if necessary.

patmonardo
Posts: 1
Joined: Thu Aug 24, 2017 3:29 am

Re: Logitech K810 Bluetooth Keyboard

Thu Aug 24, 2017 3:40 am

I purchased 4 raspberry pi 3's a couple months ago and have them hooked up
to a samsung s32d850t which has 3 inputs and supports PBP.
I also have a chromebook with HDMI so I have 5 HDMI sources hooked up to
a samsung and decided to interface to keyboard/mouse through a multi-device bluetooth
keytooth system ... indeed the K810 and Master MX.

I have not really been able to use the K810 and Master MX with Jessie, full-upgrade.
It was an intense struggle but I wanted to learn bluetooth and kept at it.
It would work but I was never certain why. so if I left things alone, good stuff.
A glitch and it was back to K810 / Master MX bluetoothctl hell.

Some good news. I upgraded to Stretch and these problems are all solved.
Using the standard out of the box bluez interface...simple Add Device
done. With the MX I still get the dreaded 'there are no services with this device'.
but now the mouse works so the no service message is harmless.

Now all connections are restored with reboot and when I switch to a different rpi,
the mouse and keyboard hook back up no problem. KI get an annoying
message telling me Master MX wants to pair, I click OK and things work fine.
I bet this can prompt to allow the MX to pair can be configured away,
it really is annoying.

So now whew, I was about out of patience with this and the upgrade to Stretch
seems to make this situation ... and read this thread to understand the extent of this situation.....SOLVED!!!

Return to “Troubleshooting”