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

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. 

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.

I’m still seeing the DNS resolve error, so thing’s still not right.

Just a question if the service works in South Africa? I have the Alexa app and all that goes with the products, but not sure if the monocle service is separate from this “supported regions” category?

Thanks so much!

I can’t connect Alexa to my security cameras. I have installed the Monocle Gateway in a Docker container hosted on my NAS. Since the NAS uses port 443, I have set up macvlan on a dedicated IP. I have an existing recording software that runs on a container in the same NAS, so I know the cameras are working. I have verified the RTSP streams, but nothing seems to be reaching the Monocle Gateway. I manually connected and saw that connection in the log:

•         __  __  ___  _  _  ___   ___ _    ___              *
  

•        |  \/  |/ _ \| \| |/ _ \ / __| |  | __|             *
  

•        | |\/| | (_) | .` | (_) | (__| |__| _|              *
  

•        |_|  |_|\___/|_|\_|\___/ \___|____|___|             *
  

•                                                            *
  

•               MONOCLE RTSP PROXY SERVER                     
  

(built using the LIVE555 Streaming Media library version 2018.04.25; licensed under the GNU LGPL)

[Monocle Connected]

[RTSP Server Registered]

MONOCLE RTSP SERVICE - INITIALIZED

FQDN = X-145f-4783-85a4-X.mproxy.io

HOST = 192.168.X.XX

PORT = 443

2024-11-27T17:32:17.830Z [INFO] [192.168.3.251:63663 <Lk-tD2VoQ>] RTSP CLIENT SOCKET CONNECTED

2024-11-27T17:32:17.831Z [WARN] [192.168.3.251:63663 <Lk-tD2VoQ>] RTSP CLIENT INVALID REQUEST: GET / HTTP/1.1

2024-11-27T17:32:17.838Z [INFO] [192.168.3.251:63663 <Lk-tD2VoQ>] RTSP CLIENT SOCKET CLOSED

Any pointers on what I’m doing wrong is greatly appreciated. I tried with @tunnel and @proxy stages, but nothing seems to work.

Thanks!

https://pastebin.com/5GUuM0RW

First run is the Overview “camera” which is the problem child

Second run is a working camera - Amcrest front door.

The computer running Monocle Gateway does not need a public IP address on the Internet. It can certainly be a private IP address inside your network behind your router/NET. It does however require outbound Internet access to communicate with the monocle services. This computer also need to be accessible on your network from the Alexa devices. The Alexa devices will talk to the Monocle Gateway when requesting camera stream rather than talking to your IP cameras directly.

Another question, if I change the Monocle settings on the official website, do I need to generate a new token?

No, settings are communicated for each camera stream every time the camera stream is requested/triggered from Alexa. We do suggest generating a new token if your IP address changes on the computer running Monocle Gateway. It’s not required but it can take up to 24 hours for the new IP address to get propagated in the DNS record. Thus a new token speeds this process up by issuing a new DNS record fore your Monocle Gateway instance.

Thanks, Robert

• Hiding cameras from the main listing (Hidden cameras will continue to work with Alexa.)
• Disabling cameras (Hidden from the main listing and will no be available to Alexa)
• Added additional context help on the camera editor for tagging, etc.
• Removed the camera resolution and timeout fields on the camera editor. These are not really used by Alexa anyway.
• Other minor bug fixes.

Thanks, Robert

But it’s still a side-project and freely provided and hosted :-). So support is not always immediate and sadly in this case a bit more delayed than usual. I’m usually able to address any server-side related outage in a more timely manner. But I dropped the ball this time around.
Thanks, Robert

Thanks a lots @Robert it was a joke ;)
Your work it’s very good, and i know, that isn’t easy to manager a free project.
Monocle it’s very cool project, and I will make a donation

great

good job
a long life for you and monocle ;)