New Echo Show 5 Gen 3 not working with Monocle

MRE

I just purchased a new Echo Show 5 Gen 3 device and it replies with a “camera is not responding” error for all my cameras. My other Echo devices work just fine through the same gateway setup and have for a few years now. I am running the latest version of the gateway.

Apparently, there is something different with Amazon’s new unit. If anyone has encountered this issue and solved it, the solution would be appreciated!

ericwass

@MRE Same exact problem. I bought the Echo Show 5 specifically to be able to see my cameras from my kitchen and I cannot get it to work no matter what I try. I have my own thread on it but jumping on this one as well. I really hope someone can crack this.

MRE

@ericwass Me too. I think the author is going to have to investigate it. The new devices must be looking for something that Monocle isn’t providing.

Frank nKansas

Are you folks using Blink cameras?

What app are the Shows attempting to use to display the video? Is Silk used?

MRE

@FranknKansas All sorts of Chinese IP cameras. Using the Monocle skill on Alexa.

Frank nKansas

OK.

I have a Show 5, 8, and 10. I’ll try them with Monocle. I use Blue Iris. Can Blue Iris be used in some manner with the Echos or is it best to just use the IP address of each camera?

I’ve been using Voice Monkey to display camera video. Voice Monkey uses the Silk browser to display the video.

ericwass

@FranknKansas I have 6 Hikvision cameras and 3 Foscams. It’s the Hikvision exterior perimeter cameras I care about. Thanks!

Frank nKansas

Well… I didn’t as well as I had hoped. I did add the Monocle Skill to the Alexa app and I added each of my 7 cameras to it. And the app scanned for new devices and found all seven cameras. I checked off each one.

Now in the Alexa app under ‘cameras’ all seven are listed and each one says, “Live view unavailable in Alexa App”. My ‘Ring’ camera is listed and it works.

I had figured there would be a prompt to add the IP of each camera, but that didn’t happen.

I know I am missing something. But I don’t know where to go from here.

MRE

@FranknKansas Go to https://portal.monoclecam.com/ and set up your cameras in the dashboard. Note that you may have to install the monocle gateway service on one of your home computers.

Frank nKansas

@MRE Thank you…

What I know: I can view the video of each camera using rtsp:// from VLC. And each does use H.264.

But none support audio. I ran through the troubleshooting questions and made it OK until I had to answer ‘no’ to the audio question… “If NO then sorry, you are out of luck. The Alexa devices only supports AAC and G.711 encoded audio streams.”

Does that mean that I am indeed out of luck? Of course, all I expected to be able to do was to display the video on my Echo Shows. And not to hear audio on any of them.

Thank you for the help!

Frank nKansas

I did go to the dashboard and the rtsp:// WAN IP port info looks correct and the cameras do show up in VLC with each URL.

I don’t have a gateway service on a home computer. I’ll have to read about that.

Thanks

MRE

@FranknKansas Most of my cameras don’t have audio. That should not be a problem. You most likely will have to set up the gateway.

ericwass

@MRE I set up the gateway and I still couldn’t get it to work. @MRE let me know if you have any luck.

MRE

@ericwass Monocle works for everything I have except on the new Echo Show 5 gen 3 unit. I had trouble with the 0.006 gateway version not working with a few cameras I set up through Blue Iris so I went back to the 0.005 version. That said, all the cameras I had direct links to the rtsp feeds did still work in 0.006.

Frank nKansas

I installed the gateway. But it did not install properly as shown below. Blue Iris uses port 443. So I don’t know how the same port could be used by Monocle.
Can anyone offer advice?

MONOCLE GATEWAY SERVICE         (Version: 0.0.6)
-------------------------------------------------
[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=13212)
[RTSP Server Listening] 0.0.0.0:8554 (PROXY)
[RTSP Server Started]
2023-11-10T22:20:05.760Z [ERROR] [PROXY SERVER ERROR] Error: listen EADDRINUSE: address already in use 0.0.0.0:443
[
  '[PROXY SERVER ERROR]',
  Error: listen EADDRINUSE: address already in use 0.0.0.0:443
      at Server.setupListenHandle [as _listen2] (node:net:1319:16)
      at listenInCluster (node:net:1367:12)
      at doListen (node:net:1505:7)
      at processTicksAndRejections (node:internal/process/task_queues:84:21)
      at process.runNextTicks [as _tickCallback] (node:internal/process/task_queues:65:3)
      at Function.runMain (pkg/prelude/bootstrap.js:1848:13)
      at node:internal/main/run_main_module:17:47 {
    code: 'EADDRINUSE',

ericwass

I bought my mother-in-law an Echo Show 8 (second gen) for the holidays but I unboxed it and set it up to see if it would work. It doesn’t. Same error. I’ve tried everything: different tags, gateway, no gateway, etc. So frustrating.

ericwass

[UPDATE] I take it back. I got it working with a combo I guess I never tried (running the gateway with only the @tunnel tag). So the Echo Show 2nd Gen works but the Echo Show 5 3rd Gen does not. I actually read the other day that the 5 is running a new, Amazon specific OS. I wonder if that’s the problem.

MRE

@ericwass It could be a new OS or something. The 5 gen 3 is definitely different than my 5 gen 1. I think I like the gen 1 better.