hcitool/hciconfig are now deprecated in upstream bluez

[parker@satellite ~]$ sudo ds4drv 
[error][daemon] 'hcitool' could not be found, make sure you have bluez-utils installed.

Under the first notes section https://wiki.archlinux.org/index.php/bluetooth#Installation

There is a compat package but it’s only on the AUR so not everybody will have access to it.

[BlackLight]

Somebody decided to deprecate the executables that have been used for years by tons of devs and scripts to interact with the bluetooth stack without providing any viable alternative (“experiment with the dbus interaction to emulate what bluetoothctl does”, “pipe a bunch of echos to bluetoothctl”, “btmgmt is the new hciconfig - oh sorry, it’s not going to be official yet”).

That’s probably one of the dumbest things a software developer can do. Would it have been that expensive to keep the old executables until a new, stable way to handle bluetooth scripting with the new ones was out? You CAN’T deprecate something unless the alternative allows you to do exactly the same things you were able to do with the previous implementation! And the documentation is totally absent too - lots of pages still reference the hci* tools, and some (like the Arch Linux wiki) are themselves confused on what’s the right way to do things now. Most of all, users haven’t yet received an answer to a simple question: why were they deprecated in the first place?

I hope the guys at Bluez will soon recover from their unjustified booze and provide us with new reliable ways to do what we used to do until a year ago.

[parkerlreed]

Just putting this here as reference for the dbus locations

$ qdbus --system org.bluez /org/bluez/hci0 org.bluez.Adapter1.Powered 
true

That same value has read/write enabled on it.