@ymurawski said in UniFi Cams dont work with Alexa:

Hi, i have several Unifi cams and the Unifi Protect app running.

i activated rtsp and edit the link to use it with rtsp and not rtsps
e.g rtsp://192.168.1.1:7447/ZGoIJw4x5h52MWoj

I added this cam to the Online Portal https://portal.monoclecam.com/ and then connected it to Amazon with the monocam skill.

But when i try to view it on my Echo it wont work and says that the camera can not be acessed.

Any ideas ?

i forgot…VLC just works perfectly :)

On the new server, I deleted the new token and installed the one from the prior server, and DNS worked. I conclude that there is a problem with DNS registrations for new tokens.

@Monocle said in Camera Not Working:

@bdydrp

Is the Hikvision set to the H.264 codec? Some newer cameras now ship using H.265 by default and Alexa devices do not yet support H.265.

I forgot one other tag combination you can try.

Try @proxy-tcp instead of @tunnel. Also add @noaudio … if I recall correctly I think several Hikvision cameras had audio streaming issues with Alexa, at least some of the older ones.

Thanks, Robert

Thanks, i will give those a try!

AFAIK, the hikvision is set to H.256, but ill double check.
Nothing has changed settings wise in the hikvision, so definitely something has changed on amazons end

@Monocle said in Pi3b+ VS Pi4 for monocle (or a chromebook OS):

@bk said in Pi3b+ VS Pi4 for monocle (or a chromebook OS):

That died this weekend, so I’ll be getting a Pi4 8g to replace that old little Win7 brick.

The Rpi4B is a great little SBC!
The official price for the 8GB (barebones) model is $75 USD. Anyone charging more than that is taking advantage of limited availability due to global supply chain issues.

The Pi400 is also a neat package where it’s basically a Pi4B built into a keyboard shell. Although I’m not sure its available in an 8GB RAM config.

And they all are to some extent… sux. But a workstation is down. So…
yea, bought a Pi4 8g kit from canakit… only place I could get Pi4 8g kit, which was the same price as just the board on amazon. eeek$ either way. Kit s/b 100-130 tops. I looked at the Pi400, big thing, at the bench I prefer wireless K&M, easier to turn 'em off an put them aside when needing space. The logitech K360 and 510 mouse on a unify dongle (already paired from use on the Win7 brick thin client) worked flawlessly on start up of the Pi3 . Since now the Pi3 is headless and VNC /SSH access, that K&M will go with the Pi4 station.

When the Pi’s get back to normal pricing (if ever), I plan on getting a few more for a few other projects I had in mind as the Pi3B+ was collecting dust, but never broke the box open for.

@krattner said in Echo Show 10 3rd gen:

I’m curious if anyone has gotten an Echo Show 10 3rd Gen to show the camera feeds. I just ordered the Echo Show 15 and it doesn’t work with that either, but my older shows 5 and 8 2nd gen do work. I’ve read Amazon claim it’s not their problem and this issue may be due to a SSL tunneling requirement. Any new directions would be helpful. Using Amcrest cameras.

I have not tested with the Echo Show 15 but I did briefly have an Echo Show 10 3rd Gen and reported my success in this thread where I list the camera I tested with. I have seen at least one report of success on the 15, but with a Unifi camera. I would suggest that whatever device you get, just make sure to test within the free return window :-)

I you are not currently using the Monocle Gateway (https://monoclecam.com/gateway) software, I suspect that is probably the issue. All newer Alexa devices seem to require using Monocle Gateway (due to more stringent security and protocols.)

Thanks, Robert

@Monocle I have and Thank YOU Robert. Grabbing image as I write this
D

@Monocle Thank YOU Robert - we really appreciate it.

D

@vmsman said in Reolink RLC-820A Not working on Monocole Gateway:

Does it help you that these other three programs handled /h264Preview_01_main and worked with this camera?

Not really … (unfortunately)
The hardware is probably capable of playing the stream … it’s the viewer software that must support the H265 codec. The URL signature /h264Preview_01_mai really does not matter … it’s the data returned in the SDP (stream descriptor) that is telling the player to use the H.265 codec. Specifically this line:

a=rtpmap:96 H265/90000

I only noticed a single video stream (#96) and single audio stream (#97) in the log data you posted above. It’s telling the viewing software the stream supports H.265 for video and AAC audio.

Unfortunately Amazon has not added support for any newer video codecs since H.264 for Alexa camera streaming. See https://developer.amazon.com/en-US/docs/alexa/device-apis/alexa-camerastreamcontroller.html#supported-video

You could try using the @fakefmtp tag … but I seriously doubt it will work.

The only thing I can think of suggesting is to have some other software (like FFMPEG/FFSERVER) ingest the H.265 stream and re-encode (transcode) it and output it via H.264. Clearly this will add latency and is a somewhat ugly solution. Other users have mentioned using SCRYPTED for their Unifi cameras. I have not tried it out yet, but I think it may be using FFMGEG under the hood to transcode the stream.

Thanks, Robert

Would you need the @tunnel tag?

Will try take a look this week 👍

Please see this thread for a test version available to address the Unifi camera issues:
https://forum.monoclecam.com/topic/1242/unifi-camera-update-fix-available-for-testing-now/14?_=1659280156800

Thanks, Robert