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

Could not connect to any Plejd device. Starting reconnect loop... #305

Open
FredrikVaaland opened this issue Jul 8, 2024 · 5 comments
Open

Comments

@FredrikVaaland
Copy link

What is wrong? Any ideas?

at handleMessage (/plejd/node_modules/dbus-next/lib/bus.js:101:11)
at EventEmitter. (/plejd/node_modules/dbus-next/lib/bus.js:151:9)
at EventEmitter.emit (events.js:314:20)
at /plejd/node_modules/dbus-next/lib/connection.js:116:14
at Socket. (/plejd/node_modules/dbus-next/lib/message.js:63:9)
at Socket.emit (events.js:314:20)
at emitReadable_ (_stream_readable.js:557:12)
at processTicksAndRejections (internal/process/task_queues.js:83:21)
2024-07-08 15:31:28 ERR [plejd-ble] Could not connect to any Plejd device. Starting reconnect loop...
2024-07-08 15:31:28 INF [plejd-ble] Starting reconnect loop...
2024-07-08 15:31:28 WRN [plejd-ble] Tried reconnecting 10 times. Will power cycle the BLE adapter now...
2024-07-08 15:32:03 INF [device-comm] Bluetooth reconnecting...
2024-07-08 15:32:08 INF [plejd-ble] Reconnecting BLE...
2024-07-08 15:32:08 INF [plejd-ble] init()
2024-07-08 15:32:13 INF [plejd-ble] BLE init done, waiting for devices.
2024-07-08 15:32:15 INF [plejd-ble] Device discovery done, found 1 Plejd devices
2024-07-08 15:32:15 INF [plejd-ble] Connecting to /org/bluez/hci0/dev_F7_2A_C5_DD_4E_FB
2024-07-08 15:32:16 WRN [plejd-ble] Unable to connect. le-connection-abort-by-local
DBusError: le-connection-abort-by-local
at methodReturnHandlers. (/plejd/node_modules/dbus-next/lib/bus.js:343:27)
at handleMessage (/plejd/node_modules/dbus-next/lib/bus.js:101:11)
at EventEmitter. (/plejd/node_modules/dbus-next/lib/bus.js:151:9)
at EventEmitter.emit (events.js:314:20)
at /plejd/node_modules/dbus-next/lib/connection.js:116:14
at Socket. (/plejd/node_modules/dbus-next/lib/message.js:63:9)
at Socket.emit (events.js:314:20)
at emitReadable
(_stream_readable.js:557:12)
at processTicksAndRejections (internal/process/task_queues.js:83:21)
2024-07-08 15:32:16 ERR [plejd-ble] Could not connect to any Plejd device. Starting reconnect loop...
2024-07-08 15:32:16 INF [plejd-ble] Starting reconnect loop...
2024-07-08 15:32:16 INF [device-comm] Bluetooth reconnecting...
2024-07-08 15:32:21 INF [plejd-ble] Reconnecting BLE...
2024-07-08 15:32:21 INF [plejd-ble] init()
2024-07-08 15:32:26 INF [plejd-ble] BLE init done, waiting for devices.
2024-07-08 15:32:28 INF [plejd-ble] Device discovery done, found 1 Plejd devices
2024-07-08 15:32:28 INF [plejd-ble] Connecting to /org/bluez/hci0/dev_F7_2A_C5_DD_4E_FB
2024-07-08 15:32:29 WRN [plejd-ble] Unable to connect. le-connection-abort-by-local
DBusError: le-connection-abort-by-local
at methodReturnHandlers. (/plejd/node_modules/dbus-next/lib/bus.js:343:27)
at handleMessage (/plejd/node_modules/dbus-next/lib/bus.js:101:11)
at EventEmitter. (/plejd/node_modules/dbus-next/lib/bus.js:151:9)
at EventEmitter.emit (events.js:314:20)
at /plejd/node_modules/dbus-next/lib/connection.js:116:14
at Socket. (/plejd/node_modules/dbus-next/lib/message.js:63:9)
at Socket.emit (events.js:314:20)
at emitReadable
(_stream_readable.js:557:12)
at processTicksAndRejections (internal/process/task_queues.js:83:21)
2024-07-08 15:32:29 ERR [plejd-ble] Could not connect to any Plejd device. Starting reconnect loop...
2024-07-08 15:32:29 INF [plejd-ble] Starting reconnect loop...
2024-07-08 15:32:29 INF [device-comm] Bluetooth reconnecting...
2024-07-08 15:32:34 INF [plejd-ble] Reconnecting BLE...
2024-07-08 15:32:34 INF [plejd-ble] init()
2024-07-08 15:32:39 INF [plejd-ble] BLE init done, waiting for devices.
2024-07-08 15:32:41 INF [plejd-ble] Device discovery done, found 1 Plejd devices
2024-07-08 15:32:41 INF [plejd-ble] Connecting to /org/bluez/hci0/dev_DE_A6_67_C0_13_1B
2024-07-08 15:32:42 WRN [plejd-ble] Unable to connect. le-connection-abort-by-local
DBusError: le-connection-abort-by-local
at methodReturnHandlers. (/plejd/node_modules/dbus-next/lib/bus.js:343:27)
at handleMessage (/plejd/node_modules/dbus-next/lib/bus.js:101:11)
at EventEmitter. (/plejd/node_modules/dbus-next/lib/bus.js:151:9)
at EventEmitter.emit (events.js:314:20)
at /plejd/node_modules/dbus-next/lib/connection.js:116:14
at Socket. (/plejd/node_modules/dbus-next/lib/message.js:63:9)
at Socket.emit (events.js:314:20)
at emitReadable
(_stream_readable.js:557:12)
at processTicksAndRejections (internal/process/task_queues.js:83:21)
2024-07-08 15:32:42 ERR [plejd-ble] Could not connect to any Plejd device. Starting reconnect loop...
2024-07-08 15:32:42 INF [plejd-ble] Starting reconnect loop...
2024-07-08 15:32:42 INF [device-comm] Bluetooth reconnecting...
2024-07-08 15:32:47 INF [plejd-ble] Reconnecting BLE...
2024-07-08 15:32:47 INF [plejd-ble] init()
2024-07-08 15:32:53 INF [plejd-ble] BLE init done, waiting for devices.
2024-07-08 15:32:55 INF [plejd-ble] Device discovery done, found 1 Plejd devices
2024-07-08 15:32:55 INF [plejd-ble] Connecting to /org/bluez/hci0/dev_F7_2A_C5_DD_4E_FB
2024-07-08 15:32:56 WRN [plejd-ble] Unable to connect. le-connection-abort-by-local
DBusError: le-connection-abort-by-local

