@Monocle is there any update on this? I know others cameras can do this like blink.

@griceluke I had the same issue with Monocle unfortunately. I passed the camera feeds through Frigate and used the restreamed feed from there to feed through to Alexa rather than direct from camera.

Otherwise, you could try using ONVIF Device Manager to absolutely confirm the url and if you have 2 streams or more available, start by trying to view the lowest res stream first on the Alexa device.

I did run into a camera that I could not get to work in Monovle no matter what I did. I ended up after WAY to many hours of trying to solve it, moving to Scrypted. That also works with Alexa. Good luck!

@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.

@calumartin So after a month of troubleshooting and being a bit of a numpty I’ve narrowed my issue down to Vodafone blocking dns rebinding on their routers with no way of turning it off whatsoever.
I recently moved to their Pro2 fibre 900 plan with all the bells and whistles including a VoIP landline, which if I wanted to, I could trade for using my own router but unfortunately, I still use my landline daily.
With what I’ve seen on the patchiness of the show 5 gen3’s working at all I’m gonna wait to see if they get supported better before I get a seperate line run for my landline.
Its a shame because I went for the pro package as I thought there might be more functionality.

@ferrellsl Thanks for the tip. I did have it at 1080p because I thought the Echo Show 5 (I accidentally put 4 in my original post) supported it. However, I did change the camera to 720p and it didn’t fix the issue. I’ve tried everything I can think of. So frustrating.

@brianjd My experience with Monocle has been that it always tends to work perfectly with the Echo Show 10 and not with the 5 or 8.

I have a video on this subject. Hopefully this will help:

If that doesn’t help, join my chat at:
https://chat.scottibyte.com/

@hakkai94 said in Interesting find.......DNS options:

Hello,
I have the same error. Perhaps the problem is that I use my Synology as DNS Server ? Did you solve this problem ?
Thanks

I solved this problem by forcing DNS servers in my docker-compose.yml file :

version: '2' services: monocle-gateway: container_name: monocle-gateway hostname: monocle-gateway image: monoclecam/monocle-gateway restart: always volumes: - /volume1/monocle:/etc/monocle dns: - 1.1.1.1 - 1.0.0.1 networks: monocle-gateway-network: ipv4_address: 192.168.1.114 networks: monocle-gateway-network: driver: macvlan driver_opts: parent: ovs_eth0 ipam: config: - subnet: 192.168.1.0/24 gateway: 192.168.1.1

@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.

@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!

@yvm_22 I also wanted to add that I tried using all the tags suggested on monoclecam.com troubleshooting session.
I used the following tag combinations, but to no avail.

@tunnel
@tunnel, @noaudio
@proxy
@proxy, @noaudio

@arthur360

Hi what cameras are you using?
How are you adding the cameras to the monocle web interface (direct to the camera or through the DVR)?

Can you post more of your log? (The part with io.proxy address)

Hopefully we can help

@vmsman
Thanks again, great job! The video is very helpful to me, I will try to implement your solution.