ERROR: Error: Cannot find module 'bluetooth-hci-socket'

[BChen61]

Hi all,

I created a new project on Intel XDK IoT edison which used BLE-ibeacon template

And I did step by step from the tutorial:

https://software.intel.com/en-us/creating-a-bluetooth-low-energy-ibeacon-application https://software.intel.com/en-us/creating-a-bluetooth-low-energy-ibeacon-application

But I got a error message

ERROR: Error: Cannot find module 'bluetooth-hci-socket'

Can anyone help me to fix it up?

Thanks

[Pedro_M_Intel]

Hello BrianPHChen,

Did you make sure update your board's libraries as well as the XDK daemon? Let us know more about your environment, which image are you using and which version of the XDK are using?

Peter.

[BChen61]

Hi Peter,

My environment is as below

Thanks

[mkawa8]

I think workaround.

1. Delete dependenes in package.json(noble and bleno)

2. Enter Edison terminal as ssh. and run the command below.

root@edison~:npm install async

root@edison~:npm install bleno

root@edison~:npm intall noble

3. Deleate npm nodule from /node_app_slot/node_module

root@edison~:cd /node_app_slot

root@edison~:rm -rf bleno

root@edison~:rm -rf noble

4. May be you can running the application.

I encount same problem but i can try this workaround. And running application with noble and bleno

[BChen61]

Hi masato-ka

I tried your way to run the application.

Although it can run without error, I can't see it on ibeacon scanning app

Thanks

Brian

[BChen61 · Accepted solution]

Hi all,

I found a weird workaround(?)

If I tried to connect to edison by LightBlue which is a Mac app that can access BLE device and get the service

then another error will be happened as below

and after this error. I run the ibeacon app again, it will show on the ibeacon scanning app successfully

so weird~

Brian

[Pedro_M_Intel]

That is in fact very weird, however I'm glad to hear that you were able to find a solution to your issue.

Peter.

[idata]

I'm actually having this same issue. I've managed to resolve it by

1. sshing into my edison
2. cd /node_app_slot
3. npm install bleno

(effectively reinstalling bleno in the place the xdk uploads the program.)

What's really strange is if I look at the bleno folder that the xdk built, and the one that the above steps produced, they're very different.

XDK:

On Edison after NPM:

[EMass1]

I am having the same issue and was able to work around it with steps similar to asp55.

@Intel_Peter do you have any additional insight into this issue? Seems bad to have this bug with an out of the box example.