@jn73
Copy link

jn73 commented Aug 22, 2024

I have exactly the same problem. Raspberry 5

@jn73
Copy link

jn73 commented Aug 28, 2024

Looks like it will connect eventually (usually after a couple of hours) if I just leave the add-on running.

@FredrikVaaland
Copy link
Author

FredrikVaaland commented Aug 29, 2024

Im lost, any chance you can give me a short discription of your set up?

Now I got this:

Error: Failed to start discovery. Make sure no other add-on is currently scanning.
at PlejBLEHandler._startGetPlejdDevice (/plejd/PlejdBLEHandler.js:445:13)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2024-08-29 13:46:13 INF [device-comm] Bluetooth reconnecting...
2024-08-29 13:46:18 INF [plejd-ble] Reconnecting BLE...
2024-08-29 13:46:18 INF [plejd-ble] init()
2024-08-29 13:46:20 ERR [plejd-ble] Discovery timeout elapsed, no devices found. Starting reconnect loop...
2024-08-29 13:46:20 INF [plejd-ble] Starting reconnect loop...
2024-08-29 13:46:23 ERR [plejd-ble] Failed to start discovery. Operation already in progress
DBusError: Operation already in progress
at methodReturnHandlers. (/plejd/node_modules/dbus-next/lib/bus.js:343:27)
at handleMessage (/plejd/node_modules/dbus-next/lib/bus.js:101:11)
at EventEmitter. (/plejd/node_modules/dbus-next/lib/bus.js:151:9)
at EventEmitter.emit (events.js:314:20)
at /plejd/node_modules/dbus-next/lib/connection.js:116:14
at Socket. (/plejd/node_modules/dbus-next/lib/message.js:63:9)
at Socket.emit (events.js:314:20)
at emitReadable
(_stream_readable.js:557:12)
at processTicksAndRejections (internal/process/task_queues.js:83:21)
2024-08-29 13:46:23 INF [plejd-ble] If you continue to get "operation already in progress" error, you can try power cycling the bluetooth adapter. Get root console access, run "bluetoothctl" => "power off" => "power on" => "exit" => restart addon.
2024-08-29 13:46:23 WRN [plejd-ble] Failed reconnecting. Failed to start discovery. Make sure no other add-on is currently scanning.

