Antidote on Raspberry Pi

[Ryan Yetter]

Greetings,

Has anyone had any luck getting his to work on a Raspberry Pi 2?  I have healthd running and test_healthd.py running and I keep getting an error in the syslog when it gets to the call to dbus_connection_send_with_reply_and_block in healthd_service.c.  The error that comes up is: MCAP cannot get control PSM: getpeername Transport endpoint not connected.  Now I haven't worked with C in years and python in a while, so after a week, this is as far as I've been able to get with it.  Google searches have come up empty on the particular error and what I have found has not lead to anything useful because they seem to be for very different errors.  I have tried with the bluetooth adapter both plugged into the Pi itself and a powered hub just to make sure it wasn't a power issue.  I'm running Raspbian Wheezy (based on debian 7) on it right now.  I've tried newer versions of Raspbian as well but at the time thought the newer kernel might be causing problems so went back to an earlier version.  I have it working fine on debian 7 and 8 on a pc.  I also tried both the 2.0.0 version on the wiki page and master from the github repo.  All of my attempts lead to the same error in syslog.  Presumably as a result of this error, even if a device is paired that works fine against a PC running the same version, there's no activity recorded in healthd or test_healthd.py output when a reading is taken.  I am assuming this error is preventing the communication from being established.

Any help on this would be very appreciated.

Thanks,

-Ryan

[João Bentes]

Hey, Ryan.

Have you had any evolution in your issue? I've tried to set-up the healthd on the Raspberry Pi 2 (running Raspbian Jessie Lite), but it hasn't work at all. Basically I'm facing the same issue that you did. Here's my log:

DEBUG   <create_health_application in plugin_bluez.c:996>  network:dbus Can't create application

ERROR   <create_health_application in plugin_bluez.c:999> Rejected send message, 2 matched rules; type="method_call", sender=":1.27" (uid=1000 pid=2787 comm="healthd --trans ") interface="org.bluez.HealthManager" member="CreateApplication" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=1881 comm="/usr/lib/bluetooth/bluetoothd ")

Thanks,

Joao

[Ryan Yetter]

I eventually was able to get it to work but I don't remember all of the details.  It was a combination of patches and configuration changes as well as running a combination of specific bluez versions with specific kernel versions.  It was such a fragile situation that I ultimately abandoned it.