Gateway/Alexa only works when gateway open on computer. [SOLVED]

Don

I have two Besdersec model# BES-SD053 IP cameras paired with wifi to my system that are working fine. I wanted to be able to view them on all my Alexa devices (Echo Spot, Echo Show 5 2 of em, Alexa Fire TV sticks 3 of em, Echo Show 8 coming soon) which is why I enabled the Monocle skill, but it would only work on my Echo Spot. Come to find out I needed to install the Monocle-Gateway which I did and being some what computer savvy but not a bunch I was able to get the gateway working and every one of my Alexa devices can now view the live feed from my cameras, even my Fire TV sticks which was a nice surprise, however, as soon as I close the gateway none of my devices will no longer recognize the cameras. My question is, does the gateway have to be open on my computer for it to work? I’d like to be able to just ask Alexa to show me a camera without having to turn on my computer each time. Also, I gave the IP address of my computer (HP Omen 880) not my router (Linksys-ea7300). And I did not install the Gateway with a command prompt window, I just double clicked the .exe file.
It’s just odd to me that all my Alexa devices show both cameras when the gateway is open but as soon as I close it … nothing.

This is what I get using an Echo Show 5.

-------------------------------------------------
MONOCLE RUNTIME ENVIRONMENT
-------------------------------------------------
VERSION   = 0.0.4
OS/ARCH   = win32\x64
PROCESS   = monocle-gateway (PID=20952)
TIMESTAMP = 2019-11-22T17:27:13.844Z

-------------------------------------------------
MONOCLE GATEWAY SERVICE         (Version: 0.0.4)
-------------------------------------------------
[Monocle Starting]
[Monocle Connecting]
[Monocle Started]
[RTSP Server Starting]
[RTSP Server Listening] 0.0.0.0:8555 (RTSP)
[RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS)
[RTSP Proxy Started] (PID=3528)
[RTSP Server Listening] 0.0.0.0:8554 (PROXY)
[RTSP Server Started]
[Monocle Connected]
[RTSP Server Registered]

-------------------------------------------------
MONOCLE RTSP SERVICE - INITIALIZED
-------------------------------------------------
FQDN = 978206d5-7f90-48e3-ab9a-8fd3209719e2.mproxy.io
HOST = 192.168.1.134
PORT = 443
-------------------------------------------------

-------------------------------------------------
INITIALIZE RTSP STREAM:  Robby
-------------------------------------------------
 - NAME  : Robby
 - LABEL : PRIMARY
 - URL   : rtsp://192.168.1.126:554/11
 - UUID  : STREAM:98aed033-d158-4cbf-8d5f-4de9aa05dd2a
 - SESS  : 55450c26-f249-4a63-b73e-5b8fd04b7e44
 - MODIF : Thu Nov 21 2019 10:02:40 GMT-0600 (Central Standard Time)
 - TAGS  : @tunnel
-------------------------------------------------

2019-11-22T18:27:59.374Z [INFO]  [192.168.1.100:49036 <Syv2OoH2S>] RTSP CLIENT SOCKET CONNECTED
2019-11-22T18:27:59.503Z [INFO]  [192.168.1.100:49036 <Syv2OoH2S>] RTSP CLIENT ATTACHED TO STREAM: Robby (STREAM:98aed033-d158-4cbf-8d5f-4de9aa05dd2a)
2019-11-22T18:27:59.510Z [INFO]  [192.168.1.100:49036 <Syv2OoH2S>] RTSP ENDPOINT SOCKET CONNECTED {192.168.1.126:554}
2019-11-22T18:27:59.512Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT REQUEST]  --> [DESCRIBE] rtsp://978206d5-7f90-48e3-ab9a-8fd3209719e2.mproxy.io:443/STREAM:98aed033-d158-4cbf-8d5f-4de9aa05dd2a?session=55450c26-f249-4a63-b73e-5b8fd04b7e44
2019-11-22T18:27:59.513Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT REQUEST]  --> [HEADERS] {
  "accept": "application/sdp",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "1"
}
2019-11-22T18:27:59.514Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT REQUEST]  --> [DESCRIBE] rtsp://192.168.1.126:554/11
2019-11-22T18:27:59.515Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT REQUEST]  --> [HEADERS] {
  "accept": "application/sdp",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "1"
}
2019-11-22T18:27:59.634Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [401 (Unauthorized)] <cseq=1> (session=undefined)
2019-11-22T18:27:59.636Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [HEADERS] {
  "cseq": "1",
  "server": "Hipcam RealServer/V1.0",
  "www-authenticate": "Digest realm=\"Hipcam RealServer/V1.0\", nonce=\"b3537e7e79b5a850ab75f0576ec073db\""
}
2019-11-22T18:27:59.637Z [INFO]  [192.168.1.100:49036 <Syv2OoH2S>] RTSP ENDPOINT REQUIRES AUTHENTICATION: Digest realm="Hipcam RealServer/V1.0", nonce="b3537e7e79b5a850ab75f0576ec073db"
2019-11-22T18:27:59.637Z [INFO]  [192.168.1.100:49036 <Syv2OoH2S>] RTSP ENDPOINT ATTEMPTING AUTHENTICATION: DIGEST
2019-11-22T18:27:59.638Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT REQUEST]  --> [DESCRIBE] rtsp://192.168.1.126:554/11
2019-11-22T18:27:59.639Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT REQUEST]  --> [HEADERS] {
  "accept": "application/sdp",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "1",
  "authorization": "Digest username=\"admin\", realm=\"Hipcam RealServer/V1.0\", nonce=\"b3537e7e79b5a850ab75f0576ec073db\", uri=\"rtsp://192.168.1.126:554/11\", response=\"eae107854e86bb6ae25385d9aad276e8\""
}
2019-11-22T18:27:59.754Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2019-11-22T18:27:59.755Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [HEADERS] {
  "cseq": "1",
  "server": "Hipcam RealServer/V1.0",
  "content-type": "application/sdp",
  "cache-control": "must-revalidate",
  "content-length": "427",
  "content-base": "rtsp://192.168.1.126:554/11/"
}
2019-11-22T18:27:59.756Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [BODY]
 v=0
