search

motioneye-project / motioneye

A web frontend for the motion daemon.
GNU General Public License v3.0
3.95k stars 650 forks source link

Motion graph #59

Open ghost opened 8 years ago

ghost commented 8 years ago

Is there any way to implement motion graph based on quantity of captured photos per hour? Same as its done in Zoneminder for example?

ghost commented 8 years ago

Hello? Should I wait for any update?

ccrisan commented 8 years ago

Don't. This is definitely not a priority and there are many other pending requests. My apologies for not getting back to you with an answer sooner.

ghost commented 8 years ago

Bad do hear, thanks for the prompt answer. Will try implement myself then,

ccrisan commented 8 years ago

Please do, if you have the necessary resources and knowledge. You could share it with us then (if you want, of course) and I'll consider integrating it into motionEye.

mvanbreeden commented 8 years ago

Google UA would be nice, requires just a few lines of code, an extra account field in UI and you can track online in realtime. I'll see what I can do coming days.

[update] It's not as easy as it seems. The difficulties do not weigh up to added feature, so I won't pursue it further.

ebuzzz commented 8 years ago

@mvanbreeden could you elaborate on the difficulties, just for future reference?

mvanbreeden commented 8 years ago

The difficulties are threefold: First of all the UA features are not quite as simpel as they seem. That makes it difficult to grasp and use for end-users. Secondly implementing UA feeds would mean to either pick and choose info and categories to send upfront or to implement very broadly. Both are not ideal for a project like motioneye.

Lastly: to keep motioneye light and compact, one would expect an elegant and self-contained graph, UA would be shooting a fly with a bazooka.

My intentionaliteit is to experiment loosely with UA on other stuff first

Op do 14 jan. 2016 09:55 schreef Eric Bus notifications@github.com:

@mvanbreeden https://github.com/mvanbreeden could you elaborate on the difficulties, just for future reference?

— Reply to this email directly or view it on GitHub https://github.com/ccrisan/motioneye/issues/59#issuecomment-171575661.