mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
Movie starts too early for Doorbird with Movie Passthrough #2160
Labels
No labels
Android app
Arch Linux
CI/CD
CSS
FreeBSD
HTML/HTTP
Home Assistant addon
JavaScript
Python
Raspberry Pi
Stale No Activity 60 Days
bug
code format
dependencies
dev branch
docker
documentation
duplicate
enhancement
feature
help wanted
i18n/l10n
invalid
legacy motionEye
meta
motion
motionEyeOS
notourproblem
python update
question
question
security
troubleshooting
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/motioneye#2160
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @salzrat on GitHub (Mar 19, 2022).
This is a separate issue for the third item mentioned here:
https://github.com/motioneye-project/motioneye/issues/2368
I have the MotionEye addon (0.17.0) installed in Homeassistant, which is running in a Virtualbox on a Macbook Air connected via LAN.
The camera is a Doorbird D101s also connected via LAN.
When I have movie passthrough enabled, the movie starts 5-10 seconds before the actual motion. So it seems somehow the timestamps of the captured video may not be interpreted correctly or something? This does not occur when disabling passthrough, here the movie starts correctly with the detected motion. The relevant settings are 30/1/60/5 for motion gap, captured before/after and minimum motion frames.
I would like to use passthrough because the video files from the camera are much smaller.
I have managed to ssh into the motioneye docker image in Homeassistant, so I can hack around there as well if it helps...
Please let me know what further information I can provide to debug this...
Thanks!
@MichaIng commented on GitHub (Mar 19, 2022):
Would be interesting to know whether this happens the same way with a native installation of the current motionEye
devbranch:github.com/motioneye-project/motioneye@fcf1b1f/README.md (installation)Not sure when I find time to test the HA addon.
@salzrat commented on GitHub (Mar 19, 2022):
I don't think I have a device where I can easily do that. But I don't think HA plays a role here, this rather seems an issue with how motion handles the video stream it gets from doorbird...
@zagrim commented on GitHub (Mar 20, 2022):
@salzrat Did you already mention the version of Motion you have? That might be relevant, at least if its pretty old. I'm not sure of the HA addon setup if Motion could be upgraded easily if necessary.
@salzrat commented on GitHub (Mar 20, 2022):
Hi, according to %{ver} on the text overlay the version is 4.3.2. I can try to upgrade the plugin and see whether it comes with 4.4.0... (edit: nope, just updated to newest addon version, still at 4.3.2) (edit2: the addon maintainer just replied that Motion 4.4.0 has configuration problems with MotionEye and therefore can't be upgraded yet...)
@zagrim commented on GitHub (Mar 20, 2022):
Yep, 4.3.2 should be fine.