o=StreamingServer 3331435948 1116907222000 IN IP4 192.168.1.126
s=10
c=IN IP4 0.0.0.0
t=0 0
a=control:*
m=video 0 RTP/AVP 96
a=control:trackID=0
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=4D002A;sprop-parameter-sets=Z00AKp2oHgCJ+WbgICAgQA==,aO48gA==
a=framesize:96 1920-1080
m=audio 0 RTP/AVP 8
a=control:trackID=1
a=rtpmap:8 PCMA/8000/1
a=ptime:20
a=fmtp:8 packetization-mode=1

2019-11-22T18:27:59.757Z [INFO]  [192.168.1.100:49036 <Syv2OoH2S>] RTSP ENDPOINT AUTHENTICATION SUCCESSFUL: DIGEST
2019-11-22T18:27:59.759Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2019-11-22T18:27:59.759Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT RESPONSE] <-- [HEADERS] {
  "cseq": "1",
  "server": "Hipcam RealServer/V1.0",
  "content-type": "application/sdp",
  "cache-control": "must-revalidate",
  "content-length": "427",
  "content-base": "rtsp://192.168.1.126:554/11/"
}
2019-11-22T18:27:59.760Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT RESPONSE] <-- [BODY]
 v=0
o=StreamingServer 3331435948 1116907222000 IN IP4 192.168.1.126
s=10
c=IN IP4 0.0.0.0
t=0 0
a=control:*
m=video 0 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=4D002A;sprop-parameter-sets=Z00AKp2oHgCJ+WbgICAgQA==,aO48gA==
a=control:trackID=0
a=framesize:96 1920-1080
m=audio 0 RTP/AVP 8
a=rtpmap:8 PCMA/8000/1
a=fmtp:8 packetization-mode=1
a=control:trackID=1
a=ptime:20

