Ok, so I have removed the user for troubleshooting and that seemed to help it get further. Now I am having another problem where a connection seems to be made between the Fire Stick and RTSP stream, but then immediately disconnects.

Figured this out. If you are running Unifi Video as a docker container as well as Monocle Gateway you are going to have problems. If you follow the guide on here for installing the Monocle Gateway it advises you to configure it to run on a macvlan using a different IP to your Synology. This is because Synology normally uses port 443 however I already had my Synology running on a different port so 443 was free. Therefore I redeployed the Container without the Compose file and set the Container to use the same network as the docker host. I now have all my cameras functioning.

@Monocle Thank you very much for your feedback. The cameras are working normally.

@kaf27033 said in Setting up in Docker:
I actually made it past the initial error by shutting off the firewall (so I can work on allowing port 443 through) but I am not getting the following error.
Untitled1.png

Untitled2.png

One more note, I ended up downloading and modifying the Monocle.Properties configuration file and putting in my gateway ip address. This way I could continue using Wireguard VPN setting.

#--------------------------------------

#--------------------------------------
#rtsp.register.fqdn=
rtsp.register.host=192.168.1.** :Remove # and put in your gateway server address
#rtsp.register.port=443

@Ver1tas I had the same issue with the unexpected host ip address. It turns out it was a virtual adapter created by my vpn software. The easiest fix was to download and modify the Monocle.Properties file and put it in the Monocle directory. Just had to add my ip address and all was good.

#--------------------------------------

#--------------------------------------
#rtsp.register.fqdn=
rtsp.register.host=192.168.1.13 <----- remove the hashtag and enter your ip address, restart service.
#rtsp.register.port=443

SOLVED!
The problem was only on the logical ports.
If you want to set more cams, then you must set each cam with a different RTSP port.
So you will see every cam with the same gateway without problem !

@mattman
The file is monocle.token
If you type into console “sudo vi etc/monocle/monocle.token” then paste the key from the website into that. Press shift+; and type in “wq” and press enter. That will create the file in that directory.

I managed to solve this issue based on another post.

I am using the Virgin Media Hub 3 which doesn’t have any DNS Settings so I couldn’t put in an exception for the DNS Binding.

Instead I set the DNS for the ethernet port on my PC to the Google DNS 8.8.8.8 and 8.8.4.4. After a while when it had time to udpate then I was able to ping and nslookup the mproxy.io FQDN and it resolved to the IP of my machine.

Cameras are still not working but this hurdle is solved.

@admin Thank you – I that did the trick!

@vmsman said in Reolink RLC-820A Not working on Monocole Gateway:

Does it help you that these other three programs handled /h264Preview_01_main and worked with this camera?

Not really … (unfortunately)
The hardware is probably capable of playing the stream … it’s the viewer software that must support the H265 codec. The URL signature /h264Preview_01_mai really does not matter … it’s the data returned in the SDP (stream descriptor) that is telling the player to use the H.265 codec. Specifically this line:

I only noticed a single video stream (#96) and single audio stream (#97) in the log data you posted above. It’s telling the viewing software the stream supports H.265 for video and AAC audio.

Unfortunately Amazon has not added support for any newer video codecs since H.264 for Alexa camera streaming. See https://developer.amazon.com/en-US/docs/alexa/device-apis/alexa-camerastreamcontroller.html#supported-video

You could try using the @fakefmtp tag … but I seriously doubt it will work.

The only thing I can think of suggesting is to have some other software (like FFMPEG/FFSERVER) ingest the H.265 stream and re-encode (transcode) it and output it via H.264. Clearly this will add latency and is a somewhat ugly solution. Other users have mentioned using SCRYPTED for their Unifi cameras. I have not tried it out yet, but I think it may be using FFMGEG under the hood to transcode the stream.

Thanks, Robert

Update - At least with a GV-EBD8711 8 Mpix eyeball camera with v1.06 firmware, you can set the main stream to H.264 and HD and use whatever authentication you want. Downside is you lose all the resolution you paid for and can’t get it back on another substream for your NVR.

I’m 99% sure the problem is with Geovision Firmware in that it always returns the main stream video regardless of substream path given.

To get around this: You can use a sub stream set H.264 and HD resolution. H.264 (vs H.265) is required by Alexa and HD is the max resolution since Alexa isn’t able to downscale video.

You must turn off RTSP authentication, and use the RTSP path: rtsp://aaa.bbb.ccc.ddd:554/media/video#/video

Where video# is either video1 or video2 and correlates to the substream you want–video0 is the main stream

Downside – your camera will be open and without a password to view and hear audio via RTSP to anyone that can connect directly to your camera network. You also might not get audio since RTSP DESCRIBE handshake isn’t really occurring and instead going directly to the media source.

@iorifly said in Using the skill Brazil [ANSWERED]:

Esteemed,
   Sorry if this is the wrong place. But I need help! I got a alexa echo show 5. I would love to use MONOcle. However, the skill is not enabled for my language. How do I make this request? To use I need to install the Monocle server on my pc?
But first I need to have the skill available for my country. Can anyone help with the way?

Hello @iorifly.
I could solve this problem changing my default country on amazon settings to United States.
You should look for “preferences” under the menu “content & devices”.
This way you can enable the skill, and move back to Brazil.

Regards

@Monocle it started working sometime earlier today. I tested at approximately at 2:30pm cdt. I hadn’t restarted the echo or anything else today. Thanks for the super fast fix!

@Monocle thanks again Robert.