Motion is great for one or two cameras, but changes take a while and viewing the output is hard. However I really like motioneye:
it works well on a pi and is basically a nice gui for motion (with the ability to paint motion masks in the browser, which is a very nice touch)
the only down side is that video viewing isn't supported directly in the browser, but that might change if someone is willing to help out.
>video viewing isn't supported directly in the browser
Reading your comment caused me to log in to my security server and make sure I'm not nuts about the ease of viewing Motion feeds. Viewing its feeds in a browser is simple, from anywhere on the network. I'm curious what problems you had.
On a similar note, I stuck with plain-old Motion because of its super-low overhead. GUI aside, is Motioneye much of an upgrade? How does its resource footprint compare to Motion's?
Where it falls down is remote viewing history on unprivileged machines. The nice thing about motioneye is that it creates a nice GUI for remote config and viewing.
However if I had a working motion config thats properly tuned, with all the simple auth setup for remote viewing, would I replace it with motion eye? no.
I switched from unifi video to ZM because unifi was very buggy back then.
Kerberos.io was looking pretty cool until I read that they want a Raspi or Docker container running for every single camera you have. I have quite a few IP cameras. To run a web interface & container for each one is silly. It requires a lot more infrastructure and I don't buy that it would be more reliable.
It additionally uses docker to accomplish most things. I made https://github.com/amingilani/chronopill on Resin to use my Raspberry Pi as a timemachine backup device. :)