MichaIng
MichaIng
Wow, awesome, looks very good. I'll start updating German translations tomorrow 🚀.
Could you please open a new issue about this? Let's keep individual things separated 😉. I'll mark this as closed as the original question has been answered.
> AFAIK the MMAL driver isn't available any more in newer distros like Bullseye It is, but legacy display drivers need to be enabled, e.g. via `raspi-config` or by removing...
Not sure whether it makes sense to re-add support for older `motion` versions, keeping 4.3 support when adding 4.4 support at least. And you are right, when settings are not...
Nice, there is some pre/post v4.2 motion config mapping done already: https://github.com/motioneye-project/motioneye/blob/c58ad0f/motioneye/config.py#L138-L167 We can build on this and add v4.4 support just the same way 👍.
v4.3.2 is v4.3 (otherwise I'd have written v4.3.0 or so) 😉. The patch version (last digit) never includes any breaking changes or renamed settings.
This was just in case you use a different motion version, e.g. the newest v4.4 available upstream or the older v4.1 shipped by Debian Buster and alike. Since you are...
> And there's actually some sort of motion version detection in Otherwise the mapping wouldn't be possible. It uses exactly the `motion -h` parsing I found as a way to...
PR up but I need help to finish it: #2462
The new `dev` branch has support for Python 3 and can hence be installed on Debian/Raspbian Bullseye. Depending on how you want to install `pip` and whether `motionEye` shall be...