Skip to content

Some devices fail setNotify #170

Closed
@wakwak-koba

Description

@wakwak-koba

First of all, there are items to be confirmed before the main subject.

NimBLERemoteDescriptor* desc = getDescriptor(NimBLEUUID((uint16_t)0x2902));
if(desc == nullptr) {
NIMBLE_LOGW(LOG_TAG, "<< setNotify(): Callback set, CCCD not found");
return true;
}

If descriptor 0x2902 does not exist, setNotify() returns true, which is correct, isn't it false?
That's because I found that some devices couldn't get descriptor 0x2902 even though canNotify() == true.

I don't think it's similar to the 16bit uuid problem I had before, but do you have any idea?

The device used for evaluation is this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions