@osensnolf

Glad to hear it’s working now. Thanks, Robert

Issue resolved via PM.

@sextonbr

I apologize for the delayed response. I missed this thread until today.

You can PM me your old and new email address and I can make that change for you.
There is not currently a means to update your account email address via the Web Portal.

Thanks, Robert

@gln2 said in instructions to add Gateway to a QNAP NAS?:

QNAP HTTPS port default is 443, do I just need to change this setting and then the install would be much simpler than the Synology install?

I think using Docker you can allocate a private IP address for the Docker container instance (using “bridge” network) and that instance will listen on port 443 on its own dedicated IP.

If you were using the “host” network then yes you would have to free up port 443 so that Monocle Gateway could use it.

Thanks, Robert

@Tobi

My apologies, I missed this thread until today.

You can run the Monocle Gateway on an x86/x64/ARMv7/ARMv8 Linux system, x86/x64 Windows or x64 MacOS. We also have a Docker container that runs an Alpine Linux distro on x64 based systems.

The amount of technical detail required varies depending on the system you are using. We have an installer for Debian based Linux distributions like Ubuntu and Raspbian.

I’m sorry but I don’t know about a “VU solo 4k+ Sat receiver”? I don’t have any experience with that type of device.

Thanks, Robert

@dathomas85

It should be fully working now. Glitch encountered while upgrading forum software :-(

@dathomas85

The gateway, if everything were working properly, would show additional lines a detail showing the Alexa devices connecting and then performing RTSP negotiations withe the IP cameras.
This is almost always a network issue.

It could be a firewall blocking access to port 443 where the Monocle Gateway is running. It could be that port 443 is already in use by some other service already running on the same system where the gateway is installed. It could be (and often is) an issue of DNS rebinding (https://monoclecam.com/monocle-gateway/troubleshooting/dns-rebinding) It could be (albeit a more rare situation) that the Alexa devices and Monocle Gateway are on different networks (Guest WiFi network or VLANS)

For Reolink cameras I believe that just @tunnel is needed along with the manufacturer set to “Reolink” in the Monocle web portal.

From the log, everything else looks to be working correctly. The link between your Alexa account and Monocle is working and your Monocle Gateway is authenticated and communicating successfully with the Monocle servers. We can clearly see the incoming camera stream requests, but we are missing the Alexa device connections that should immediately follow the “INITIALIZE RTSP STREAM” blocks.

Thanks, Robert

@dathomas85

I followed up on your other thread:
https://forum.monoclecam.com/topic/607/alexa-camera-not-responding

Thanks, Robert

@aaky said in New resolution and problems with gateway:

640 x 352

640 x 352 resolution has been added.

Yeah i would assume this wouldn’t be backported to version 4. I upgraded to 5 just to stay current and get support. Obviously we know many vaporware that come and go but i will be watching for this and reminding him if a couple months pass… I really want access to the groups of streams.

@kd

FYI, if you are exposing your monocle gateway (port 443) to the Internet, you may want to have a look at this thread:
https://forum.monoclecam.com/post/2382

We have added additional security in the form of authenticated requests to the monocle gateway for users who want/need to expose the service to the Internet.

Thanks, Robert

I am hardwired ethernet thru poe switch to each camera
I am using the following settings
Digest
H264
None on audio
1920*1080
@noaudio, @proxy

Thanks for the reply’s
Wayne

@Monocle
Thank you for the reply. I have both the PC running the Gateway as well as the Show 5 on the same network.

Note - I have Google Wifi - and confirmed both devices are on the same AP.

I opened 443 and the device running the Gateway.

Confirmed firewall is allowing the monocle apps (even temporarily turned if off just to test).

I was able to ping the dns assignment and it responded with the proper IP for the device running the Gateway.

Still unable to connect.

Please let me kbow of there is anything I can check.

@LosBoricua I also have the UVC-G4-Bullet, and it works fine with Monocle/Gateway depending on the Echo device’s capability. I have tested it with two models:

Fire TV Stick 4K running FireOS v6.2.6.8 and FireTV Home v6200198.1, linked to an Echo Plus - Works

Echo Spot running FW v649600321 - Does NOT work

@Auspician , @Velocity

I believe the Echo Show 8 is limited to 1080P streams. Try the low resolution stream (secondary stream) from the ReoLink:

rtsp://192.168.0.24:554/h264Preview_01_sub

Thanks, Robert

@Birdbrainuk said in Help setting up AccFly camera with gateway:

7b3594ab-b21f-4472-a1f1-6432f7bd548d.mproxy.io

That DNS records is not working for me either. Odd. Typically this would be a DNS REBINDING issue but the fact that I cannot get it to resolve suggests it was never properly registered.
There was an SSL certificate issue going on with one of our servers around this time and I wonder if that caused some problem here. Try going to your user profile in the Monocle web portal and create a brand new API TOKEN and replace the token file with the new one and let’s see if that helps.

Thanks, Robert

Thank you for the informative explanation of the process of Monocle Gateway and Alexa. I can understand it better now.

Alas, as yet I have been unable to find any settings to change within the router itself to allow mproxy.io through or prevent it’s blocking. It’s definitely being blocked in/at the router as the router’s own internal logs state as such. And it’s certainly not being blocked “further up the chain” as you say, as I have turned off completely the “safe mode” on my online account. In any case, if it was being blocked in this manner, it would also be blocked for my Asus router. I have been chatting to the Tech team at the ISP to see if there’s any way around it. Not holding my breath but we’ll see. For now, I’ll stick to using my own Asus router, at least it works.

Again, many thanks for all the help and info.

@Monocle

i figured that the Proxy was unable to update internal IP but this Issue is now solved.

But i hoped that monocle is able to handle the Connections better or faster but it takes ages to connect from my Echo Devices and the delay is around 5-8 Seconds sometimes more.

My Internal Structure is a

Reolink C1-Pro connected thru cable with the Router

My Echo Devices are connected to a 5G Network served by a Wifi Access Point from ubiquti 5G Nano AP with ranges around less then 10 Meters Air Range.

What can i do to lower the delay?