balena-motioneye's Introduction

resin-motioneye

WIP A MotionEye server deployed on resin.io.

Usage

Navigate to the device's IP/hostname over http to open the interface
Alternatively enable the public device URL, and navigate to that to see the interface

The interface uses the default MotionEye credentials. There you can add your settings (cameras, etc) that are stored in a non-volatile way (in docker volumes).

To use an attached PiCamera, check our documetation for settings it up, and use gpu_mem set at least to 192.

Configuration variables

Some device settings can be adjusted with Device/Fleet service variables. These should be set for the motioneye service:

SERVER_NAME: the name of the server in the MotionEye UI. If not set, then the device's name (from the RESIN_DEVICE_NAME_AT_INIT variable) will be used automatically.
TIMEZONE: the device's local time, one of the timezone names from the available time zones. If not set, the default UTC time is used.

Notes

The current setup only supports ARMv7 devices (especially Raspberry Pi 3). Other device types are WIP
The default docker-compose.yml exposes 10 MotionEye camera streaming ports on the port range used by MotionEye by default (8081-8090), if need more than that, you need to edit the compose file.

balena-motioneye's People

Stargazers

Watchers

balena-motioneye's Issues

Update to latest Motion

That should be 4.2.2, as of now https://github.com/Motion-Project/motion/releases

Add tolling to run on other device than armv7hf

Should check how to run it on x86, or other

Use buster base image

Update from stretch. Also related to #3

Build fails

[Error] Could not detect project type: Service motioneye: Could not find a Dockerfile for this service
[Error] Not deploying release.
Remote build failed

Ideas?