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.

Sign up for GitHub

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

Jump to bottom

TypeError: Object #<Object> has no method 'emit' #297

Open
mone741120 opened this issue Apr 26, 2017 · 4 comments · May be fixed by #369
Open

TypeError: Object #<Object> has no method 'emit' #297

mone741120 opened this issue Apr 26, 2017 · 4 comments · May be fixed by #369
Labels
help wanted

Comments

@mone741120
Copy link

When I set my BLE module as the peripheral mode and run the echo example.

If I subscribe the indication and then unsubscribe it, the following error will occur.

root: /home/ubuntu/test/node_modules/bleno/lib/hci-socket/gatt.js:914
handleAttribute.emit('unsubscribe');
^
TypeError: Object # has no method 'emit'
@pimterry
Copy link

pimterry commented May 5, 2017

I can reproduce this too:

/usr/src/app/node_modules/bleno/lib/hci-socket/gatt.js:914
            handleAttribute.emit('unsubscribe');
                            ^

TypeError: handleAttribute.emit is not a function
    at Gatt.handleWriteRequestOrCommand (/usr/src/app/node_modules/bleno/lib/hci-socket/gatt.js:914:29)
    at Gatt.handleRequest (/usr/src/app/node_modules/bleno/lib/hci-socket/gatt.js:344:23)
    at Gatt.onAclStreamData (/usr/src/app/node_modules/bleno/lib/hci-socket/gatt.js:274:8)
    at emitTwo (events.js:111:20)
    at AclStream.emit (events.js:194:7)
    at AclStream.push (/usr/src/app/node_modules/bleno/lib/hci-socket/acl-stream.js:26:10)
    at BlenoBindings.onAclDataPkt (/usr/src/app/node_modules/bleno/lib/hci-socket/bindings.js:201:21)
    at emitThree (events.js:116:13)
    at Hci.emit (events.js:197:7)
    at Hci.onSocketData (/usr/src/app/node_modules/bleno/lib/hci-socket/hci.js:456:14)

In my case this is reproducible by just connecting, subscribing to 0x1801 and then unsubscribing, with nRF Connect. The unsubscribe immediately throws this error and ends the process for me.

@sandeepmistry sandeepmistry linked a pull request Mar 12, 2018 that will close this issue
Open
@sandeepmistry
Copy link
Collaborator

@mone741120 @pimterry could you please try out PR #369 and provide you feedback.

@pimterry
Copy link

I can't easily, sorry @sandeepmistry, I'm not working on any bluetooth stuff right now, and I don't have any hardware to hand.

@pekoka pekoka mentioned this issue Mar 5, 2021
Closed
@lilerout1590
Copy link

Excuse me for cutting in, I started using bleno recently.

Same error was occured, in my case too.
Then I added code at line between 914-915 that referring to #369.
But error was not fixed it.
Console says "handleAttribute.emit is not a function".
The action of temporarily disapear error is to comment out statement else block at line 913. I know that doesn't become a solution to the root of the problem...

I'm using:
bleno Version 0.5.0
blueZ Version 5.50
Linux version 4.19.75+

Might be something is missing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check if attribute handle supports emit before calling noble/bleno
4 participants
@sandeepmistry @pimterry @mone741120 @lilerout1590