When monitoring for iBeacons in the background with uuid=123 the triggerd event when iBeacon is in range dosen´t contain major or minor.
Wow, that's annoying - I thought that was the whole point.
What about switching to iBeacon only when there's an alert?
If you use something like the nRF connect app on the phone, what does it show for the Puck when it's back in connectable mode?
I guess it might be worth explicitly setting connectable:true again? Also the IDE works based on an advertised NUS service (in the scan response packet) but also just the name as a fallback. If the name doesn't begin with Puck.js it's possible it may not pick it up if it hasn't been able to read the NUS service UUID.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Wow, that's annoying - I thought that was the whole point.
What about switching to iBeacon only when there's an alert?
If you use something like the nRF connect app on the phone, what does it show for the Puck when it's back in connectable mode?
I guess it might be worth explicitly setting
connectable:true
again? Also the IDE works based on an advertised NUS service (in the scan response packet) but also just the name as a fallback. If the name doesn't begin withPuck.js
it's possible it may not pick it up if it hasn't been able to read the NUS service UUID.