Well, you're exposing the Python BaseHTTPRequestHandler (https://docs.python.org/2/library/basehttpserver.html) to the Internet. I myself feel quite safe doing so, but your mileage may vary. If you don't want to do that and only need say iBeacons at home and not geofencing in "the world" you could use one of the apps that doesn't rely on a cloud service and only expose the plugin to your LAN.haavarda wrote:I want to try to avoid exposing my system.
Is this plugin solution secure? Or am I exposing my system in any way when I use this plugin?
Yes, you can rename the device.jbaker2290 wrote:i successfully set up this plugin with geomancy, and the device for my set location was created, but can i rename this device, or will it cause it not to work
Been playing around with Geofency after reading this thread and it's pretty good. I'd now like to get into beacons and was thinking about getting a couple of the SticknFind stickers. Is there anything I should be aware of when trying to pair them up in Geofency?flic wrote:I just posted a new version that supports Geofancy as well as Geohopper and Beecon. (http://geofancy.com) Tried it out with SticknFind stickers in iBeacon mode (https://www.sticknfind.com), works pretty well!
Good to know... thanks for the heads-up on the failures. I was looking at the estimotes also but it seems like their new stickers are not to iBeacon standards and the batteries are not replaceable. I may just get the bigger ones.flic wrote:No, it's really straight forward. You need to know the beacon uuid, major version and minor version. You create a new location, enter the values and you're set.
That said, all of my sticknfinds have failed since I wrote that post. If you don't mind the larger size, buy Estimotes instead.
