4a: adjust 4a_wait_bt.sh due to changes in bluetooth-manager API

The verb 'power' is now replaced by 'adapter_state'. The response
object is also different (no compatibility with older API).

Bug-AGL: SPEC-1630

Change-Id: I2e08c33e2936d93cfdec0c498570c77177a4b81e
Signed-off-by: Stéphane Desneux <stephane.desneux@iot.bzh>

diff --git a/meta-audio-4a-framework/recipes-multimedia/agl-service-audio-4a/files/4a_wait_bt.sh b/meta-audio-4a-framework/recipes-multimedia/agl-service-audio-4a/files/4a_wait_bt.sh
index a1df1ea..9dec435 100755 (executable)
--- a/meta-audio-4a-framework/recipes-multimedia/agl-service-audio-4a/files/4a_wait_bt.sh
+++ b/meta-audio-4a-framework/recipes-multimedia/agl-service-audio-4a/files/4a_wait_bt.sh
@@ -64,9 +64,9 @@ function waitloop() {
 
        # wait for bluetooth-service to return something
        while havetime; do
-               res=$(afb-client-demo -d unix:/run/user/$UID/apis/ws/Bluetooth-Manager power true)
+               res=$(afb-client-demo -d unix:/run/user/$UID/apis/ws/Bluetooth-Manager adapter_state true)
                [[ "$res" =~ \"response\":(.*)}$ ]] && res=${BASH_REMATCH[1]}
-               [[ "$res" == '{"power":"on"}' ]] && {
+               [[ "$res" =~ \"powered\":true ]] && {
                        echo "Bluetooth-Manager/power: $res"
                        break
                }