Right now kdeconnect provides 2 set of dbus api: /module/kdeconnect which governs adding/removing devices and multiple /modules/kdeconnect/devices/123456 where 123456 is phone-specific id which is unpredictable This renders automated code generation tools based on dbus introspection unusable. Would be great to have stable dbus api available under /modules/kdeconnect/devices with the same methods (sendPing(), isPaired(), charge() etc) but with one additional parameter indicating device id: "String id". This would greatly simplify using kdeconnect dbus api. Reproducible: Always
It's not a bad idea, but we are not going to do BOTH approaches and we won't break backwards compatibility for this. Scripting becomes a bit more convoluted the way it is, but it is still possible since you can discover all subpaths withing a path in dbus.