Using Fing as a new way to detect smartphone presence

Sorry 22.10 for me and I need to be up early, wi gladly try stuff for you tomorrow

you some how started fingscan from the download directory

please quit that fingscan:
- open activity monitor
- find fingscan
- click on fingscan
- right click and select force quit, or in mavericks click on "x" button to force quit

then start fingscan in ~/Documents/fing (double-click on figscan.app)

Karl

killed the process, re-ran.

mini:~ user$ ps aux | grep 'fingscan.app' | grep -v 'grep'
user 5553 2.6 0.3 2510012 10516 ?? S 3:11PM 0:00.51 /Users/user/Documents/fing/fingscan.app/Contents/MacOS/applet -psn_0_3826598
mini:~ user$

This version should handle situation where 2 instances are running and by accident launched from download directory

https://www.dropbox.com/s/iyyjn36znuwmw5z/fingscaninstall-1-6-6.zip

Karl

I'd already tried the killing the thread option in case two were running with no change, but stopping the indigo server and restarting it seems to have cleared a log jam (I have already rebooted and started / stopped indigo - this time it was just the server). Investigating now....

so does it work now?

I won't have time to play with this until maybe later tonight. I'll try to get back to it after work.

Thanks for taking your personal time to help out the indigo community. I truly appreciate it!

i ran the latest script and see this.

Dec 9, 2013, 5:42:43 PM
Script FINGSCAN-1-6-6: initialize
Trigger fing new ip number
Error failed to execute script because script could not be compiled
Trigger fing new ip number
Error failed to execute script because script could not be compiled

copied the files to the desktop and ran the script again. it looks like it is trying to run and I get this:

Dec 9, 2013, 7:44:43 PM
Script FINGSCAN-1-6-6: initialize
Trigger fing new ip number
Error failed to execute script because script could not be compiled

could we do a step by step:

1. download the latest from dropbox (1.6.6)https://www.dropbox.com/s/iyyjn36znuwmw5z/fingscaninstall-1-6-6.zip
2. do a fingscanINSTALL (click on fingscaninstall in the download zip (not fingscan)
3. check if fingscan.app is in ~/Documents/fing
4. check log file if 1.6.6 is running
5. doubleclick on fingscan in ~/documents/fing or better execute schedule "relaunchfingscan" in indigo
6. get log file entries

then post the log file entries.

This "can not compile" seems really wrong. it should not compile at all. its an APP. and it is running, don't know what it wants to compile..

Karl

the string "new ip number" is not in fingscan.app. Do you have something else running that is using fing?


Karl

'fing new ip number' was what i named the trigger from step 2.

Code: Select all

2.) create a trigger that fires if thee is  change in any ip Number
 Step 1: create a trigger
name: “NewIPNumber”
trigger on: any change of variable ipDevsNewIPNumber
action: execute script, select applescript

I renamed it, ran the install script, and get this:

Dec 10, 2013, 6:01:03 AM
Script FINGSCAN-1-6-6: initialize
Trigger NewIPNumber
Error failed to execute script because script could not be compiled
Trigger NewIPNumber
Error failed to execute script because script could not be compiled

in the NewIPNumber script dialing, I see 'expected expression but found unknown token' in red text.

this is not an error message from fingscan but the script you are using to detect a new ip number.

could you post THAT script. it looks like you might have selected py instead of applescript in YOUR trigger.

to test if the your script compiles, go into your trigger and in action click on compile.

Karl

Karl,
Sorry I was away for a while.

OK it is now working perfectly, for some reason fing.bin was not running, I'n not sure why, but ever since I restarted the server (not indigo) suddenly I started to get notifications and I can confirm that everything seems to be working perfectly and I can see ring.bin and fingscan running as they should.

I wrote the short script you gave as an example to delay off by 10 mins and then send me a growl / prowl message and it works exactly as it should. Also the new devices on network works fine as they woke me up last night when my two Nest Protects woke up and connected! I've put a do not disturb on it now

Thanks very much
Gareth

are you on OSX10.9 (Mavericks)? then fingscan can not communicate with indigo if you just start indigo once. It is waiting to be able to communicate before it does anything else.

You have to stop indigo and restart it in order to enable the communication. This is not an indigo problem, but mavericks has some errors.

se also the discussion on mavericks and indigo: reinstall indigo, launch it twice .. seems to help