Unifi Camera Update! (Fix Available for Testing Now)
-
There are some reports of issues with certain resolutions not working which I have with my doorbell, are you able try 1080p from the g4 instead of 720p?
-
Just from my experience (on my setup can’t confirm if this the same for all devices) my show does seem to respect/use the dns server supplied by DHCP and therefore if you host your own DNS server (I use a synology) and are able to “host” the mproxy.io record that the echo devices use (not the gateway pc/device) it can get around the issues with DNS.
Hope this helps
-
@RS Thanks for the suggestion! G4 typically only outputs 3 stream presets 640p, 720p, and 4k. However, I found this link with instructions to enable a 1080p output: https://community.ui.com/questions/UVC-G4-PRO-is-able-to-produce-1080p/a30a8dc4-80c7-4e17-bc5a-6d0c07467689#answer/87194840-96e2-4013-a83f-960f19576f05
This finally fixed my issue!! Thank you so much @RS!!
-
Maybe that changed with newer released or maybe I just remember it wrong. It was several years ago I last attempted testing that. Nevertheless, I do still need to look into any potential DNS issues in the backend servers.
Thanks, Robert
-
!! ATTENTION !!
I was able to track down a problem on the backend with creating new DNS records for
*.mproxy.iodomain names!
I’ll write up a more comprehensive post about it soon, but for now … it should be resolved.This issue would only impact users attempting to use Monocle Gateway and would primarily impact newer users or users that have created a new token recently. I can’t tell for certain but it looks like this issue has been a problem for several weeks.
Feel free to test on your end by restarting your Monocle Gateway and performing a public DNS resolve on your custom assigned
*.mproxy.iodomain name. You can use an online tool like this: https://dnschecker.org/all-dns-records-of-domain.php
It should resolve to your private IP address where your Monocle Gateway is running.Again, the Monocle Gateway should not require you to setup custom DNS resolution on your local network as these records should be created on a public DNS server and propagated publicly. There still can be local DNS resolution problems due to some ISP or local firewall/gateway/router DNS servers blocking local IP address resolution from public DNS records. (See: DNS REBINDING)
More details coming soon, but post back your test results in the meantime.
Thanks, Robert -
Thanks Robert, tested and confirming working using external DNS.
Thanks again for your continued effort in supporting Monocle Gateway
-
No probs, also thanks to the monocle community as they found the issue with some resolutions, not me!
-
I have version 0.0.6 (my Pi install, back when you advised to dump win7 support) , just checked , and my .io dns does resolve to the Pi’s IP … been running great. It’s also been more robust in recovery to when my internet connection drops out.
-
Could someone post the commands needed to update my Monocle Gateway on a RPi from 0.0.4 to 0.0.6? I am a little rusty with Linux. I am having the same issues where Alexa cannot display my Unifi cameras. That function quit about 6 months ago.
-
@Mooose said in Unifi Camera Update! (Fix Available for Testing Now):
Could someone post the commands needed to update my Monocle Gateway on a RPi from 0.0.4 to 0.0.6? I am a little rusty with Linux. I am having the same issues where Alexa cannot display my Unifi cameras. That function quit about 6 months ago.
curl -O https://download.monoclecam.com/monocle-gateway/monocle-gateway-0.0.6-beta/linux/monocle-gateway-linux-raspi-v0.0.6.deb systemctl stop monocle-gateway sudo dpkg -i monocle-gateway-linux-raspi-v0.0.6.deb systemctl status monocle-gateway monocle-gateway --tail -
Anyone else keep getting their posts flagged as spam?
-
When I attempt to connect through the gateway to the camera I get the message that the camera is not responding.
In the gateway i get this 3 times
Anyone have any ideas of what i can do to troubleshoot this?
-
@4th8
Could you let us know a bit more infoWhat version of Gateway are you running?
What device are you running it on?
What cameras do you have?
Has this been working and just stopped or never worked?Thanks
-
@4th8 I had the same problem until I updated to the Gateway Version 0.0.6
-
Sorry I had created a post that had all that information in it but it kept getting flagged as spam for some reason. This is my initial setup. I just got the Alexa for my wife for Christmas.
I am using an alexa show 8.
I have tried both 0.0.4 gateway as well as 0.0.6 (I am on 0.0.6) at this point.
Cameras are ubiquiti g4 pro.’Thanks for the help!
-
@SchmuFoo Thanks for the reply. I am up and running again.
-
@4th8 I don’t have any g4 cameras myself however some users have reported it not working with certain resolutions, however switching on the 1080p resolution as reported below and then using that stream appeared to great round the is issue. Are you able to try?
@HomeTechDad said in Unifi Camera Update! (Fix Available for Testing Now):
@RS Thanks for the suggestion! G4 typically only outputs 3 stream presets 640p, 720p, and 4k. However, I found this link with instructions to enable a 1080p output: https://community.ui.com/questions/UVC-G4-PRO-is-able-to-produce-1080p/a30a8dc4-80c7-4e17-bc5a-6d0c07467689#answer/87194840-96e2-4013-a83f-960f19576f05
This finally fixed my issue!! Thank you so much @RS!!
-
@4th8 Also you do need to be on version 0.0.6 for ubiquity cameras as their latest update changed the format of some of the video streams
-
@RS Your awesome! That seems to have worked. At least without audio.
Now i just need to figure out if i can get audio to work
-
For the next person trying to do this…
To get a Unifi G4 Pro camera to work.
- Use the tags @fixaudio and @tunnel.
- Set the audio codec to G711
- Set the video quality to 1080p
- Within the camera itself turn on high frame rate mode
Camera > recording > recording quality > toggle high frame rate mode.
Just got it working! Thanks everyone for the help!
