Skip to content
This repository was archived by the owner on Feb 20, 2025. It is now read-only.
This repository was archived by the owner on Feb 20, 2025. It is now read-only.

Getting stuck when acquiring target "noble: unknown peripheral null connected!" #60

@ItIsMe4894

Description

@ItIsMe4894

I'm trying to connect to a smart lock I've and I'm facing the exact same error as in issue #2 . After the whole set up is up and running, I choose the lock from within the web interface the Bluetooth button aspect doesn't change. When I look into the hose I get the following error:

noble: unknown peripheral null connected!

1

I'm using version 1.1.11 on both the core and the proxy. I'm using an external Bluetooth dongle for the host and it is working fine. And using the onboard Bluetooth on the core and it is working fine as well. By working fine means I was able to connect to them and they were both UP RUNNING.

Getting this on the core:

2

@virtualabs said that he was able to reproduce it 4 years ago and it was patched in v1.1.3 but for some reason, I'm still getting this error. It is driving me nuts, please help!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions