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.

@chunsanger said in Separate VLANs Issue:

I am running into some issues with my Alexa devices (on a dedicated IoT VLAN) communicating to my Monocle Gateway/Unifi Protect cameras.

If I move the Alexa Device (Echo Show 5) to my main LAN then I can connect and view the RTSP stream without issue. But if I am on my dedicated IoT LAN, then I can see the camera listed, but cannot stream.

I have enabled communication on the firewall on port 443 using a LAN IN rule from my Echos to the Monocle Gateway without any luck. I also tried adding a LAN IN rule from my Echos to my Unifi Protect IP and RTSP stream port without luck.

Any suggestions would be appreciated.

I have my UI cams and NVR on my main network, no reason to put them on the IoT Vlan. If I were using some odd ball name IP cams, I would. But I’m trusting all of the UI hardware with my network, so why move the cams?? I have my Alexa stuff on the IoT lan as well as my RPi running monocle. There are some firewall rules to make sure your “admin” (main Vlan network) can talk to all of the Vlans. And then yes open up the port for the monocle on the monocle IP. IIRC, that’s all I did. With all the Alexa stuff on the same IoT network as the monocle PI, makes it a bit easier IIRC.

@rbull said in Run the Gateway in the background:

Hey all, do you know how you can run the gateway program in the background and start automatically on a windows restart?

So complete instructions are here :
https://monoclecam.com/monocle-gateway/install/windows

See the section about running it as a service.

When had it running on my Win machine, I didn’t bother running it as a service, I added it to the start menu, so it would run on boot up. I’m an idiot and just wanted access to the session window all the time and had bat files to stop and restart it w/o going to the cmd line. Once covid hit, and everyone working from home we had a lot of losses of the internet, and it was simplier to see when it was down, and stop and restart it, the way I was set up.

Now I’m running it on a headless RPi, and access it with VNC viewer as I wish.
I have the RPi restart each night, and it just seems more robust on the RPi than it was on my Win7 machine/workstation that was very busy all day long.

Seems to have fixed my issues. Is this still in beta coming up on year now?

Hello Robert @Monocle

is MJPG still possible? Tried to add my Loxone Intercom but cant see the MJPG Option:

Cheers,
Jan

Screenshot_20230414_120817_Chrome.jpg

@rbull Actually, got it. Had to put in the following tags: @fake-fmtp, @hangup, @noaudio, @proxy

@TracyReznik1325 said in camera terminals disconnected:

My wifi camera terminals got disconnected. Need to connect the blue and brown wire. Pl kindly provide the guidance to connect the two wire so that it will be useful to me further.

In general, the blue and brown wires could be part of a power supply, Ethernet cable, or some other type of connection. The process for connecting them can vary depending on the specific camera model and the type of connection involved. So, the more information you can provide, the better I can assist you.

I am also facing this issue.

topping this as I also looking to install the container on my arm32v7 pi.

I was going to just build my own image on the pi, but noticed that the source build is specially compiled for x64 on alpine linux. not sure if that would be a problem if i otherwise selected the arm32v7 or raspberrypi packages.

I found one of the forks was updated to use a base image of debian buster-slim with intensions of being used on a Pi 4. So I created my own image and tested it

https://hub.docker.com/r/steinauf/monocle-gateway-rpi

I’ll submit a PR to see if this can be added.

I had this issue too, though I was running the gateway in a container with macvlan networking. it creates a new IP address to use, and I had forgotten to forward ports to that IP. I attempted to forward TCP 443 that port, but being a macvlan it was on a different subnet and my Orbi wouldn’t allow that.

no matter, I just switched back to host networking for now (which already had port 443 forwarded) and it works

------------------------------------------------- MONOCLE GATEWAY SERVICE (Version: 0.0.4) ------------------------------------------------- [Monocle Starting] [Monocle Connecting] [Monocle Started] [RTSP Server Starting] [RTSP Server Listening] 0.0.0.0:8555 (RTSP) [RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS) [RTSP Proxy Started] (PID=16) [RTSP Server Listening] 0.0.0.0:8554 (PROXY) [RTSP Server Started] [Monocle Connected] [RTSP Server Registered] ------------------------------------------------- MONOCLE RTSP SERVICE - INITIALIZED ------------------------------------------------- FQDN = redacted.mproxy.io HOST = 192.168.1.99 PORT = 443 -------------------------------------------------