malvarez00

[SUPPORT] malvarez00 - MotionEye

40 posts in this topic Last Reply

Recommended Posts

I have managed to get one camera working using http://192.168.x.x/video/mjpg.cgi and using port 80. I want to use a few more cameras also, do all the cameras have to use port 80?

 

Share this post


Link to post

I can't seem to passthrough my camera.

lsusb gives me this

Bus 002 Device 003: ID 045e:075d Microsoft Corp. LifeCam Cinema

 

I passthrough a device pointing to : /dev/bus/usb/002/003

And the container doesn't recognize the camera.  (no cameras found)

 

And in /dev there's no device with ttyusb# either...

 

 

Share this post


Link to post

Any luck with correcting the timezone on MotionEye?  I'm on Pacific Standard Time.

Share this post


Link to post

I have not had success resolving the timezone issue. I did find this, which may be a solution, but I am not knowledgable enough to implement it to test:

 

Quote

Use the following command to start motionEye inside a Docker container. You don't need to download the images first. If you just fire the start command, the images are downloaded automatically, if they do not exist locally.


docker run --name="motioneye" \
    -p 8765:8765 \
    --hostname="motioneye" \
    -v /etc/localtime:/etc/localtime:ro \
    -v /etc/motioneye:/etc/motioneye \
    -v /var/lib/motioneye:/var/lib/motioneye \
    --restart="always" \
    ccrisan/motioneye:dev-amd64

Add additional port mappings with the -p parameter if you want to use the streaming feature of motion. Change the two bind paths /etc/motioneye and /var/lib/motioneye according to your needs. The first contains the configuration files for motionEye and the second will be used as file storage for still images and movies. The bound file /etc/localtime is necessary for a proper timezone configuration inside the container using the timezone of the host.

Source (Highlighting added)

 

Can anyone determine if this is a viable/applicable methodology?

Share this post


Link to post

Hi all,

 

I've been able to fix the time zone issue. Seems like the time was off because this docker isn't including the tzdata package (https://github.com/aartrost/Docker-MotionEye/commit/acfd7929ab1a989bcb6c6f0bb48dd991aeb365b8). I've created a fork of this repository that does include this package as a temporary work-around. If somebody is interested you can find it here: https://hub.docker.com/r/aartr/docker-motioneye/. To apply this fix to your own unraid docker container, just edit the docker container config and update the Repository field to aartr/docker-motioneye . Hopefully malvarez00 can update the official docker with this minor change so that everybody will get the fix automatically.

 

 

  • Like 1

Share this post


Link to post

aartr's fork works well to solve this issue!

Looking forward to his changes being merged into the main branch.


Thank you aartr!

Share this post


Link to post
Just now, Ruthalas said:

aartr's fork works well to solve this issue!

Looking forward to his changes being merged into the main branch.


Thank you aartr!

 

Good to hear! After posting I also updated the container to the latest version of Motion (4.0 -> 4.1.1) and updated MotionEye from 0.39 -> 0.39.1. This required an update to Ubuntu 18.04 as well. 

 

Doing so fixed some issues for me with video saving. Stored videos were playing back too fast, updating to Motion 4.1.1 fixed this.

Share this post


Link to post

hi everyone. i've tried to update the docker config to aartr/docker-motioneye but it deleted my motioneye image making it orphan. What did I do wrong? Any help's gonna be very much appreciated.

 

Share this post


Link to post
Posted (edited)

In my case, it replaced my existing MotionEye container (and left the previous image orphaned).
 

Did your MotionEye instance disappear entirely instead of being replaced?

Edited by Ruthalas
I can't spell.
  • Like 1

Share this post


Link to post

hi ruthalas, thanks for your answer. i have the orphan image but no new-motioneye at all. I'm sure it's me doing something wrong, just dunno what :))

Screen Shot 2018-06-19 at 01.00.04.png

Screen Shot 2018-06-19 at 01.00.28.png

Share this post


Link to post
11 minutes ago, steve9992000 said:

hi ruthalas, thanks for your answer. i have the orphan image but no new-motioneye at all. I'm sure it's me doing something wrong, just dunno what :))

Screen Shot 2018-06-19 at 01.00.04.png

Screen Shot 2018-06-19 at 01.00.28.png

 

Hey Steve,

 

Not quite sure what's up. I'd just try to fully remove all the motioneye related containers and do a fresh install. This shouldn't affect your container's config in stored in appdata.

Share this post


Link to post

hi aartr, thanks for your answer. tried it, but no success. I've even removed my config dir starting a brand new motioneye instance, then changed the repo field, but once again, orphan image and no new one. Is it possible that I kinda have to add your repo somewhere before tryng to pull from it? it says data pulled 0 bytes (?). maybe I just don't reach your repository?

Screen Shot 2018-06-19 at 01.54.00.png

Share this post


Link to post
12 minutes ago, steve9992000 said:

hi aartr, thanks for your answer. tried it, but no success. I've even removed my config dir starting a brand new motioneye instance, then changed the repo field, but once again, orphan image and no new one. Is it possible that I kinda have to add your repo somewhere before tryng to pull from it? it says data pulled 0 bytes (?). maybe I just don't reach your repository?

Screen Shot 2018-06-19 at 01.54.00.png

 

I'm guessing there's something wrong in your container's config or your server can't reach dockerhub properly. I just tried and everything seems to be working well for me. I don't have a lot of experience with docker either so I'm afraid I can't help any further.

Share this post


Link to post

it's ok my friend, you've been very kind. I'll keep digging and if ever figure it out I'll post it here just in case someone else had this issue. Thank for your time

Share this post


Link to post

Kinda solved my issue, just reporting in case someone ever had the same problem. Attaching screenshot of CA settings, so that the writing "click here to get more results..." appeared after a "motioneye" search in ca. than I finally found the aart repo/app listed, created a new installation with a different name and port nr, then copied/pasted the config folder from the original motioneye image config using krusader.

Then deleted the original motioneye image.

Sorry, didn't mean to write so much in the tread, hope it can be useful to other al least. Thanks everyone.

ps. aartr/docker-motioneye actually solved the time zone issue thanks1087407139_ScreenShot2018-06-21at02_19_55.png.1239a95b17ed1a7c205abf3c27df1554.png1252054036_ScreenShot2018-06-21at02_19_48.png.4d24ddbdee5b8c679b3097631223d67a.png

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.