We did finally get Beecon to find it, although we had to unplug the Geohopper a couple of times. No idea what the problem was although ICE from reviews that other people also had issues.
We are continuing to experiment with the Geohopper. Still waiting on estimotes.
Detection continues to be fast and reliable. Using the Beecon app gives a lot more choices, so that’s the one I’m using.
The issue is still getting the trigger to SmartThings. We’ve tried RSS, email, gmail, and Twitter, all through IFTTT, and everything works fine, but with delays between three minutes and 15 minutes. So good for a lot of purposes, but not when I’m looking for.
In my particular case, I really want to use immediate proximity for touchless switches, so I need something quicker.
Right now I’m getting really quick response with IFTTT and SMS messages for other presence detection methods, but I need to figure out how to trigger those from Beacon detection. I looked into zapier, but it only polls every five minutes at the expensive rate, and every 15 at the regular rate so that doesn’t help.
Both Geohopper and beecon can do a get or a push to Web servers, so someone who had a local server set up could probably get really fast processing. I’m not planning to go that route myself.
Beecon has some built-in home automation integrations, but it’s all stuff I don’t have: wemo, Phillips, and LifX. I’m going to borrow some WeMo switches just to see how that goes. I don’t know for sure, but based on what they do have and don’t have, I’m assuming this is all via Wi-Fi. They also have built-in integration for gLOBAL cache’s Wi-Fi to IR Bridge, iTach, which is intriguing.
Someone with a set up like at @scottinpollock , where he already has the ITach and he already has a local server set up, could probably do a lot with ibeacons now.
Oh, I should note now that iBeacons work differently in android and iOS. If you have most Apple devices, the device is always listening for the iBeacon at the operating system level, with very low battery draw. If you are using native android, you have to have an app open that is listening, and batteries may not be as efficient. I expect there’s some way around that, maybe with Tasker, but I don’t use android so I don’t know.
The one Apple exception is the new watch. The watch can recognize beacons, but you have to have the app open. If you don’t have the app open on the watch, the paired phone takes over. That’s a battery draw issue.
So that’s what we’ve got so far. Still need to find a way to send an SMS via web service to IFTTT and get the timings on that.