Unifi Camera Update! (Fix Available for Testing Now)

Toto

@Monocle
i ´ve updated my System Linux-x64 and try with @noaudio or @fixaudio
but always camera is´nt responding…Echo Show8

Start Server again , same thing…

deepbluesee

@Monocle
I upgraded too with my Unifi Cams and it work very well with the last Protect update (2.1.2)!
I used @tunnel an @fixaudio
I use a UDMPRO and 3x G3Pro and 1xG4 Doorbell
And I use 3x Echo Show 5 and 8

Toto

@deepbluesee

ok, my fault…

need to set " , " between the tags…did´nt know

deepbluesee

@Toto
Ok I used one character distance between

Monocle

@deepbluesee

Thanks for the confirmation report! Glad to hear its working for you!

vmsman

@Monocle I used the @fixaudio and @tunnel and I have Unifi Protect 2.1.2 with G3 Instant cameras and I am unable to display on Echo Shows or Fire TV 4k Max. Both of which worked back with Unifi Protect 2.0.
file:///home/scott/Desktop/Staging/unifi.png

toksvaeth

@Monocle Thank you.

noaudio log (not working)
fixaudio log (working)

Same behaviour with either of rtsp/s.

Looking at a diff between yours and mine, the only major difference seems to be on the a=fmtp line.

vmsman

@toksvaeth So, from your message, does yours work? Also what do you mean by “a=fmtp”? Are you guys using a newer Monocle Gateway code? Is there something that I also need to update on my “@tunnel” local server?

toksvaeth

@toksvaeth @Monocle

Weirdly, switching from the 960 stream to the 1600x1200 stream made @noaudio work. To summarise: All working well for me now. Thank you!

Here’s the log for the working 1600x1200 stream if it helps at all.

toksvaeth

@vmsman I had issues getting it to work with the 960x720 feed and @noaudio, however switching to the 1600x1200 feed made that work fine.

To be clear:

Running the updated test build (0.0.6)
Using the 1600x1200 RTSPS feed from my G4 doorbell (remove ?enableSrtp from the URI)
Using tags: @noaudio, @tunnel, @insecure

RS

@Monocle

Hi Robert

Fantastic news thank you! Working here with 4 x G3Flex and 1xG4 Doorbell.

Only issue as others have said is the 960x720 camera feed from the doorbell, switching to the 1600x1200 works ok.

I know you are not monetising/commercialising the product but do you have a method to donate?

I and I am sure others would gladly donate something for your time and effort!

Thanks again

Monocle

@toksvaeth

I never tried the lower resolution streams. I’ll try one out from my G4 Pro camera soon and see if I can get the same failure.

Thanks, Robert

Monocle

@RS said in Unifi Camera Update!:

…
I know you are not monetising/commercialising the product but do you have a method to donate?

I and I am sure others would gladly donate something for your time and effort!

Thanks again

Yes you can donate here (no obligation):
https://monoclecam.com/donate

The donations received help keep the cloud servers/services and other infrastructure costs paid to continue running this service :-)

Thanks, Robert

navy2x

The beta update works great for my 6 camera setup with @fixaudio. G3 Micros, G4 pro, G4.

pathfinder

After butchering the dockerfile from monocle-gateway-docker to build the 0.6 beta, I can also confirm that the updated code and the addition of the @fixaudio tag works for G3 Flex, G4 Bullet, G4 Doorbell, and G3 Instant. Thanks Robert!

Monocle

@vmsman ,

Scott, are you using the newer (latest test) v0.0.6 Monocle Gateway?

There also seems to be some problem with the 720P streams. I tested yesterday on a G4 Pro camera and the high resolution and low resolution streams worked but for some reason the middle quality which is 720P did not.

Lastly, in your screenshot your camera RTSP URLs seem to be missing the path portion of the URL address? Example: rtsp://10.1.1.1:7447/Aqf2cTyOvd96zDde <-- the Aqf2cTyOvd96zDde part. Of course yours will be unique for each camera.

Thanks, Robert

Monocle

@vmsman said in Unifi Camera Update!:

… Also what do you mean by “a=fmtp”? Are you guys using a newer Monocle Gateway code? Is there something that I also need to update on my “@tunnel” local server?

The a=fmtp is just part of the SDP (stream descriptor) that the camera sends to the viewer. In this case Monocle Gateway is receiving this information and displaying it in the log before sending it to the Alexa device. There is nothing to modify here it was just being noted that there was a difference between the example I posted and what @toksvaeth was seeing on his end. This is normal and can vary between streams and cameras.

You just need tags @tunnel and either @noaudio or @fixaudio on each camera just like what you have in your screenshot. If you use the RTSPS (secure) protocol and port then you may also need the tag @insecure but in your screenshot example, you are not using RTSPS.

Thanks, Robert

Monocle

@toksvaeth said in Unifi Camera Update!:

@vmsman I had issues getting it to work with the 960x720 feed and @noaudio, however switching to the 1600x1200 feed made that work fine.

To be clear:

Running the updated test build (0.0.6)

Using the 1600x1200 RTSPS feed from my G4 doorbell (remove ?enableSrtp from the URI)

Using tags: @noaudio, @tunnel, @insecure

In my case, similar to what you experienced … using a G4 Pro, the Medium (1280x720) resolution does not seem to be working. However the “High (3840x2160)” and “Low (640x360)” stream are working with Alexa.

Not really sure what going wrong with this one. I’ll dig deeper as I have time but at least we have a workaround for now.

Thanks, Robert

Monocle

@navy2x
@pathfinder

Thank you for confirming your success with this test version!

-Robert

Monocle

@RS said in Unifi Camera Update!:

@Monocle

Hi Robert

Fantastic news thank you! Working here with 4 x G3Flex and 1xG4 Doorbell.

Only issue as others have said is the 960x720 camera feed from the doorbell, switching to the 1600x1200 works ok.

@RS,
In my case, similar to what you experienced … using a G4 Pro, the Medium (1280x720) resolution does not seem to be working. However the “High (3840x2160)” and “Low (640x360)” stream are working with Alexa.

Not really sure what going wrong with this one. I’ll dig deeper as I have time but at least we have a workaround for now.

Thanks, Robert