Upcoming Maintenance Alert:

The UBNT Community will be upgraded at 5pm MDT on April 25th. During this time the community forums will be set to read-only status.

Learn more

×
Reply
Highlighted
New Member
Posts: 2
Registered: ‎10-12-2017

Potentially Problematic G3 Camera Batch (5 pack)

[ Edited ]

Hello,

 

First time posting on here, as this is the first time I ran into problems with Ubiquiti's Unifi Video series of products. I have been more than happy so far.

 

I have a brand new batch of G3 Bullets, and 2 out of 5 of the cameras appear to have issues I cannot solve.

 

I have tested with two NVRs (one as a VM under ESXI, one an older workstation for testing), two UBNT PoE Edgeswitches, and multiple patch cables for testing.

NVR1: Dual E5-2683 V4, 256GB ECC DDR4, RAID 10 32TB  on PERC H830 - Running Ubuntu Server x64

NVR2: E3-1220 V3, 8GB ECC DDR3 - Running Windows 10 Pro x64

 

Both NVRs are running latest 3.8.1 software.

 

PoE1: ES-24-250W - latest 1.7.1 firmware

PoE2: ES-16-150W - latest 1.7.1 firmware

First Camera (Unifi G3 Bullet Firmware 3.8.3):

 

This is one odd-behaving camera. I noticed immediately after install while spotting, the preview image with the Unifi Video app would display a grey dummy JPG, even though the stream worked. What I am noticing is that the camera is disconnecting from the NVR after a few hours, and will not come back until the camera itself is rebooted. Restarting the NVR does not help.  I have also re-flashed freshly downloaded 3.8.3 firmware to the camera, which did not help. This camera behaves this way on both the production Ubuntu NVR VM and the test Windows 10 box, and it does not matter which switch or port powers it.

 

What is even more bewildering, is upon logging into the camera after it disconnects, it displays _UNINITIALIZED_ in the "Name" and "Administrator Username" fields. Rebooting the camera, it comes back to the proper settings I set upon install, only to eventually go back to saying "_UNINITIALIZED_" after a few hours and disconnecting. Oddly, I have also caught this camera cycling it's cut filter/infrared continuously until it was rebooted.

 

EDIT: This camera responds to pings perfectly, with no response greater than 1ms over a few hours.

 

Below is a small portion of the error log before it disconnects, and attached are images of the UI upon logging into the camera directly.

 

Error Log before disconnect:

1507757709.548 2017-10-11 17:35:09.548/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch motion heatmap for Recording[59de8e69dd2b8f56f94565bb]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-015
1507757709.548 2017-10-11 17:35:09.548/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de8e69dd2b8f56f94565bb]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-001
1507757711.314 2017-10-11 17:35:11.314/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de8e85dd2b8f56f94565e2]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-028
1507757723.779 2017-10-11 17:35:23.779/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de8e85dd2b8f56f94565e2]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-023
1507757723.780 2017-10-11 17:35:23.780/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch motion heatmap for Recording[59de8e85dd2b8f56f94565e2]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-011
1507757755.526 2017-10-11 17:35:55.526/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de8eb1dd2b8f56f945661a]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-008
1507757768.484 2017-10-11 17:36:08.484/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch motion heatmap for Recording[59de8eb1dd2b8f56f945661a]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-014
1507757768.484 2017-10-11 17:36:08.484/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de8eb1dd2b8f56f945661a]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-024
1507757773.611 2017-10-11 17:36:13.611/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de8ec3dd2b8f56f9456633]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-018
1507757778.612 2017-10-11 17:36:18.612/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Camera sent 0 byte image (IndoorMechanical_NW) in CameraService-TaskExecutor-010
1507757783.633 2017-10-11 17:36:23.633/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de8ec3dd2b8f56f9456633]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-036
1507757783.634 2017-10-11 17:36:23.634/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch motion heatmap for Recording[59de8ec3dd2b8f56f9456633]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-020
1507757803.012 2017-10-11 17:36:43.012/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de8ecedd2b8f56f9456642]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-012
1507757803.012 2017-10-11 17:36:43.012/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch motion heatmap for Recording[59de8ecedd2b8f56f9456642]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-019
1507757969.127 2017-10-11 17:39:29.127/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de8f87dd2b8f56f9456714]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-022
1507757982.394 2017-10-11 17:39:42.394/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de8f87dd2b8f56f9456714]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-024
1507757982.394 2017-10-11 17:39:42.394/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch motion heatmap for Recording[59de8f87dd2b8f56f9456714]: Timed out after 15000ms (IndoorMechanical_NW) in CameraService-TaskExecutor-014
1507759212.492 2017-10-11 18:00:12.492/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de9462dd2b8f56f9456c1a]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-021
1507759812.508 2017-10-11 18:10:12.508/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de96badd2b8f56f9457325]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-002
1507760414.524 2017-10-11 18:20:14.524/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de9914dd2b8f56f9457a45]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-020
1507761014.544 2017-10-11 18:30:14.544/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de9b6cdd2b8f56f9458167]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-005
1507761614.560 2017-10-11 18:40:14.560/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59de9dc4dd2b8f56f945888e]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-016
1507762214.583 2017-10-11 18:50:14.583/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59dea01cdd2b8f56f9458fc0]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-025
1507762814.617 2017-10-11 19:00:14.617/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59dea274dd2b8f56f9459709]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-015
1507763414.651 2017-10-11 19:10:14.651/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59dea4ccdd2b8f56f9459e45]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-025
1507764014.684 2017-10-11 19:20:14.684/EDT: ERROR  Camera[59d94f4fdd2b9f1b4e3d6c7e] Unable to fetch image for Recording[59dea724dd2b8f56f945a58d]: null (IndoorMechanical_NW) in CameraService-TaskExecutor-005

 

