Developer: | Karl's Plugins Like this plugin? Show your appreciation! |
Category: | Location and Presence |
Github: | Github Repo |
Assistance: | Get help! Check the online documentation |
Plugin ID: | com.karlwachs.homeAway |
Latest release: | v7.2.16 released on Jan. 11, 2020 (this release is only compatible with Indigo 2022.2 and earlier) |
Release downloaded: | 0 times |
Requires: | Indigo v7.0.2 thru v2022.2 |
(Check the Releases tab below for older releases that may have different requirements) | |
Download latest release |
define triggers that allow a combination of information from different indigo devices (sensors) to be combined to set home / away events . It can be combined with a door time gate and other variable or device/state conditions to veto a trigger
The plugin can currently use info from fingscan(any ip device), unifi(any ip device) and pibeacon devices(ibeacons, BLE devices ..) called sensors in the following.
Any plugin that can send indigo broadcasts could participate.
Thesensor are combined with an "AND" to indicate how many sensors have come home or went away . NOT how many are home or are away - a slight difference.
A snapshot would poll all devices and add their states.
This plugin will receive updates on changes and then determine if a sensor went away or came home.
THEN it determines how many came home / went away.
In addition the plugin can use information from any other on/off type device (called doors in the followoing) to set a time gate function:
only accept a come home or go away sensor change if the door was opened/closed x seconds before or y seconds after the sensor device came home or went away.
This will reduce the false positives / negatives. Only when the door opens/ closes it will accpt a change in a sensor state.
the plugin supports:
* all home all devices must have come home
* one home at least one device just came home
* xx home with door gate same as above, but the door must have opened or closed before / after the sensor(s) came home and the same for away
* all away all devices must have went away
* one away at least one device just went away
* xx away with door gate same as above, but the door must have opened or closed before / after the sensor(s) went away
you can set various timing parameters and select which of the doors and sensors you want to use for THIS event trigger
first you select event type: all/one home; all/oneaway
* min time between 2 triggers to avoid multiple triggers for one comming home / going away event
* trigger delay wait some seconds to make sure the sensor state does not change.. to avoid false positives
* reset sensor for a home event a sensor will stay home until it leaves AND a door open/close happens
This option allows to have the sensor reset its state to away (for home events and visa versa for away events) without the door event
* variable condition you can add a test on any variable <,<=, ==, >=, > "in" a test value. If not true the event will not trigger
* device/state condition you can add a test on any device/state <,<=, ==, >=, > "in" a test value. If not true the event will not trigger
* select/delete sensors then manage the sensors (one or many) that are part of this event group.
* select/delete doors then manage doors (eg front and back door) that define the door time gate. You can set a before and an after time window
v7.2.16 | Requires Indigo v7.0.2 thru v2022.2 | Released Jan. 11, 2020 | fixed: The following field ID has an invalid visibleBinding identifier: selectExistingSensor |
Released on: | Jan. 11, 2020 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
fixed: The following field ID has an invalid visibleBinding identifier: selectExistingSensor
Released on: | Jan. 11, 2020 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
fixed: loggin errors
v7.2.14 | Requires Indigo v7.0.2 thru v2022.2 | Released Jan. 9, 2020 | fixed: The following field ID has an invalid visibleBinding identifier: selectExistingSensor |
Released on: | Jan. 9, 2020 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
fixed: The following field ID has an invalid visibleBinding identifier: selectExistingSensor
v7.2.13 | Requires Indigo v7.0.2 thru v2022.2 | Released Jan. 22, 2019 | added several checks and moved log and config files to std indigo ser… |
Released on: | Jan. 22, 2019 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
added check for incomplete event definitions
change to std logging
moved all files to indigo server directory
Released on: | Sept. 7, 2018 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
various small bug fixes, added space in menu if lines are hidden, this will avoid resizing dialog boxes if fields are visible / not visible
Released on: | Aug. 14, 2018 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
v7.2.6
Released on: | Aug. 9, 2018 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Download this release |
Added option to add a variable veto/enable for event trigger.
In event edit define variable and enable value.
if at trigger time the variable is NOT = to the defined value, the trigger is suppressed
Released on: | Aug. 14, 2018 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
v7.1.5
Released on: | Aug. 9, 2018 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Download this release |
debugged version, ready to be used
indigo 7.1