Added a 4a-info script use to test if 4a can work

Test various things to check if 4a can work in this environment.

Change-Id: Ica4b739d7e8c6401db05a3b9b4d6ef9048ca1002
Signed-off-by: Loïc Collignon <loic.collignon@iot.bzh>

1 files changed, 23 insertions, 0 deletions

diff --git a/bin/4a-api b/bin/4a-api
new file mode 100755
index 0000000..4a26121
--- /dev/null
+++ b/bin/4a-api
@@ -0,0 +1,23 @@
+#!/bin/bash
+
+WS4A=unix:/run/user/0/apis/ws/ahl-4a
+
+afb-client-demo -H -d $WS4A get_roles ""
+
+# commandes HAL manager:
+# 4a-hal-manager loaded
+# 4a-hal-manager loaded { "verbose": true } <= +metadata
+# 4a-hal-manager loaded { "all": true } <= hals avec un json
+# 4a-hal-manager loaded { "all": true, "verbose":true }
+
+# open/close  multimedia
+#afb-client-demo -H -d $WS4A << EOF
+#multimedia { "action":"open" }
+#multimedia { "action":"close" }
+#EOF
+
+# volume  multimedia
+#afb-client-demo -H -d $WS4A << EOF
+#multimedia { "action":"open" }
+#multimedia { "action":"close" }
+#EOF