1. DNS ENODATA Error Resolved:
The DNS RESOLVE ERROR: queryA ENODATA on the FRITZ!Box was successfully resolved. The router was strictly blocking the dynamically generated *.mproxy.io subdomains via its DNS Rebind Protection. Adding the root domain mproxy.io as an exception in the FRITZ!Box configuration immediately cleared the error.

2. Properties Override Implemented:
We discovered that the Windows gateway executable does not accept command-line arguments (throwing Unsupported command argument(s) for --port or --register). To bypass this and ensure exact binding, we successfully deployed a local monocle.properties file inside the %USERPROFILE%.monocle\ directory. The gateway now successfully initializes with the following explicit overrides:
• rtsp.host=192.168.1.5
• rtsp.ssl.port=443
• rtsp.register.host=192.168.1.5

3. Camera Stream Optimization (Axis Specific):
To ensure absolute Alexa compatibility, the Axis P3245-LVE stream profile has been strictly optimized directly on the camera’s web interface:
• Video Codec: H.264 (Strict Baseline/Main profile, Zipstream completely disabled).
• Resolution: Adjusted to 640x360 (16:9 widescreen profile matching the Monocle portal configuration).
• Frame Rate: Hard-capped at a stable 15 FPS.
• Audio: Completely disabled/stripped from the stream to prevent Alexa from dropping the connection due to unsupported audio codecs.
• Monocle Tags: Switched from @tunnel to @proxy to bypass the deprecated tunneling service.

4. The Remaining Bottleneck:
With the custom properties active, the gateway starts flawlessly, binds to port 443 (LISTENING confirmed via admin netstat), and successfully registers the camera stream directly with a 200 (OK) response from the Axis camera.
However, despite clearing all local firewalls, ensuring the Echo Show 8 is on the main private Wi-Fi network, and forcing a full Alexa Smart Home device rediscovery, the gateway logs still show absolutely zero inbound connection lines when requesting the stream via the Echo Show 8. The window remains completely stagnant at the registration handshake.

Current Targeted Questions based on this state:
• Given that the gateway claims it expects inbound traffic via rtsp://[unique-id].mproxy.io:443/STREAM:[stream-id], is it verified that the Amazon Alexa Cloud infrastructure still considers the *.mproxy.io SSL/TLS root certificates valid, or are Echo devices silently dropping the connection due to expired or untrusted gateway certificates?
• Why does the Windows gateway log show that it successfully registers @proxy, but completely ignores the custom rtsp.register.host=192.168.1.5 setting in the log printout, still insisting on printing the public mproxy.io URL instead of the local IP fallback?
Any guidance on why the Echo Show 8 completely fails to hit the open port 443 on the host PC despite a clean local handshake would be highly appreciated.

Is there any way to see my cameras using monocle?
I do know the UID of each camera and the internal IP that uses.

As you can guess, I would like to use monocle with my Alexa to see me cameras.

Setup details:

• Gateway version: 0.0.6 (official monoclecam/monocle-gateway Docker image, host networking mode, running on Debian 13)
• Gateway connects to api.monoclecam.com fine and initializes correctly ([Monocle Connected], [RTSP Server Registered])
• DNS resolution for my gateway’s FQDN (6bc13cc1-6619-4191-a3f8-be07e910dbd9.mproxy.io) is correct, resolving to my local IP
• Port 443 confirmed reachable from other devices on my LAN

Verified directly with:
openssl s_client -connect <my-gateway-ip>:443 -servername 6bc13cc1-6619-4191-a3f8-be07e910dbd9.mproxy.io

Result:
verify error:num=10:certificate has expired
notAfter=Nov 28 23:59:59 2025 GMT

Since Alexa correctly refuses to connect to a server presenting an expired cert, this blocks camera discovery/streaming entirely — shows as “camera not responding” on the Echo Show side. Everything else in my setup (network, DNS, RTSP conversion, camera tagging with @tunnel/@fixaudio) checks out fine; this is the only remaining blocker.

Is anyone still actively maintaining certificate renewal for *.mproxy.io? Happy to provide more logs/details if useful.

But I’m having the same issue with my HiKvision cameras. They used to work with @tunnel & @noaudio. As of about a year ago, they stopped wotking. Just like the example there is no inbound connection.

The FQDN resolves correctly with ping. I don’t have any firewall rules that I think are at fault.
Both main & substreams, always H264; camera firmware is up-to-date.

I have checked and regenerated the token several times no no effect. I’ve tried the alternative tags using TCP & proxy but still nothing.

We have three Echos in our house and none of them can access the camera. I’ve disabled the Ring skill and the Monocle skill multiple times.

Anyone have ideas?

Apply for a Gold Mandate License - Minmidt.com

Buyers’ permit license in Cameroon - Minmidt.com

Gold Vendor List in Cameroon - Minmidt.com

Buy Gold in Cameroon, full CIF - Minmidt.com

CIF Gold for sale in Cameroon - Minmidt.com

Buy Gold in Cameroon with no upfront payment

Ministry of Mines in Cameroon - Minmidt.com

The Official Website of the Cameroon Ministry of Mines - Minmidt.com

minmidt Cameroon

minmidt.com official site

minmidt.com website

ministry of mines in Cameroon

Thanks,
Marc

Importance of Quality Commercial Roofing

Commercial properties—such as warehouses, offices, retail spaces, and schools—require roofs that can handle large surface areas, heavy equipment, and exposure to Florida’s weather. High-quality commercial roofing not only protects your structure but also enhances energy efficiency, reducing cooling costs during hot Miramar summers. Additionally, a well-installed roof helps prevent leaks, structural damage, and costly repairs in the future.

Types of Commercial Roofs in Miramar

There are several types of commercial roofs suitable for Miramar’s environment:

Flat Roofing Systems – Common in commercial buildings, these are cost-effective and easy to maintain.

Metal Roofs – Highly durable and energy-efficient, metal roofing is resistant to wind and fire damage.

TPO and EPDM Roofs – These single-ply membranes are known for flexibility, UV resistance, and excellent waterproofing.

Built-Up Roofing (BUR) – A traditional system made of layers of bitumen and fabric, offering strength and reliability.

Each type has unique benefits, and a professional commercial roofer in Miramar can help you choose the best option based on your property’s needs and budget.

i have a westshine hybrid and that will let me see all the cams. does any one know if i can get a program to put in the jooan unit so it will work like the westshine? or maybe the westshine program and flash that into this jooan unit thru the usb port from a thumb stick and have it become a westshine unit. this is the data tad on the jooan unit. 

I’ve already tried with different addresses (Gmail and Outlook) and checked spam folders.

Could you please manually activate my account?

Basically, for security reasons, Amazon dropped support for local RTSP streaming. That requires all camera streams to use Amazon’s “Smart Home Camera API” (cloud-based, authenticated HTTPS HLS or DASH), not direct RTSP. Therefore, although Monocle Gateway presents RTSP streams, Alexa devices no longer know what to do with the streams that Monocle Gateway presents.

I found a solution called “Scrypted” which may provide a solution. I’ve not had any luck getting it to work probably due to the same issues. Basically, Amazon will control displaying all camera streams on their devices.

My advice is to look for specific camera skills for your cameras to add to Alexa, or do what I do which is to just use TinyCamPro on your Fire TV to display your cameras. Using voice commands to display cameras on Echo Shows is now strictly limited to Amazon skills.

I have created my own voice commands to display my cameras via my Google Chromecast 4k. By not serving your cameras to the cloud, security is greatly improved.