Error is gone. Thanks.
Greetings,
Adrian
Using Fing as a new way to detect smartphone presence
Re: Using Fing as a new way to detect smartphone presence
Having actual devices is a big improvement. No problems and great app. Thanks for all of your work on this.
Re: Using Fing as a new way to detect smartphone presence
https://www.dropbox.com/s/3izupm31s2or4 ... -4-6-4.zip v 6-6-4
fixes:
- one logic error if distance information was used.
added:
- complete set of documentation (PDF) on install, process, background, how it works, how to use , basic example and complex example.
- it dynamically adjusts the find my i device distance info update frequency depending on distance away from home. If the state is DOWN it updates more frequently if the device comes closer to home.
Karl
fixes:
- one logic error if distance information was used.
added:
- complete set of documentation (PDF) on install, process, background, how it works, how to use , basic example and complex example.
- it dynamically adjusts the find my i device distance info update frequency depending on distance away from home. If the state is DOWN it updates more frequently if the device comes closer to home.
Karl
Re: Using Fing as a new way to detect smartphone presence
https://www.dropbox.com/s/wtskpss0ja5zb ... -4-7-1.zip v 4-7-1
fixes:
- display of status-datestamp was not updated immediately (the state :status" was)
added functionality:
++ added option for frequency of updates 1secs -10 seconds to allow for different users needs. 1 second is the fastest, but somewhat taxing on CPU if you have a smaller box. 2 -3 seconds is a good compromise.
++ added better integration with findMyIdevices (you need to download the edited version, the link is in the zip file):
+++++ added more device states to find my i device; time stamp of device data, not request of update timestamp, update sequential# to better control update validity, location method, and manualUpdateNoWait action to avoid occasional timeouts that kill the plugin.
+++++ update frequency of distance is dynamically adjusted depending on distance and state of device. If it is connected to the wifi network: lowest update frequency, If out of wifi range AND
< 1.miles: once every 1.5 minutes
<3 miles: once every 2 minutes
< 6 miles once every 7 minutes
< 12 miles once every 15 minutes...
this will reduce the number of times findmyidevice is contacting the apple server, but ensures accurate distance information when coming closer to "HOME"
++ added dynamic changes in update frequency after a change of STATE (i.e. AWAY). For 12-30 seconds the state is tested more frequently to avoid temporary "AWAY" modes if the the ip device is not responding to a ping or temporality leaves the wifi range. The length of increased testing.checking can be set to 12 or 30 seconds.
++ improved configuration interface, less configuration options are shown if they are not enabled. -- makes it look nicer.
In my version I can get information accuracy down to ~ 1 second if my iPhone comes or leaves the building. It enables door opening and looking "almost" error free. ==>. WiFi must be on!
the included PDF describes the setup with examples.- the README has a quick install guide.
Karl
footnote: the modified FindMyIdevice is not an authorized version by the author. All credits go to Benjamin. Use at your own risk. BUT I thought, I share this version as it delivers more flexibility& information and some bug fixes for some rare situations. 99.999% of the code is from Benjamin, just adopted it to my needs.
fixes:
- display of status-datestamp was not updated immediately (the state :status" was)
added functionality:
++ added option for frequency of updates 1secs -10 seconds to allow for different users needs. 1 second is the fastest, but somewhat taxing on CPU if you have a smaller box. 2 -3 seconds is a good compromise.
++ added better integration with findMyIdevices (you need to download the edited version, the link is in the zip file):
+++++ added more device states to find my i device; time stamp of device data, not request of update timestamp, update sequential# to better control update validity, location method, and manualUpdateNoWait action to avoid occasional timeouts that kill the plugin.
+++++ update frequency of distance is dynamically adjusted depending on distance and state of device. If it is connected to the wifi network: lowest update frequency, If out of wifi range AND
< 1.miles: once every 1.5 minutes
<3 miles: once every 2 minutes
< 6 miles once every 7 minutes
< 12 miles once every 15 minutes...
this will reduce the number of times findmyidevice is contacting the apple server, but ensures accurate distance information when coming closer to "HOME"
++ added dynamic changes in update frequency after a change of STATE (i.e. AWAY). For 12-30 seconds the state is tested more frequently to avoid temporary "AWAY" modes if the the ip device is not responding to a ping or temporality leaves the wifi range. The length of increased testing.checking can be set to 12 or 30 seconds.
++ improved configuration interface, less configuration options are shown if they are not enabled. -- makes it look nicer.
In my version I can get information accuracy down to ~ 1 second if my iPhone comes or leaves the building. It enables door opening and looking "almost" error free. ==>. WiFi must be on!
the included PDF describes the setup with examples.- the README has a quick install guide.
Karl
footnote: the modified FindMyIdevice is not an authorized version by the author. All credits go to Benjamin. Use at your own risk. BUT I thought, I share this version as it delivers more flexibility& information and some bug fixes for some rare situations. 99.999% of the code is from Benjamin, just adopted it to my needs.
Re: Using Fing as a new way to detect smartphone presence
https://www.dropbox.com/sh/1d60h3xuh6xg ... -4-8-1.zip v 4-8-1
fixes:
- when a device changes IP numbers (*) FING lists them twice in its report. This version will pick the right one and display proper state. The logic is a bit tricky to decide which one is the right one.
- some smaller fixes on log file formats config menus, event triggering etc.
added:
- PDF: examples for an ACTION how to send email with proper information when a new device enters network or when an ip number changed.
Karl
(*) IP cameras do that sometimes when they reconnect or you setup a local IP number vs a DHCP assigned IP number..
for find my iDevices I added one more error control: in case the network is down, it does not crash. download yourself from the link given in the zip file.
fixes:
- when a device changes IP numbers (*) FING lists them twice in its report. This version will pick the right one and display proper state. The logic is a bit tricky to decide which one is the right one.
- some smaller fixes on log file formats config menus, event triggering etc.
added:
- PDF: examples for an ACTION how to send email with proper information when a new device enters network or when an ip number changed.
Karl
(*) IP cameras do that sometimes when they reconnect or you setup a local IP number vs a DHCP assigned IP number..
for find my iDevices I added one more error control: in case the network is down, it does not crash. download yourself from the link given in the zip file.
Re: Using Fing as a new way to detect smartphone presence
https://www.dropbox.com/s/moh4t09n26x27 ... -4-9-1.zip V 4.9.1
Fixed:
some formatting, printing to log file
Added:
- can now utilize PING information injected in-between FING cycles (1/minute) This can speedup the detection of status change from UP to DOWN to ~[EDIT] 3 seconds
this feature can be switched on and off in Config
- each device can be enabled to "usePing" individually, go into device editor and set accordingly per device
- WIFI/ ethernet can be set in the device editor. This information is just used for information display in the device listing (after the IP number)
- option to save and reload device information. The Menu option will read the previously saved file and will repopulate all device information from scratch from the information in the file
Hierarchy of information :
In raising priority and detection speed
1. 1 Minute: FING scans network once a minute. It detects UP or DOWN through ping and other traffic on the network
2. 1 Second*): FING listens to traffic for a new device joining or a DOWN device rejoining the network setting device status to UP
3. 1 Second*): usePing to detect transition from UP to DOWN.
4. 1 second*): WiFi information from router. The ASUS router (others to follow) detect within milliseconds if a device is online or offline.
*) The time to detect a status change depends on the setting “seconds to sleep between action”. It can be set to 1..10 seconds.
If information is available from #4 it will overwrite # 1, 2, 3 and if information is available from #3 it will overwrite #1, 2 and #2 will overwrite information from # 1.
With all 4 methods in place detection time can be ~ 1-3 seconds for all cases i.e. UP or DOWN state detection. (**)
More information in the included PDF
Karl
-there are some special circumstance that will not be detect: if a device goes up/down/up within 1 minute it will only detect the first UP and Down not the second UP- that will take 1 minute.
-without the WIFI router information you will find some false "down" states for wireless devices as they might not be answering a ping when in power save mode.
- FINGSCAN will be checking time to perform PINGs, if it takes longer than 2/4/8/.. seconds the frequency of PINGs will be throttled, to not overload the MAC (not a network issue)
- PING option is setup to send max 2 pings and wait for 1 seconds for each PING. If the first answers it does not send another ping to that device.
If all devices answer it takes ~ 0.2-0.8 seconds to finish pinging 20 "up" devices (in my network), if a device is not answering add 2 seconds per device.
Fixed:
some formatting, printing to log file
Added:
- can now utilize PING information injected in-between FING cycles (1/minute) This can speedup the detection of status change from UP to DOWN to ~[EDIT] 3 seconds
this feature can be switched on and off in Config
- each device can be enabled to "usePing" individually, go into device editor and set accordingly per device
- WIFI/ ethernet can be set in the device editor. This information is just used for information display in the device listing (after the IP number)
- option to save and reload device information. The Menu option will read the previously saved file and will repopulate all device information from scratch from the information in the file
Hierarchy of information :
In raising priority and detection speed
1. 1 Minute: FING scans network once a minute. It detects UP or DOWN through ping and other traffic on the network
2. 1 Second*): FING listens to traffic for a new device joining or a DOWN device rejoining the network setting device status to UP
3. 1 Second*): usePing to detect transition from UP to DOWN.
4. 1 second*): WiFi information from router. The ASUS router (others to follow) detect within milliseconds if a device is online or offline.
*) The time to detect a status change depends on the setting “seconds to sleep between action”. It can be set to 1..10 seconds.
If information is available from #4 it will overwrite # 1, 2, 3 and if information is available from #3 it will overwrite #1, 2 and #2 will overwrite information from # 1.
With all 4 methods in place detection time can be ~ 1-3 seconds for all cases i.e. UP or DOWN state detection. (**)
More information in the included PDF
Karl
-there are some special circumstance that will not be detect: if a device goes up/down/up within 1 minute it will only detect the first UP and Down not the second UP- that will take 1 minute.
-without the WIFI router information you will find some false "down" states for wireless devices as they might not be answering a ping when in power save mode.
- FINGSCAN will be checking time to perform PINGs, if it takes longer than 2/4/8/.. seconds the frequency of PINGs will be throttled, to not overload the MAC (not a network issue)
- PING option is setup to send max 2 pings and wait for 1 seconds for each PING. If the first answers it does not send another ping to that device.
If all devices answer it takes ~ 0.2-0.8 seconds to finish pinging 20 "up" devices (in my network), if a device is not answering add 2 seconds per device.
Re: Using Fing as a new way to detect smartphone presence
https://www.dropbox.com/s/9rf11vkcnhhsj ... 4-10-2.zip v4-10-2
fixed:
FING was started each time you restart fingscan. This was working before, somehow the code changed, must have done an edit / replace ... at some late night session. Anyway its back again to normal: only one FING instance will run.
added
- test WiFi signal strength. If it drops for more than xx seconds for more than yy devices by more than zz dBm it will create a BADWiFi event you can set a trigger on.
- the last version introduced pings in-between FING cycles for devices that are UP.
Each ping was done in a linear sequence one device after the next. In this version it is now done in parallel processes so that the plugin does not have to wait for each PING.(*)
The total load on my MAC-PRO2008 for ~ 15 "UP" devices continuously pinged every second (fastest setting) is < 1%.
The network impact should be negligible~ 1.5kbytes per second < 0.1% network load (on a 54Mbit WiFi network)
see attached PDF for more details and examples.
Karl
out for a vacation trip to Cape Cod for 1 week...
(*)
for those who like to look at UNIX shell commands:
A unix shell command loops:( sends a ping and goes back to sleep until the next time slot) It sleeps as configured in the cycle time setting one ping every (~ 1/2 of the cycle time =1...5.5 seconds)
explanation:
1500: never create endless loops, start another process when this one ends
-c 1 : one ping and one ping only (per loop)
>/dev/null : no output created, send it into the black hole "null"
-W 900: ping timeout at 900 milli seconds
/sbin/ping : as it is a shell not stared from a regular terminal session, it does not know where ping is, have to add the path to it.
echo up >...: will ONLY be executed if ping was successful due to the && in front of it, i.e. create a new file ..153.ping with a new date stamp that will be checked by fingscan
sleep 1.5: wait for 1.5 seconds for the next cycle.
fixed:
FING was started each time you restart fingscan. This was working before, somehow the code changed, must have done an edit / replace ... at some late night session. Anyway its back again to normal: only one FING instance will run.
added
- test WiFi signal strength. If it drops for more than xx seconds for more than yy devices by more than zz dBm it will create a BADWiFi event you can set a trigger on.
- the last version introduced pings in-between FING cycles for devices that are UP.
Each ping was done in a linear sequence one device after the next. In this version it is now done in parallel processes so that the plugin does not have to wait for each PING.(*)
The total load on my MAC-PRO2008 for ~ 15 "UP" devices continuously pinged every second (fastest setting) is < 1%.
The network impact should be negligible~ 1.5kbytes per second < 0.1% network load (on a 54Mbit WiFi network)
see attached PDF for more details and examples.
Karl
out for a vacation trip to Cape Cod for 1 week...
(*)
for those who like to look at UNIX shell commands:
A unix shell command loops:( sends a ping and goes back to sleep until the next time slot) It sleeps as configured in the cycle time setting one ping every (~ 1/2 of the cycle time =1...5.5 seconds)
Code: Select all
for ((i=0;i<1500;i++)); do /sbin/ping -c 1 -W 900 -o 192.168.1.153 &>/dev/null && echo up>/Users/yourusername/Documents/fing/pings/153.ping && sleep 1.5 ; done1500: never create endless loops, start another process when this one ends
-c 1 : one ping and one ping only (per loop)
>/dev/null : no output created, send it into the black hole "null"
-W 900: ping timeout at 900 milli seconds
/sbin/ping : as it is a shell not stared from a regular terminal session, it does not know where ping is, have to add the path to it.
echo up >...: will ONLY be executed if ping was successful due to the && in front of it, i.e. create a new file ..153.ping with a new date stamp that will be checked by fingscan
sleep 1.5: wait for 1.5 seconds for the next cycle.
Re: Using Fing as a new way to detect smartphone presence
Hi,
Getting errors after installing v4.10.2.
Thank’s, Cuono
Getting errors after installing v4.10.2.
Thank’s, Cuono
Code: Select all
fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2470, in runConcurrentThread
File "plugin.py", line 2644, in updateDeviceWiFiSignal
<type 'exceptions.UnboundLocalError'>: local variable 'theMAC' referenced before assignment
fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)Re: Using Fing as a new way to detect smartphone presence
Seeing this same issue as the post above.
Re: Using Fing as a new way to detect smartphone presence
https://www.dropbox.com/s/xywjpp8lejmpa ... 3.zip?dl=0 v 4-10-3
this should fix that..
sorry for the error
Karl
this should fix that..
sorry for the error
Karl
Re: Using Fing as a new way to detect smartphone presence
Tried upgrading right to 4.10.3 from 4.8.1. Got this error upon installing:
So I started downgrading one version at a time. The same error kept occurring until I was back at 4.8.1.
Code: Select all
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)M4 Mac mini.
Re: Using Fing as a new way to detect smartphone presence
I am out of town. Will try to look into it. But it will take some time.
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
Re: Using Fing as a new way to detect smartphone presence
looked at the code line 2333:
"updateStates.append("ipNumber")"
has nothing to do with the error message.. rally don't know where to look
could share a bit more on your setup.. is there any other message anything else in the log file?
do you get the same line number error in the other versions?
Karl
"updateStates.append("ipNumber")"
has nothing to do with the error message.. rally don't know where to look
could share a bit more on your setup.. is there any other message anything else in the log file?
do you get the same line number error in the other versions?
Karl
Re: Using Fing as a new way to detect smartphone presence
This was in the event log after installing 4.10.3
2014-08-23 18:16:01.411 Application Upgrading plugin "fingscan" to newer version 4.10.3 (previous version moved to trash)
2014-08-23 18:16:01.470 Application Loading plugin "fingscan 4.10.3"
2014-08-23 18:16:01.476 Application Starting plugin "fingscan 4.10.3" (pid 52202)
2014-08-23 18:16:02.799 Application Started plugin "fingscan 4.10.3"
2014-08-23 18:16:02.799 fingscan FINGSCAN--V 4.10.3 initializing will take ~ 2 minutes...
2014-08-23 18:16:02.876 fingscan Error Error in plugin execution startup:
Traceback (most recent call last):
File "plugin.py", line 195, in startup
File "plugin.py", line 1811, in getIndigoIpVariablesIntoData
<type 'exceptions.IndexError'>: list index out of range
2014-08-23 18:16:08.940 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2496, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:16:08.941 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:16:25.049 fingscan Error Error in plugin execution runConcurrentThread:
Then 4.10.2
2014-08-23 18:19:06.211 Application Starting plugin "fingscan 4.10.2" (pid 52276)
2014-08-23 18:19:06.556 Application Started plugin "fingscan 4.10.2"
2014-08-23 18:19:06.557 fingscan FINGSCAN--V 4.10.2 initializing will take ~ 2 minutes...
2014-08-23 18:19:06.611 fingscan Error Error in plugin execution startup:
Traceback (most recent call last):
File "plugin.py", line 195, in startup
File "plugin.py", line 1811, in getIndigoIpVariablesIntoData
<type 'exceptions.IndexError'>: list index out of range
2014-08-23 18:19:12.659 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2470, in runConcurrentThread
File "plugin.py", line 2644, in updateDeviceWiFiSignal
<type 'exceptions.UnboundLocalError'>: local variable 'theMAC' referenced before assignment
Then 4.9.1
2014-08-23 18:20:15.509 Application Starting plugin "fingscan 4.9.1" (pid 52311)
2014-08-23 18:20:16.026 Application Started plugin "fingscan 4.9.1"
2014-08-23 18:20:16.026 fingscan FINGSCAN--V 4.9.1 initializing will take ~ 2 minutes...
2014-08-23 18:20:16.041 fingscan Error Error in plugin execution startup:
Traceback (most recent call last):
File "plugin.py", line 184, in startup
File "plugin.py", line 1708, in getIndigoIpVariablesIntoData
<type 'exceptions.IndexError'>: list index out of range
2014-08-23 18:20:22.346 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:20:22.347 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:20:38.725 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:20:38.726 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:20:54.980 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:20:54.980 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:21:10.982 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:21:10.982 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:21:27.127 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:21:27.128 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:21:30.236 Application Stopping plugin "fingscan" (pid 52311)
2014-08-23 18:21:30.291 fingscan stopConcurrentThread called 1
2014-08-23 18:21:30.291 fingscan stopConcurrentThread called 2
2014-08-23 18:21:30.328 fingscan shutdown called
2014-08-23 18:21:31.354 Application Stopped plugin "fingscan"
2014-08-23 18:16:01.411 Application Upgrading plugin "fingscan" to newer version 4.10.3 (previous version moved to trash)
2014-08-23 18:16:01.470 Application Loading plugin "fingscan 4.10.3"
2014-08-23 18:16:01.476 Application Starting plugin "fingscan 4.10.3" (pid 52202)
2014-08-23 18:16:02.799 Application Started plugin "fingscan 4.10.3"
2014-08-23 18:16:02.799 fingscan FINGSCAN--V 4.10.3 initializing will take ~ 2 minutes...
2014-08-23 18:16:02.876 fingscan Error Error in plugin execution startup:
Traceback (most recent call last):
File "plugin.py", line 195, in startup
File "plugin.py", line 1811, in getIndigoIpVariablesIntoData
<type 'exceptions.IndexError'>: list index out of range
2014-08-23 18:16:08.940 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2496, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:16:08.941 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:16:25.049 fingscan Error Error in plugin execution runConcurrentThread:
Then 4.10.2
2014-08-23 18:19:06.211 Application Starting plugin "fingscan 4.10.2" (pid 52276)
2014-08-23 18:19:06.556 Application Started plugin "fingscan 4.10.2"
2014-08-23 18:19:06.557 fingscan FINGSCAN--V 4.10.2 initializing will take ~ 2 minutes...
2014-08-23 18:19:06.611 fingscan Error Error in plugin execution startup:
Traceback (most recent call last):
File "plugin.py", line 195, in startup
File "plugin.py", line 1811, in getIndigoIpVariablesIntoData
<type 'exceptions.IndexError'>: list index out of range
2014-08-23 18:19:12.659 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2470, in runConcurrentThread
File "plugin.py", line 2644, in updateDeviceWiFiSignal
<type 'exceptions.UnboundLocalError'>: local variable 'theMAC' referenced before assignment
Then 4.9.1
2014-08-23 18:20:15.509 Application Starting plugin "fingscan 4.9.1" (pid 52311)
2014-08-23 18:20:16.026 Application Started plugin "fingscan 4.9.1"
2014-08-23 18:20:16.026 fingscan FINGSCAN--V 4.9.1 initializing will take ~ 2 minutes...
2014-08-23 18:20:16.041 fingscan Error Error in plugin execution startup:
Traceback (most recent call last):
File "plugin.py", line 184, in startup
File "plugin.py", line 1708, in getIndigoIpVariablesIntoData
<type 'exceptions.IndexError'>: list index out of range
2014-08-23 18:20:22.346 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:20:22.347 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:20:38.725 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:20:38.726 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:20:54.980 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:20:54.980 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:21:10.982 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:21:10.982 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:21:27.127 fingscan Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 2333, in runConcurrentThread
<type 'exceptions.AttributeError'>: 'Plugin' object has no attribute 'updatePrefs'
2014-08-23 18:21:27.128 fingscan Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
2014-08-23 18:21:30.236 Application Stopping plugin "fingscan" (pid 52311)
2014-08-23 18:21:30.291 fingscan stopConcurrentThread called 1
2014-08-23 18:21:30.291 fingscan stopConcurrentThread called 2
2014-08-23 18:21:30.328 fingscan shutdown called
2014-08-23 18:21:31.354 Application Stopped plugin "fingscan"
M4 Mac mini.
Re: Using Fing as a new way to detect smartphone presence
Ok I can do something with that. But I am out and no access to my home mac. Will need to wait until next Sunday.
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk