-
-
Notifications
You must be signed in to change notification settings - Fork 125
RegisterAdvertisement dbus errors on bluez 5.50 #69
Comments
Hi David Samples are here https://github.com/muka/go-bluetooth/tree/master/scripts If not the case, can you try to have a setup with 5.50 and run a plain example to see if this is still happening? Let me know so we can investigate further Thanks |
Hi @muka, thanks for helping out! Yes, I have removed the standard bluetooth permissions file and replaced it with the two that are in the
|
Can you have a try with an example from the repository? It could be easier for me to replicate. |
Yes, sure! Just tried the
|
Seems an issue in the configuration of the system / yocto build. To recap, your user is In the code you could try to play with the object name / object path and ensure they match with the one in your config eg.
Nice project the blockchain based candy dispenser, I want one of them! 👍 |
That's a good suggestion, I will try to adjust the object name / object path and see if the policies match. I find it very hard to find information regarding the dbus gatt API and how to use it to expose BLE services. Is there anything I have to keep in mind when selecting I really appreciate your help @muka 🙌
Thank you!
I think we can make that happen |
Hi @muka, just wanted to update you that I wasn't able to identify the problem so far. That's why I've tried downgrading the bluez5 package to 5.47. With that everything works very well. I hope I'll have time again to investigate what changes between 5.47 and 5.50 there were that caused my problems, it won't be a huge priority though. If someone stumbles over this issue and has had experience with |
I will check as on a plain Ubuntu seems to work. Can you share something I
can try, also on a py eventually
Thanks
sent from my phone
…On Fri, Mar 29, 2019, 11:51 David Knezić ***@***.***> wrote:
Hi @muka <https://github.com/muka>, just wanted to update you that I
wasn't able to identify the problem so far. That's why I've tried
downgrading the bluez5 package to 5.47. With that everything works very
well.
I hope I'll have time again to investigate what changes between 5.47 and
5.50 there were that caused my problems, it won't be a huge priority though.
If someone stumbles over this issue and has had experience with
go-bluetooth and bluez 5.50, it would be interesting to learn how it went!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA-VVSt6D1EZnaAswxMnrNKVWPqTCraOks5vbfA6gaJpZM4cFZPb>
.
|
Hi, after upgrading to ubuntu 19.04 I was having the same issue on 5.50. To overcome I updated go deps (just updated in I am closing the issue, please reopen if needed Thank you |
I've managed to integrate
go-bluetooth
and run a GATT service on my Raspberry Pi 3 with Raspbian. (bluez 5.43
)Now I'm trying to get it to work on a yocto based image. (
bluez 5.50
)However, during the call to
RegisterAdvertisement
some things don't seem to work properly, looking at the dbus logs:Full dbus log excerpt
This is my code that triggers these errors: https://github.com/the-lightning-land/sweetd/pull/14/files#diff-2650556a5ae8d1b4833240d0c10b6238R175
Is it possible that something has changed in
bluez
between5.43
and5.50
that leads to theObject does not implement the interface
error? Or could there be something else that might lead to this problem?Help very appreciated!
The text was updated successfully, but these errors were encountered: