@sdetweil No joy. No errors being posted for mystandings. I am using facial reco as well. And I see messages showing when mystandings (and myscores) indicating the module being hidden, suspended, and resumed according to the personna set in the config file. The same messages are being posted for the myscores module using the same personna definitions which works just fine. But mystands doesn’t appear to be resuming (or unhidden?) on the screen like it should.

@sdetweil my console log captures 12 hours before it wraps, but no errors are present when I notice the module has stopped. If it stopped within this timeframe I’ve not found errors.

After an indeterminate period if time ( hours, days??), the MMM-MyStandings module either stops or just disappears from the screen. I don’t know exactly when it happens but haven’t found any related messages written to the console log. Does anyone have thoughts on how to catch if errors are being issued? Also is there a way to restart a single module without restarting everything ?

@nischi If a user who isn’t known by Face-Reco-DNN moves in front of the camera, is a notification message generated and picked up by MMM-MotionControl? It doesn’t look like the “default” and/or “everyone” classes toggles the screen to un-blank. I was expecting that ANY motion (changes in the capture frames from the camera) would un-blank, but I’m not seeing this behavior. No log-in message gets written to the log.

My dataclass boolean operation error got solved. https://forum.magicmirror.builders/post/78948

@sdetweil “after all this time” is right! I kept telling myself the issue couldn’t be the code itself because there were no posts about it on the forum, so it had to be something I (or my environment) was doing wrong.

FIXED: updated the ap.add_argument statement (line 66) of facerecognition.py to include “type=float” on the --tolerance variable

It does look like there is a dataclass issue with the “tolerance” variable. Running facerecognition.py from the commandline with only the --cascade & --encodings parameters, the module executes. However, if adding the --tolerance parameter which alters the variable from the default value, it fails on the boolean statement. Also, even commenting out the variable in the MM config.js file apparently still passes something to the module for this variable, because it fails the same as including the --tolerance value at stand alone startup. So, any thoughts on how to fix it??

@ghiesseldorf ```
[ERROR] Whoops! There was an uncaught exception…
[2020-07-20 13:16:36.029] [ERROR] PythonShellError: TypeError: ‘<’ not supported between instances of ‘numpy.ndarray’ and ‘str’
at PythonShell.parseError (/home/pi/MagicMirror/modules/MMM-Face-Reco-DNN/node_modules/python-shell/index.js:246:21)
at terminateIfNeeded (/home/pi/MagicMirror/modules/MMM-Face-Reco-DNN/node_modules/python-shell/index.js:129:32)
at ChildProcess. (/home/pi/MagicMirror/modules/MMM-Face-Reco-DNN/node_modules/python-shell/index.js:121:13)
at ChildProcess.emit (events.js:200:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
----- Python Traceback -----
File “modules/MMM-Face-Reco-DNN/tools/facerecognition.py”, line 143, in
if minDistance < args[“tolerance”]: {
traceback: 'Traceback (most recent call last):\n File ’ +
'“modules/MMM-Face-Reco-DNN/tools/facerecognition.py”, line ’ +
‘143, in \n if minDistance < args[“tolerance”]:\n’ +
"TypeError: ‘<’ not supported between instances of " +
“‘numpy.ndarray’ and ‘str’\n”,
executable: ‘python3’,
options: null,
script: ‘modules/MMM-Face-Reco-DNN/tools/facerecognition.py’,
args: [
‘–cascade=modules/MMM-Face-Reco-DNN/tools/haarcascade_frontalface_default.xml’,
‘–encodings=modules/MMM-Face-Reco-DNN/tools/encodings.pickle’,
‘–usePiCamera=1’,
‘–source=0’,
‘–rotateCamera=0’,
‘–method=dnn’,
‘–detectionMethod=hog’,
‘–interval=2000’,
‘–output=0’,
‘–extendDataset=False’,
‘–dataset=modules/MMM-Face-Reco-DNN/dataset/’,
‘–tolerance=0.6’
],
exitCode: 1