Search results for:

This may be a tough one to get to the bottom of since it might only happen once a week (sometimes more sometimes less).

I have a Puck that I use as a Bluetooth "button". Pressing the button causes it to advertise "on" or "off". Then I have a simple NodeRed setup that reacts to the change and turns on/off a light.

However at random intervals on the Node Red RaspberryPi, Noble crashes and takes down EspruinoHub. I've tried updating to latest EspruinoHub master a few times but that hasn't helped. Console output below.

I know it's probably more a bug for the Noble author but I wondered if anything obvious jumped out or if there was more debug output I could generate?

30:e1:37:00:43:1d - ? (RSSI -65)
48:d6:d5:58:3b:db - Office TV (RSSI -64)
  fe9f => {"type":"Buffer","data":[0,0,0,0,0,0,0,0­,0,0,0,0,0,0,0,0,0,0,0,0]}
  fea0 => {"type":"Buffer","data":[3,250,143,202,1­50,110,139,98,32,32,32,15,255]}
98:7b:f3:96:06:28 - YUNMAI-SIGNAL-H1US (RSSI -82)
c0:28:8d:37:ae:15 -  (RSSI -82)
c5:2e:b9:d5:27:a3 - Im On A Call Switch (RSSI -73)
  ffff => {"level":0}

buffer.js:977
    throw new RangeError('Index out of range');
    ^

RangeError: Index out of range
    at checkOffset (buffer.js:977:11)
    at Buffer.readUInt16LE (buffer.js:1023:5)
    at Gap.onHciLeAdvertisingReport (/home/pi/EspruinoHub/node_modules/noble­/lib/hci-socket/gap.js:149:31)
    at emitMany (events.js:147:13)
    at Hci.emit (events.js:224:7)
    at Hci.processLeAdvertisingReport (/home/pi/EspruinoHub/node_modules/noble­/lib/hci-socket/hci.js:651:10)
    at Hci.processLeMetaEvent (/home/pi/EspruinoHub/node_modules/noble­/lib/hci-socket/hci.js:608:10)
    at Hci.onSocketData (/home/pi/EspruinoHub/node_modules/noble­/lib/hci-socket/hci.js:479:12)
    at emitOne (events.js:116:13)
    at BluetoothHciSocket.emit (events.js:211:7)
pi@raspberrypi:~/EspruinoHub $ ./start.sh 

Sorry, wrong forum. Can't see how to delete/move tho.

Great to see them embracing Espruino!

https://www.cnx-software.com/2018/02/17/­stmicro-introduces-two-stm32-discovery-k­its-with-2g-3g-or-4g-lte-iot-cat-m1-nb1-­connectivity/

https://blog.st.com/p-l496g-cell01-p-l49­6g-cell02-cellular-discovery-kit/

Thanks Gordon. Hadn't realised that about Eddystone.

I suspect the issues were a mix of user error and the start.sh script not updating the names displayed. When it refreshes, it spots new devices ok, but doesn't seem to switch from "?" to actual name (e.g. when I tried NRF.SetAdvertising to try and force a name whilst trying to figure out what was going wrong).

Still not sure why the Pi and Windows with Bluetooth polyfill were showing hex ids instead of names.

So maybe a bunch of red herrings.

It's fantastic to have this now. All my Windows issues are a thing of the past!

Not 100% sure I've got a consistent answer but relatively new 1v95 on both nRF device and badge causes the Hub to see them with proper names. Everything seems to be working now. Could be all user error so thanks for your patience Gordon!

I tried an old 1v95 on the generic nRF device. It still appears as "?". When I try NRF.setAdvertising({},{name:"Puck 2"}) it stays as "?" on EspruinoHub but switches to the new name in the IDE on OSX.

I've also tried some of the very new 1v95 nrf52832 builds but they refuse to connect at all (unrelated to this thread, I just noticed it last weekend).

I'll try updating the badge now to see how that fares with latest 1v95.

Progress! The Puck update to 1v95.153 caused it to be correctly identified by EspruinoHub (once) and it appeared as a connectable device on Windows. Unfortunately then it disappeared again and was just showing "?" for name, as above. Reboot of Pi didn't help.

Then I did a full reset of the Puck and now all seems to be fine. Running Led on/off as we speak :-)

But there is definitely some issue with names. I just tried a NodeConf EU badge running a pretty old version of the firmware from the event and it's showing up as "?" too. But a Garmin that came into the room immediately showed up in the Hub logs with the correct name.

Does this new approach only work with 1v95.150+?

I did all of that (and disabled Web Bluetooth and rebooted). I also re-ran setcap to be sure.

I also stopped the Hub service and ran it manually. It's showing 3 BLE devices including the two Espruino ones. But nothing appearing in IDE.

Do I have to add anything to the IDE config to make the websockets-based "ports" appear?

Or could it be related to the Pi not being able to see the Puck's name (and the generic nrf device running the DK firmware)? Does it filter by name to show the connection list?

I'll update Puck now to latest firmware just in case. It's on official 1v95.

Not much useful on Windows or OSX in the console.

