LR BT worked great. It is a bit tough to write rules for since there was no real fence to be in/out of ... IE - Did the car just start ...or did it just arrive. (had no access to rssi data)...but.
If you don't have good cell service, it can be far more reliable. They came in and added towers and now I'd say Geofency is as solid as apps can be.
@ajardolino3
Rebooted on to beta .147 this morning and the gateway went a but nuts on
hub event overload.
I had to repower the gateway to calm it down.
Here is one snipped with the Debug/Logs turned on.
Maybe just a quirk, I'm know I have rebooted since installing the gateway.
app:18882025-01-14 10:30:05.464errorcom.hubitat.app.exception.LimitExceededException: App 1888 generates excessive hub load on line 256 (method postGateway)
app:18882025-01-14 10:30:05.450debugbeacon ID: 426C7565436861726D426561636F6E71:3838:4949 present: true
app:18882025-01-14 10:30:05.435debugiBeacon detected: uuid: 426C7565436861726D426561636F6E71, major: 3838, minor: 4949, power: -59, rssi: -88, distance: 92, dni: 426C7565436861726D426561636F6E71:3838:4949
app:18882025-01-14 10:30:05.431debugset beacon data: [success:true, parsed:[[length:2, type:01, segment:06], [length:26, type:FF, segment:4C000215426C7565436861726D426561636F6E710EFE1355C5]], beacon:[data:0201061AFF4C000215426C7565436861726D426561636F6E710EFE1355C5, distance:999999999, dni:, mac:DD340209C38F, power:999999999, rssi:-88, type:auto]]
app:18882025-01-14 10:30:05.425debugiBeacon detected: uuid: 426C7565436861726D426561636F6E73, major: 3838, minor: 4949, power: -63, rssi: -62, distance: 3, dni: 426C7565436861726D426561636F6E73:3838:4949
app:18882025-01-14 10:30:05.421debugset beacon data: [success:true, parsed:[[length:2, type:01, segment:06], [length:26, type:FF, segment:4C000215426C7565436861726D426561636F6E730EFE1355C1]], beacon:[data:0201061AFF4C000215426C7565436861726D426561636F6E730EFE1355C1, distance:999999999, dni:, mac:DD340209C580, power:999999999, rssi:-62, type:auto]]
app:18882025-01-14 10:30:05.411debugParsed payload from Gateway: [beacons:[[data:0201061AFF4C000215426C7565436861726D426561636F6E730EFE1355C1, mac:DD340209C580, rssi:-62, type:auto], [data:0201061AFF4C000215426C7565436861726D426561636F6E710EFE1355C5, mac:DD340209C38F, rssi:-88, type:auto]]]
app:18882025-01-14 10:30:05.394debugSending payload to device: Beacon - Gateway, payload: {"v":1,"mid":2,"time":39,"ip":"192.168.1.249","mac":"5443B2C94C70","devices":[[0,"DD340209C580",-62,"0201061AFF4C000215426C7565436861726D426561636F6E730EFE1355C1"],[0,"DD340209C38F",-88,"0201061AFF4C000215426C7565436861726D426561636F6E710EFE1355C5"]],"rssi":-58}
app:18882025-01-14 10:30:05.390debugPOST received from Gateway: {"v":1,"mid":2,"time":39,"ip":"192.168.1.249","mac":"5443B2C94C70","devices":[[0,"DD340209C580",-62,"0201061AFF4C000215426C7565436861726D426561636F6E730EFE1355C1"],[0,"DD340209C38F",-88,"0201061AFF4C000215426C7565436861726D426561636F6E710EFE1355C5"]],"rssi":-58}
Are there any app (google play) equivalents to the gateway? I have a phone running tycam using web hooks into Hubitat already
this is awesome!!! i got it working with hubitat in janurary 2025 with blue charm beacons! it's got a quirk or 2 for my situation, but nothing i couldn't work around!
today i updated from hubitat firmware 2.3.7.146 to 2.4.1.167...and it just quit...no more updates from the beacons. i reverted the firmware back to 2.3.7.146 and everything started working again. it's a fine short term solution, but i figured i should bring it up!
thanks @ajardolino3 !
Can you turn on debugging in the app and share any errors you may see in the logs?
I'm on the current release and it has migrated from every beta, almost daily, in the last 3 months without issue.
There has been the occasion in the past where it has gone a bit log crazy and stopped working but a simple power cycle seemed to fix the issue.
Maybe just this?
i loaded the new firmware again to capture the logs, and this time it worked! false alarm - sorry about that...no idea what happened the first time.
i attached the log anyway since i did see an error.
my project goal was to know if i was home or not.
quirks with my setup...
thanks!
no sooner did i post when i noticed it quit on the new firmware (it may have been dead in my previous screen shot - not sure exactly when it died).
if i reboot it starts working again - but only for 10-15 min before stopping.
log from when it quit...this time with a java error?
One of those is an Excessive Hub load.
I've had that before on BLE and Owntracks.
I have set my tags to 10000ms so they only report every 10s.
Are you on the default?
Can't remember but it's way less than 10000.
i think i was on the defaults?
looks like my beacons were set to 1022.5ms (adv interval), and my gateways were set to 100ms.
i changed them both to match - both now at 1000ms. that's the max for my gateways - can't set them to 10 seconds.
still no good.
then i tried turning off both my beacons and rebooting the hubitat. the log is still going crazy...so maybe it's picking up other random transmitting devices?
132 debug messages in 1 second with my beacons turned off.
screen shot of a fraction of log with my beacons turned off:
I changed the timing in the tag and the config tool; I have Blue Charm iBeacons and April Brothers gateway.
On the April gateway, you can filter so it only transmits data to the hub for specific devices.
Download the Hubitat app
