Can you tell me more about the iBeacon you are using? Can you find it with a BLE Scanner app on your phone? Could you tell me the UUID (unique identifier) of the beacon?
If you can find it with a phone, and it’s definitely using the iBeacon standard, could you please make sure it’s close to the Raspberry Pi running balenaLocating. There is an environment variable you can set called RSSI_THRESHOLD which determines how strong/weak a signal from a beacon that will be added to the database, it’s documented here: https://github.com/balenalabs-incubator/balena-locating#configure
Similarly you can set the DEBUG variable to true and the project will log more, and tell you if your beacon is being ignored for some reason.
Unfortunately I appear to be having the same issue.
I have run Beacon Simulator on my phone, and tested it with the Beacon Scanner on another phone, and it finds it correctly.
However the BalenaLocating Dashboard never shows any tags.
I have turned DEBUG on, but the only entry for the beaconService is “Started to scan.” and nothing else. The UUID of the iBeacon is e04e82c5-afd0-49b8-95bc-e92e4c50d620
I have the sam problem. I use the Beacon simulator on Android. When I create a IBeacon, Balena doesn’t see it. When I create an Eddystone-beacon, Balena sees it.
Could you please set the environment variable DEBUG to true and make sure the Android device is close to the balena device when testing. Also check that the power output of the simulated iBeacon is higher than -75dBm. The debug option should give us some logging if there is an issue with the iBeacon formatting.
I bought Bluetooth nRF51822 iBeacon and the BalenaLocating Dashboard picks them up. The only problem now is that the beacons were delivered without password. They all show up with the same UUID, but that’s not Balena’s fault.
EDIT: By using the app NRF connect, I logged into the beacon and changed the Minor / Major values. The beacons now show up as seperat beacons in Balena.