Onvif motion detections based on Motion Guard settings? Wrong resolution in prudynt.json?

[pw-h]

Hi, Installed Thingino on my 2 Wyze V3 camera's, great stuff!

One camera reports Motion detections just fine via ONVIF, but they are large motions due to cars passing by.
My other camera seems to miss a lot of smaller motions, and i have 2 questiosn:

• is the sensitivity of Onvif motion detections based on the Motion Guard sensitivity?
• in prudynt.json, the motion: stub looks like this. Shouldnt the resolution be 640x320 to represent the substream?
  "motion": { "cooldown_time": 5, "debounce_time": 0, "enabled": true, "frame_height": 1080, "frame_width": 1920, "init_time": 5, "ivs_polling_timeout": 1000, "min_time": 1, "monitor_stream": 1, "post_time": 0, "roi_0_x": 0, "roi_0_y": 0, "roi_1_x": 1919, "roi_1_y": 1079, "roi_count": 1, "script_path": "/usr/sbin/motion", "sensitivity": 2, "skip_frame_count": 5
  BTW: setting changes in the Motion Guard tab (sensitivity, Delay, Send info) are not saved to prudynt.json, i have to manually change that file to make changes.

[themactep]

There is no onvif motion detection. There is motion detection and a number of services that get notified of the event. Onvif is just one of them. Motion detection sensitivity can be increased in range 1 to 8 with 1-5 being suitable for regular cameras and larger values reserved for cameras with wide and super wide angle lenses.

Motion detection on camera is done using full frame, substream is used by for preview and motion detection done off-camera (using frigate and such).

WebUI is being rewritten so things may be broken here and there.