• Re: handling multiple BT adapters,

    We've started to think about how to proceed at https://bugs.chromium.org/p/chromium/issues/detail?id=635111

    In the mean time, as suggested by @Gordon, I would simply make hci1 default for now with the select command from bluetoothctl and restart Chrome. Hopefully this will help:

    $ bluetoothctl 
    [NEW] Controller 12:34:56:12:34:56 Foo [default]
    [NEW] Controller 12:34:56:12:34:57 Bar
    [bluetooth]# list
    Controller 12:34:56:12:34:56 Foo [default]
    Controller 12:34:56:12:34:57 Bar
    [bluetooth]# select 12:34:56:12:34:57 
    [bluetooth]# list
    Controller 12:34:56:12:34:56 Foo
    Controller 12:34:56:12:34:57 Bar [default]
    
  • Yeah.. I did that.. I even managed to connect to the PuckJS using bluetoothctl.

    [bluetooth]# devices
    Device F8:37:BB:11:74:A7 Puck.js 74a7
    [bluetooth]# connect F8:37:BB:11:74:A7
    Attempting to connect to F8:37:BB:11:74:A7
    [CHG] Device F8:37:BB:11:74:A7 Connected: yes
    Connection successful

    Sadly, Chrome like the braindead piece of software it is does not see that there is a device already connected to the default device and continues to try and probe hci0 and seeing nothing.

    I have tried building the IDE from git and got a little further by just removing the requirement of winnus from the package.json file.

    it 'installed' fine. But when I do npm start

    npm start
    
    espruino-web-ide@0.65.11 start /home/user/devel/git/EspruinoWebIDE
     nw .
    
    
      Usage: nw-gyp <command> [options]
    
      where <command> is one of:
        - build - Invokes `make` and builds the module
        - clean - Removes any generated build files and the "out" dir
        - configure - Generates a Makefile for the current module
        - rebuild - Runs "clean", "configure" and "build" all at once
        - install - Install node development files for the specified node version.
        - list - Prints a listing of the currently installed node development files
        - remove - Removes the node development files for the specified version
    
    nw-gyp@3.4.0  /usr/local/lib/node_modules/nw-gyp
    node@4.6.1
    

    However, now I have some sort of weird incompatibility with node-gyp and whatever build file it uses.

    nw configure .
    gyp info it worked if it ends with ok
    gyp info using nw-gyp@3.4.0
    gyp info using node@4.6.1 | linux | x64
    gyp ERR! configure error 
    gyp ERR! stack Error: Invalid version number: undefined
    gyp ERR! stack     at getNodeDir (/usr/local/lib/node_modules/nw-gyp/lib/configure.js:71:25)
    gyp ERR! stack     at /usr/local/lib/node_modules/nw-gyp/lib/configure.js:43:7
    gyp ERR! stack     at /usr/local/lib/node_modules/nw-gyp/lib/configure.js:460:9
    gyp ERR! stack     at ChildProcess.exithandler (child_process.js:204:7)
    gyp ERR! stack     at emitTwo (events.js:87:13)
    gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
    gyp ERR! stack     at maybeClose (internal/child_process.js:829:16)
    gyp ERR! stack     at Socket.<anonymous> (internal/child_process.js:319:11)
    gyp ERR! stack     at emitOne (events.js:77:13)
    gyp ERR! stack     at Socket.emit (events.js:169:7)
    gyp ERR! System Linux 4.8.0-2-amd64
    gyp ERR! command "/usr/bin/nodejs" "/usr/local/bin/nw" "configure" "."
    gyp ERR! cwd /home/user/devel/git/EspruinoWebIDE
    gyp ERR! node -v v4.6.1
    gyp ERR! nw-gyp -v v3.4.0
    gyp ERR! not ok 
    

    To be honest I would feel happier if I was trying to debug a C++ program because nodejs gives me a headache.

    sighs

About

Avatar for François @François started