MotionEye 10.2 unable to connect to some cameras

[Shadowpheonix]

Problem/Motivation

My camera feed stopped working after upgrading from MotionEye 0.8.1 to 10.2.

Expected behavior

My camera feed should continue to work.

Actual behavior

I get a "no camera" icon instead of my camera feed.

Steps to reproduce

Setup MotionEye with a generic IP cam in Home-Assistant. In my case, Home-Assistant is the Docker version running on an Ubuntu Linux VM.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

MotionEye 10.2 Log.txt
For comparison, here's the log from MotionEye 8.1 working on the same system (I reverted the HASS snapshot for MotionEye after 10.2 failed)...
MotionEye 8.1 Log.txt

[frenck]

There is nothing in the logs that indicate an issue.

[Shadowpheonix]

Is there some other log I can get that might help (and if so, how do I get it)? The one I provided is what shows up when selecting the Log tab for the MotionEye add-on in Home-Assistant.

The only thing I noticed in those logs myself is that 10.2 reports "ERROR: mjpg client timed out receiving data for camera 1 on port 8081" while 8.1 does not (8.1's log makes no mention of port 8081 at all).

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[Shadowpheonix]

This is still an issue for me. Is there any additional logging or other troubleshooting that I can do? I really would like to update from the old 8.1 version.

[Shadowpheonix]

This is still an issue with the new version 0.11.0.

[doublepedaldylan]

Experiencing what looks like similar issue.

Operating System: Debian GNU/Linux 10 (buster)
Docker version: 20.10.2
Version: supervisor-2021.02.6
Version: core-2021.2.1
motionEye Version: 0.42.1
Motion Version: 4.3.2

I have two Amcrest rtsp cams. Existing one (IP2M-841W) added fine and continues to work, new one (ASH26-W) is accepted by MotionEye, but I get a grey screen saying "unable to open video device".

Log results:
[09/Feb/2021:12:13:44 -0600] [viewingIP], 172.30.32.1(172.30.32.2) GET /picture/1/current/?_=[13_digit_number]&_username=admin&_signature=[40_digit_hex_string] HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.146 Safari/537.36) ERROR: mjpg client timed out receiving data for camera 2 on port 8082

I can connect to the new rtsp cam through VLC just fine.

Possibly related threads
https://community.home-assistant.io/t/motioneye-rtsp-and-virtualbox/174267
motioneye-project/motioneye#2022 (comment)

Possibly unrelated note:
When adding the non-working camera, once I enter URL, under "camera" I see "authentication failed". but once I enter "admin" as user but no password yet, "camera" switches to a dropdown menu.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[Shadowpheonix]

This is still an issue in 0.11.1.

Is there ANYTHING that I can do to help get this fixed?

[doublepedaldylan]

The digging I have done seems to suggest some kind of issue that tends to be related to docker and ports. Issues related to HA addon posted to Motion's github point us to resolve here. I can link in the related issues I've seen, but the "grey screen" issue seems repeatedly related to docker and a time out on a specific port. Each time, people seem to be able to access their RTSP stream using VLC.

[Shadowpheonix]

I can confirm that VLC is able to successfully access my RTSP stream when this is occurring.
I would really like to be able to update from MotionEye 0.8.1, but cannot due to this ongoing issue.
If there is any logging or other testing I can do that would help find a solution, please let me know.

[mwy6283]

Hi , I have been having this issue for months , all cameras are accessible on HA dashboard, ( Onvif integration) but motioneye grey screen no stream. here is my log,

`_=1618557996882&_username=admin&signature=31bcf5d9b8ffcf79ac5d69666b9b3aa66076ce77 HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36)
[16/Apr/2021:08:26:36 +0100] 200 192.168.0.38, 172.30.32.1(172.30.32.2) GET /picture/1/current/?=1618557996929&_username=admin&signature=72d217a88ec9af5702726cf10c68c18b1da32321 HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36)
[16/Apr/2021:08:26:36 +0100] 200 192.168.0.38, 172.30.32.1(172.30.32.2) GET /picture/1/current/?=1618557996975&_username=admin&signature=819e26ab33ce494bfb7e229978f46479c57faadc HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36)
[16/Apr/2021:08:26:37 +0100] 200 192.168.0.38, 172.30.32.1(172.30.32.2) GET /picture/1/current/?=1618557997022&_username=admin&signature=a438c1ca033aba6faac520f50c98bc00361d47fa HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36)
[16/Apr/2021:08:26:37 +0100] 200 192.168.0.38, 172.30.32.1(172.30.32.2) GET /picture/1/current/?=1618557997069&_username=admin&signature=f5a4a4335a56ba3fa03e7f7044afe852882a5b00 HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36)
[16/Apr/2021:08:26:37 +0100] 200 192.168.0.38, 172.30.32.1(172.30.32.2) GET /picture/1/current/?=1618557997116&_username=admin&signature=63678499ea634936d76551038566fc6607e06af2 HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36)
[16/Apr/2021:08:26:37 +0100] 200 192.168.0.38, 172.30.32.1(172.30.32.2) GET /picture/1/current/?=1618557997163&_username=admin&signature=7a565fca40855033229f1c7af9eb7cb20da49068 HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36)
[16/Apr/2021:08:26:37 +0100] 200 192.168.0.38, 172.30.32.1(172.30.32.2) GET /picture/1/current/?=1618557997213&_username=admin&_signature=2818723777324a47c074b10c39e6361a96211dab HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36)
ERROR: mjpg client timed out receiving data for camera 1 on port 8081'

any advice would be heplfull I aslo had the same situtaion on a RPI4.

[doublepedaldylan]

Still having the same issue noted above on addon version 0.12.0.
Adjusted log level to 'trace'. After adding the offending camera, I basically get this repeatedly:

   ERROR: mjpg client timed out receiving data for camera 2 on port 8082
   DEBUG: received relayed event stop for motion camera id 2 (camera id 2)
   DEBUG: clearing motion detected for camera with id 2
   DEBUG: 200 POST /_relay_event/?_username=admin&event=stop&motion_camera_id=2&_signature=[hex-string] (127.0.0.1) 0.65ms

@frenck Is there anything more we can do to help trace the issue here? Thanks.

[doublepedaldylan]

Same issue with 0.13.0. Also, another user having same issue. Seems to indicate the camera can be connected to on a non-addon instance of motioneye:
#233 (comment)

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[Shadowpheonix]

This is still an issue with 0.14.0. Is there anything that can be done to help resolve this, or are those of us experiencing this issue stuck forever on the older version?

[Shadowpheonix]

This is still an issue with 0.15.0.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[Shadowpheonix]

Any chance of a fix for this, or am I forever going to be stuck on the old 0.8.1 version?
If there is any data gathering or testing that I can do to help, please let me know.

[Shadowpheonix]

This is still an issue.

[saltabas]

Same issue at 0.15.0 to 0.15.1 update, no error logs. To show a camera (just for a while) I duplicate one then delete it, so the first camera shows again, but as soon as you try to configure something in the add-on, it disappears again.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[Shadowpheonix]

This is still an issue. Is there any hope of a fix?

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[Shadowpheonix]

This is still an issue. Should I just go ahead and assume it cannot be fixed?

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[saltabas]

This is still an issue

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!