FOSCAM FI9928P

jacky2307

VideoSub works with VLC but still don’t work on Alexa. I send you my monocle gateway

monocle 2.PNG

Monocle

Those errors in the log are a problem. Something else is using port 443.

Based on the fact that all the listener ports are in conflict, you may be running an instance of Monocle Gateway as a service in the background. Then if launching the executable “monocle-gateway” while its also running in the background would definitely cause these errors.

Thanks, Robert

jacky2307

I’ve searched on my FritzBox and Foscam is using the TCP port 88, 888 and 443

Monocle

@jacky2307

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.

Thanks, Robert

jacky2307

Ok I’ve deleted the Windows Service and now this is the prompt

Monocle

@jacky2307

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:
https://forum.monoclecam.com/topic/248/the-camera-does-not-respond/4

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.

Thanks, Robert

jacky2307

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?

Monocle

@jacky2307 said in FOSCAM FI9928P:

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:
https://forum.monoclecam.com/topic/248/the-camera-does-not-respond/6

Thanks. Robert

pfeffi

try this it works for me

https://en.avm.de/service/fritzbox/fritzbox-7390/knowledge-base/publication/show/663_No-DNS-resolution-of-private-IP-addresses/

jacky2307

On the DNS rebind i have to add this string?

Monocle

@jacky2307

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.

Thanks, Robert

jacky2307

OK thanks a lot it worked. I noticed that sometimes alexa does buffering. Do you have any suggestions?

Monocle

@jacky2307

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 @noaudio tag to your camera in the Monocle Web Portal. (alongside your existing @tunnel or @proxy tags) . 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.

Thanks, Robert