You are reading a single comment by @Robin and its replies. Click here to read the full conversation.
  • chrome://bluetooth-internals

    That's cool - I didn't even realise that was there.

    There's nothing specific I have for debugging BLE on Bangle.js, but you could do:

    On my computer I see something like:

    <BLE> Device Name:       Bangle.js fdaa
    puck.js:362 <BLE> Device ID:         EAjaDdhfFHRyKIhQd+QknA==
    puck.js:362 <BLE> Connected
    puck.js:362 <BLE> Got service
    puck.js:362 <BLE> RX characteristic:{}
    puck.js:362 <BLE> TX characteristic:{}
    puck.js:362 <BLE> Sending "LED1.set();\n"
    puck.js:362 <BLE> Sent
    puck.js:362 <BLE> Received "LED1.set();\r\n=undefi"
    puck.js:362 <BLE> Received "ned\r\n>"
    

    It sounds a little like your computer is never getting to the puck.js:362 <BLE> Got service line - which is where the connected device is scanned for the 'services' is offers. It's possibly something that you could report to the Chrome team.

    Right now if you want to develop then there's still the Web IDE relay.

    You can now use your PC for development, while using your phone as the Bluetooth radio.

    I have plans to make it a bit easier using a proper login system, but right now I'm a bit busy!

  • Wed 2020.03.25

    This is an observation only.

    Ref post #12

    While I found the Puck.debug=3 setting a nice find, I receive a different output on my PC.

    <BLE> ERROR: NotFoundError: User cancelled the requestDevice() chooser.
    puck.js:362 <BLE> Device Name:       Bangle.js 157c
    puck.js:362 <BLE> Device ID:         dz/kKr6HEWvSHQN22FFfTg==
    puck.js:362 <BLE> Connected
    > Puck.debug=3
    

    Tried twice and waited five minutes.


    Opened:

    https://www.espruino.com/Bangle.js+Devel­opment

    These work:
    process.env
    Bangle.buzz();
    E.showMessage("Hello","A Title")

    So in my case am connected and communicating via the WebIDE, but debug=3 doesn't render as suggested in:

    'never getting to the puck.js:362 Got service line - which is where the connected device is scanned for the 'services' is'

About

Avatar for Robin @Robin started