Wow, thanks! I will give it a try tomorrow.
This app is like Excel. Looks pretty basic at first, but the deeper you get into it, the more you realize how powerful it is!
Oooooh, now I see. I read several places on this forum where people said to report it on the main page, and I assumed they meant the main page of the forum. Could not find any "Report a bug" link or subforum on the main page of the forum...Sorry about that!
Not sure if this is where I should post a bug report. If not, please move it for me moderator. Thanks.
Bug: App only allows a single beacon. For example, you can have an "in range" trigger for Beacon A and also an "out of range" trigger for Beacon A. Both work fine. If you then add a trigger...
Just to add some explanation here, a Tile is not a beacon. It is a BLE device that requires a connection.
A beacon is a BLE device that does not require a connection, and in fact, stops broadcasting if you connect to it. You only connect to a beacon when you want to change its setting...
Would love it if you could add "bluetooth beacon" as a connectivity constraint. I see you have it working pretty well in the trigger/connectivity section as an experimental option, and would like the same thing in constraints.
With this, users could use two beacons to do some cool stuff...
You could do this with a bluetooth beacon. Set the trigger based on connectivity/bluetooth beacon. then select in range and enter the uuid of the beacon. I think you have to turn on "experimental" in settings in order to see "bluetooth beacon" appear as a choice under the connectivity triggers.