FINGSCAN - download program

[kw123]

https://www.dropbox.com/s/0b14hmlpcj9lu ... 1.zip?dl=1


V 4-17-1


Fixed:
logic for away was not correct gave false positives under certain circumstances

new:
you no can use piBeacon devices (http://forums.indigodomo.com/viewforum.php?f=187)to trigger events, like Mother/Cookies, iFindstuff etc. You can add up to 5 iBeacons to an event.


Karl

[kw123]

https://www.dropbox.com/s/923mpjhvtrakv ... 4.zip?dl=1
v-4-17-4

fixed:
- if not all fields in the config menu where populated a string to integer conversion error could occur.
- the home trigger is now more precisely define: the timer of still home restarts when the last home signal from the sensors (iPhone, piBeacon etc) gets received. Before sometimes the time was not reset as it should have been. This makes the HOME trigger more reliable, it worked most of the time before, just under special circumstance not.


Karl

[kw123]

https://www.dropbox.com/s/c5zj0qpgid99p ... 5.zip?dl=1

v 4-17-5

added:
newly discovered& added devices now are called:
new-seq#-mac#
e.g. new-5-00:55:6:dd:ee:ff

The seq# gets incremented every time a new device gets created. Before the name was either iPhone-new or mac-5-00:55:6:dd:ee:ff

Benefit: if you don't maintain the device names (like me) you will have a bunch of mac-00:55:6:dd:ee:ff etc devices where you down know anymore what is what. Now you can at least see in which sequence the devices were created

Nice little feature that makes life a tiny bit easier.

Karl

[kw123]

https://www.dropbox.com/s/29abrxe1c1f4b ... 1.zip?dl=1

v 4.19.1
fixed:
when a device used in an event was deleted in indigo the event was not updated. now THAT device is removed from the event config


added:
support for UNIFI Wifi AP info. You need to select a unify device in an event configuration. then it will be used like a normal fingscan device. - same as for Mother/cookies or piBeacon devices.
Keep in mind that timing of status change (up--> down) is done in the unifi plugin as well as in fingscan.
EG if yo have set an expiration of devices in unify to 1 minute and the same in fingscan changes from up--> down will happen after 2 minutes.

These devices then can be used as and OR with other devices for anyone home or anyone away or as AND and for all-home or all-away


Karl

[kw123]

https://www.dropbox.com/s/v5t0phvop8an2 ... 2.zip?dl=1
V.7-21-2

fixed:
allAway status was set too early in multi device events. Also added a time-out (100 secs) after plugin (re)start where no trigger is fired to make sure that all info is present (which happens ~00:19 am every day)

added:
improved debug/ logging
- option to send logging to file (~/documents/fing/fingPlugin.log)
- each debug area can be selected individually and combined

eg checking Events - debug will produce output like this - it should give you better info on when and why a trigger fires:

Code: Select all

16:22:44 EVENT# 1    -oneHome:0; allHome:0; oneAway:1; allAway:1
16:23:06 EVENT# 1    -Dev#  HomeStat HomeTime    HomeDist    AwayStat    AwayTime    AwayDist     oneHome allHome oneAway allAWay
16:23:06 EVENT# 1    -  1   False       4891.0      False       True        4834.0      True        False   False   True    True    
16:23:06 EVENT# 1    -  2   True        4903.0      False       False       4891.0      True        True    False   True    False   
16:23:06 EVENT# 1    -oneHome:0; allHome:0; oneAway:1; allAway:1
16:23:06 EVENT       -triggerEvent: EVENT-1-oneHome 
16:23:16 EVENT# 1    -Dev#  HomeStat HomeTime    HomeDist    AwayStat    AwayTime    AwayDist     oneHome allHome oneAway allAWay
16:23:16 EVENT# 1    -  1   True        4901.0      False       False       4844.0      True        True    True    False   False   
16:23:16 EVENT# 1    -  2   True        10.0        False       False       10.0        True        True    True    False   False   
16:23:16 EVENT# 1    -oneHome:1; allHome:0; oneAway:1; allAway:0
16:23:16 EVENT       -triggerEvent: EVENT-1-allHome 
16:23:43 EVENT# 1    -Dev#  HomeStat HomeTime    HomeDist    AwayStat    AwayTime    AwayDist     oneHome allHome oneAway allAWay
16:23:43 EVENT# 1    -  1   False       27.0        False       True        27.0        True        False   False   False   False   
16:23:43 EVENT# 1    -  2   True        27.0        False       False       37.0        True        True    False   False   False   
16:23:43 EVENT# 1    -oneHome:1; allHome:1; oneAway:0; allAway:0
16:23:43 EVENT# 1    -Dev#  HomeStat HomeTime    HomeDist    AwayStat    AwayTime    AwayDist     oneHome allHome oneAway allAWay
16:23:43 EVENT# 1    -  1   False       27.0        False       True        0.0         True        False   False   False   False   
16:23:43 EVENT# 1    -  2   False       0.0         False       True        37.0        True        False   False   False   False   
16:23:43 EVENT# 1    -oneHome:1; allHome:0; oneAway:0; allAway:0
16:24:44 EVENT# 1    -Dev#  HomeStat HomeTime    HomeDist    AwayStat    AwayTime    AwayDist     oneHome allHome oneAway allAWay
16:24:44 EVENT# 1    -  1   False       88.0        False       True        61.0        True        False   False   True    True    
16:24:44 EVENT# 1    -  2   False       61.0        False       True        61.0        True        False   False   True    True    
16:24:44 EVENT# 1    -oneHome:0; allHome:0; oneAway:0; allAway:0
16:24:44 EVENT       -triggerEvent: EVENT-1-allAway 
16:24:44 EVENT       -triggerEvent: EVENT-1-oneAway 
16:25:22 EVENT# 1    -Dev#  HomeStat HomeTime    HomeDist    AwayStat    AwayTime    AwayDist     oneHome allHome oneAway allAWay
16:25:22 EVENT# 1    -  1   False       126.0       False       True        99.0        True        False   False   True    True    
16:25:22 EVENT# 1    -  2   False       99.0        False       True        99.0        True        False   False   True    True    
16:25:22 EVENT# 1    -oneHome:0; allHome:0; oneAway:1; allAway:1
16:25:22 EVENT# 1    -Dev#  HomeStat HomeTime    HomeDist    AwayStat    AwayTime    AwayDist     oneHome allHome oneAway allAWay
16:25:22 EVENT# 1    -  1   False       126.0       False       True        99.0        True        False   False   True    True    
16:25:22 EVENT# 1    -  2   False       99.0        False       True        99.0        True        False   False   True    True    
16:25:22 EVENT# 1    -oneHome:0; allHome:0; oneAway:1; allAway:1
16:25:22 EVENT# 1    -Dev#  HomeStat HomeTime    HomeDist    AwayStat    AwayTime    AwayDist     oneHome allHome oneAway allAWay
16:25:22 EVENT# 1    -  1   False       126.0       False       True        99.0        True        False   False   True    True    
16:25:22 EVENT# 1    -  2   False       99.0        False       True        99.0        True        False   False   True    True    
16:25:22 EVENT# 1    -oneHome:0; allHome:0; oneAway:1; allAway:1
16:2

Karl

[kw123]

https://www.dropbox.com/s/m5pld30wzk3yl ... 2.zip?dl=1

v 7-22-2:

added:
you can set the indigo variable or device folder names in config to anything you like.

if you have already devices in a folder:
(1) change config,
(2) move existing devices / variables into the new folder
(3) delete the old folders after ~ 5 minutes to see if any issues arise

Karl

[kw123]

version 7-22-3
https://www.dropbox.com/s/cnatjnu6tkatx ... 3.zip?dl=1
fixed(hopefully): umlauts... in printouts

Karl

[kw123]

version 7-22-5
https://www.dropbox.com/s/7xhlrk85ll8sa ... 5.zip?dl=1

added/fixed: added filter for pibeacon devices. Now considers only iBeacon devices for fingscan events- no sensors.. They mostly do not have UP/down states, temp pressure ..)

