#Radbeacon not working Bluetooth

There's been enough noise about group conditions and actions that I don't ever use them at this point and I don't know what works and what is broken. Humour me and delete that and add the same condition to each of the triggers. One thing I do notice is that you are using a group condition.

If all of the above is how you have things set up, it shouldn't even matter if it becomes 'not near', as the first change to 'near' should trigger the event. I presume the 2 trigger devices in your event are those PHL devices that represent your GeoFency iBeacon devices? I am sure that's what you have, but the wording confused me. The device in your Geofency app is the one that switches from 'not near' to 'near' as you approach the beacon and that should be updating the equivalent PHL device in HS3 via the GeoFency webhook to the plugin. If I can get it to be reliable enough I will unlock the door even when the house is empty.The current event works when the 100 mtr fence is crossed, using an ibeacon near front door with give me a fence of a couple of metres.įor clarity, the beacon isn't in a particular state, other than just USB powered and broadcasting it's signal. The event condition in this case is that the virtual occupancy has to be on, this serves as security and will only unlock the door when one of us are at home.

When I arrive home it would detect the beacon and unlock door (via a solenoid and z wave module) As stated this doesn't work properly as the beacon ( is already powered up, it accepts the 'near' but then drops it a little while after. However, you will see from the screenshot that originally I wanted to locate an ibeacon near the front door with a power setting of a couple of metres. I have now started using the same method as you and Randy, the Ibeacon serves as a'event condition' and triggers only when the 100 metre fence is crossed. I am sure that there are other folks using fixed beacons and near/not near to the beacon as the trigger, which is what I think you are doing here.

Homeseer uses that as the event trigger and the 'near' status of the beacon as the event condition and then one or more actions kick off from that. As I drive up my street and cross into my 100m fence, GeoFency tells HomeSeer that I crossed that fence. In my typical work day, as I walk up to my car in the parking lot in the evening, the phone detects the beacon and GeoFency tells HomeSeer that I am in the car. We are both triggering events based on crossing a regular GeoFency fence (in my case 100m radius from my house) but only IF we are already 'near' to our beacons. Randy and I are not using these to trigger events based on connecting/disconnecting with the beacon (unless Randy also has another use case that I don't know about). What do you have it powered by and which beacon do you have? Have you tried reducing the power of the beacon, so that the phone only detects it within a few metres? You mention this is for unlocking your door. I also find my phone is OK on calls, so still a little stumped!So a few further thoughts. This is exactly what I would expect to happen but thats not the case, when beacon is already powered and I cross the fence, Geofency acknowledges fence, but then drops it randomly even when i'm still in the fence, so appears that its a phone/bluetooth issue.

#Radbeacon not working Bluetooth

What I haven't tested positively is if the beacon loses connectivity to my phone if I use the phone for a Bluetooth call. If the beacon is powered, moving in/out of range should trigger every time and if it's in range it should stick that way. I think this sounds contrary to your experience, however it's the phone or other Bluetooth device that keeps the near/not near status in relation to the beacon. As I only use the iBeacon status when I cross my 100m fence this doesn't cause me any issues and I haven't bothered trying to solve for it. So, when my Audi is parked in the driveway and I am outside with my phone it triggers in/out status on Geofency every time I go near it. The lighter socket on the Audi is always on. The lighter outlets and USB ports on the Toyota are controlled by the ignition. In our household we have a 10yo Audi A4 and a 2 yo Toyota Highlander. This is perfect for this scenario and how Randy and others are using them.Īs previously stated, they do not hold their 'near' status if the beacon is already powered up and you enter the their fence.Īnyone has any luck with getting this to work as proximity detectors in this setup, please share. they 'hold' their near status until powered off (ignition switched off). Can confirm when ibeacons (in cars) are powered up from usb/cigarette when ignition is switched on, bluetooth does not drop out.