thanks for the report!

yea, i saw that right after release. it happens only if you dont have a bt input device connected at startup. i saw also that everything works. in fact, bluetooth buttons still work when you then DO connect a bt device later, without restarting.

so its a harmless, if misleading, error message. i decided not to fix it, because actively hiding error messages that n9bm didnt actually generate seems wrong.

p.s.: as you probably know, you shouldnt have to start this on the CLI. it should startup all by itself about 90 seconds after boot, and it should reload your changes to the conf file automatically.