[RELEASE] Amcrest IPM-721 & IP2M-841 LIVE Video/PTZ/Night Vision/Motion/Video Record/+More IP Camera DTH

Did already and no change.

So I just recently bought an IP2M-841W hoping to get some ST love on it. Honestly I read the first 100 or so posts before buying it and back then most things seems fine. I then bought it and set it up and it works fine via the web interface and from the IOS app. I installed the DTH (thank you by the way for all the hard work) I made sure it didn’t have the latest firmware (has an older 2016 one) It did not work the first try out the gate so I went back and read the next 375 posts or so. So I’m all up to date and didn’t want to post before trying everything in this thread. Unfortunately I’m running out of ideas as like many people recently I can not get live video. I can take snapshots all day and use PTZ till my finger tips get raw. No settings seem to make the streaming work. I’ve got this setup on the following settings:

10.0.0.99 port 80 (tried all the other ones too and changed the deviceid each time as well)
RTSP port is 554
Camera Channel is 0
Video Channel is 1
debug is on

I’ve tried over several days with no luck. Here are some logs from most recent attempt.
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:50:09 PM: info ¦¦¦¦ ipIsLocal -> Host IP ‘10.0.0.99’ is Local
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:50:09 PM: info ¦¦¦¦ ipIsLocal -> Found = 00001010
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:50:09 PM: info ¦¦¦¦ convertIPtoBinary -> IP address passed in is 10.0.0.99 and the converted binary is 00001010000000000000000001100011
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:50:09 PM: info ¦±- videoStart -> Streaming MJPEG video; apiCommand = /cgi-bin/mjpg/video.cgi?channel=1&subtype=0, IP = 10.0.0.99, Port = 80
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:50:09 PM: info ±-- videoStart -> camVideoChannel = 1, state.camVideoChannel = 1, camChannelModString =
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:50:09 PM: info videoStart -> Turning Video Streaming ON

eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ¦¦¦¦ convertIPtoHex -> IP address passed in is 10.0.0.99 and the converted hex code is 0a000063
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ¦±- hubGet -> BEGIN
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ¦¦¦¦ convertIPtoHex -> IP address passed in is 10.0.0.99 and the converted hex code is 0a000063
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ¦¦¦¦ hubGet -> headers = [‘HOST’:10.0.0.99:80, ‘Authorization’:‘Basic YWRtaW46R3I4dmV0dGU=’]
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ¦±- hubGet -> BEGIN
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ¦¦¦¦ hubGet -> Network Device Id = 0A000063:0050
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ¦¦¦¦ hubGet -> Using IP '10.0.0.99’
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ¦±- setFlipMirrorMotionRotateNv -> Current: flipStatus = off, mirrorStatus = off, motionStatus = off, nvStatus = off, recordStatus = auto, rotateStatus = off (movement speed = Default:1, motion sensitivity = 1)
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ¦¦¦¦ hubGet -> apiCommand = /cgi-bin/configManager.cgi?action=getConfig&name=VideoInOptions&name=MotionDetect (size = 81)
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ¦±- ‘apiCommand’ command string built
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ±-- poll -> BEGIN
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: trace Poll
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info Refreshing Values…
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info configure -> Executing
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:43 PM: info ‘updated()’ called…
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:17 PM: info ¦¦¦¦ ipIsLocal -> Host IP ‘10.0.0.99’ is Local
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:17 PM: info ¦¦¦¦ ipIsLocal -> Found = 00001010
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:17 PM: info ¦¦¦¦ convertIPtoBinary -> IP address passed in is 10.0.0.99 and the converted binary is 00001010000000000000000001100011
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:17 PM: info ¦±- videoStart -> Streaming RTSP video; apiCommand = /cam/realmonitor?channel=1&subtype=0, IP = 10.0.0.99, Port = 554
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:17 PM: info ±-- videoStart -> camVideoChannel = 1, state.camVideoChannel = 1, camChannelModString = 1
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:17 PM: info videoStart -> Turning Video Streaming ON
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:03 PM: info ¦±- parse -> END
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:00 PM: info ¦¦¦¦ parse -> Detected: Temp image response; Sending picture to SmartThings…
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:00 PM: info ¦¦¦¦ parse -> descMap RAW = [‘index’:‘17’, ‘mac’:‘9C8ECD109D8A’, ‘ip’:‘0A000063’, ‘port’:‘0050’, ‘requestId’:‘999239a6-a428-4339-90f8-8bdda004154c’, ‘tempImageKey’:‘901468cc-75b5-49b9-8266-593cee5b2dd5’]
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:49:00 PM: info ¦±- parse -> BEGIN
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ¦±- hubGet -> hubAction = GET /cgi-bin/snapshot.cgi?channel=0 HTTP/1.1
Accept: /
User-Agent: Linux UPnP/1.0 SmartThings
HOST: 10.0.0.99:80
Authorization: Basic YWRtaW46R3I4dmV0dGU=

eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ¦¦¦¦ hubGet -> headers = [‘HOST’:10.0.0.99:80, ‘Authorization’:‘Basic YWRtaW46R3I4dmV0dGU=’]
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ¦±- hubGet -> BEGIN
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ¦¦¦¦ hubGet -> Using IP '10.0.0.99’
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ¦¦¦¦ ipIsLocal -> Host IP ‘10.0.0.99’ is Local
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ¦¦¦¦ hubGetImage -> Local IP detected: Switching to HubAction
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ¦¦¦¦ ipIsLocal -> Found = 00001010
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ¦¦¦¦ convertIPtoBinary -> IP address passed in is 10.0.0.99 and the converted binary is 00001010000000000000000001100011
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ¦¦¦¦ hubGetImage -> Using IP '10.0.0.99’
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ±-- hubGetImage -> BEGIN
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ¦¦¦¦ apiCommand = /cgi-bin/snapshot.cgi?channel=0
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info Taking Photo
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info configure -> Executing
eaee7180-deef-445a-a80d-7aff8a4faaa0 9:48:54 PM: info ‘updated()’ called…

Hi @LCSteve,

I am sorry to hear that this has been so frustrating for you. To be honest, I am at a loss for suggesting anything other than the lame “the ST video streaming is not a supported API” blah… blah… blah…

The fact that you are able to use the PTZ and the picture capture tells me that the DTH appears to be installed and configured properly.

The only remaining questions to ask that I can think of are:

  1. Can you view video streams from the AMCrest phone app?
  2. Have you tried toggling the DTH “video stream” type for both RTSP and MJPEG?

@Belgarion thanks for the reply, as I mentioned I read this whole thread so I’m definitely aware of how many times this question has come up and how you’ve patiently helped and worked with people. At least I’m not asking how come I can’t view it outside my local network or how again do I get it to trigger an alarm in ST :wink:

I’m with you in that I think it’s got to be something with ST causing the issue, I’ve tried every conceivable iteration of settings. I went so far last night spending 2 more hours working at it with things like switching to Ethernet vs WiFi, different WiFi connections, static vs DHCP, changing the video stream type from 264 to mjpeg 1080 down to 640 etc. Then reset them back to normal. Through all of this the IOS Amcrest app worked fine as did the direct login on my Macbook via the IP.

After none of that worked I tried using the generic camera streamer from PStuart. After some tinkering and finding the correct address needed I could not get that to work either. I did though find that if I took the address listed on the device ie the same one I tried with the generic viewer and pasted it in my Safari browser it opened in my copy of VLC and I could see the feed fine. So the settings must be correct since outside of the ST app it works.

The only 3 items I have left to check as a possibility in my book aside from just waiting to see if ST changes something are:
Upgrading to the next firmware above mine, I think mine is an early 2016 one like 15R. But not going to the latest one breaking things.
[Update for those even remotely interested, I had firmware 11R and installed the 16R from 9/9/16 but it did not make any difference]

Look into if there is some streaming conflict in the app because I have an integration with Arlo already.
See if there is a way to have the camera record to my local media computer sort of like a DVR and be able to somehow integrate that feed into ST. I’d love to use Blue Iris but it doesn’t look like they are mac friendly so I’d need to get a 2nd box setup live 24/7 to use them.

The nice thing is even if I can’t ever get the full functionality to work I was able to setup a test CoRE piston and have the camera take a snapshot if one of my motion detectors went active so I can at least get some ST integration that way even if I can’t get it to record video. Is it possible to do something with the snapshots like forward them from ST? I know the Amcrest interface allows for this but my goal is to make my camera ‘offline’ from their cloud and host my own video.

I appreciate all your work on developing the DTH and the tremendous amount of support you’ve offered and I learned a lot about DDNS and some VPN info to boot :slight_smile:

Steve

I am running into issues like everyone above, but I’m trying to connect to the stream by connecting to the nvr the camera is currently connected to. I can take snapshots and control the ptz, but cannot access the live stream in this way either. I do have another Amcrest camera connected (wireless outdoor cam) that works fine with connecting via the nvr… But I do have it set to connect via DDNS. I may try with the same settings to see if it makes any difference, but I doubt it will. It seems that the video channel doesn’t make any difference as well… I can take snapshots using different numbers entered.

UPDATE:
I finally got it to connect to Smartthings using the DDNS. It’s not how I wanted to use the system, but until another solution is found, I’ll stick to it.

You were not able to stream to the app when you used a local IP? Then you setup that camera through DDNS and have been able to get full functionality in ST? I’m paraphrasing because it sounds like I’m in a similar boat as you were but I hadn’t considered the DDNS route due to the numerous comments in this thread discouraging it. If that is the fix I might be able to utilize that and incorporate it into some form of work around.

Thanks in advance,
Steve

Actually I went back and did not swap out the camera settings (changed to ip and changed the forwarded ports to the regular ports) and all was well… The camera settings must have been what was wrong… But I spent most of the morning trying different combinations. I could’ve swore I used those settings before though. So connecting to the camera via nvr works fine (841)

I find it interesting that the resolution to your problem was related to “camera settings”. Do you mean the AMCrest configuration or my DTH config settings?

