Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewritten version todo's #9

Open
xrucka opened this issue Dec 10, 2018 · 3 comments
Open

Rewritten version todo's #9

xrucka opened this issue Dec 10, 2018 · 3 comments

Comments

@xrucka
Copy link
Owner

xrucka commented Dec 10, 2018

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.
  2. Get rid of development code wrappers.
@xrucka
Copy link
Owner Author

xrucka commented Feb 14, 2019

  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
Copy link
Owner Author

xrucka commented Feb 14, 2019

  1. Move configuration out of binding to (perhaps) service?

@xrucka
Copy link
Owner Author

xrucka commented Feb 23, 2019

  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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant