I just wanted to thank Michael for adding the ability to monitor the presence of Bluetooth devices with this plugin directly from the default MS Windows 10 stack. This allows for stable geofencing to run locally with no need for MYHS, Internet access, or even a phone app. For me, a huge value add is there is no other programming needed...like ESP boards. This is VERY plug-and-play.
Please don't expect this post to be near as well done as his plugin documentation
...
Just a quick overview of how mine is set up to show how simple this is...
The Feasycom product is the real game changer. Due to it's range, it can penetrate the steel and glass of the inside of a vehicle, go through the walls of my house, and reach the server. Currently, mine is inside the vehicle and that works fine for me. I'm likely going to mount mine outside the vehicle under the front bumper. I'm thinking I can waterproof it with some large heat shrink tubing, but that extra effort really isn't needed I'd expect unless you have range issues.
I've found that even with all the glass/steel/walls/etc detection occurs at somewhere around 150ft when coming home. Since among other things, my events lock and unlock doors I have a few safety net entries in my events, but in general my approach is fairly simple. I'm guessing there are better ways to write the events, but here is what I did.
1) An event that watches for BT device the plugin creates in HS4 for the BP109 to change state and for that event to "turn on" a virtual device that I used to differentiate between departing and arrival. In my case, I call it "Jeep Trip Status." It has three possible values; jeep home, waiting to leave, and on trip. Waiting to leave allows me to start the vehicle and not run events that do things like instantly lock the doors. If for no other reason your wife will likely not really appreciate that if you're in the car first.
2. An second event that triggers when the BP109 “turns off” when I drive out of range AND the virtual device Jeep Trip Status is "waiting to leave" from the first routine running. Among a lot of other things that events does is to lock up the house. It also sets the Jeep Trip Status device to “On Trip” which must be on for the next event to run when the Jeep BP109 comes into range on arrival.
3. An event for detecting arrival. I marked out one line simply because it is a step that assures it’s actually me coming home since this unlocks the house. In general, this event triggers when the BP109 HS4 device “turns on” as I pull into range of the server AND the virtual device “Jeep Trip Status” is set to “On Trip.”
Please don't expect this post to be near as well done as his plugin documentation
...Just a quick overview of how mine is set up to show how simple this is...
- Insert a class 1 BT usb in a Windows 10 server running HS4 - I used a TRENDnet Low Energy Micro Bluetooth 4.0 Class I USB 2.0 with Distance up to 100Meters/330. (about $15)
- Insert a USB BT device in your vehicle - I used a Feasycom 4000m Mobile USB Long Range eddystone ibeacon. For my events, I found it better to use USB ports that only power up when the vehicle actually starts vs. as in my vehicle that most power up when I open the door. (About $32).
- Load the plugin and discover and select devices you wish to monitor. As a side note, make sure you turn back off discovery in his plugin. I left it on for a few days and it added to the table every BT device in cars or on the sidewalk that came by. This makes that list long, but the plugin will only create devices for the ones you want.
The Feasycom product is the real game changer. Due to it's range, it can penetrate the steel and glass of the inside of a vehicle, go through the walls of my house, and reach the server. Currently, mine is inside the vehicle and that works fine for me. I'm likely going to mount mine outside the vehicle under the front bumper. I'm thinking I can waterproof it with some large heat shrink tubing, but that extra effort really isn't needed I'd expect unless you have range issues.
I've found that even with all the glass/steel/walls/etc detection occurs at somewhere around 150ft when coming home. Since among other things, my events lock and unlock doors I have a few safety net entries in my events, but in general my approach is fairly simple. I'm guessing there are better ways to write the events, but here is what I did.
1) An event that watches for BT device the plugin creates in HS4 for the BP109 to change state and for that event to "turn on" a virtual device that I used to differentiate between departing and arrival. In my case, I call it "Jeep Trip Status." It has three possible values; jeep home, waiting to leave, and on trip. Waiting to leave allows me to start the vehicle and not run events that do things like instantly lock the doors. If for no other reason your wife will likely not really appreciate that if you're in the car first.
2. An second event that triggers when the BP109 “turns off” when I drive out of range AND the virtual device Jeep Trip Status is "waiting to leave" from the first routine running. Among a lot of other things that events does is to lock up the house. It also sets the Jeep Trip Status device to “On Trip” which must be on for the next event to run when the Jeep BP109 comes into range on arrival.
3. An event for detecting arrival. I marked out one line simply because it is a step that assures it’s actually me coming home since this unlocks the house. In general, this event triggers when the BP109 HS4 device “turns on” as I pull into range of the server AND the virtual device “Jeep Trip Status” is set to “On Trip.”
Comment