motioneye-project
Cannot add camera with 0.43.1b1
motionEye Version 0.42.1 Motion Version 4.3.2 OS Version Ubuntu 22.04
motionEye Version 0.42.1 is Python2 only, it won't work with Python 3.12 which you seem to have. Please install the prerelease of 0.43 using these instructions.
However as I now notice the title of this issue mentions 0.43.1b1: which one is correct?
I start the script with python3, so why is it picking up py2 libs?
On Thu 30. May 2024 at 7.10, Esa Tikka @.***> wrote:
motionEye Version 0.42.1 is Python2 only, it won't work with Python 3.12 which you seem to have. Please install the prerelease of 0.43 using these instructions https://github.com/motioneye-project/motioneye?tab=readme-ov-file#installation .
— Reply to this email directly, view it on GitHub https://github.com/motioneye-project/motioneye/issues/2990#issuecomment-2138639940, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJU4T5TYBMRYGLPDNMZRVU3ZE2RERAVCNFSM6AAAAABINERLWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZYGYZTSOJUGA . You are receiving this because you authored the thread.Message ID: @.***>
However as I now notice the title of this issue mentions 0.43.1b1: which one is correct?
?
This error seems to occur when network camera is unavailable, so poor error handling here. Working cameras don't throw this error
The version confusion came from your problem description which specifically said "motionEye Version 0.42.1". But ok, if you are really running 0.43.x then fine, let's move on.
Having the full stack trace would likely make it easier to figure out the reason things go wrong (=why the callback passed to tornado lacks a positional argument), unless someone with more experience on dealing with Tornado can guess the cause from that snippet you posted.
Please also post the output of this command in case there's some sort of version incompatibility:
pip freeze | grep tornado
There are no more stack traces in logs.
I'll send tornado version later.
On Thu 30. May 2024 at 7.33, Esa Tikka @.***> wrote:
The version confusion came from your problem description which specifically said "motionEye Version 0.42.1". But ok, if you are really running 0.43.x then fine, let's move on.
Having the full stack trace would likely make it easier to figure out the reason things go wrong (=why the callback passed to tornado lacks a positional argument), unless someone with more experience on dealing with Tornado can guess the cause from that snippet you posted.
Please also post the output of this command in case there's some sort of version incompatibility:
pip freeze | grep tornado
— Reply to this email directly, view it on GitHub https://github.com/motioneye-project/motioneye/issues/2990#issuecomment-2138658966, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJU4T5ULV55HMD74AEZ2CALZE2TYJAVCNFSM6AAAAABINERLWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZYGY2TQOJWGY . You are receiving this because you authored the thread.Message ID: @.***>