Second Camera (Unifi G3 Bullet Firmware 3.8.3):

 

This camera's problems seem easier to pinpoint. Installed with an IR LED Infrared Ring, you can see the ring functions in the dark, but the cut filter does not seem to work in low-light (or no light, with no hot-spots), leaving all low-light recordings dark. I have tested with and without the IR LED ring. I have re-flashed freshly downloaded 3.8.3 firmware to the camera, which did not help. Testing with either NVR or either switch yields the same result.

 

My question to the UBNT community is:

 

Would it be reasonable to RMA both of these cameras, or is there something in particular I can do to get them working as expected? The other three cameras from that five pack are currently working as expected on firmware 3.8.3.

I am just perplexed by getting two problematic cameras in one 5 pack, when I have -never- received a bad G3 in the past year and I have installed >40 of them, all still going.

Configure.PNG
System.PNG
New Member
Posts: 2
Registered: ‎10-12-2017

Re: Potentially Problematic G3 Camera Batch (5 pack)

Has anyone experienced similar issues to the above with one or more of their G3 cameras?

 

I see a few other threads with the "_UNINITIALIZED_" issue popping up, one recent:

 

https://community.ubnt.com/t5/UniFi-Video/UVC-G3-Disconnecting-and-Autoswitching-Infrared-not-workin...

 

https://community.ubnt.com/t5/UniFi-Video/All-of-a-sudden-lost-preview-of-one-of-the-cameras/td-p/19...

 

https://community.ubnt.com/t5/UniFi-Video/G3-Bullet-suffer-from-regular-kernel-panics/td-p/1950592

 

 

When the web interface works with the problematic G3, shortly after a power-on, I can upgrade the firmware without issue. But the problems decribed above re-appear after just a few hours, leaving the camera bricked until a "manual" reboot (toggle port 24V PoE). Firmware version seems to be irrelevant. Is there a component onboard you think could be flakey and cause these specific issues? Like losing contact with the NV flash and/or controller the device configuration sits on? Could the issue be heat-related, as the (any) G3 bullet does get quite warm after a few hours?

 

Is it safe to say when you see  "_UNINITIALIZED_" in the G3's webUI, there is nothing you can do, and an RMA is needed?

 

I am willing to experiment a bit, as I have 8-9 other cameras sitting around still to install.

 

Thank you for your input!

Ubiquiti Employee
Posts: 2,616
Registered: ‎06-18-2015
Kudos: 842
Solutions: 231

Re: Potentially Problematic G3 Camera Batch (5 pack)

Hi @VS0,

 

Could you download and share the logs from the camera itself (from the camera's WebUI) after the camera shows that _UNINITIALIZED_ error?

 

One thing you could try to do is a TFTP Recovery on that camera, just to ensure that all its bits are in order; but please provide camera logs before doing that so I can have our firmware team review them.

 

https://help.ubnt.com/hc/en-us/articles/205204040-UniFi-Video-TFTP-Reset-Recovery

 

 

UBNT_Alternate_Logo.png
Ubiquiti Networks Enterprise Support Team

Check out our ever-evolving Help Center for answers to many common questions!

Reply