PoE External IPCam with MotionEyeos

235 views
Skip to first unread message

T C

unread,
Oct 21, 2020, 10:55:05 AM10/21/20
to motioneye

I have tried to add an external PoE cam to Motioneyeos (it is an Abus TVIP42561). The vendor offers zero information on the URL feeds. Also I cannot find a direct indication of a working RTSP URL for that cam on www.ispyconnect.com, this cam probaly is too new and it is not there. However from a similar model I have found a rtsp URL that seems promising. 

This one:

rtsp://192.168.x.x:554/Streaming/Channels/1 

If I try to connect to this stream via the VLC viewer to see if it works, this one really does:

#vlc rtsp://192.168.x.x:554/Streaming/Channels/1 
(VLC prompts me for username and password)

via VLC I can actually see the streaming. So I am sure the feed is there and that it works via rtsp, authentication included.

But whenever I try to add that cam to Motioneyeos as an external IP cam with the same URL, then I get a grey square. Not a barred camera, which would make me think of an authentication problem, but an entirely gray square (I aligned the settings in Motioneye to the ones of the camera).

For the life of me, anyone knows how to make this work with motioneyeos?


Alternatively: 

Anyone knows/has tested a PoE External cam that is known to work with Motioneyeos?

It needs to be:

- External/Resistant to rain/snow (IP66 if possible)
- PoE (not wifi or not only wifi)
- Possibly with a working known URL (so I don't have to take a half day to find one)
- Tested with Motioneye
- Auto Infrared (if possible)

also would be great if you could post an amazon or a vendor link to the model, if that vendor&model did really work for you.

Thank you!!!

Kevin Shumaker

unread,
Oct 21, 2020, 11:04:38 AM10/21/20
to T C, motioneye
did you try rtsp://<ip_address>/cam[channel]/h264  << changing [channel] to 0 or 1?

--
You received this message because you are subscribed to the Google Groups "motioneye" group.
To unsubscribe from this group and stop receiving emails from it, send an email to motioneye+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/motioneye/b247ad0b-1cb3-4c7d-b48c-ffa4f07bbb57n%40googlegroups.com.


--
Thanks

Kevin Shumaker


N38° 19' 56.52"
W85° 45' 8.56"

Semper Gumby
“Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA
Ethics are what we do when no one else is looking.
Quis custodiet ipsos custodes?
“There is no end to the good you can do if you don’t care who gets the credit.” - C Powell
You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?

T C

unread,
Oct 21, 2020, 11:21:15 AM10/21/20
to motioneye

:-( 

I can access that in VLC, but again I get a grey square with an "unable to access video device" from MotionEyeos. So it looks like the stream is there, but MotionEye is not getting that or I configure something bad.
where to find the logs in Motioneyeos? maybe I can see something more informative there...



On Wednesday, October 21, 2020 at 5:04:38 PM UTC+2 StarbaseSSD wrote:
did you try rtsp://<ip_address>/cam[channel]/h264  << changing [channel] to 0 or 1?

T C

unread,
Oct 21, 2020, 11:26:41 AM10/21/20
to motioneye
Last comment is related to the URL  rtsp://<ip_address>/cam[channel]/h264 

Kevin Shumaker

unread,
Oct 21, 2020, 11:31:55 AM10/21/20
to T C, motioneye
Which version of motionEyeOS are you using? Specifically, with date and Pi version.

On Wed, Oct 21, 2020 at 11:21 AM T C <fuzz...@gmail.com> wrote:

:-( 

I can access that in VLC, but again I get a grey square with an "unable to access video device" from MotionEyeos. So it looks like the stream is there, but MotionEye is not getting that or I configure something bad.
where to find the logs in Motioneyeos? maybe I can see something more informative there...

T C

unread,
Oct 21, 2020, 11:35:46 AM10/21/20
to motioneye
This is what I am using:

OS Version: motionEyeOS 20200606
PI: PI3 Model B V1.2  



On Wednesday, October 21, 2020 at 5:31:55 PM UTC+2 StarbaseSSD wrote:
Which version of motionEyeOS are you using? Specifically, with date and Pi version.

T C

unread,
Oct 21, 2020, 11:38:01 AM10/21/20
to motioneye
PI3 Model B V1.2   is from 2015

Kevin Shumaker

unread,
Oct 21, 2020, 12:09:05 PM10/21/20
to T C, motioneye
I found several non-english manuals for the camera. Does it have mpeg or mjpeg output?
Do you have rtsp authentication on or off?
You are using Network Camera for type? the previous settings for address, the correct user and password as set int the camera app, etc?
Have to ask...


--
You received this message because you are subscribed to the Google Groups "motioneye" group.
To unsubscribe from this group and stop receiving emails from it, send an email to motioneye+...@googlegroups.com.


--
Thanks

Kevin Shumaker


N38° 19' 56.52"
W85° 45' 8.56"

Semper Gumby
“Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA
Ethics are what we do when no one else is looking.
Quis custodiet ipsos custodes?
“There is no end to the good you can do if you don’t care who gets the credit.” - C Powell

T C

unread,
Oct 21, 2020, 1:39:29 PM10/21/20
to motioneye
 Thank you! answers are inline below in Bold/Italics

On Wednesday, October 21, 2020 at 6:09:05 PM UTC+2 StarbaseSSD wrote:
Yes it is from there

I found several non-english manuals for the camera. Can you link me those? I can read some other languages (if DE, SP, IT and FR to some extent)
 
Does it have mpeg or mjpeg output?
 Honestly I don't know, but I would assume yes. However I have read that with mpeg, mjpeg the motion detection doesn't work. If this is the case, I definitely wouldn't want to use mpeg, mjpeg. The main reason to use MotionEye for me was the motion detection feature.

Do you have rtsp authentication on or off? On. When I use VLC, I get an authentication prompt that works there. So it has to be on. And I use the same credentials in the Network Camera fields. However I have purposely used wrong credentials and right credentials. In both cases I have the grey box with the "Unable to open the device"

 
You are using Network Camera for type? Yes the previous settings for address, the correct user and password as set int the camera app, etc? Yes (and as above, tested also with wrong creds)
 
Have to ask...Actually thank you :)
 
The moral of the story is that now I don't know if the issue is auth or conf, considering I have same results with wrong creds.
Mmhhhh....Abus a retour is looming 

:D

Kevin Shumaker

unread,
Oct 21, 2020, 1:55:39 PM10/21/20
to T C, motioneye
Since you are trying to use motionEyeOS, you can do the motion detection there, instead of the camera.
Have you tried Port 80 or port 8000 or just plain 554?
http://<ip_address>:80
http://<ip_address>:8000
http://<ip_address>:554
rtsp://<ip_address>:554
or rtsp://<ip_address>:554/cam[channel]/h264

T C

unread,
Oct 22, 2020, 4:56:44 AM10/22/20
to motioneye
I am really thinking to give up on this cam. Which is somewhat sad. Although not cheap, it really has a nice and heavy metal case. It looks solid enough to resist a lot of physical strain, if any physical attack is attempted.

This is what I get when I try to nmap the services that are on the cam, it looks like rtsp is only on 554. 
I have full access to the Cam's web interface on both 80 and 443 (not 8000, there I have no response although it looks open for that http-alt? service which I don't know what's for). 
The web interface is ok, nice and fully configurable. But it doesn't integrate to MotionEye.

$ nmap -sV -T4 192.168.x.x

Nmap scan report for 192.168.x.x
Host is up (0.0021s latency).
Not shown: 995 closed ports
PORT      STATE SERVICE   VERSION
80/tcp    open  http      webserver
443/tcp   open  ssl/https webserver
554/tcp   open  rtsp      Hikvision 7513 POE IP camera rtspd
8000/tcp  open  http-alt?
49153/tcp open  upnp      Portable SDK for UPnP 1.6.17 (Linux 3.18.20; UPnP 1.0)

For the streaming I cannot get any stream from 80, 443 nor 8000 using both VLC or MotionEye



On Wednesday, October 21, 2020 at 7:55:39 PM UTC+2 StarbaseSSD wrote:
Since you are trying to use motionEyeOS, you can do the motion detection there, instead of the camera.
Have you tried Port 80 or port 8000 or just plain 554?
http://<ip_address>:80
http://<ip_address>:8000
http://<ip_address>:554
rtsp://<ip_address>:554
or rtsp://<ip_address>:554/cam[channel]/h264

T C

unread,
Oct 24, 2020, 10:41:43 AM10/24/20
to motioneye
Sorted out. 

I was focusing on MotionEye issues, while probably I had a hardware issue or an issue of this particular release of MotionEyeos. 

With a different release (motioneyeos-raspberrypi4-dev20201012 vs motioneyeos-raspberrypi3-20200606) and a different hardware (Pi 4 model B with 2 GB RAM vs Pi 3 model B v1.2 with 1 GB RAM) I can finally see to the streaming at rtsp://192.168.x.x:554.
I cannot test dev20201012 on the Pi 3 now. So I am not sure if the issue is the HW or the OS, but it has to be either one or the other. Perhaps 1GB is not enough?

I only changed the stream to 1280x720 with H265 instead of H264

So, in the end all is good.
Reply all
Reply to author
Forward
0 new messages