ZoneMinder Forums

If you turn off database logging, then it goes away because there is nothing to show.

I would expect the login page to use whatever theme is set as the default. Perhaps there just aren't drak styles applied to it. Seems weird. Will have to look into it.

Weird. Can you inspect the url in the img tag for the stream and post the differences?

Yeah it does that. I just bumped the actual version to .67 now so it will match up.

Big new feature is Go2RTC support.

I think I can speed up the events listing api too...

Took another look... most of the stuff I was doing is apparently not required. query params are all parsed by the paginator. But there is no way to get the paginator to return all results, so now we only do pagination if either limit or page is specified in the query. Your initial url works fine for ...

THe Amcrest_API thing is entirely separate from ONVIF. It is an entirely different API. I need to get aroudn to removing it from the ONVIF page.

I also see no purpose in using it if ONVIF works.

The settings you had work for my amcrest cams.

Path should just be /Events.

Use the ONVIF_Alarm_Text to match the message. THe default of Motion should have worked for you.

TUrn on debug and see what the logs say.

If you put pagination=true in the query it should restore the old behaviour of returning paginated results.

New packages are building that should fix these issues

ZoneMinder will always provide options to best use features of cameras, or provide those features in a secure manner. THe cameras that I have Annke c800 I think... and Tapo C520WS are not using cloud for it. SO that's ok by me. Yeah, I always recommend locking the cameras down to not access internet ...

Ok, so maybe the db lookup is slow... the frames table is huge and if the event is long there would be a ton of frame records to search through...

So this is not ideal, will put it on the todo list to look into

I can't imagine what would take that long, but at the same time... not sure who is actually using mlapi and the python apis keep changing, etc.

I will fire up my ai box and take a look.

The ZM_STRICT_VIDEO_CONFIG is a bit of a red herring. The error could pertain to any config value. That's just the first it hits. There is a disconnect between your dbconfig entries and what is compiled into zmc. Are you self-compiling zm? If you have updated zmc etc, but not updated the perl ...

Lots of new features have gone in, but I don't have time right now to do a proper update. I just merged support for go2rtc and it works so much better than rtsp2web or janus. So for live 264 viewing with audio... right now this is the way to go.