I have the XMEYE DVR system with 16 cameras recorded in a hard drive box. I can see these cameras using the Firestick version of IPCAM Viewer Pro (Robert Chio) but when I bought ROKU, I see your app does not support it.
I have a stream line that will work in any brouser, VLC or even in OSB but unfortunately you dont' allow a stream command this long...
This is what it takes to load and get output from the XMEYE dvr (see an actual command line below). The Variables for others would be to change the IP Address:192.168.0.240, change the user -:yourname and change the passord -:yourpassword, and the channel=:01 through 15 for the camera number.
Works like a champ but I need a platform that can access it on Roku.
ACTUAL WORKING COMMAND LINE:
"rtsp://192.168.0.240:554/user=net&password=net&channel=12&stream=0.sdp?real_stream--rtp-caching=100" ----->remove "" as was necessary to be accepted to post.
This app supports almost nothing. I'm surprised people have not complained to have it removed. The author says 'don't use cheap cameras' but what does that mean? Is a $50.00 camera cheap these days? There's a lot of amazing hardware out there that's cheap. Entire computers I use all day long, Libre computer, $35.00. I have cameras from $50.00 to $150.00 and not one works with this 'app'.
Majority that have problems are trying to use cameras that only have h264/h265 streams. IP Camera Viewer only supports jpeg encoded streams (mjpeg, rtsp), or snapshots directly, or, with extra hardware, supports h264 streams too: https://github.com/e1ioan/rokuphp
Also, there is a Basic version which is free, if you want to test it with your cameras, use that version.
There are several thousands of happy customers, I'm sorry it doesn't work for you. The limitation for h264 rtsp is from Roku, not from me and that's why I built the extra software linked above.
IP Camera Viewer only supports jpeg encoded streams (mjpeg, rtsp), or snapshots directly, or, with extra hardware, supports h264 streams too: https://github.com/e1ioan/rokuphp
So the problem was I ran out of field typing in what the rstp stream would need for almost any XMEYE DVR. There are hundreds of thousands of these in use and the rtsp command won't fit.
Example, this plays my 12th camera the First stream:
"rtsp://192.168.0.240:554/user=net&password=net&channel=12&stream=0.sdp?real_stream--rtp-caching=100"
Once I got to about "stream-0", the field was filled and I could not see to type beyond that point.
This example RTSP command line will make every XMEYE DVR out there a prospect for your app. All they would need to do is change the IP adress and the user/password to get channel 12.
I'll be happy to test this and get it functioning with you if you ask.
Really wish I could get this app to work, but it just doesn't.
I have 6 hikvisions. Three are old (almost a decade) and three are < 3 years. The old ones don't support onvif and I cannot come up with any combination of URL/port to get them to work. They do work on a multitude of other smartphone apps I've tried. RTSP is a dead end, even allowing for ports, etc. This may be in part because the app refuses to accept modified URLs I put in without "helpfully" updating them; e.g. I have another app that shows me the fullly-functioning URL to one of my RTSP streams but this app adds some httpviewer query string on the end if I recall correctly.
Of the newer onvif-supporting cameras, even when I turn onvif on only one of the three can be found--but without audio. The other one I can get the app to find it but it displays nothing unless I use the JPEG option, which briefly flashes an image every two seconds or so followed by mostly grey.
Your cameras do not meet the complete ONVIF compliance standards, which results in the absence of a jpeg encoded rtsp stream, a requirement for the application. Moreover, the Roku device has limitations that prevent it from supporting the h264 rtsp stream.
Regarding the jpeg stream, if you intend to showcase the cameras' high resolution, it may lead to slow performance. Transmitting a jpeg (mjpeg) stream entails capturing each frame as a full jpeg image, which can be quite large in size. To achieve a smoother stream, you could decrease the cameras' resolution.
I was hoping to use this channel, or even the pro version, but I have a somewhat unique camera setup. I'm using a battery (solar) powered Reolink Argus 2E wireless camera that does not support RTSP or ONVIF. BUT, I found an open source package named "neolink" that provides an RTSP bridge to NVR's, etc. I can stream the live view now from the camera using VLC with the following, basic URL:
rtsp://192.168.1.10:8554/mycamera
I tried setting up a camera with the IP 192.168.1.10 and the port 8554, but when I try to edit the stream url to add "mycamera" (without the quotes), and save, your channel adds a "?" to the end of "mycamera", which will not work.
Anyone know of an easy way to fix this, or do I have to resort to also adding an NVR program like BlueIris? Not even sure I would be able to display that on roku at this point? TIA...
I've never been able to get this to work. The developer said it was because people use cheap cameras.
That's objective and there are a lot of good cameras in all price ranges these days.
Has anyone been able to get a hikvision camera to work? Surely a $200+ dollar camera should work with this but how? So far, no matter what settings I've tried, it never works.
Can anyone share some configs?
Hikvision, Reolink, SV3C HX Series (aka fuswlan SD10w-5MP), Amcrest???
Why is there not a config page somewhere to help us?
@DaBlues I gave up on it. The vendor here said my cameras do not fully support Onvif. This may indeed be the case. However, I'm back to the simple reality that all of the other software I've tried on my smart phone always works, with all of my cameras. I gave up on this particular effort, as it was a waste of time for me. I found a surplus laptop that just pulls them all down instead on windows software.