Hi Karl,
Prior to installing your update, I did some digging and found this in the indigo log. It seems the plugin is resetting sometime shortly after midnight.
- Code: Select all
13 Oct 2020 at 00:19:03
fingscan Error --> setup config, save then a manual reload of plugin
fingscan --> while loop break stopping ... quitNOW was: please setup config , waiting
fingscan Error --> you have 2 minutes to fix config, before restart
fingscan Error --> do a manual reload of plugin
Reloading plugin "fingscan 7.31.54"
Stopping plugin "fingscan 7.31.54" (pid 4681)
fingscan Warning stopConcurrentThread called 2
fingscan runConcurrentThread stopping plugin due to: ::::: no :::::
Plugin restart request ignored (plugin is currently stopping or starting)
fingscan killing 2
Stopped plugin "fingscan 7.31.54"
Starting plugin "fingscan 7.31.54" (pid 29104)
fingscan ========================= initializing ==============================================
fingscan path To files: ==================
fingscan indigo /Library/Application Support/Perceptive Automation/
fingscan installFolder /Library/Application Support/Perceptive Automation/Indigo 7.4/
fingscan plugin.py /Library/Application Support/Perceptive Automation/Indigo 7.4/Plugins/fingscan.indigoPlugin/Contents/Server Plugin/
fingscan Plugin params /Library/Application Support/Perceptive Automation/Indigo 7.4/Preferences/Plugins/com.karlwachs.fingscan/
fingscan !!!!INFO ONLY!!!! logger enabled for INFO !!!!INFO ONLY!!!!
fingscan Warning !!!!INFO ONLY!!!! logger enabled for WARNING !!!!INFO ONLY!!!!
fingscan Error !!!!INFO ONLY!!!! logger enabled for ERROR !!!!INFO ONLY!!!!
fingscan Critical Error !!!!INFO ONLY!!!! logger enabled for CRITICAL !!!!INFO ONLY!!!!
fingscan check /Library/Application Support/Perceptive Automation/Indigo 7.4/Logs/com.karlwachs.fingscan/plugin.log <<<< for detailed logging
fingscan Plugin short Name fing
fingscan my PID 29104
fingscan set params for indigo V 7.4
Started plugin "fingscan 7.31.54"
fingscan testing if variable enableTimeTracking_fing is == on/off/print-option to enable/end/print time tracking of all functions and methods (option:'',calls,cumtime,pcalls,time)
fingscan myLogSet setting parameters -- logFileActive= standard; logFile= ; debug plugin:[]
fingscan FINGSCAN-- initializing will take ~ 2 minutes...; sending logs to
fingscan Warning leaving WiFi parameters at default, not configured in 'fingscan/Configure...'
fingscan getting password
fingscan get password done; checking if FING is installed
fingscan fing install check done
fingscan loaded indigo data
fingscan Warning network info: {'netWorkId': '192.168.1.0', 'broadcast': '192.168.1.255', 'netMask': '255.255.255.0', 'maxHosts': 254, 'hostRange': '192.168.1.1 - 192.168.1.254'}
fingscan ifind plugin: com.corporatechameleon.iFindplugBeta
fingscan MAP2Vendor initializing
fingscan FING initializing parameters
fingscan FING waiting for first data
13 Oct 2020 at 00:19:35
fingscan FING initializing checking if output created, old timeStamp:1602544698.28; new timeStamp:1602544760.68
fingscan FING initialized .. created new data waiting ~ 1 minute for stable operation
fingscan Warning FING pids after step3 = ['29220']
fingscan Warning (re)started FING
fingscan Warning FING initialized
fingscan
fingscan switching off SQL logging for variables
:ipDevsLastDevChangedIndigoName; ipDevsLastUpdate; ipDevsNewDeviceNo; ipDevsNewIPNumber; ipDevice88;
fingscan switching off SQL logging for variables END
fingscan
fingscan switching off SQL logging for devices/state[lastfingup]
:new-10-0A:C1:ED:90:69:4C;
fingscan switching off SQL logging for devices END
13 Oct 2020 at 00:20:13
fingscan FINGSCAN initialized
This is immediately followed by my 'presence' trigger firing:
- Code: Select all
13 Oct 2020 at 00:25:17
Trigger Zero phones at home
This isn't accurate, because all our phones were at home.
I also found this, from the middle of yesterday afternoon:
- Code: Select all
12 Oct 2020 at 16:07:17
fingscan Error updating ipDevice 88 does not exist , (re)creating
There are no other fingscan errors in the log
In answer to your specific questions:
"Just to confirm the devices just disappear from the event definitions, not from the IPdevices folder?"
Correct.
"And could you check if those devices change their indigo device ID before/ aver they disappear?"
Will do, though I'll have to wait for them to disappear again for this. What I do know is that the devices remain in the device subfolder I created for them. I expect Indigo uses the device ID to determine what belongs where, but I don't know that for certain.