luisv

Awesome! I for one appreciate everyone's time and efforts! Maybe I'm oversimplifying things, but what are the next steps to get the updated plugin within CA.

+1 on a separate tab.

Just saw the info for this docker via Twitter... very cool and simple. Can you pass multiple webapp URLs in a txt file to import? Made it my browser's homepage.

Thanks! New cameras adopted and functional.

Received a couple of new cameras and looking for the latest Unifi Video Controller Beta; however, I don't see it available yet. Can you please update to 3.9.2 B1 https://community.ubnt.com/t5/UniFi-Video-Beta/UniFi-Video-3-9-2-Beta-1-Release/m-p/2227249

No sure and I understand optional, no right nor wrong. Some folks might not have another system to attach multiple drives to perform tests like WD Lifeguard, etc, so within the system that will or is running unRAID what are those options. Since preclear, plugin or script, was the optional standard and recommendation, whats the new one?

Totally understandable and agreed, I'm not qualified to accurately articulate the differences nor say which is better, a preclear and smart, but shouldn't there be some guidelines and or recommendations? Just as it was highly recommended to run the preclear script and or plugin, shouldn't there be replacement as a direction for new users that wish to perform some sort of test?

Thanks for the history and details, much appreciated. I understand it's not needed for unRAID to function, but I for one would like to at least have some sort of warm and fuzzy feeling that a drive was tested and therefore shouldn't fail shortly after placed into operation. I know it might not be 100% perfect, and placebo or not, it provides a warm and fuzzy feeling.

I'm certainly not a seasoned unRAID user, but this is the first I'm hearing about badblocks, so that's part of the frustration and confusion. If there are multiple ways to perform this, what are they?

The plugin isn't supported, the script isn't supported and many users live happily without the preclear plugin? Can someone explain and recommend what the process should be to a new or relatively new unRAID user like myself? Is the consensus of developers and or recommendation from @limetech not to run a test on new drives before adding them to the array? Or is the consensus to hold off using the preclear plugin and script until they are updated and ready for use? Sorry, but I'm a little confused as there are numerous forum posts, wiki instructions, videos, etc. recommending and indicating how important it is to use the preclear plugin and or running a script before adding a disk to the array. If those recommendations and or processes have changed, shouldn't someone update the documentation, videos, etc. to indicate what the new recommended process is? Isn't the purpose of plugins to make certain tasks easier and more foolproof for the end user? Keep in mind that some users might not be as comfortable navigating and or running command line type scripts. Please don't take my comments / questions the wrong way, I appreciate everything that the community, developers and @limetech do... I'm just looking for some clarity and direction in regards to what the new process should be.

Unifi Video 3.9.0 was made available a few weeks ago, so under advanced, I removed the :beta from the docker repository and updated the docker. Everything seems to be working fine, except it shows as not unavailable in the docker tab. Any ideas?

Thanks! Looking forward to the update.

Great, thanks for the info. Curious if there will; be a new support thread or will this thread be renamed and stay active?

Exactly why I switched to the beta controller.

Hmm... let @Pducharme chime in as I don't recall doing anything special other than making sure the repository was set to use beta in the advanced properties. pducharme/unifi-video-controller:beta I've only recently switched due to a new camera.

I use the Unifi Video docker and it's running 3.9.0 Beta 6. Have you restarted the docker?

After updating the Unifi-Video docker this morning, my cameras were stuck in a managing state. I did a little research and based on the released notes for 3.8.0, it looks like folks will need to add another port or update the port list to the docker properties. https://community.ubnt.com/t5/UniFi-Video/NVR-3-0-8-Cameras-stuck-in-quot-managing-quot-State/m-p/2068710#M86596 https://community.ubnt.com/t5/UniFi-Video-Blog/UniFi-Video-3-8-0-Release/ba-p/2067768

32GB... was thinking about 64GB so I can run a bunch of VMs within a lab type setting.

After taking a break, I was able to get the setup wizard to run, configured it as well as adopt it into my UBNT cloud account. My mistake was leaving the quotes in the system properties file. So this is all you need to invoke the wizard: is_default=true

Currently having issues with the Unifi-Video docker. It's not available from Community Apps, so I had to add it from DockerHub. Once installed, I had to manually create the system.properties file and I added the following into the file: "is_default=true" Only way to get the docker to start was to set it to "Privileged". Once the docker was restarted and I tried to open the webui, it opened a blank page without the URL string to the UI, so I have to manually type in the address with the proper port. Can you let me know how to fix that? Once I manually type the URL into a browser, I was presented with the Uni-Fi UI saying that it was upgrading and then it is asking me to log in... the install / configuration wizard is not presented. I tried to log in via the default UBNT ID / PW, but no good. Below is the docker log. 2017-08-26 19:17:08.204564 [warn] PUID not defined (via -e PUID), defaulting to '99' 2017-08-26 19:17:08.259225 [warn] PGID not defined (via -e PGID), defaulting to '100' 2017-08-26 19:17:08.311434 [info] Permissions already set for volume mappings Starting unifi-video... done. One last thing... the docker icon was not set, so I manually had to set it to: https://dl.ubnt.com/press/Company_Logos/U_Logo/WEB/U_Logo_RGB.png Any help is appreciated...

Hello... I just wanted to say thanks for providing this docker, it was easy to install and works like a dream!

If this is the wrong place for this post, please let me know, but I"m curious as to how Code32's announcement will affect the docker and future support: https://www.crashplan.com/en-us/consumer/nextsteps/

Same here, thanks bonienl for providing this plugin and kudos to Bill for the interim solution.