2019-11-22T18:27:59.771Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT REQUEST]  --> [SETUP] rtsp://192.168.1.126:554/11/trackID=0
2019-11-22T18:27:59.772Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT REQUEST]  --> [HEADERS] {
  "transport": "RTP/AVP/TCP;interleaved=0-1",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "2"
}
2019-11-22T18:27:59.773Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT REQUEST]  --> [SETUP] rtsp://192.168.1.126:554/11/trackID=0
2019-11-22T18:27:59.774Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT REQUEST]  --> [HEADERS] {
  "transport": "RTP/AVP/TCP;interleaved=0-1",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "2",
  "authorization": "Digest username=\"admin\", realm=\"Hipcam RealServer/V1.0\", nonce=\"b3537e7e79b5a850ab75f0576ec073db\", uri=\"rtsp://192.168.1.126:554/11\", response=\"eae107854e86bb6ae25385d9aad276e8\""
}
2019-11-22T18:27:59.873Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=2> (session=udDDgZURGez)
2019-11-22T18:27:59.874Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [HEADERS] {
  "cseq": "2",
  "server": "Hipcam RealServer/V1.0",
  "session": "udDDgZURGez",
  "transport": "RTP/AVP/TCP;unicast;interleaved=0-1"
}
2019-11-22T18:27:59.875Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=2> (session=udDDgZURGez)
2019-11-22T18:27:59.875Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT RESPONSE] <-- [HEADERS] {
  "cseq": "2",
  "server": "Hipcam RealServer/V1.0",
  "session": "udDDgZURGez",
  "transport": "RTP/AVP/TCP;unicast;interleaved=0-1"
}
2019-11-22T18:27:59.923Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT REQUEST]  --> [SETUP] rtsp://192.168.1.126:554/11/trackID=1
2019-11-22T18:27:59.924Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT REQUEST]  --> [HEADERS] {
  "transport": "RTP/AVP/TCP;interleaved=2-3",
  "session": "udDDgZURGez",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "3"
}
2019-11-22T18:27:59.926Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT REQUEST]  --> [SETUP] rtsp://192.168.1.126:554/11/trackID=1
2019-11-22T18:27:59.926Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT REQUEST]  --> [HEADERS] {
  "transport": "RTP/AVP/TCP;interleaved=2-3",
  "session": "udDDgZURGez",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "3",
  "authorization": "Digest username=\"admin\", realm=\"Hipcam RealServer/V1.0\", nonce=\"b3537e7e79b5a850ab75f0576ec073db\", uri=\"rtsp://192.168.1.126:554/11\", response=\"eae107854e86bb6ae25385d9aad276e8\""
}
2019-11-22T18:27:59.983Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=3> (session=udDDgZURGez)
2019-11-22T18:27:59.985Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [HEADERS] {
  "cseq": "3",
  "server": "Hipcam RealServer/V1.0",
  "session": "udDDgZURGez",
  "transport": "RTP/AVP/TCP;unicast;interleaved=2-3"
}
2019-11-22T18:27:59.986Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=3> (session=udDDgZURGez)
2019-11-22T18:27:59.986Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT RESPONSE] <-- [HEADERS] {
  "cseq": "3",
  "server": "Hipcam RealServer/V1.0",
  "session": "udDDgZURGez",
  "transport": "RTP/AVP/TCP;unicast;interleaved=2-3"
}
2019-11-22T18:28:00.033Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT REQUEST]  --> [PLAY] rtsp://192.168.1.126:554/11/
2019-11-22T18:28:00.034Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT REQUEST]  --> [HEADERS] {
  "session": "udDDgZURGez",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "4"
}
2019-11-22T18:28:00.036Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT REQUEST]  --> [PLAY] rtsp://192.168.1.126:554/11/
2019-11-22T18:28:00.036Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT REQUEST]  --> [HEADERS] {
  "session": "udDDgZURGez",
  "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)",
  "cseq": "4",
  "authorization": "Digest username=\"admin\", realm=\"Hipcam RealServer/V1.0\", nonce=\"b3537e7e79b5a850ab75f0576ec073db\", uri=\"rtsp://192.168.1.126:554/11\", response=\"eae107854e86bb6ae25385d9aad276e8\""
}
2019-11-22T18:28:00.103Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=4> (session=udDDgZURGez)
2019-11-22T18:28:00.105Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [ENDPOINT RESPONSE] <-- [HEADERS] {
  "cseq": "4",
  "server": "Hipcam RealServer/V1.0",
  "session": "udDDgZURGez",
  "rtp-info": "url=192.168.1.126/trackID=0;seq=1;rtptime=10000,url=192.168.1.126/trackID=1;seq=1;rtptime=10000"
}
2019-11-22T18:28:00.106Z [DEBUG] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=4> (session=udDDgZURGez)
2019-11-22T18:28:00.106Z [TRACE] [192.168.1.100:49036 <Syv2OoH2S>] [CLIENT RESPONSE] <-- [HEADERS] {
  "cseq": "4",
  "server": "Hipcam RealServer/V1.0",
  "session": "udDDgZURGez",
  "rtp-info": "url=192.168.1.126/trackID=0;seq=1;rtptime=10000,url=192.168.1.126/trackID=1;seq=1;rtptime=10000"
}
2019-11-22T18:28:00.107Z [INFO]  [192.168.1.100:49036 <Syv2OoH2S>] RTSP ENDPOINT PLAYING MEDIA STREAM: Robby (STREAM:98aed033-d158-4cbf-8d5f-4de9aa05dd2a)
2019-11-22T18:28:00.107Z [INFO]  [192.168.1.100:49036 <Syv2OoH2S>] RTSP CLIENT PLAYING MEDIA STREAM: Robby (STREAM:98aed033-d158-4cbf-8d5f-4de9aa05dd2a)

Gunn

@Don Surprised you haven’t received a reply yet, so I’ll give it a go. Yes the Monocle service needs to run on your computer to work. That is how it forwards the requests to and from the Echo devices. Each time you make a request, it is routed through that skill to your computer and then back again. So it must be running at all times.
Many people have servers that run 24/7 and can put the app there, but I’m guessing you don’t have this.
Anyway that’s my understanding.

