Most recent activity
-
When I use setTimeout to regularly change the BLE advertising (once a day or so), it will surely increase power consumption a bit. But will it lead to the interpreter running permanently wasting power or will it use (deep)sleep to minimise consumption? I have read here that nRF52 boards sleep automatically ...?
-
Thank you Gordon, looks good now. Some device scanner just don't seem to update their data correctly, even if restarted. "nRF Connect" works best.
-
Yes, my twice-setting of advertising didn't work, somehow it looked like it would.
-
Aha – I think I have found a solution, at least it looks better now. I set the name first and adv after it. They don't seem to overwrite eachother:
NRF.setAdvertising({}, {interval:1500,name:ble_name,showName:true,discoverable:true,connectable:false,scannable:true}); NRF.setAdvertising(adv, {}); -
Thank you for the hint ... so I have changed it to
const adv = [ 0x1e, 0xff, 0x4c, 0x00, 0x12, 0x19, 0x00, key[6], key[7], key[8], key[9], key[10], key[11], key[12], key[13], key[14], key[15], key[16], key[17], key[18], key[19], key[20], key[21], key[22], key[23], key[24], key[25], key[26], key[27], key[0] >> 6, 0x00, {}]; NRF.setAdvertising(adv, {interval:1500,name:ble_name,showName:true,discoverable:true,connectable:false,scannable:true});Although there is no error or message the device seems to fall back so I can connect via IDE ... it does not advertise like I want it to. I am a little out of ideas now.
-
I just want the device to advertise like here ... working as an "AirTag". From what I understand this code not really loops it just sets the device in advertising mode. How much will it consume? Is there something I can disable to even lower the consumption?
-
Ah, I see it sometimes takes very long for scanning apps to recognise the change of the name. The IDE is fastest mostly. Even when I restart Puck (battery out). Is that an issue of the scanning app (device) or am I missing something?
Thank you!