motioneye-project/motioneye

Amcrest ASH26-W (Smart Home) Unable to Open Video Device, on both Home Assistant and Docker

Open

#2,175 opened on Aug 17, 2021

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Python (3,533 stars) (636 forks)batch import
Home Assistant addondockerhelp wanted

Description

I have been unable to add an ASH26-W camera to motioneye addon for Home Assistant. The RTSP stream is accessible via VLC provided device login credentials.

I have the same error on a separate stock PiOS running docker. ERROR: mjpg client timed out receiving data for camera 2 on port 8082

On both instances, I have an amcrest IP2M-841 that shows the same errors unless I enter the IP2M's web interface and add a new surveillance user, as I am unable to get a stream with the camera's admin user. The ASH26-W does not have a web interface or any way to add additional device users.

Docker run command used for testing of the issue on the PI:

docker run --name="motioneye" \
    -p 8765:8765 \
    -p 8081:8081 \
    -p 8082:8082 \
    --hostname="motioneye" \
    -v /etc/localtime:/etc/localtime:ro \
    -v motioneye:/etc/motioneye \
    -v motioneye_lib:/var/lib/motioneye \
    --restart="always" \
    --detach=true \
    ccrisan/motioneye:master-armhf

Contributor guide

Tech stack
pythondocker
Domain
backenddevops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
DockerPythonRTSP streamingmotioneye configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate motioneye's RTSP handling code (likely in motioneye/source/motion.py or similar) to understand how it connects to cameras. Check if the camera's RTSP stream requires specific authentication headers or URL parameters that differ from the standard format. Compare with working camera (IP2M 841) configuration to identify differences. The timeout error suggests network or protocol incompatibility. Look for existing issues or PRs related to RTSP authentication or timeout handling.