I cleared a lot of the errors in Chromium on the Pi with a good old reboot. Now saying "Websockets> Connected" in Chromium console but still showing "Searching...No Ports Found" in the connection pop-up if I try to connect to anything (same on OSX and Windows trying to access http://raspberrypi.local:1888/ide)

Quick update when testing on OSX:

• It sees the names properly in the Web Bluetooth pop-up on the online IDE, not just hex
  
• It can connect fine to the two devices using the online IDE
  
• It gives same failure as Pi and Windows trying to use http://raspberrypi.local:1888/ide and can't see any ports
  
  

So I guess the issue may be on something to do with the config of the Pi itself? This was an all new clean install of latest Raspbian from this morning and following all the steps for setting up Hub and WebIDE.

A few websocket errors in console on Pi too. Screenshot attached.

The mac address thing is happening on Windows/Chrome with the Web Bluetooth Polyfill. I'm not having a good Bluetooth day. The existing standalone IDE isn't even listing Web Bluetooth any more. Time to update it.

Ooh I hope so re Windows! Do I have to still re-pair every time I take the battery out of the Puck?

If I can get the Pi method working, I'm definitely sticking with that.

Ah the problem is http vs https. Chromium on Pi (and Chrome on PC) refusing to use Web Bluetooth when accessing IDE over http. Anything we can do with self-signed certs or something?

Also has something changed in the online IDE very recently? I'm only getting Mac addresses now, not names. It still connects on Chrome/Windows. But on Chromium/Pi I get "Error NotFoundError: No services matching UUID blah-blah-blah found in device" in console.

After seeing your video Gordon, I had to go set up a Pi3 with the Hub software! I'm hoping it gets rid of all my Windows BLE/Puck issues.

However I've hit a glitch. When I access localhost:1888/ide and try to connect to my Puck, Chromium reports no ports available. But if I go to the usual http://www.espruino.com/ide, it works fine and I see the Web Bluetooth port. I've obviously enabled experimental web features on Chromium on the Pi.

Is the online IDE running a slightly different version of the code or am I misunderstanding something?

That NRF52832 board arrived last week. I can find absolutely no information about it online except that it's intended as a plug-in module for their bigger development board.

There are no pin markings but a bit of continuity testing found VDD/GND/SWDIO/SWDCLK and I was able to flash the stock espruino_1v95.166_nrf52832.hex - Seems to work fine.

With a pin spacing of 2mm and double rows of pins, it can't be used with breadboards. Having all the pins exposed is handy. I just have to figure out the rest of the layout! It'll probably end up being fitted inside a ring of RGB LEDs.

I'll report back when it arrives. Usual Aliexpress random number :-)

I ordered one of these recently to see if it's any good. $12. Hasn't arrived yet.

https://www.aliexpress.com/item/Bluetoot­h-4-2-Module-Bluetooth-5-BLE-Module-NRF5­2832-Module-2-4G/32834109708.html

Having a repo of UUIDs would be really helpful. I found zero info trying to Google "KuLight" other than the Android App.

That's a brilliant tip re Wireshark!

That's definitely not the bulb. Can they re-use URLs like that on eBay for different products?

Ah no, the message at the top of the page is that the original product is gone and they are showing a possible alternative.

I think this is the thing I ordered: http://www.ebay.co.uk/itm/E27-RGB-4-5W-L­ED-Bulb-Light-Wireless-Bluetooth-Control­-Home-Bar-Lamp-Decor/292209739874

Running the code connected via Serial-USB shows that it's just an "error: Connection Timeout" happening. Not sure why that would cause such issues for the PC-Puck connection.

Here's what NRF.findDevices returns for that light:

BluetoothDevice { 
    "id": "e1:fb:c1:6b:81:6f random", 
    "rssi": -64, 
    "services": [  ], 
    "data": new ArrayBuffer([8, 9, 75, 117, 76, 105, 103, 104, 116, 3, 25, 52, 18, 2, 1, 6]), 
    "name": "KuLight"
   }

Ah wait a sec, just changing the ID to "e1:fb:c1:6b:81:6f random" did the trick! What does that even mean?

Now happily communicating with the light. Managed to turn it off. Now to figure out the rest of the config settings via the nRF Connect App.

Ok this is even weirder. On the off-chance, I decided to try and connect to a Milestone Pod instead. It worked perfectly. So it seems that the lightbulb is doing "something" to mess with the Puck. I'll try and connect a Serial-USB dongle later.

findDevices sees the bulb but only when very very close.

I'll check the UART RX pin, thanks! The first general clean-up didn't seem to help.

Slightly different on Mac. Again the console freezes but then the IDE says Disconnected and it takes 10-20 seconds before I can reconnect again. The problem only seems to occur when trying to connect. I can do this no problem:

var devices;
NRF.findDevices(function(d) {
  devices = d;
  console.log(devices);
}, 1000);

Same result if I paste. Console freezes, and then recovers after a few keypresses and gives that <-Serial1 message.

I'm not sure if they are BLE at all. Should that still work?

Going to check Puck itself too. I had some stuff soldered which I removed and I wonder if I've bridged two pads or something.

I've been struggling with some basic attempts to connect to a "KuLight" (BT 4.0 RGB LED light from here: http://www.ebay.co.uk/itm/332254514323)

Any attempt at connecting seems to kill the console connection to the PC. The IDE prompt hangs until I hit Enter a few times and often prints out "<- Serial1" or "ERROR: Prompt not detected - upload failed. Trying to recover"

This is with code as simple as:

NRF.connect("e1:fb:c1:6b:81:6f").then(fu­nction(gat) {
  console.log("Gat: " + gat);
}).catch(function(e) {
      console.log( "catch caught an error!");
      console.log( "error:", e );
});

Tried on 1v92. 1v93 and master.

I have no issues communicating with the light using either its own ColorfulLight App or nRF Toolbox.

This is on standalone IDE on Windows 10. New battery etc.

Do I need to setup a hardwired serial connection to Puck to really get to the bottom of it?

Feels like I'm missing something very obvious.