The port conflict is on the computer running the gateway, not the router.
It’s most likely two instances of monocle-gateway running, one in the background as a service and one you manually launched via the command line “monocle-gateway”.
I would suggest stopping/disabling the service and just running it in the terminal/command window for testing.
Ok I’ve deleted the Windows Service and now this is the prompt
OK, the log looks much better … lets see what is shows as you ask Alexa to show you the camera stream.
You also mentioned Fritzbox, please see my comments on Fritzbox here:
Basically you will need to add a provision to the Fritzbox to allow you gateway’s DNS hostname to resolve on your network. Fritz blocks these by default.
In Alexa display I read “waiting for Foscam” and Alexa says “The device seems not responding”.
For the fritz box i have to modify settings on my router or on monocle gateway?
Its some setting on the Fritzbox. I don’t know exactly how to do this, but you might ask the author of this thread as he figured it out on the Fritz:
try this it works for me
On the DNS rebind i have to add this string?
Yes, unless it has changed. It is printed on the startup of the Monocle Gateway in the log file listed as “FQDN”. It should only change if you create and use a new monocle token file.
Basically your router needs to allow this DNS hostname to be resolved via public DNS servers. It’s blocking it now because it sees that it resolved to a local/internal address and perceives that as a threat. In my PFSense router, I can allow that single hostname or I can allow all *.mproxy.io hostnames using a wildcard.
OK thanks a lot it worked. I noticed that sometimes alexa does buffering. Do you have any suggestions?
Lots of things can lead to buffering, but I would suggest trying the following:
- Make sure you Monocle Gateway is running on a system connected via Ethernet, not WiFI
- Try adding the
@noaudiotag to your camera in the Monocle Web Portal. (alongside your existing
@proxytags) . Sometimes the audio channel causes Alexa to lag/buffer.
- Try the camera’s secondary/sub stream.
- Try a lower camera resolution by adjusting your camera’s own internal settings.
- Make sure the camera is connected to Ethernet instead of WiFi wherever possible.