@jn73
Copy link

jn73 commented Sep 4, 2024

Sorry for the late reply :-(

I've seen those logs also (DBusError: Operation already in progress) and the "Make sure no other add-on is currently scanning."-line.

Now I just restarted my Raspberry Pi 5 and seeing this:

2024-09-04 21:09:47 ERR [plejd-ble] Could not connect to any Plejd device. Starting reconnect loop...
2024-09-04 21:09:47 INF [plejd-ble] Starting reconnect loop...
2024-09-04 21:09:47 INF [device-comm] Bluetooth reconnecting...
2024-09-04 21:09:52 INF [plejd-ble] Reconnecting BLE...
2024-09-04 21:09:52 INF [plejd-ble] init()
2024-09-04 21:09:57 INF [plejd-ble] BLE init done, waiting for devices.
2024-09-04 21:09:59 INF [plejd-ble] Device discovery done, found 1 Plejd devices
2024-09-04 21:09:59 INF [plejd-ble] Connecting to /org/bluez/hci0/dev_DD_ED_05_FB_B1_62
2024-09-04 21:09:59 WRN [plejd-ble] Unable to connect.  le-connection-abort-by-local
DBusError: le-connection-abort-by-local
    at _methodReturnHandlers.<computed> (/plejd/node_modules/dbus-next/lib/bus.js:343:27)
    at handleMessage (/plejd/node_modules/dbus-next/lib/bus.js:101:11)
    at EventEmitter.<anonymous> (/plejd/node_modules/dbus-next/lib/bus.js:151:9)
    at EventEmitter.emit (events.js:314:20)
    at /plejd/node_modules/dbus-next/lib/connection.js:116:14
    at Socket.<anonymous> (/plejd/node_modules/dbus-next/lib/message.js:63:9)
    at Socket.emit (events.js:314:20)
    at emitReadable_ (_stream_readable.js:557:12)
    at processTicksAndRejections (internal/process/task_queues.js:83:21)
2024-09-04 21:09:59 ERR [plejd-ble] Could not connect to any Plejd device. Starting reconnect loop...
2024-09-04 21:09:59 INF [plejd-ble] Starting reconnect loop...
2024-09-04 21:09:59 WRN [plejd-ble] Tried reconnecting 320 times. Will power cycle the BLE adapter now...
2024-09-04 21:10:35 INF [device-comm] Bluetooth reconnecting...

I'm pretty sure it will reconnect within a few hours and then work fine until next restart.

My system is pretty basic. Raspberry Pi 5 and a SkyConnect (which shouldn't have anything to do with this).

@jn73
Copy link

jn73 commented Sep 9, 2024

I saw a log warning from the "Rasperry Pi Power Supply Checker" that my system is "Under-voltage". I checked it up and realize that i need a more powerful PSU. I ordered the standard rasperry adapter but haven't received it yet. Not really counting on this to fix it, but i read that it could have some impact on buses etc. Just thought i should point out that it wasn't the standard raspberry pi setup after all.

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

2 participants