Unifi Camera Update! (Fix Available for Testing Now)

Monocle

Can you post the log info from Monocle Gateway after requesting the camera stream from Alexa?

Thanks, Robert

Monocle

I have not had a chance to test v0.0.6 on Windows yet but can you try re-installing the VC++ runtime dependencies – maybe thats the issue?

https://www.microsoft.com/en-us/download/details.aspx?id=26999

Thanks, Robert

bk

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

@bk

I have not had a chance to test v0.0.6 on Windows yet but can you try re-installing the VC++ runtime dependencies – maybe thats the issue?

https://www.microsoft.com/en-us/download/details.aspx?id=26999

Thanks, Robert

Thanks Robert. So downloaded it again, ran the install. And gave it a try.
Results, the exact same symptoms. The 0.6 beta does the same thing : from the batch freezes at the command line where the monocle-gateway.exe is called.
If I go into windows file manager, and double click on the monocle-gateway.exe, get the same warning window.

If I put the OG (V 0.0.4)files back on, it all runs , from the batch or from double clicking on the monocle-gateway.exe.

mp101

Thank you!!
Will you update the docker image once testing is finished?

bk

This post is deleted!

Monocle

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

the docker image once testing is finished?

Docker image for v0.0.6 has been published.
https://hub.docker.com/repository/docker/monoclecam/monocle-gateway

A new version v0.0.7 will be coming in the weeks ahead.

Thanks, Robert

Monocle

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

…
Results, the exact same symptoms. The 0.6 beta does the same thing : from the batch freezes at the command line where the monocle-gateway.exe is called.
If I go into windows file manager, and double click on the monocle-gateway.exe, get the same warning window.

I have been working on tracking down this issue and it appears this is related to Windows 7 and its end of life. The underlying runtime and some dependencies have discontinued support for Windows 7.

Are you running Monocle Gateway on Windows 7?

I’ll PM you something to try, but we may need to drop support for Windows 7 due to lack of support from the underlying tools and frameworks.

Thanks, Robert

bk

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

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

…
Results, the exact same symptoms. The 0.6 beta does the same thing : from the batch freezes at the command line where the monocle-gateway.exe is called.
If I go into windows file manager, and double click on the monocle-gateway.exe, get the same warning window.

I have been working on tracking down this issue and it appears this is related to Windows 7 and its end of life. The underlying runtime and some dependencies have discontinued support for Windows 7.

Are you running Monocle Gateway on Windows 7?

I’ll PM you something to try, but we may need to drop support for Windows 7 due to lack of support from the underlying tools and frameworks.

Thanks, Robert

Yup running Win7 on Monocle.

Richie

This is working for me with G3 instant, G4 Bullet & Pro cameras. It also fixed the problem I had with the latest Echo Show 10 that I posted in this forum HERE.
Thank you very much @Monocle!

JHoover

Hi Robert -
I’m experiencing the same issue all on this string have experienced since updating Unifi protect to Version 2.x.x on my UDM Pro. I am not as savvy with Linux/ raspberry pi and so to date I’ve just used the monocle web portal directly to my Alexa account with an Echo Show 10. IE, I haven’t been using any hardware gateway and it was working great…but no longer.
Per the monocle website it seems like the gateway is just needed for some fire TV devices, certain cameras and increased security desires right?

Is there a fix for the (non-gateway) web-portal-only setup or will I be forced to figure this out with a gateway going forward?

Thanks -

Jeff

vmsman

@JHoover Jeff, you really do need the gateway for many of the cameras on the market. My channel is devoted to most things hosted and I too use Unifi Protect v2.x on my UDM Pro. Drop by my chat at https://chat.scottibyte.com/ and I may be able to answer some of your gateway questions more simply.

JHoover

@Monocle
I forgot to direct this question directly to you Robert. Any plans to make this fix on the web portal (no gateway) scenario?
Thanks -

Jeff

JHoover

@JHoover , @vmsman
I spent some time and figured out how and what (stable) version to downgrade my Unifi Protect firmware back via SSH. I was able to downgrade to 1.19.2. Anything in the 1.20.x put the downgrade into a boot loop. 1.19.2 is relatively new and stable and still allows protect to work with Alexa through the Monocle web platform (no gateway required).

@Monocle, please let us know if you end up writing a fix for the web based Monocle platform for the 2.x.x protect.
Thanks!

Jeff

monome

@JHoover how old is your Alexa? Gateway is required with the newer Alexas to provide the rtsp stream via https port and a valid certificate, something unifi cannot currently do.

vmsman

@JHoover With the new Monocle Gateway beta, you will be able to run the latest Unifi Protect 2.x just fine with your cameras. The web portal cannot accomplish the data conversion. That has to be done on the customer local network. If you need further help, contact me at https://chat.scottibyte.com/. The version of your Amazon Echo device has nothing to do with getting this working. I can voice command an original version 1 cylindrical Amazon Echo to display my G3 Instant camera on my Fire Stick to my TV and it works fine.

mp101

@Monocle
Thanks so much, confirm working on 1080p,

Thanks again

JHoover

@monome
I have an Echo Show 10 2nd generation. The unifi protect firmware downgrade made it work so I can voice command into my (2) G3 Flex Cameras and (3) G4 Bullet cameras with audio and video. These are just for my house and so I’m fine running an older version of the firmware.

Jeff

GreggC

@Monocle @bk I’m also running Win7 on the machine I use for Monocle and ran into error “The procedure entry point GetHostNameW could not be located in the dynamic link library W32_32.dll”.

The function was introduced in Windows 8.
https://docs.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-gethostnamew

Is Monocle Gateway on Win7 in fact a dead-end now?

GreggC

@Monocle In general, v0.0.6 works like a champ! I moved to a RaspberryPi from Win7, and am using RTSP streams and @fixaudio. Video and audio streams are working on Echo Spot, FireStick and FireTV.

The only camera that it’s not working with is an AI-360. Although the native fisheye view (non de-warped) is not that useful with Alexa anyway (imho), I think it was working previously. It starts to launch, but the following are displayed in the gateway log:

RTSP ENDPOINT PLAYING MEDIA STREAM
RTSP ENDPOINT SOCKET CLOSED
RTSP ENDPOINT SOCKET CLOSED
RTSP CLIENT SOCKET CLOSED
RTSP CLIENT DETACHED FROM STREAM

I’m really not worried about having the AI-360 fixed and haven’t spent any time tinkering with it, but am just reporting the issue.

I’m very happy to have Monocle working again with regular UniFi cameras.

Robert, thank you very much!

GreggC

@GreggC Actually, the AI-360 is working fine. The problem was a mismatch in supported resolutions.

I couldn’t get the high-quality stream (1920x1920) to work at all on my devices.

Medium-quality (1280x1280) works on Echo Show but not on my 720P FireTV or FireStick devices.

The low-quality stream (640:640) works all around. There is no 640640 setting within Monocle’s Video Resolution field, but I left it at 19201920 and it works fine.

This turns out to be more useful than I remembered, especially on the round screen of an Echo Spot!