search

xrucka / bluetooth-manager-dbus

Bluetooth transport implementation bypassing tinyb and using directly dbus binding instead
Apache License 2.0
1 stars 2 forks source link

Rewritten version todo's #9

Open xrucka opened 5 years ago

xrucka commented 5 years ago

So far, I was able to run the transport for cuple of weeks, encountering: 1) Sometimes, something dies (in BlueZ, i believe - will be probably speciffic to my system). Binding therefore seems to hang. 2) Transport does not correctly handle BlueZ restarts - notifications do not reattach. 3) Get rid of development code wrappers.

xrucka commented 5 years ago
  1. Find a way to limit the number of intermediate objects created (performance).

(numerous instances of following for every object created) [INFO ] [sport.dbus.proxies.NativeBluezDevice] - Created bluez device proxy for /org/bluez/hci3/dev_E0_E5_CF_E5_4E_60

xrucka commented 5 years ago
  1. Move configuration out of binding to (perhaps) service?
xrucka commented 5 years ago
  1. When connection to dbus is reestablished, proper notifications for devices held should be fired to restore the state. This becomes important in multi-machine setup with dbus-proxy + socat + socat + openhab when network gets disconnected.