Hello,
I had the same issue and found another work around rather than reverting to the previous version.
The topic is discussed here:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931
It seems that this is intentional will not be changed in future versions.
As mentionned right at the beginning of that post the workaround is the following:
It worked for me.
Maybe its worth digging a little bit more to know what is the more suitable way of handling this new way of working of BlueZ...