@ericwass It could be a new OS or something. The 5 gen 3 is definitely different than my 5 gen 1. I think I like the gen 1 better.

I came here looking for this exact solution and found it, i am not much of a computer guy at all, but found the instructions and managed to get it up and running very well, albeit after a week of torture, i managed to find all the solutions here in the forums, personally i thinks works well and i cannot find anything else near, to do what Monocle does.

I do have a Smartthings hub which seems to predominantly work via Github and have only ever had headaches trying to install and get stuff working with the open source stuff, it just seems to be a minefield, a confusing one especially for people like myself who just want a nice .exe to do all the work, to the point where my ST hub is just a coaster for my cup of tea now. I cannot even get my Sage doorbell to work though ST to Alexa and all i see recently on the forums is people complaining.

The majority want something that just works and Monocle seems to, without to much hassle.

@Monocle mine did not get fixed automatically. I tried restarting the container which did not resolve the issue either. The only thing that fixed it was to stop the container and then start it a minute later. Now everything is back to working.

@andi said in Unable to login via Alexa Skill:

@Monocle Hi Robert,

Thank you for your fast and in-depth support. I could solve the issue by switching to the Desktop version of the website. It seems the Alexa App uses Google Chrome on my Android device.

Using the Desktop Version the login worked fine.

With best regards

Andreas

Glad to hear its working now.

A couple of other points worth a mention…

When forwarding an RTSP feed on your router choose the TCP protocol (not both TCP and UDP).

When changing the resolution of a camera you not only need to update the monocle configuration but you also need to delete and re-add the camera in Alexa.

@Monocle said in Cannot get it Working :-(:

@Alarm_guy1
Based on the log the gateway is still not receiving inbound requests from Alexa.
From another computer (not the gateway) try to perform a NSLOOKUP command using the FQDN (ea400744-dbb9-4a49-864a-2f31f366xxxx.mproxy.io)
nslookup ea400744-dbb9-4a49-864a-2f31f366xxxx.mproxy.io

It should resolve to your private IP address where the gateway is running inside your network.
Is the HOST address (192.168.x.x) reported at the beginning of the log the correct IP address for this machine? The Monocle Gateway will attempt to automatically detect the IP address but sometimes if there are multiple addresses associated to the computer, it can assign the wrong one.
Are the Alexa devices are the same network as the Monocle Gateway … meaning they are not on a Guest WiFi network or isolated VLAN? The Alexa devices will need to communicate directly with the gateway on the local network.
Thanks, Robert

Right back on this for today anyway:
nslookup.jpg

The nslookup results posted.

The only issue I think is I have a Ubiquity Unifi WiFi extender but the as my router now doesnt have built in WiFi.
the Pi that monocle is on is hardwired into a switch that is connected to the switch that the Unifi is connected to…

it would be good to get this going :-)

cheers for the continued help

@Monocle Though maybe it was my VPN for when I download torrents, no such luck. Turned it off, restarted everything and came up with the same results in the log. Going to look at the router (also Synology) and try and dig deeper.

Thank you once again for your help. I know just enough about networking to get myself in trouble!

@kickapoo as much of an annoyance as it is, you could try changing the audio codec to NONE which may help with the buffering

Is the camera and the rasbery pi connected to the same router

I was having issues as I had my rasbery pi connected to a different router, I connected both to my main router and it works fine

Thank you for the informative explanation of the process of Monocle Gateway and Alexa. I can understand it better now.

Alas, as yet I have been unable to find any settings to change within the router itself to allow mproxy.io through or prevent it’s blocking. It’s definitely being blocked in/at the router as the router’s own internal logs state as such. And it’s certainly not being blocked “further up the chain” as you say, as I have turned off completely the “safe mode” on my online account. In any case, if it was being blocked in this manner, it would also be blocked for my Asus router. I have been chatting to the Tech team at the ISP to see if there’s any way around it. Not holding my breath but we’ll see. For now, I’ll stick to using my own Asus router, at least it works.

Again, many thanks for all the help and info.

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

Evening all

Is anyone able to please assist me further with getting this working?

I have changed the tag from @tunnel to @proxy and can now see activity on the gateway, but I don’t really know what it should be saying / what I should be looking for? To diagnose where it’s failing the connection as still getting the same on the TV?

I’m tempted to purchase a show 5 as there on offer, but don’t want to waste money if it’s still not going to work.

Any further help would be really appreciated. Does @Monocle no longer participate in support?

Thanks

Thanks, I will try again if we ever get one of the physical devices. Hugh

I have blueiris as well. Unfortunately as it stands it isn’t supported. I did reach out to the developer of Blue Iris. He said this is his top priority so expect it in the next couple of months he said

@TexasBill

Just a screenshot of the error you were getting.

If you have the Monocle Gateway installed locally and your camera tagged (@tunnel) to use the gateway, you can copy the log data to this post and I can review it for any errors. Make sure to include the part of the log that includes the startup messages as well as the period of time that covers you asking Alexa for the camera feed.

I just thought of one more technical item that Google WIFI could be blocking (if you are using the Monocle Gateway software). DNS Rebinding, please see: https://monoclecam.com/monocle-gateway/troubleshooting/dns-rebinding

Thanks, Robert

@fusswolf Still cant get it working :-( I tried installing the gateway on another machine and get the same issue.

@Monocle Thanks for the heads up. I’ll take a look.

OK and finally @proxy-tcp, @noaudio , seems same as without noaudio. Seems that the Echo show is sending the OPTIONS request and I think the ESP RTSP protocol i’m using isn’t responding? I’m using this code for the ESP32, hevn’t looked through the code in depth so don’t know how it is supposed to handle the request.
https://github.com/bnbe-club/rtsp-video-streamer-diy-14
link text
image_2020-12-01_213802.png

I am also facing this issue.

@Sammy

The Emby server is doing some transcoding on the feeds. So hopefully your Emby server has enough muscle to get the job done. I have not tested on any small devices such as the RaspberryPi or other ARM based systems. I installed Emby server on an Intel i7 NUC for testing. So it does have hardware acceleration support enabled.

Thanks, Robert

@kwijibo00

Nope, same issue running on a different system, (Windows 10). Same error

Cannot read property ‘match’ of null’