search

hassio-addons / addon-motioneye

motionEye - Home Assistant Community Add-ons
https://addons.community
MIT License
278 stars 45 forks source link

Added 2nd camera and only shows 1 FPS counter overlay #167

Closed sirweazel closed 3 years ago

sirweazel commented 3 years ago

Problem/Motivation

(Why the issue was filed) I added a 2nd camera, but the Streaming/Capture FPS counter is only showing 1 FPS counter. So i don't know if its showing me the streaming or the Capture counter

Expected behavior

(What you expected to happen) I should see 2 counters like the first camera that is added.

Actual behavior

(What actually happened) Only see 1 counter

Steps to reproduce

(How can someone else make/see it happen) Currently running Motioneye 11.0 via Home Assistant, but i once ran motioneyeos and i think i saw this same issue. I am running different models of IP cameras via rtsp streams. The first camera was a cheap IP camera, and the 2nd camera i'm adding is an Amcrest IP camera. Let me know what other information you may need.

Sorry if i'm missing something, i'm probably just overlooking a configuration maybe?

Screenshot attached: FPS_Counters_Troubleshooting

sirweazel commented 3 years ago

I just now realized i opened this ticket under the hassio addon... i wonder if i should of opeend it via the motioneye github, but i'll start here and see if anyone else has this issue, then i can open up an issue somewhere else if needed.

sirweazel commented 3 years ago

I'm also adding the version info here. Running under Hassio QCOW2 KVM image from the downoads.

Motioneye version under Motioneye settings: motionEye Version | 0.42.1 Motion Version | 4.3.2 OS Version | Linux 5.4.86

Hassio MotionEye version under Supervisor: Current version: 0.11.0 Hassio Version Info: core-2021.1.5 supervisor-2021.01.7

Clewsy commented 3 years ago

Hi @sirweazel, sorry I can't help but I think you're right with your second comment - your issue is regarding motioneye proper, not the hassio-addon implementation. Probably more likely to find someone there that can help.

sirweazel commented 3 years ago

@Clewsy , Thank you for the response, and i did post there as well. But the one person i was working with thinks it might be related to the hassio fork. Are you able to replicate or do you see this issue?

Clewsy commented 3 years ago

I'm unable to replicate. I've got four IP cams in my current configuration, various kinds but not Amcrest specifically. I'm seeing both FPS values with all feeds. The add-on isn't a fork, it's kind of a wrapper around motioneye which remains un-changed. If your feed is otherwise working then I can't imagine how it could be an issue with the add-on, though I could be wrong.

frenck commented 3 years ago

But the one person i was working with thinks it might be related to the hassio fork.

Add-ons are not forks. Add-ons wrap applications as is. From an add-on perspective, there is nothing we can do. Please report your issue upstream. Thanks 👍

sirweazel commented 3 years ago

@frenck Maybe fork wasn't the correct term, I'll follow up upstream with issues and refer back to your comments here. In upstream, it sounded like I should pay attention to your comments though.

I do feel that's it's a little premature to close this issue though, since the cause hasn't been found yet. So far each issue had referred to the other maintainer to investigate.

What I can do, but more time intensive would be to spin up another server vm that is straight server os with motion, or I might flash a pie with motioneyeos to compare results.

I know at the surface, from your perspective it isn't related. But I'd like to rule that out. Can you reopen this for a little bit until we confirm eitherway? Maybe someone else who has the same issues might run across this if it's open? I know this issue is an annoyance, so it isn't critical and most people probably wouldn't care or take the time to notice the counters. I can provide any info needed to track down. I might not be a developer, but I'm a tech person, and I can contribute by testing, reporting, bug tracking, helping others, ect...

Thank you for your time and help.

frenck commented 3 years ago

I do feel that's it's a little premature to close this issue though

I don't, as the application is run as-is. We don't develop the application.

I'm not re-opening the issue.