i figured it out, no it does not need internet access. spin up a new vm and deploy this with a docker and you’re good to go. i can post my docker-compose if anyone is interested.

I did some additional tests.
I installed the lite version of Raspbian OS on the Rasperry Pi B+ 2014 (without GUI), to optimize performances, but I didn’t get any improvement of the 10 seconds latency.
Then reading other posts I understood that 10 seconds latency is normal.

I got also the audio working setting the audio codec to AAC.
I added the @hangout tag but I didn’t see any difference.

This is the the new Monocle Gateway configuration for Sricam SP017:
Camera feed: rtsp://x.x.x.x:554/onvif1
Authentication: DIGEST
Video Resolution: 640*360 (16:9)
Video Codec: H264
Audio Codec: AAC
Tags: @hangout, @proxy-tcp

I experienced again that @proxy-tcp is working better than @proxy.

After a certain period (1 to 3 minutes) the video on the Echo Show 5 turns blank, or the screen starts flashing.
I tested the Sricam SP017 on wifi and network cable but the problem is still there.
Is this a known problem?
Is there anything I can do to have the video lasting as long as needed?

Update:

I switched to using @proxy and @hangup and this now connects each time (takes around 10-15s which I can live with).

But… the video stream often becomes garbled (flickering lines and pink/grey/green screens). This happens with my Foscam cameras in addition to the Dericam S1.

I don’t think its a region issue. Monocle doesn’t restrict your location as far as I am aware.

Manual Anleitung
😀
how to install the camera. And all the others.
wie man die Kamera installiert. Und alle anderen

Did you ever solve this. I have the exact same situation except it is with a foscam cam. I setup the Gateway, tagged it as @tunnel and made sure MFG was set to foscam, Even tried the @noaudio tag. Still on my Alexa show, it says camera doesn’t support that. I reviewed this https://forum.monoclecam.com/topic/47/foscam-compatibility-readme and set it up as described.

The “401” error you are getting when using @tunnel is an authentication failure. The monocle gateway is failing to authenticate with the IP camera at 192.168.0.205 using BASIC authentication. I would suggest trying DIGEST authentication and maybe check your camera access password.

Thanks, Robert

@oldsap

I don’t believe Amazon offers support for this type of skill for the Philippines yet.

The following links show the languages and regions where this type of skill (CameraStreamController) is supported by Amazon.

https://developer.amazon.com/en-US/docs/alexa/smarthome/build-smart-home-camera-skills.html#device-support-and-regions
https://developer.amazon.com/en-US/docs/alexa/device-apis/list-of-interfaces.html
(see CameraStreamController)

I believe Monocle supports all of these regions with the exception of Japan at this time.
We would be happy to add the Philippines once Amazon adds support for it.

Thanks, Robert

@bigtxnutz ,

Apologies for the delayed response. I’ve unfortunately had to take a few weeks off from Monocle to deal with other priorities in life. I’ll be trying to play catch up over the next couple of weeks.

Glad to hear you were able to get it working using the tag: @fakefmtp.

You are correct in that its not documented at all as this is an experimental tag and may not be supported by all distros of the gateway software. My hope in future versions is to be able to auto-detect this type of condition and not have a reason for this tag to exist. But we are not there yet and it’s a work in progress. So in part it’s not documented because we don’t want it to exist permanently and in part because its very experimental. It’s basically lying to Alexa about the stream encoding just to get her to accept the stream and attempt to play it.

Thanks, Robert

@ferry

Glad to hear it’s working for you.

Thanks, Robert

@Jonathan-burge

If you are still having trouble, please post your log from Monocle Gateway where you ask for the camera stream until Alexa gives you the failure response.

Thanks, Robert

Yeah thanks for the jumping in over there.

From the searching that i have done, it appears that it supports just about everything that a regular Amazon Alexa show would. It lists somewhere I recall that it supports cameras. I’ll have to see if i can find where i read that. Appreciate the help.

@foomanchu

Thanks for the follow up.

@ijhammo

Based on the log snippets you posted, it does look like the Alexa devices are not able to connect to the Monocle Gateway instance. We should see additional lines of log data showing TCP connections and RTSP negotiations between the Alexa devices and the Monocle Gateway and then out to the IP cameras.

So the typical problems for these symptoms are :

DNS REBINDING - the network is not allowing the unique hostname (FQDN) to be resolved to your local/private IP address running the gateway instance Alexa device and Monocle Gateway are not on the same network or one is on a Guest network or isolated VLAN. Something is already using port 443 or port 443 is getting blocked by a firewall on the machine running the Monocle Gateway software.

Thanks, Robert