Don

@Gunn Thanks for the reply, I am curious though if you are saying a server if you mean router because I do have my ISP connected to my router which is on 24/7 but I do turn off my computer when not in use. Do you happen to know if Monocle is going to update the Alexa skill so we don’t have to run the gateway, sure would be a lot simpler.

Gunn

@Don said in Gateway/Alexa only works when gateway open on computer.:

@Gunn Thanks for the reply, I am curious though if you are saying a server if you mean router because I do have my ISP connected to my router which is on 24/7 but I do turn off my computer when not in use. Do you happen to know if Monocle is going to update the Alexa skill so we don’t have to run the gateway, sure would be a lot simpler.

Don, no, I did mean to say server. As in a computer that runs 24/7 to do things all the time…like home automation, weather station, Monocle, etc. But disregard since you don’t. Don’t want to confuse the issue.

I have no idea if Monocle is going to update. From what I understand, that is beyond their control. Monocle is a way to get 3rd party cameras to work with Alexa; a clever solution that otherwise Amazon doesn’t allow. So unless you want to switch to cameras that are fully supported by Amazon/Echo, I think this is the best you’re going to get.

I hope someone else can chime in and elaborate more…

Jouster-74

@Don

To add to the explanation…the gateway wasn’t needed prior to the release of the Show 5 and Show 8, at least in my experience. It is the new security protocols that Amazon has put in place that has resulted in the requirement for the gateway.

As you’ve discovered, if the gateway is running on a computer and that computer is shutdown, access to the gateway is lost and therefore that new required link won’t work.

So you have a couple of options. Either leave that machine running (not the best as could be very power hungry).run the gateway on something like an rPi (this is my way of doing things and it’s working fine and uses very little power).

It is also possible to run this on a NAS which would be left on permanently as well but I won’t suggest buying one just for this reason.

Don

@Jouster-74 - Thanks Jouster, I do hope that Monocle is working on updating they’re Alexa skill so we don’t have to use the gateway, I don’t like leaving my computer on, usually when I’m done I shut it off. Not sure what you mean by rPi or NAS but not sure I’d even wanna mess with it. As far as what devices I’m using, 2 Echo Show 5’s, New Echo Show 8, Echo Spot which did work just using the Alexa skill, plus I have 2 Toshiba Fire TV Editions ( 32" HD & 43" 4K) and a Fire TV Stick 4K with a 70" LG TV which when I have the gateway open I can view my cameras on any one of my devices, haven’t tried viewing on two or even three devices at once, I’ll have to try it.

Jouster-74

@Don its all down to new security protocols put in place by Amazon and nothing to do with Monocle…I’m not sure there is another way of doing things other than the gateway…but I’m sure they will keep up posted on here…

and rPi is a small computer the size of a pack of playing cards that costs a out £30 and uses very little power…the gateway can be run on that on your network and left running 24/7 at next to no cost.

I don’t believe there is any other way around this at the moment

Don

Thank you Gunn and Jouster for your input, since what I have right now is working on all my Amazon devices, albeit having to have the computer on and the gateway open, I do believe I’ll stay status quo until something better comes long. Again, Thanks !!

Monocle

@Don

Yes, it’s unfortunate that this intermediate (gateway) service is required, but I don’t imagine that Amazon will reverse its opinion on this and will continue to further limit existing devices with new/future firmware updates.

It is possible to use a small embedded device like a Raspberry Pi if you don’t want to have your computer running with this gateway service at all times.

Thanks, Robert

Monocle

@Don said in Gateway/Alexa only works when gateway open on computer.:

@Gunn Thanks for the reply, I am curious though if you are saying a server if you mean router because I do have my ISP connected to my router which is on 24/7 but I do turn off my computer when not in use. Do you happen to know if Monocle is going to update the Alexa skill so we don’t have to run the gateway, sure would be a lot simpler.

I wish we could. In fact when we started with the first release of Monocle, there was no gateway at all and the original FireTV models and Echo Show (gen 1 & 2) worked fine without the need of a gateway. However with the release of newer Show devices and all the latest FireTV 4K models, the gateway is required to satisfy the connection encryption requirements.

Thanks, Robert

Don

Robert @ Monocle, Thank you for your reply, I’ll look into this Raspberry Pi to see what kind of a hassle it might be, otherwise, not sure. I was able to use your Alexa skill with just my Echo Spot 1st gen but was unable to with my subsequent newer Echo devices, however using your gateway I can view my camera’s on all my Alexa and Fire TV devices which I will continue to do for now. Thanks again Robert.