ZoneMinder Forums

EDIT : found it - you have yolo_type configured in common_params.py as being in the yolo section, but the objectdetect.ini has that variable at the top in the general section. Moving the variable into the yolo section fixes it. Good catch! I over ride yolo_type on a per monitor basis, so I suppose ...

I somehow get the feeling you are possibly using an older version of the hooks somewhere. Lets do it cleanly, to make sure: 1. git clone https://github.com/pliablepixels/zmeventnotification 2. cd zmeventnotification 3. cp /etc/zm/objectconfig.ini mynewconfig.ini 4. Modify mynewconfig.ini to use tiny...

I honestly don't have a clue. I just plan to SSH into your system and print a whole bunch of debug logs to get started. I was surprised the previous version actually fixed it. Isaac knows more about this than me, but I can try and tinker around. In the mean time, if Isaac knows exactly what to fix, ...

I don't use Pi4/Buster.
I am on ubuntu

I built everything from source because I use the GPU. As long as you are on Python 3 & OpenCV 4.1.x, its all good (there are packages available - not sure about buster, don't have to build from source)

Yes, /etc/zm/objectconfig.ini
Try running it from command line (not as a daemon) and see what it picks up

Is there any chance you can set up a test instance where I can SSH into (as well as get ZM access)? I can't replicate the issue on my systems.

I just tried it and it had no problem using tiny.

1. Make sure you are on the latest ES and hooks (the logs you posted don't show the version). Note that ES and hooks have different version #s
2. Make sure you are using the right config file

Hi,
Glad you got it worked out. This is actually covered in the install steps. See this

I've come across one system where Python3 was the only version and "pip3" did not exist. pip was the right tool to use. That's why I chose to leave it as pip and not explicitly state pip3 everywhere.

You can't. The mobile skin has been deprecated. 1.29 was the last release that officially supported it. See this
In fact, in newer releases, you'll see this error in your logs:

Some important notes: 1. Make sure AUTH_HASH_LOGIN is on 2. Make sure AUTH_RELAY is hashed 3. restart ZM 4. When ZM 1.34 is released, ZM 1.31 will be the minimum supported version (I'd strongly recommend you upgrade to 1.34 - it brings in a new token system that is more secure and faster) If you sti...

1.29 is not supported.
But If you are able to send me an email with a temp access to ZM console I can have a look.

Correct. Needs to be in either modect or mocord (maybe even nodect, if you trigger events externally). ZM needs to be in a mode where it is doing motion detection, which it does not do in record or monitor mode.

Right after this line https://github.com/ZoneMinder/zoneminder/blob/master/web/includes/auth.php#L291 Can you add these logs: ZM\Info ("key elements used in hash computation: user=".$user['Username']." password= ".$user['Password']."remote IP= ".$remoteAddr); ZM\Info ("now is:$now localtime is:$time...

Could you be more specific - 1. Are you _always_ getting logged off within 30 seconds? 2. Can you start a browser in incognito, login and time exactly how long it takes for you to get logged out? 3. Repeat step 2 a few times, see if it occurs at a boundary of an hour or some other pattern 4. Keep AU...

utf-8. See web/api/app/Config/Database.php