We are working on adding support for Italian region/locale. Please contact us directly if you would like to be a BETA tester -- we will need your email address used with Alexa to add you to the beta group for the Alexa skill. Thanks, Robertit is possible to have this skill in Italian or alternatively publish it on the amazon.it store? thanks
Some IP cameras (many Amcrest, Lorex, Unifi, HikVision, Dahua, etc) work out of the box without needing any intermediate service (proxy/gateway). However, many cameras (including Sercomm, ReoLink, Foscam, D-Link) do need an intermediate gateway for compatibility. Also if you are using any FireTV 4K and newer device, all these require using our Monocle Gateway service. (Monocle Gateway) This service does need to run inside your local network so that no audio/video traffic is routed across the Internet -- it all stays local/private.@Monocle Noob here! Trying to confirm whether there is a requirement to have a service running locally i.e. installing some Monocle software on a computer etc, ? I don't see it there listed on your website under instructions. I've a Monocle account setup and added to alexa etc. I can play the rtsp stream on VLC; but it doesn't work with my echo spot. The response from Alexa 'Hmmm camera isn't responding'. I feel like I'm missing something in the setup. Any help would be appreciated.
P.S. My camera model is Sercomm Icamera2.
Can you verify the RTSP URL coming from BlueIris works first using a tool like VLC? If its working, then try using the @tunnel tag and feel free to forward us a log from Monocle Gateway and we can try to see what's going on/wrong.
This would be an issue on the Alexa side. It's the Alexa device that is refusing the stream with the audio disabled. Monocle is simply a conduit between the IP cameras and Alexa devices. To be fair, I have seen several cameras continue to report an audio channel in the stream descriptor even when the audio feature is disabled on the camera. If this is the case, then that may explain why Alexa is failing, she is expecting an audio stream, but no audio data is actually present in the raw stream data. If you are using the Monocle Gateway service, you can tag you camera with "@noaudio" which will force the Monocle Gateway to strip out the audio channel from the stream descriptor. This seems to work for most cameras with this issue. You can read more about this special tag here: Tagging Cameras for Monocle Gateway | MonocleI have been playing with Monocle and have discovered something that might help a few people get it working. .... It appears that if Monocle doesn't connect to both the video and audio streams it will not play the video and results in a "Camera is not responding" message. I have created a support ticket with the company and reported this. May be something to fix in a future update.
Troubleshooting:Hello, my friends,
I have 4 dahua ip cameras. And dont understand what i’m doing wrong. Please help.
I have fire tv stick 4k.
Monocle provides separate username and password fields for the RTPS URL. We use separate fields because we store the access credentials as encrypted data in the backend. When we send the RTSP URL to Alexa, we send it in the exact same format as you described with the credentials included in the URL.I have one simple question, for my Foscam camera.
The RTSP way to get the camera's streaming is rtsp://usernamewd@IPort/videoMain
But when I set it to Monocle, it gives me the error: RTSP URL should not contain any username or password?
What is the right URL should I input?
Monocle provides separate username and password fields for the RTPS URL. We use separate fields because we store the access credentials as encrypted data in the backend. When we send the RTSP URL to Alexa, we send it in the exact same format as you described with the credentials included in the URL.
Just use those dedicated fields and then your RTPS URL would be:
For Foscam cameras, please see this compatibility note ... you will need to use our Monocle Gateway software/service to get Foscams working:Code:
----------FOSCAM COMPATIBILITY README----------