Can't connect devices when bt-agent is run with daemon flag

[rshatch]

When I run bt-agent in the foreground (bt-agent --capability=NoInputNoOutput) or manually backgrounded (bt-agent --capability=NoInputNoOutput &) I'm able to pair my phone correctly with the system, but running it with the daemon flag (bt-agent --capability=NoInputNoOutput -d), the system is visible to my phone, but trying to pair and connect fails with a generic 'can't connect to device' message. bluez-tools is running as the most recent repo version available on Raspbian Buster Full (version 2.0~20170911.0.7cb788c-2), on a Raspberry Pi Zero W using the built-in bluetooth chip.

[sedlund]

The NoInputNoOutput option appears to be broken as it always asks for a yes/no on stdout and awaits input.

I use the 'yes' command to authorize everything :)

In systemd I do this:

/etc/systemd/system/bt-agent.service

[Unit]
Description=Bluetooth Auth Agent

[Service]
#ExecStart=/usr/bin/bt-agent -c DisplayOnly
ExecStart=/bin/sh -c '/usr/bin/yes | /usr/bin/bt-agent --capability=NoInputNoOutput'
Type=simple

[Install]
WantedBy=multi-user.target

[CarlosDerSeher]

Any updates regarding this issue? Are there any drawbacks starting a service with bt-agent --capability=NoInputNoOutput & instead of using bt-agent --capability=NoInputNoOutput -d
I am currently building the package for openwrt 21.02 platform and it runs already, just have been wondering if this needs to be fixed and if so how to debug this...