On Monday, December 12, 2022 15:49 CET, Bastien Nocera <hadess@xxxxxxxxxx> wrote: > On Mon, 2022-12-12 at 14:32 +0100, Arthur Crepin-Leblond wrote: > > Hello, > > > > I am trying to expose the device disconnect reason over D-Bus and the > > most elegant way I found was to subscribe to the adapter notify > > callback that gives the reason as an argument. > > Any reason why this can't be a signal with the reason as an argument? I chose the easy path by copying the existing code for the device properties that get updated like the "Connected" or "ServicesResolved". I am not too familiar with BlueZ signals other than PropertiesChanged, InterfacesRemoved/Added. What would you have in mind? And apologies in advance, it's my first time submitting here, I do not have an advanced knowledge of the BlueZ internals.
