@Monocle said in Cannot get Echo Show 5 working with Foscam FI9821P V3:

Glad you got it working. I have not experienced the “I could find any enabled video skills that can find that." issue and I don’t remember anyone reporting that. If you Alexa device setup for multiple profiles? I do know that if you change provides on Alexa, you may be an on account that is not associated with your Monocle linked skill.

Io ho il modello FI9816P e avevo lo stesso problema (400 bad request) e ho risolto con @proxy al posto di @tunnel. Non è stato necessario il tag @noaudio e in questo modio l’audio si sente perfettamente su echo show 5. (Paolo)

@Monocle I still have to re-boot my camera every day, this happened all of a sudden after it was working fine for days, anyone have any ideas what I can try? I have tried re-installing firmware and downgrading it. I have also deleted the device from Monocle and re-entered it. I would set my camera up for a daily re-boot but I don’t believe it has that ability.

I found a workaround, but this is obviously a problem. The workaround was to disable and re-enable the skill re-linking the account (I had made no changes to my account or login). Upon re-enabling and signing in to monocle account, it did a new discovery which found the 2 additional cameras.

Based on priobe’s comments I thought I had an “ah-ha” moment - perhaps only 1 of my 6 cameras would work with Monocle when connected through the DVR as priobe mentioned. I was only testing with one camera.

So, I went through and added my 5 other cameras. Then I attempted to call them up through Alexa one by one, hoping that I would hit on the one camera that CAN be seen through the DVR using Monocle.

Alas, none of them work.

So next question. My home network is on the 10.10.10.XXX space. This includes the DVR. The IP cameras themselves are on a private network within the DVR and have the 192.168.254.XXX space. I know I can change the IP address of each camera within the DVR interface. Is it possible - WITHOUT BREAKING OTHER THINGS - to assign each camera to the 10.10.10.XXX network space behind my router / firewall to see if then I can address each camera individually within Monocle as opposed to the DVR??

Please advise.

That did it. Thank you very much.

@socalgman

Sorry for the delay, I have been away for a couple of weeks.

In all cases in the log, the gateway attempts to use BASIC authentication to access the RTSP stream on the camera and perform a DESCRIBE request. In all cases the camera immediately terminates the TCP/RTSP connection from the gateway. So there is something the camera does not like about the request. It should at least return an error code for invalid requests or invalid authentication attempts, but it’s just terminating the TCP socket with no response. Very odd.

If this is a camera stream that you can temporarily make available to me over the Internet for testing, I can perform some additional tests to see if there is any workaround. You can PM me the connection details and a temporary view-only access credentials.

Thanks, Robert

@MegaMatze

Sorry for the delay, I have been out of the office for a couple of weeks.

Thanks for the log. It’s telling us that the gateway is configured properly and it’s properly receiving the Alexa camera requests from the Monocle servers.

What is missing is immediately after the “INITIALIZE RTSP STREAM” block, we should see incoming TCP requests from the Echo device into the gateway and recorded in the log.

This issue usually comes down to some networking related problem. The Echo device is not communicating with the Monocle Gateway for some reason.

(1) . Is the Echo device on the same network as the Monocle Gateway. (i.e. not on a guest network or VLAN)

(2) Make sure the computer running the Monocle Gateway does not have a firewall blocking access to port 443. Make sure this computer does not already have some other service already using port 443 (Apache web server/ NGINX, etc) . You can restart Monocle Gateway and look at the log that captures the startup info to make sure it’s successfully binding to port 443.

(3) DNS REBINDING. https://monoclecam.com/monocle-gateway/troubleshooting/dns-rebinding

@nmpuk

Sorry for the delay, I have been out of the office for the past couple of weeks.

I have not experienced an issue where Alexa says “Camera is not supported on this version of Fire TV” before. The first step is to check your Monocle web portal and look for the Camera Feed History" button/icon.

5240cb58-f638-4f97-96e5-9e436da70409-image.png

A popup window should appear. It should list each request we received from Alexa and each response we provide to Alexa. Any camera request for this named camera should appear in this list. If it’s empty, then we are not receiving camera requests from Alexa for some reason. In the past issues like this had to be resolved by the Alexa customer support team.

You could try removing the camera from your Alexa app, rename the camera in Monocle and then remove and re-add the Monocle app and re-link your account. Then try it once more.

Thanks, Robert

@whtdrgn

FYI … Just reviewed and responded to that thread.

Thanks, Robert

@Spider03

Glad you were able to solve this issue :-) .

Thanks, Robert

@whtdrgn

Honestly, I’m a little surprised that it was that simple. However, I’ll take any win that gets it working!

Thanks, Robert

How To Install Monocle Gateway on a Synology NAS as a Docker Container

How To Install Monocle Gateway on a Synology NAS as a Docker Container
Article:
https://monoclecam.com/monocle-gateway/install/synology

@CoreyMac

Glad to hear that was the only issue :-)

@Lewis6643

Yes the Monocle Gateway needs to be running 24x7 or at least whenever you would expect to use Alexa to view a camera stream.

For simplicity it should be running inside your local network. The gateway will need direct access to each of your camera streams. Additionally each Alexa device will require direct access to port 443 of the gateway. You could run this on a hosted server; however, it would need inbound access to each camera stream on your local/private network as well as port 443 exposed for the Alexa devices to access it. Some additional custom configuration properties may also be needed to override the detected IP address and use your public IP to this hosted server as well.

I would suggest getting it working first locally, and then we can experiment moving it outside the local network if needed.

Thanks, Robert

Thanks for the notification, yes the API service was down … but it should be back up now.

Thanks, Robert

@pc1246

I would delete (or archive) any old files and start fresh. The most critical part is getting the network settings correct for your network.

Thanks, Robert

@schmorgs

Google DNS servers should resolve the hostname … maybe they were slow to update/synchronize at the time you were using it?
I just tested using nslookup on my unique mproxy hostname on both 8.8.8.8 and 8.8.4.4 (Google DNS servers) and it resolved just fine.

For Reolink cameras, make sure the “manufacturer” property on the camera config in the Monocle web portal is set to “Reolink”. Also as you probably already know, the tag @tunnel should also be applied to that camera.

Feel free to post the request info from your monocle gateway log here while attempting to ask Alexa for your camera stream. Maybe we can spot something obvious.

Thanks, Robert

@Dayhunter, @wolfe4656

This change is now in place. You can edit your camera feed in the web portal and remove port 554 and save the camera entry. It should no longer force the default port in the URL if it is omitted in the string.

However, there is one caveat … the existing version of Monocle Gateway does not play nice with the RTSP URL string with no defined port number. So we have made additional changes to force the default RTSP port number back into the URL string if sending this URL to a Monocle Gateway instance. Please note, the camera entry is not altered, but the URL will be updated at runtime when sending to an existing version of the gateway. We have also thus made updates to the gateway software to handle this case where a default RTSP port may not be defined. So new versions of the gateway will handle this condition and the server will send the un-altered RTSP URL to new versions of Monocle Gateway. If you are using Monocle Gateway to test this change, you will need an updated version. I can provide an experimental version upon request, just let me know what platform you are running it on.

Thanks, Robert

@ALEDOTECH

Glad to hear you were able to resolve the issue. A static IP is not required but is preferable. The IP address of the gateway is used to map the custom DNS hostname for your gateway and if it does change, the DNS update/sync may take some time. Alexa devices in particular seem to cache old DNS lookups for some time. Sometimes rebooting the Alexa device is needed to flush its DNS cache. So a static IP is better just to avoid that issue.

Thanks, Robert