Time between ProximityUUID1 and ProximityUUID2

Hello - I’m using AprilBeacon N01 (a wonderful product by the way!) in iBeacon mode.

I have configured both ProximityUUID1 (uuid: B5B182C7-EAB1-4988-AA99-B5C1517008D9, Major: 1, Minor: 25677) and ProximityUUID2 (uuid: E2C56D85-DFFB-48D2-B060-D0F5A71096E0, Major: 0, Minor: 0).

I’ve built an iOS app that listens for both UUID’s. I can range for the default ProximityUUID1 and when I move the sensor I can range for ProximityUUID2 - almost instantly (1000ms or less) . But when I stop moving the sensor it can take on average 5-6 seconds before I can range for the default ProximityUUID1 again.

If I increase the Advertising frequency above 700 - for example to 1400 I can increase the delay to 10 seconds but I can’t seem to decrease it below the 5-6 second average.

Is there anyway to reduce the time to range for ProximityUUID1 again? I would prefer that the switch between both UUID’s be equal in length - ideally 1000ms or less each time.

thanks so much!

Do you want to switch back to ProximityUUID1 in 1~ second? Could you describe your application?

Hi -
Yes I want to switch back to ProximityUUID1 in 1~ second.
The application is an iOS application using aprilbeacon as an iBeacon asset tracker. When the asset is moved ProximityUUID2 is triggered quickly, but I would like to know when the asset is stationary again quickly. I assumed that ProximityUUID1 would start advertising again within 1~ second.



The delay is hard coded. We can change it to 1 second but I think it’s too short for catch by iPhone. We will send an OTA firmware to you later

Please check your private message for how to upgrade firmware.

Hi -
Wow. I’m really impressed that you created new firmware for this issue. That by itself is really great customer service. I would make the changes myself if I had the proper tool-chain.

Results: The firmware does not seem to work. I found a reference application that we both can use to see consistent results (here: https://developer.apple.com/documentation/corelocation/ranging_for_beacons). The problem may not be with the firmware it may have to do with iPhone and it’s time-to-detect. It’s strange because it will detect a change immediately from Prox1 to Prox2 but not in reverse.

thanks again for going the extra mile.