eddystone_url.ino Does not see the program Physical WEB and Nearby

[ESAlexhi]

I'm testing eddystone_url.ino and beacon(nrF24L01) does not see the program Physical WEB and Nearby. The Program nrfConnect sees beacon as Physical Web Beacon What can be wrong?

[floe]

OK, so if nRF Connect can detect it, then Nearby is maybe applying some extra filtering (e.g. what URLs are allowed)? Does the nRF app show the correct URL?

[ESAlexhi]

Yes nRF

shows the correct address

[ESAlexhi]

If I press OPEN I get to the site https://qr.net/fNA8YZ , but the program Physical WEB and Nearby not see Beacon .

[floe]

Have you tried https://github.com/google/eddystone/tree/master/tools/eddystone-validator ?

[ESAlexhi]

Yes , not see :( Beacon see only the program nRF Connect

[floe]

Not really sure what else the reason could be, maybe @ReDetection has an idea?

[ReDetection]

No ideas so far. I did tests using the program Physical WEB too, so I'm pretty sure it should work. I haven't seen Nearby tool in android I have around, is it builtin? How to find it? Or it will just present notification under certain condition?

[ReDetection]

I recently found a person with a device which has Nearby app and I can confirm beacon didn't appear there (though it still shows in Physical WEB app and nRF Connect. Also I discovered a little piece of documentation of google, so now I wonder if I have to register every beacon URL in order to work with Nearby app?

[floe]

Hm, the way I understand it, that specifically does not apply to Eddystone-URL beacons. For -UID and -EID, you need Google support, but (theoretically) not for -URL. Maybe it's the random MAC address?

[ReDetection]

😞
https://android-developers.googleblog.com/2018/10/discontinuing-support-for-android.html