@chadsturgill

Hi Chad,

I also received your support request via our support ticket system and am following up there.
Once we find a solution, we should also post back here for other potential future readers.

Thanks, Robert

@vmsman our the man. i can’t say for sure 100% but i think i have it going. for some reason it did not like the ports i was using so i just guessed and used ports around the area the nvr was set at and now i see both camera at home and away. hip hip hurray! your help was good. i did not use most of it but not to worry any ideas people offer prompts more thought and ideas. and that is what it did for me. thanks much for all the suggestions given they gave me ideas. if for some reason it stops i will visit this again and see if anyone has more ideas. again thanks much.

@3blake7 said in Honic HN-4KA:

I also tried the modified live555proxyserver from: https://monoclecam.com/support/incompatible

We are now suggesting users try this service instead of the Live555 RTPS proxy server. Its still in BETA, but is stable at this point: https://monoclecam.com/monocle-gateway

I also compiled my own live555proxyserver from latest source code. The one I compiled had issues with OutPacketBuffer::maxSize being exceeded, so I guess that’s why monoclecam team compiled their own version?

Correct, among a few other minor changes. Our sources are here for those changes:
https://github.com/MonocleCam/monocle-proxy/tree/mods

when using ffmpeg I did run into an issue with audio. the audio uses pcm_mulaw. not sure if that matters, it’s just something different than the cameras i have working.

PCM (m/u)Law is the G711 codec which Alexa claims to support. As you have experienced, Alexa seems to struggle with certain cameras and implementations of this audio stream.

I enabled audio and selected G711U and it started working! I still have to use the RTSP proxy though. Doesn’t work without it.

This camera doesn’t have a microphone, so I guess enabling the microphone changes a flag on the rtsp stream command or something. Maybe that is your unknown issue with some cameras?

Some cameras will describe/include the audio channel in the stream even if there is no hardware to support the audio. This does seem to cause issues with Alexa devices. Often disabling the audio in the camera’s setting will help this situation but not in all cases. Here are additional tips. https://forum.monoclecam.com/topic/45/help-my-camera-stream-is-not-working-on-alexa

I know you have it working, but it may also work using our Monocle Gateway service with the “@tunnel, @noaudio” tags will will strip the audio channel from the stream.

Using a univision DVR here and the way I found is the internal POE switch will only act as it’s own seperate private network. the NVR however provides a URL for RTSP streaming with channel and stream parameters… so you can use the http://192.168.x.x:554/chX/sX format (that’s an example…but your NVR should provide the format) to add the streams for each camera to monocle

Update: I got the Phylink cameras to work using the gateway on a raspberryPi. This was needed in order to use digest authentication. If I used basic then I don’t need the gateway.

Glad to see you guys were able to find working solutions.

Thanks, Robert

@peted

Glad to hear you have made some progress.

I’ve never tested a LG TV with Alexa before, only the Toshiba FireTV Edition.

However, based on the log it appears that the TV is never attempting to establish a TCP/RTSP connection with the monocle gateway server. The gateway is receiving the camera request from the Monocle servers and thus from the Alexa Cloud and the gateway is setting up the RTSP proxy for the stream, but the Alexa enabled TV should then attempt to make a TCP connection to the local gateway service and this appears to be missing. So the first question is … is the Alexa TV connected to the same WiFi network and not a Guest network or some other VLAN? You may also need to try restarting the TV, unplug and reboot – to flush any old DNS cached entries just in case. Beyond this, I’m not sure what the issue would be. The TV needs to make a local connection to the gateway just like your other FireTV (4K Stick). So its most likely a networking issue … that or the TV may not support Alexa smart home cameras? You may check with LG or Amazon to make sure this TV model is supported.

Thanks, Robert

@Jouster-74 said in UCAM247 Cameras:

Just to add to this topic, you can also just use the following in your DNSMasq options to include all potential subdomains from the primary/base domain we use for the gateway.

rebind-domain-ok=/mproxy.io/

The explicit FQDN (fully-qualified) domain is perhaps a bit more “secure”, but in the event you replace your Monocle API token used with Monocle Gateway, you will also need to remember to update your DNSMasq options.

Either one should work, its entirely up to you!

Thanks, Robert

@Jouster-74

Thanks for posting that the issue is resolved.

@Monocle That didn’t seem to help. Is there a contact email I can send connection details too, Don’t really wanna post it here. I have about a dozen customers that would have Geovision Equipment, so they would love to have this feature, if its a easy fix.

Have you tried the EZVIZ Alexa skill? I recently installed a CTQ3W outdoor wireless camera and can stream to Echo Show.

Okay, IAM a little bit forward,
There is no change if I restart the Raspberry where is running the Monocle-gateway, Alexa can still not connect to the Camera but if I Restart the service with

monocle-gateway --restart

After this I can connect the camera with Alexa.

But why I must restart the service after rebooting the Raspberry?

Danny, You don’t have enough information about what you have tried. It isn’t specifically mentioned on Monocle that that camera is supported. That doesn’t matter as much as you have to have the gateway for access from the show 5. Have you installed the Gateway? Can you get RSTP feeds? I have looked at the iegeek website and this is from their VLC manual. d72698a7-24bd-44cc-97ca-ad81c3d043a6-image.png

Reply to myself : works with tags@proxy (because sound was previously removed from camera settings)