Replies: 4 comments 11 replies
-
|
You've done well, unfortunately you've run into a missing API. There currently is not a way to differentiate between characteristics that have the same uuid and the library will just provide the first one found. |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
it looks like you have some mismatched files, try deleting the lib and reinstalling |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Ryan,
There's a received error response from the Amazon remote in the Samsung log
that I posed at line 1506. Maybe provides a clue? I have no idea but I've
attached the log if it helps.
Regards,
Jonathan
…On Wed, Nov 5, 2025 at 9:24 PM Ryan Powell ***@***.***> wrote:
I've not seen that return code before, I'll have to look into that,. The
crash is caused by your code trying to use a characteristic that wasn't
found (nullptr).
—
Reply to this email directly, view it on GitHub
<#1050 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2FEVB5OLW6NRNX6XWWKTEL33JTJVAVCNFSM6AAAAACJO5CUEWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOBYGUYTIMY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I've tried it with a cheap Amazon TV clone and it seems to be loping the
discovery and removing the top characteristics from the top of the list:
```
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 46
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 47
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 48
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 49
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 50
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 14 handle: -1
D NimBLERemoteCharacteristic: << Descriptor Discovery
D NimBLERemoteCharacteristic: << retrieveDescriptors(): found 9 descriptors.
D NimBLERemoteCharacteristic: >> retrieveDescriptors() for
characteristic: 0x2a4d
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 45
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 46
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 47
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 48
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 49
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 50
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 14 handle: -1
D NimBLERemoteCharacteristic: << Descriptor Discovery
D NimBLERemoteCharacteristic: << retrieveDescriptors(): found 6 descriptors.
D NimBLERemoteCharacteristic: >> retrieveDescriptors() for
characteristic: 0x2a4d
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 49
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 50
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 14 handle: -1
D NimBLERemoteCharacteristic: << Descriptor Discovery
D NimBLERemoteCharacteristic: << retrieveDescriptors(): found 2 descriptors.
D NimBLERemoteService: >> retrieveCharacteristics()
D NimBLERemoteService: Characteristic Discovery >> status: 0 handle: 52
D NimBLERemoteService: Characteristic Discovery >> status: 0 handle: 55
D NimBLERemoteService: Characteristic Discovery >> status: 0 handle: 58
D NimBLERemoteService: Characteristic Discovery >> status: 0 handle: 61
D NimBLERemoteService: Characteristic Discovery >> status: 14 handle: -1
D NimBLERemoteService: << Characteristic Discovery
D NimBLERemoteService: << retrieveCharacteristics()
D NimBLERemoteCharacteristic: >> retrieveDescriptors() for
characteristic: fe151501-5e8d-11e6-8b77-86f30ca893d3
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 54
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 55
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 56
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 3240
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 0 handle: 35703
D NimBLERemoteCharacteristic: Descriptor Discovery >> status: 10 handle: -1
D NimBLERemoteCharacteristic: << Descriptor Discovery
E NimBLERemoteCharacteristic: << retrieveDescriptors(): failed: rc=10
```
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I'm way out of my depth but thick I'm so close to getting this to work.
I want to control a ESP WROOM 32 with a FireTV BLE remote.
I've used Wireshark to read a debug log from my phone and also used nRF Connect to try to work out the UUIDs, Services, Characteristics and Handles used. I believe the phone connects to the remote then writes "0100" to Characteristics with Handles:
0x005f
0x0063
0x0067
0x006b
0x0078
Then setup Armbian on my T95Z Plus TV box to connect to the remote and try to work out the button presses with btmon and gatttool:
All the previous mentioned Handles have the same UUID "00002a4d-0000-1000-8000-00805f9b34fb".
I've used example NimBLE_Client.ino and copied the Service and Characteristic UUIDs in here:
I've enabled debug in Arduino Tools>Core Debug Level>Debug and reflashed the ESP32:
Can someone please tell me if "!pChr->subscribe(true, notifyCB)" subscribes to the Characteristic (pChr = pSvc->getCharacteristic("00002a4d-0000-1000-8000-00805f9b34fb")) for all the handles for button press notifications or does it have to subscribe to each handle separately and if so how can this be done?
Appreciate any help as I've spent ages stabbing in the dark. :)
Beta Was this translation helpful? Give feedback.
All reactions