zmu not working?

[marcjw]

I just updated to 1.37.66 from 1.35 and have no complaints so far but I can't seem to get zmu to work.
This used to work in 1.35:

Code: Select all

sudo -u www-data zmu -m1 -D -U <user> -P <password>

No errors; it just doesn't disable it. It also used to change the change the activity button from green to orange but not now.
Known issue? Am I doing it wrong?

[iconnor]

The meaning of the various commands has changed... In 1.36 we have

-E, --enable : Enable detection, wake monitor up
-D, --disable : Disable detection, put monitor to sleep
-u, --suspend : Suspend detection, useful to prevent bogus alarms when panning etc
-r, --resume : Resume detection after a suspend

What's the difference between enable/resume and disable/suspend? The code implementing them was confused as well. I suspect many developers over the years got confused. SO I changed it. Now we have:

-E, --enable : Enable capture, wake monitor up
-D, --disable : Disable capture, put monitor to sleep
-u, --suspend : Suspend motion detection, useful to prevent bogus alarms when panning etc
-r, --resume : Resume motion detection after a suspend

-D should stop capturing completely.

Of course, as you noticed, it does not. I guess I never implemented that. Fix incoming. Packages building...

[marcjw]

I found your emergency build and it's good news - the zmu -D option now works works! Unfortunately, there seems to be a daemon gremlin that wants to keep restarting it after a few seconds. That is definitely not desired.

Code: Select all

06/13/2025 19:43:19.392542 zmwatch[14468].WAR [main:160] [Restarting capture daemon for Kitchen, time since last capture 46 seconds (1749861799-1749861753)]
06/13/2025 19:45:19.766598 zmwatch[14468].WAR [main:160] [Restarting capture daemon for Kitchen, time since last capture 46 seconds (1749861919-1749861873)]
06/13/2025 19:47:20.014745 zmwatch[14468].WAR [main:160] [Restarting capture daemon for Kitchen, time since last capture 47 seconds (1749862040-1749861993)]
06/13/2025 19:47:40.351236 zmwatch[14468].WAR [main:139] [Restarting capture daemon for 1 Kitchen, no image since startup. Startup time was 0 - now 1749862060 > 45]
06/13/2025 19:49:20.494701 zmwatch[14468].WAR [main:160] [Restarting capture daemon for Kitchen, time since last capture 47 seconds (1749862160-1749862113)]

The meaning of the various commands has changed... In 1.36 we have

-E, --enable : Enable detection, wake monitor up
-D, --disable : Disable detection, put monitor to sleep
-u, --suspend : Suspend detection, useful to prevent bogus alarms when panning etc
-r, --resume : Resume detection after a suspend

What's the difference between enable/resume and disable/suspend? The code implementing them was confused as well. I suspect many developers over the years got confused. SO I changed it. Now we have:

-E, --enable : Enable capture, wake monitor up
-D, --disable : Disable capture, put monitor to sleep
-u, --suspend : Suspend motion detection, useful to prevent bogus alarms when panning etc
-r, --resume : Resume motion detection after a suspend

-D should stop capturing completely.

Of course, as you noticed, it does not. I guess I never implemented that. Fix incoming. Packages building...

edited - typo