Unable to add Tapo325WB (TP-Link) in motioneye

Alex Z99

unread,

Apr 18, 2025, 5:55:45 PMApr 18

to motioneye

Hello,

I tried a lot to add my cam in ME. The stream is visible in vlc or other cam software. The cam supports onvif.

Used cam-address: rtsp://192.168.3.108:554/stream1

credetials are set.

I tried udp and tcp as well without success, the window in me stays greyed.

Any ideas?

br

Alex

StarbaseSSD

unread,

Apr 18, 2025, 5:58:47 PMApr 18

to motioneye

What resolution? There is a limitation that horizontal and vertical need to be set to a number evenly divisible by 8.

Alex Z99

unread,

Apr 20, 2025, 3:49:18 PMApr 20

to motioneye

The resolution is 640 x 480. That should not be the problem.

br

Alex

StarbaseSSD

unread,

Apr 20, 2025, 3:56:22 PMApr 20

to motioneye

I checked https://www.ispyconnect.com/camera/tp-link and was unable to find that model.

Alex Z99

unread,

Apr 21, 2025, 5:17:45 AMApr 21

to motioneye

Hi,

sorry the cam model is C325WB. I checked that model with your mentioned webside (thanks for that information) and the tool gave me the url for my model. This is:

rtsp://<user>:<password>@192.168.2.200:554/stream1

That is what I used since beginning with motioneye, but the credentials are set in the given fields in motioneye. So the url is correct. The problem isn't the rtsp-link.

br

Alex

StarbaseSSD

unread,

Apr 21, 2025, 7:24:05 AMApr 21

to motioneye

There is a second link for /stream2 , did you test it? It is possible that motionEye may not like the datastream from that particular camera, too.

Alex Z99

unread,

Apr 21, 2025, 12:21:59 PMApr 21

to motioneye

Yep, no success at all.

StarbaseSSD

unread,

Apr 21, 2025, 12:26:17 PMApr 21

to motioneye

Which version of motionEye, and what hardware? What changed recently?

Alex Z99

unread,

Apr 22, 2025, 7:46:13 AMApr 22

to motioneye

Hi,

I use:

motionEye Version
0.43.1b2
Motion Version
4.7.0
OS version
Linux 5.15.76-v8+

Motioneye is running in a docker container,

At present the image: cyb3rdoc/motioneye:latest

is running, I also tried:

# image: ghcr.io/motioneye-project/motioneye:edge

and

# image: ccrisan/motioneye:master-amd64

The hardware is a raspberry pi 4 with 4 GB RAM

br

Alex

StarbaseSSD

unread,

Apr 22, 2025, 7:52:58 AMApr 22

to motioneye

I would suggest posting this over on https://github.com/motioneye-project/motioneye/issues to see if they can help you.
I will try this with my Foscam onvif camera (I use the 0.42.1 for my primary) with a new VM (debian12) and report back.

StarbaseSSD

unread,

Apr 22, 2025, 9:29:33 AMApr 22

to motioneye

I confirm that my setup on Debian12, motionEye 0.43.1b2, and motion 4.7.0, I get a grey window instead of the camera feed.

I downgraded motion to 4.6.0, no change

I downgraded motion to 4.5.1, no change

There aren't any earlier pre-built packages for Bookworm on the https://github.com/Motion-Project/motion/releases list.

I am unable to determine the docker issue, unless you post your docker run command or docker-compose.yml file...

Alex Z99

unread,

Apr 22, 2025, 12:16:21 PMApr 22

to motioneye

Hi,

as I understand the same behavior appears with your constellation?

Here comes the docker compose file:

docker-compose.txt

StarbaseSSD

unread,

Apr 22, 2025, 12:25:30 PMApr 22

to motioneye

Yes, It happens in a clean, full Debian 12 install, Python 3.11, multiple versions of motion, and motionEye 0.43.1b2.

After lunch, I will test with a full Debian 11, and I'll test your docker file.

Alex Z99

unread,

Apr 23, 2025, 4:23:13 AMApr 23

to motioneye

Thank you much in advance!

StarbaseSSD

unread,

Apr 23, 2025, 9:52:01 AMApr 23

to motioneye

Sorry for the delay, Real Life(tm) issues...

I am not sure where the issues lie, as I've never seen the errors I'm seeing in the docker version.

I am also unable to set up any of my foscam (rtsp/onvif mode) or d-link (standard ip cameras) or RPis (mjpeg mode) in it.

I would thus attribute most of the issue to the docker container, rather than motionEye, as at least the d-link and RPis work in the clean install of motionEye 0.43.1b2 on Debian 12. There is an issue with RTSP/ONVIF in 0.43.1b2, though, but I cannot diagnose fully without getting the other camera types working first.
I did have to remark out the networking (as you are using vlans and other ips, and I don't in my lab) but my setup for this was:
Win10 host
Virtualbox 7.1.6
Debian12 guest updated to yesterday

docker.io version 20.10.24+dfsg1, build 297e128

docker-compose version 1.29.2, build unknown

When running your docker-compose file it did set up:
motionEye version 0.43.1b2

motion 4.7.0

OS version Linux 6.1.0-33-amd64

"Theoretically" it should be working for at least the non-rtsp/onvif cameras...

Alex Z99

unread,

Apr 24, 2025, 4:08:12 PMApr 24

to motioneye

Oh my first thought was also network issues, so I tried a bridged docker container without L3 VLAN, but that wasn't the fault. I've heared that motioneye isn't supported well anymore. If so than even less attention is paid to the docker version, I guess.

br

Alex

StarbaseSSD

unread,

Apr 24, 2025, 7:00:52 PMApr 24

to motioneye

I just rem'd out the network sections. I didn't think it would be a network issue, I just wasn't set up for your IP schema or vlans.

They (new devs) are supporting their fork (v 0.43.1b2) fairly decently, but I was doing so for Calin's original product (up to 0.42.1). If you post on the github issues area, you might get some responses from their support.
https://github.com/motioneye-project/motioneye/issues

Reply all

Reply to author

Forward