> This setup used to work more or less flawlessly with Raspbian Jessie. > With Stretch, however, I'm seeing a variety of behaviors from "pairing > rejected" over "paired, but not trusted" to "working OK" (rare). This > inconsistent behavior lets me believe that the BT device is missing > initialization into a predictable state (pairable, discoverable, any > other?) before the script is called. I'm currently playing with explicit > initialization sequences using 'bluetoothctl', but I'm also wondering > how this used to work with Raspbian Jessie before. >From what I can tell raspbian jessie had bluez-5.23, try downgrading to it from your current version, either by installing the exact version from your package manager, or by cloning the bluez repository, checking out the commit from that release ,building, and then running it. That way you can tell whether it's the newer versions of bluez that are causing the issue. > > The most common behavior is "paired, but not trusted", which yields the > following errors in syslog: > Jan 1 12:40:53 Raspi-2 bluetoothd[615]: Authentication attempt without > agent Are you using the exact simple-agent script you attached or a variation of it? the one you attached seems to be registering an agent, whereas this is saying it isn't. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
