Read the statement by Michael Teeuw here.
MMM-SleepWake turn off but not turn on
-
Hi. First of all, thanks for your work @sdetweil.
I wanted to use your module but I don’t know what I did wrong.
When no motion is detected, I am able to hide the screen but when I move. Nothing happen.I am using a Pi Camera module v2.
I have tried to follow the documentation on your repository:
- I have added the module in config.js:
pi@raspberrypi:~ $ nano MagicMirror/config/config.js { module: 'MMM-SleepWake', config:{ delay: 0.5, // default mode: 'hide' //debug: true } }
- I have made the changes required in motion.conf
pi@raspberrypi:~ $ sudo nano /etc/motion/motion.conf # Command to be executed when an event starts. (default: none) # An event starts at first motion detected after a period of no motion defined by event_gap. ; on_event_start /home/pi/MagicMirror/modules/MMM-SleepWake/external_motion started # Command to be executed when an event ends after a period of no motion # (default: none). The period of no motion is defined by option event_gap. ; on_event_end /home/pi/MagicMirror/modules/MMM-SleepWake/external_motion ended
Then I have checked if I had correctly installed the motion project and if it worked properly. Everything seems to work:
pi@raspberrypi:~ $ /var/log/motion/motion.log [1865352:motion] [NTC] [ALL] [Jan 18 12:19:13] motion_startup: Using log type (ALL) log level (NTC) [1865352:motion] [NTC] [ENC] [Jan 18 12:19:13] ffmpeg_global_init: ffmpeg libavcodec version 58.35.100 libavformat version 58.20.100 [0:motion] [NTC] [ALL] [Jan 18 12:19:13] main: Camera ID: 0 is from /etc/motion/motion.conf [0:motion] [NTC] [ALL] [Jan 18 12:19:13] main: Camera ID: 0 Camera Name: (null) Device: /dev/video0 [0:motion] [NTC] [ALL] [Jan 18 12:19:13] main: Waiting for threads to finish, pid: YYYY [1:ml1] [NTC] [ALL] [Jan 18 12:19:13] motion_init: Camera 0 started: motion detection Enabled [1:ml1] [NTC] [VID] [Jan 18 12:19:13] vid_start: Opening V4L2 device [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_start: Using videodevice /dev/video0 and input -1 [0:wc0] [NTC] [STR] [Jan 18 12:19:13] http_bindsock: listening on 127.0.0.1 port XXXX [0:wc0] [NTC] [STR] [Jan 18 12:19:13] httpd_run: Started motion-httpd server on port XXXX (auth Disabled) [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_get_capability: ------------------------ cap.driver: "bm2835 mmal" cap.card: "mmal service 16.1" cap.bus_info: "platform:bcm2835-v4l2" cap.capabilities=0x85200005 ------------------------ [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_get_capability: - VIDEO_CAPTURE [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_get_capability: - VIDEO_OVERLAY [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_get_capability: - READWRITE [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_get_capability: - STREAMING [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_select_input: name = "Camera 0", type 0x00000002, status 00000000 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_select_input: - CAMERA [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_select_input: Device does not support specifying PAL/NTSC norm [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_do_set_pix_format: Testing palette YU12 (320x240) [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_do_set_pix_format: Using palette YU12 (320x240) bytesperlines 320 sizeimage 115200 colorspace 00000001 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: found control 0x00980900, "Brightness", range 0,100 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: "Brightness", default 50, current 50 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: found control 0x00980901, "Contrast", range -100,100 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: "Contrast", default 0, current 0 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: found control 0x00980902, "Saturation", range -100,100 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: "Saturation", default 0, current 0 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: found control 0x00980918, "Power Line Frequency", range 0,3 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: "Power Line Frequency", default 1, current 1 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: found control 0x0098090e, "Red Balance", range 1,7999 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: "Red Balance", default 1000, current 1000 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: found control 0x0098090f, "Blue Balance", range 1,7999 [1:ml1] [NTC] [VID] [Jan 18 12:19:13] v4l2_scan_controls: "Blue Balance", default 1000, current 1000 [1:ml1] [NTC] [ALL] [Jan 18 12:19:13] image_ring_resize: Resizing pre_capture buffer to 1 items [1:ml1] [NTC] [STR] [Jan 18 12:19:13] http_bindsock: listening on 127.0.0.1 port XXXX [1:ml1] [NTC] [ALL] [Jan 18 12:19:13] motion_init: Started motion-stream server on port XXXX (auth Disabled) [1:ml1] [NTC] [EVT] [Jan 18 12:19:17] event_newfile: File of type 8 saved to: /var/lib/motion/01-20210118121917.mkv [1:ml1] [NTC] [ALL] [Jan 18 12:19:17] motion_detected: Motion detected - starting event 1 [1:ml1] [NTC] [ALL] [Jan 18 12:19:25] mlp_actions: End of event 1 [0:wc0] [NTC] [STR] [Jan 18 12:19:25] httpd_run: motion-httpd - Finishing [0:wc0] [NTC] [STR] [Jan 18 12:19:25] httpd_run: motion-httpd Closing [0:wc0] [NTC] [STR] [Jan 18 12:19:25] motion_web_control: motion-httpd thread exit [1:ml1] [NTC] [ALL] [Jan 18 12:19:25] motion_loop: Thread exiting [1:ml1] [NTC] [STR] [Jan 18 12:19:25] stream_stop: Closing motion-stream listen socket & active motion-stream sockets [1:ml1] [NTC] [STR] [Jan 18 12:19:25] stream_stop: Closed motion-stream listen socket & active motion-stream sockets [1:ml1] [NTC] [VID] [Jan 18 12:19:25] vid_close: Cleaning up V4L2 device [1:ml1] [NTC] [VID] [Jan 18 12:19:25] v4l2_cleanup: Closing video device /dev/video0 [0:motion] [NTC] [ALL] [Jan 18 12:19:26] main: Threads finished [0:motion] [NTC] [ALL] [Jan 18 12:19:27] main: Motion terminating [0:motion] [NTC] [ALL] [Jan 18 12:19:27] motion_remove_pid: Closing logfile (/var/log/motion/motion.log).
And here is the log when I am using the magic mirror:
pi@raspberrypi:~/MagicMirror $ npm start > magicmirror@2.14.0 start /home/pi/MagicMirror > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js [18.01.2021 11:49.07.972] [LOG] Starting MagicMirror: v2.14.0 [18.01.2021 11:49.08.004] [LOG] Loading config ... [18.01.2021 11:49.08.014] [LOG] Loading module helpers ... [18.01.2021 11:49.08.909] [LOG] Initializing new module helper ... [18.01.2021 11:49.08.916] [LOG] handler helper in init [18.01.2021 11:49.08.917] [LOG] Module helper loaded: MMM-SleepWake [18.01.2021 11:49.08.986] [LOG] All module helpers loaded. [18.01.2021 11:49.09.126] [LOG] Starting server on port XXXX ... [18.01.2021 11:49.09.149] [LOG] Server started ... [18.01.2021 11:49.09.153] [LOG] Connecting socket for: MMM-SleepWake [18.01.2021 11:49.09.153] [LOG] handler helper in start [18.01.2021 11:49.09.157] [LOG] Sockets connected & modules started ... [18.01.2021 11:49.09.535] [LOG] Launching application. [18.01.2021 11:49.09.681] [WARN] (electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false". It will change to be "true" in Electron 9. For more information please check https://github.com/electron/electron/issues/18397 [18.01.2021 11:49.11.953] [LOG] sleep-wake helper in socket notification=config [18.01.2021 11:49.11.996] [LOG] external source defined dir=/home/pi/MagicMirror/modules/MMM-SleepWake/motion [18.01.2021 11:49.12.005] [INFO] Checking git for module: MMM-SleepWake [18.01.2021 11:49.41.955] [LOG] sleep-wake helper in socket notification=start_sleep [18.01.2021 11:49.41.957] [LOG] processing start sleep [18.01.2021 11:49.41.962] [LOG] using HIDE approach [18.01.2021 11:50.14.012] [LOG] Shutting down server... [18.01.2021 11:50.14.015] [LOG] handler helper in stop
I am not able to see what is wrong in my configuration. I hope someone will be able to help me.
-
@krosamont remove the ; in motion.conf on the two lines u edited
no leading ; or #
-
@sdetweil thanks for the quick answer. Sorry I should have payed more attention to this. I have made the modification into motion.conf:
# Command to be executed when an event starts. (default: none) # An event starts at first motion detected after a period of no motion defined by event_gap on_event_start /home/pi/MagicMirror/modules/MMM-SleepWake/external_motion started # Command to be executed when an event ends after a period of no motion # (default: none). The period of no motion is defined by option event_gap. on_event_end /home/pi/MagicMirror/modules/MMM-SleepWake/external_motion ended
But it still doesn’t turn on after the sleep…
-
@krosamont then u have to restart motion module
u can test the start/stop commands
from a terminal window or over ssh
-
@krosamont but it sleeps on timer(no motion) and wakes on motion.
how long after motion til motion fires the ended event?look in /var/log/motion.log
may have to fiddle w some motion settings.
i changed my time gap down to 15 seconds
the camera is detecting motion constantly -
@sdetweil said in MMM-SleepWake turn off but not turn on:
start/stop commands
You mean going to the terminal and write:
pi@raspberrypi:~/MagicMirror $ sudo service motion start pi@raspberrypi:~/MagicMirror $ sudo service motion stop
I have done it. nothing happened
-
@sdetweil the default setting is:
# Maximum number of frames to be captured per second. # Valid range: 2-100. Default: 100 (almost no limit). framerate 2
and I have changed the gap event from 60 to 15:
# Event Gap is the seconds of no motion detection that triggers the end of an event. # An event is defined as a series of motion images taken within a short timeframe. # Recommended value is 60 seconds (Default). The value -1 is allowed and disables # events causing all Motion to be written to one single movie file and no pre_capture. # If set to 0, motion is running in gapless mode. Movies don't have gaps anymore. An # event ends right after no more motion is detected and post_capture is over. event_gap 15
It sounds good, isn’t it?
I have also installed the module again :
pi@raspberrypi:~/MagicMirror/modules/MMM-SleepWake $ npm install
and I have tried to use your module without using MMM-Face-Reco-DNN…
but still I don’t find the solution -
By the way, I have also noticed that no log are generated in motion.log when I am using the mirror? The log is generated only when I do this command:
pi@raspberrypi:~ $ motion
Is it normal?
-
@krosamont motion is a module outside mm
u have to run it all the timei think u will have to do
sudo motion &
to start it -
Hello @chanster,
How do you run your magic mirror project please?
@sdetweil I have tried:pi@raspberrypi:~/MagicMirror $ sudo service motion start pi@raspberrypi:~/MagicMirror $ npm start
Still nothing. And nothing appears in the log. I think this is the problem…
If I do:
pi@raspberrypi:~/MagicMirror $ sudo motion & pi@raspberrypi:~/MagicMirror $ npm start
Then I get an error and the cam is playing my mirror but there, I have the log!!! :/
I think we are close…:face_with_monocle: