-
Notifications
You must be signed in to change notification settings - Fork 452
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
'index out of range' when central tries to unsubscribe #23
Comments
not being able to figure out the deeper reason behind to that issue, I at least modified a piece of code which removes the symptom in
|
@empinator sorry I haven't had a chance to look at your sample code, it's on my list of things to look at. Can you |
->
I know how it is having a project on the side which is fun but still not your day job :-) |
I think I found the problem, when notify is enabled/disabled, the value is not stored as a Buffer. Try changing, l2cap-ble.js line 820:
to
|
@empinator this should be fixed now, with the commit above, let me know if you have any issues. |
awesome, thank you |
I also faced a similar problem but in my case the error was in my code the call to Changing it to
|
Hi,
I wrote a notifier service based on the given examples, but when noble is trying to unsubscribe from bleno's with this command:
characteristic.notify(false, notify._notifyDisable);
bleno is crashing with an 'index out of range'
Peripheral:
Machine: Raspberry PI, Kernel 3.6.11+, Bluez 5.8, GBU521 Dongle
code: http://pastebin.com/bpUBihb5
console output: http://pastebin.com/2qwBY91p
Central:
Machine: Thinkpad T400s, Kernel 3.5.0-45-generic, Bluez 5.8, GBU521 Dongle
code: http://pastebin.com/Esa5xhvz
console output: http://pastebin.com/jZ81CgMM
any idea?
Thanks.
The text was updated successfully, but these errors were encountered: