connection initiation error: Method "CreateChannel"

[tech.req...@googlemail.com]

Hello,
posted the previously message in the forum. Now I have installed Ubuntu 14.04 LTS and seems to be near but ...
I have installed antidote-master on Ubuntu 14.04 LTS

- libtool
- bluez 4.101
- libdbus-1-dev
- libdbus-glib-1-dev
- libusb-1.0-0-dev

I have paired the two bluetooth devices,  manager seems to have started correctly.

When I start the agent I get the following error...

.../antidote-master/apps$ ./sample_bt_agent 00:1A:7D:DA:71:13

IEEE 11073 sample agent
DEBUG   <agent_init in agent.c:133> Agent Initialization
DEBUG   <agent_start in agent.c:369> Agent starting...
DEBUG   <init in plugin_bluez.c:1287> Starting BlueZ link...
DEBUG   <connect_adapter in plugin_bluez.c:876> connecting adapter: /org/bluez/673/hci0
DEBUG   <connect_adapter in plugin_bluez.c:916> Getting known devices list
DEBUG   <connect_device_signals in plugin_bluez.c:782> device to be connected: /org/bluez/673/hci0/dev_00_1A_7D_DA_71_13
DEBUG   <get_device_addr in plugin_bluez.c:303>     Device address is 00:1A:7D:DA:71:13
DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_1
*** Device rediscovered
Main loop started
DEBUG   <plugin_bluez_connect_cb in plugin_bluez.c:1535> connection initiation error: Method "CreateChannel" with signature "os" on interface "org.bluez.HealthDevice" doesn't exist

Where could be the problem?

Thanks in advance!
rsp

[José Luís]

Hi,

Are you running antidote healthd as manager? If so, are you also running test_healthd.py to register the health endpoints?

Could you provide the log entries for the manager?

[]'s

--
You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

José Luís do Nascimento
Signove - Seamless Technologies for Life!
Home page: http://www.signove.com

[michaels...@googlemail.com]

Dear all,

I have already posted in another topic of the forum, that the problem seems to be the generic Bluetooth kernel driver in Ubuntu since Ubuntu 14.04 - it simply doesn't work for HDP. Unfortunately till now I could not figure out why. Testing HDP with the test-health script from the bluez-stack doesn't work in Ubuntu. After that I have tried the test-health script in Ubuntu 15.10 which uses the recent version of bluez (bluez 5.38). The test-health script from the bluez stack doesn't work here too. So I have tried another distro: manjaro. Surprisingly, the test-health script worked here out-of-the box. Another thing I have tried, is to use the recent bluez version compiled from source in Ubuntu 15.10. It doesn't work either. So it seems to be really a problem of the generic Bluetooth kernel driver in Ubuntu and not a problem with bluez.

 

So for me, I have ported the bluez-plugin of antidote to the recent version 5 of bluez because this works under Manjaro or Debian in recent versions. But the port does not work anymore with bluez 4.x. I will add eventually a configure-switch to be able to choose between the different bluez-plugin versions and commit my changes to the andidote git repository.

If you still want to use Ubuntu, you must use Ubuntu 12.04 with bluez 4.98. This works out-of-the box. But it's quite old and the support is running out.

Best regards

Michael Schmidt

[tech.req...@googlemail.com]

Yes I have,
this is the log from manager healthd

.../antidote-master/apps$ healthd
DEBUG   <manager_init in manager.c:162> Manager Initialization
DEBUG   <ext_configurations_create_environment in extconfigurations.c:128> mkdirp status 0
DEBUG   <ext_configurations_create_environment in extconfigurations.c:135> Configuration directory created
DEBUG   <ext_configurations_create_environment in extconfigurations.c:147> Configuration file created
DEBUG   <ext_configurations_load_configurations in extconfigurations.c:278> Zero-sized ext config buffer
DEBUG   <manager_start in manager.c:465> Manager starting...

DEBUG   <init in plugin_bluez.c:1287> Starting BlueZ link...

DEBUG   <connect_adapter in plugin_bluez.c:876> connecting adapter: /org/bluez/484/hci0
DEBUG   <connect_adapter in plugin_bluez.c:916> Getting known devices list
DEBUG   <connect_device_signals in plugin_bluez.c:782> device to be connected: /org/bluez/484/hci0/dev_00_15_83_3D_0A_57
DEBUG   <get_device_addr in plugin_bluez.c:303>     Device address is 00:15:83:3D:0A:57
DEBUG   <srv_object_class_init in healthd_ipc_dbus.c:1142>  
DEBUG   <srv_configurepassive in healthd_ipc_dbus.c:228> Agent: /com/signove/health/agent/2536
DEBUG   <srv_configurepassive in healthd_ipc_dbus.c:242> Data type: 1004
DEBUG   <srv_configurepassive in healthd_ipc_dbus.c:242> Data type: 1007
DEBUG   <srv_configurepassive in healthd_ipc_dbus.c:242> Data type: 1029
DEBUG   <srv_configurepassive in healthd_ipc_dbus.c:242> Data type: 100f
DEBUG   <get_agent_proxy in healthd_ipc_dbus.c:433> get_agent_proxy
DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_1
DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_2
DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_3
DEBUG   <create_health_application in plugin_bluez.c:1101> Created health application: /org/bluez/health_app_4

and from the python script

...python test_healthd.py
Starting...
Configuring...
Waiting...

but I read what Michael posted ...  :-(

[tech.req...@googlemail.com]

I am using now Lubuntu 12.04 on my laptop and  Lubuntu 12.04 VMWare on another one and is working properly!

Thanks