@LCSteve, I appreciate the fact that you have plodded through all of this information and things must be turning into a giant run-on sentence at this point, but this has to be some kind of configuration issue. I have 3 models of these AMCrest cameras that can stream video because I have not updated the firmware to the Digest version.

I can only speculate that your camera configuration is using one set of IP/port/username/password/video sub-channel/ some combination of these and the DTH config is set to something else.

I wish that I could be of more help, but if the video stream channel is set to you the correct IP & port based on your DTH setting, and you are using the right protocol for that port, all that is left is the ST API hick-ups…

This is certainly an extremely high likelihood in my opinion, while I know a fair bit about a lot of things networking is not my strong suit, persistence is though :wink: honestly most of what I’ve done on the camera side is extremely minmal. I used the iOS app and scanned the QR code initially to set it up then later went in and updated the networking section to default to wireless as default and I changed it from DHCP to static whilst updating the 10.0.0.99 address to it. Here is a borrowed image from Amcrests’ site and while my values are a little different the 3 arrows they placed on the picture are the only 3 networking related items I changed.

I know this is a total n00b question but should I have updated more here? This is my first IP camera (Arlo doesn’t count) so I didn’t want to start changing settings all crazy like till I had basic functionality working. This way I could know I’m not chasing self induced gremlins right out of the box. I’m thinking tonight I might need to hard reset and try again but this time not use the QR code and plug in via Ethernet first

Regards,
Steve

The settings in the ST app… Now I have the channels set to camera channel 1 and video channel 2 for the camera. On my other camera it is 0 and 1. I also set up two users in the nvr, one that could only access the 841 and then another used who could only access the porch camera. Not sure if that made any difference.

Okay, thx.

Your config is a special case because of the NVR. You can specify different channel numbers for each camera in the NVR. Glad you got it working! :thumbsup:

I assume that subnet mask is correct because you say that you can get the PTZ and pics working, but it is different for my network.

Did you double-check your video port configurations to make sure they match?

[quote=“Belgarion, post:485, topic:45023, full:true”]
I assume that subnet mask is correct because you say that you can get the PTZ and pics working, but it is different for my network.[/quote]

I’ll need to double check them when I get home, I assume they are as I didn’t touch them, but…doesn’t mean they are right.

I’m a little fuzzy on your reference here are you referring to the web setup here showing the TCP/UDP/HTTP/RTSP ports? Are there video port configurations elsewhere I’m missing?

Thanks again for the help.

Under the “Network” section, you have shown the “TCP/IP” sub-section. The ports used for HTTP & RTSP are in the “Connection” sub-section.

Just worth checking to make sure the camera is listening on the same port that the DTH is trying to connect to for video streaming.

I’m still working on trying to get this working but I have two questions I’m hoping the group could help me answer.

Is anyone using this DTH successfully AND have Arlo cams integrated in St?

Does anyone know of a free public broadcast camera feed from an Amcrest camera? I wanted to try a feed from a camera other than mine to try and narrow down if its a setting on the camera or not.

Thanks,
Steve

Steve, you can setup your own “public feed” with Blue Iris:

I realize that you are trying to get to someone else’s camera in the DTH… but that is a long-shot.

[Update 08/05/2017 - OK, I factory reset the camera and started from scratch. I spent a couple of hours meticulously changing each and every setting in the Amcrest web setup and tested the camera DTH after everyone. I got all the way to the end and nothing made a difference. I pondered on this a bit and thought what else I did recently before the camera started working and before. I remembered the day before I updated the profile I had to reset my hub in order to get a new Utilitech water sensor to work as I have with all my previous ones. Since I’d tried all the other settings I said what the hay what could it hurt. I rebooted the hub and viola it saw the camera instantly. Resetting the camera to factory spec made it not available again and resetting the hub made it visible again. So for what ever reason thats the winning ticket each time. I hope this helps someone else down the line.]

[Update 08/04/2017 - Well I had to soft reset the camera because it kept locking up every few hours and now I can no longer access it again :wink: Not sure what changed in the camera but switching between profiles doesn’t fix anything. If I can find what is causing the issue I’ll post another update.]

Well I figured out what has been causing my issues not being able to see the feed in ST. I can’t tell you WHY its causing the problem but it can easily be reproduced. I’m posting this up to hopefully help some of the other dozen or so people previously having the same problem. Like many others I was able to use snapshot, PTZ etc but no stream no matter what I tried. While working on other item in the camera I changed the profile on the configuration tab.

By default it comes selected on the middle one Full Time. On this setting my streaming doesn’t work, if I choose either of the other two though the streaming function works great. Switching it back to full time and the live stream in the ST app stops working. Again don’t know why this is the case but I know now it was the source of my problem since it’s reproducible and one of the few things I changed in the app.

Thanks to all the folks especially @Belgarion for putting up with my persistence and long winded posts.

Steve

1 Like

How can I provide logs to someone can who help me figure out why I cannot start live video on my IP2M-841 camera. I can PTZ and take a screen shot, but not start live video.

Did you confirm that you are not having the same issue that LCSteve found a solution for 1 post up from yours?

Does anyone have a copy of the old firmware that will work with this DH for the IPM-721 camera?