Karl

[kw123]

posted v -7-22-6.

fixed:
up --> down --> expired did not expire.

Somehow fing changed behavior. In the past devices disappeared from the fing.data file after ~ 2 minutes when they were not detected anymore. Now they stay in the list.

added a timestamp check to make them go from down--> expired after 70 seconds after they go to down.

It seems to work and have not seen any adverse effects in other areas.


Karl

[kw123]

posted V: 7.22.10

fixed
-some issue with new directory structure. - was still using ~documents in some of the variables
- detecting if fing was running had a "grep -v indigo" in there .Iis now "grep -v Indigo". (to not look for the plugin process but the FING.bin itself.
now it detects correctly if FING.bin is running. Before it was restarting FING.bin every 5 minutes.

`
Karl

[kw123]

posted V: 7.22.11


changed:

changed all variable/device/folder/event names from using a - to _ as indigo does not fully support a - in names.

if you are using events you must update them as the names have changed.

Karl

[kw123]

posted v 7.23.12

added:

will check
/usr/bin/curl http://api.macvendors.com/11:22:33:44:55:66 (11:22: = mac number )
to get the vendor name for each existing devices.

it will go though ALL devices at start and if the length of the contents of hardwareVendor field is < 4 it will try to get it.

Also when a new device is added it will also check.

So if you run it the first time it might take a minute to start. the second time it starts it will go again, but only those that are blank .


Karl

Ps one thing missing. If you don’t have internet access during loading of the plugin it will take a looooong time as it will need to time out at each query. 10 sec times number of queries
Will add a check. In the next fix.

{EDIT] added check if no internet connection: no vendor checking

[kw123]

posted V 7-23-15

fixed:
-added a check on max(xx) (if xx==[] it causes an error)
- this should normally never be the case.. but anyway thats fixed now

Karl

[kw123]

posted V 7.23.16

changed:
Text in device edit.

The fields hardware vendor and device info are always empty when devices edit is started.
They are used to OVERWRITE the device states. If they are empty they are ignored. The device edit screen now describes that.

Karl

[kw123]

posted v 7.24.19 in the plugin store , fixed events and added network type back into the config op[tions