Unifi Camera Update! (Fix Available for Testing Now)

Monocle

…
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

mjd

@Monocle

I just updated to the latest beta 0.0.6 version and it works! Using the @tunnel, @fixaudio tags. Thank you so much for your work on this! So glad to have Unifi cameras working with Echo’s again after the Unifi Protect 2.0 update.

vmsman

@Monocle Bad me. I had assumed that the fix was on the website. I have now updated my Monocle Gateway to the 0.6 beta version. I installed the DEB package and verified that the service is up and running with a sudo systemctl status monocle-gateway. I uninstalled the 0.0.4 gateway with the uninstall script prior to installing 0.6.

None of my cameras work now. Unifi or otherwise. The token is still located in /etc/monocle/monocle.token. Has this changed?

antoun22

Hi Robert

Fantastic news, thank you so much for your work!!

Monocle

@vmsman

No, nothing changed related to token. It certainly should not have broken existing working cameras. Can you post a copy of the log at the service is started and making a single camera request?

Thanks, Robert

vmsman

@Monocle I had to restart the service a second time and now it is up and humming. Hey, look at my posting regarding my Reolink RLC-820A 4k camera. After a year, I have not had anyone suggest a solution to it not working. With the new beta of Monocle Gateway both of my G3 Instant cameras on Unifi Protect are now working great on my Echo Show 10’s and my Fire TV 4k max.

Andreas912

Works fine again, tested with G4 Pro and G3 Bullet. Thank you so much!

What is not working (but that is no new issue, that also didn’t work before):

3840x2160 stream from G4 Pro (tested on Echo Show 8)

The other streams

1280x720 from G4 Pro
640x360 from G4 Pro
1920x1080 from G3 Bullet
work fine.

stev

So happy to have my cams back on my Echo devices!

New building working well so far this evening.

Thank you!

Monocle Gateway on a Raspberry Pi 4
Protect 2.1.2 running on a UNVR
G4 Doorbell
2x G3 Instants
Echo Show 5
Echo Show 10 (3rd gen)

bk

Finally found this thread.
Running a Win7 machine.
Have been running monocle from a batch file, the night I got it working, it worked , left it alone.
Easy to stop and restart when there’s an issue.

So downloaded the beta file "monocle-gateway-windows-x64-v0.0.6.zip "
Replaced the 3 files.
When I attempted to start if from my batch file, it just stops at the monocle directory where the call is made to start monocle-gateway.exe.

If double click on monocle-gateway.exe from the 0.6 beta, via the win explorer (which I could do with the older version and it fired up), I get…

Input appreciated…
TIA.

bk

@Monocle

sorry for the dup, can’t delete the OG.

Finally found this thread.
Running a Win7 machine.
Have been running monocle from a batch file, since the night I got it working, it worked , left it alone.
Easy to stop and restart when there’s an issue from the batch files.

So downloaded the beta file "monocle-gateway-windows-x64-v0.0.6.zip "
Replaced the 3 files.
When I attempted to start if from my batch file, it just stops at the monocle directory where the call is made to start monocle-gateway.exe.

If double click on monocle-gateway.exe from the 0.6 beta, via the win explorer (which I could do with the older version and it fired up), I get…

Input appreciated…
TIA.

cory_booth

Confirming fix on my end:

Unifi Protect running on Cloudkey Plus.
Cameras = G3 Flex

Upgraded my Rasberry PI install:
Stopped Service
Downloaded Beta .6
Unzipped Beta .6
Started Service

Changed my Unifi RTSPS URL to RTSP and removed the ?enableSrtp

Ensured my resolution was set to “max” (1920x1080) on both RTSP feed and the camera configuration

Added tags: @noaudio, @tunnel

Cameras working

Echo Spot
Echo Show 5 (1st Gen)

vmsman

@cory_booth Sounds about right. If you are still having an issue, drop by the Ubiquiti-Unifi channel on https://chat.scottibyte.com/ and I can see if I can help.

Monocle

@bk said in Unifi Camera Update! (Fix Available for Testing Now):

@Monocle

When I attempted to start if from my batch file, it just stops at the monocle directory where the call is made to start monocle-gateway.exe.

If double click on monocle-gateway.exe from the 0.6 beta, via the win explorer (which I could do with the older version and it fired up), I get…

This seems like something did not compile correctly on the Windows build.
Let me try testing it here and I may need to rebuild it and send you another build to try out.

Thanks, Robert