Michael,
After using this to interface with BT/BLE devices for a few weeks now, I think a couple things might make this even more adaptable/flexible for interfacing with both different types of BT devices and use cases. The settings I'll be referring to are these...
After using this to interface with BT/BLE devices for a few weeks now, I think a couple things might make this even more adaptable/flexible for interfacing with both different types of BT devices and use cases. The settings I'll be referring to are these...
- The plugin currently allows the value passed to HS4 for the BT device it is monitoring to be set to constantly report the actual varying RSSI from -1 to +129, or report only in and out of range using a -1 or 0.
- There is also a setting for how long a BT device takes to change to being marked in HS4 as being out of range by setting the “Out of Range Timeout Seconds” parameter.
- The USB based BT devices in my vehicles need to appear as on or off so that their fluctuation does not trigger events falsely. Setting the global parameter to only report -1 for off and 0 for anything -1 to 126 fixes that issue. That is awesome but turns off the ability to trigger events based on things like a signal becoming stronger or make a choice between being closer to one BT device than another. RSSI seems a little hard to track perfectly but I'd think differentiating between under 20 and over 80 is probably realistic.
- When writing events that trigger when a device goes out of range completely, detection speed of that drop often matters. For several of my events, setting the "Out of Range Timeout Seconds" to 10 seconds works best. Being able to tweak that is awesome, but then since it is a global setting any battery powered devices constantly toggle on/off the device representing it in HS4 since they themselves are always fluctuating between on and off. That makes events which monitor their presence tougher to write and increases both device state change churn and events constantly rerunning. The event running issues can be reduced, but I am thinking that HS4 must still constantly spend cycles evaluating the triggers to be false and not running.
Comment