It’s been a few years since I made the round of various apps to test them out. Tasker was one of the ones I tested, but I honestly don’t remember any of the details. My written summary at the time, which might not be accurate anymore, was:
“While Tasker is a popular automation app on Android, it does not have a well functioning system for working with beacons. The killer weakness is the reaction time; it will react to being near a specific beacon (“BT Near”) in 47 seconds at best when the screen is turned on; that’s terrible. When the screen is off, reaction time is 4 minutes or more…That’s a very, very long time to stand in a dark room waiting for the lights to come on automatically! Basically this app is unusable for most time-sensitive usage cases, but if you have a case that is not time-sensitive, this might be a good one to try.”
I reviewed a few more here: https://bluecharmbeacons.com/app-suggestions/
My best advice when you have any issues with an app is to contact the app developer. You can tell them you are using a standard iBeacon (or Eddystone UID beacon if that is the case; our beacons can act as either type). Their “first line of defense” is usually to cast doubt on the beacon, but you can be confident that our beacons are 100% standard issue and follow the iBeacon/Eddytone protocols.
If you want to confirm that your beacon is broadcasting without using the app in question (e.g. Tasker), you can use our KBeaconPro app. The scan screen of our app will show your beacon, and the rssi figure will be slightly moving up and down if the beacon is actively broadcasting. If you use an Android phone, the scan screen of the KBeaconPro app will also show you the active UUID and major/minor of the beacon.
