Page 1 of 1

uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Thu Jun 02, 2016 10:16 pm
by kw123
you can install controller on a raspberry pi with:

This is well documented and easy to follow
http://www.lowefamily.com.au/2016/06/02/installing-ubiquiti-unifi-controller-5-on-raspberry-pi/2/

in addition I suggest to install VNC server:
https://www.raspberrypi.org/documentation/remote-access/vnc/

now you can use your uniFi- controller either through VNC to the rPi desktop or directly in your browser https://rpi-ipnumber:8433 (*)

an thanks to Bollar for the hints

Karl

(*)the connection is insecure if you don't have a certificate system setup on your rpi. As long as you do things locally only it should not be a problem.

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Fri Jun 03, 2016 9:35 am
by FlyingDiver
I think the reason that Ubuntu doesn't support running the controller software on an rPi anymore is that they now sell a stand alone controller that does what the rPi implementation did, plus more.

https://store.ubnt.com/unifi/unifi-cloud-key.html

For only $79 list, with POE and a gigabit port, I'm not sure I'd bother with an rPi. I know if I ever decide to remove the controller from my Mac mini, I'd probably just get one of these.

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Sat Jun 04, 2016 9:19 am
by kw123
I just ordered one..

BUT please check if the controller runs well on your MAC. on mine it opened one port every 2 seconds until the mac had problems. restarting the controller fixes it.

Karl

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Sat Jun 04, 2016 9:58 am
by FlyingDiver
kw123 wrote:
I just ordered one..

BUT please check if the controller runs well on your MAC. on mine it opened one port every 2 seconds until the mac had problems. restarting the controller fixes it.

Karl


I run the standard controller on the same mini as Indigo, SecuritySpy, Plex, and a few other things. No issues so far.

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Sat Jun 04, 2016 10:25 am
by kw123
Please check activity monitor info /open files /scroll to the bottom check how many open ports.


Sent from my iPhone using Tapatalk

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Sat Jun 04, 2016 10:40 am
by FlyingDiver
kw123 wrote:
Please check activity monitor info /open files /scroll to the bottom check how many open ports.


My server is running Yosemite, and there's no count of open ports at the bottom of the open files tab. On the Summary tab, however, there is a ports entry and it says 373.

That's for the "UniFi" process with the flying saucer icon.

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Sat Jun 04, 2016 12:34 pm
by WouterK
Hi,

Running the Unifi controller on a Mac Mini with El Capitan the port numbers are growing every 2 secs, like Karl explained.
Restarting the controller does remove the port in use, but they will be used again after the restart.
Is there another solution then restarting the controller app?

Regards,

Wouter

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Sat Jun 04, 2016 12:37 pm
by FlyingDiver
Guess I won't be upgrading from Yosemite anytime soon then.

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Sat Jun 04, 2016 2:45 pm
by kw123
I have yosemite too with the growing #of ports.
Must be something in my environment.. but as long as it works for you ..

Karl

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Mon Jun 06, 2016 5:38 am
by Bollar
kw123 wrote:
I have yosemite too with the growing #of ports.
Must be something in my environment.. but as long as it works for you ..

Karl

The behavior in 5.0.7 appears to be different. Can you confirm?

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Mon Jun 06, 2016 7:38 am
by kw123
I have moved on to the CloudKey.
Different = better?


Sent from my iPhone using Tapatalk

Re: uniFi-WiFi-AP: RaspberryPi controller

PostPosted: Mon Jun 06, 2016 8:19 am
by Bollar
kw123 wrote:
I have moved on to the CloudKey.
Different = better?


Sent from my iPhone using Tapatalk

I'm not seeing the ports being created continually.

But I also changed the ports (away from 8443) to get rid of the conflicts with Mac OS X Server, so maybe that is part of it.