starting with v 7-37-37 the plugin supports a device type = CAR
1. create a device plugin = pibeacon, type = CAR, eg Volvo or Moms car ...
2. select
(A) a battery type beacon (i.e. with AAA battery), place that beacon in the CAR (fixed)
(B) a USB powered beacon put into USB output in CAR
(C) 0-3 beacons attached to your car keys (eg xy)
The CAR device will have 3 states with the following values:
(a) LOCATION= HOME/ AWAY
(b) ENGINE = ON/OFF/""
(c) MOVING = STOP/LEAVING/LEFT/ARRIVING
Conditions for the states:
LOCATION:
-HOME: if Beacons A or B or all C are UP (at least one of the beacon is how so the car must be home)
-AWAY: if Beacons A and B and one of C are down (none of the beacons is home)
ENGINE:
ON if beacon B is on
OFF if beacon B is off
"" if STATUS =AWAY
Moving:
- STOP if home and Beacon B = off (HOME and car is off = must be home standing)
- LEAVING if HOME and Beacon B = ON ( car is home and battery beacon or key is on and USB key comes on. = home starting engine --> must be leaving)
- LEFT if AWAY (no beacon visible so car must be gone)
- ARRIVING if AWAY and any beacon on (was away, have detected at least one beacon so it must come home)
the state "status can be set to show either one or 2/3 of the states described above.
This can be used to detect your CAR(s) home/ away, coming home, leaving ..
It utilizes "fastDown" option for the beacons: if a beacon does not send a signal for x seconds the RPI will send a "fastDown" message to the plugin. for the status to go down ALL RPI must send the fastDown signal.
This is in contrast to not sending anything to the plugin and the plugin will set the beacon status to Down after seconds expiration time.
This will allow a faster reaction time. The fastDownTime used here is 15 seconds. You can manually adjust it for each beacon in beacon device edit. Increase if you have just one RPI, or you could go down to 10 seconds if you have 10 beacons. But you might get some false positives.
Karl