@pfeffi

Unfortunately not. I believe the latency is due to the platform and RTPS/Codec implementation on the small embedded device. I have tested similar camera stream on a Raspberry Pi (embedded ARM-based device) and experienced similar latency.

@tomsoyer

FYI, generate a new Monocle token for testing on your PC, else they will both compete for the same DNS hostname.

@cdudeman

It probably won’t matter but you could also try using @proxy-tcp (instead of @proxy) to see if it can maintain the connection for more than 30 seconds.

Thanks, Robert

@MNB

Glad it was something simple to resolve the issue :-)

Thanks, Robert

@Cyrillec

As far as we know, Reolink Argus cameras don’t support RTSP and all other ReoLink cameras require using our Monocle Gateway software to achieve compatibility. Or course Amazon could fix the issue in Alexa or Reolink could fix it in an updated firmware, but at this point we are not aware of any such fixes. So it should be able to work now, but you would have to use the Monocle Gateway locally.

Thanks, Robert

@tyrone-creed

No you should not have to reboot the machine.

You can restart the Monocle Gateway service either using the Windows Service Manager (GUI) tool or by using the following command in a command/shell window from the directory where you have the Monocle Gateway files:

monocle-gateway.exe --restart

(See: https://monoclecam.com/monocle-gateway/install/windows#windows-service for more commands.)

Thanks, Robert

@TexasBill

Just a screenshot of the error you were getting.

If you have the Monocle Gateway installed locally and your camera tagged (@tunnel) to use the gateway, you can copy the log data to this post and I can review it for any errors. Make sure to include the part of the log that includes the startup messages as well as the period of time that covers you asking Alexa for the camera feed.

I just thought of one more technical item that Google WIFI could be blocking (if you are using the Monocle Gateway software). DNS Rebinding, please see: https://monoclecam.com/monocle-gateway/troubleshooting/dns-rebinding

Thanks, Robert

@mescopr

You should not need to open any ports on your router.

Do you have Monocle Gateway installed on a computer inside your network? That is what is needed first. The Monocle Gateway service running on this computer must listen on port 443 and the Alexa devices must be able to access this computer (on port 443) inside your local network.

The Monocle Gateway service does communicate over the Internet to coordinate when an Alexa device requests a camera stream, but you don’t need to expose any inbound ports for this to work. All the streaming data is maintained locally inside your private network.

Thanks, Robert

@giang said in Problems with website anyone !!!:

Website won’t open for me… only thing I can access is this forum.

This issue has been fixed now. Thank you for the heads up.