I have 5.7.20
@sportsfan986 I donāt know what to suggest. I suppose you could try updating your controller software, but thatās a complete guess on my part. Then again, itās not like 5.7.20 is old (March 2018)ā¦
Maybe someone else (@mgbowman?) has an idea of the cause of the problem?
I am on 5.6.29 - will try an upgrade
I have upgraded today from 5.7.x to 5.9.29 and everything still works fine with OH2.3 and the latest Unifi Binding.
Iām running the Unifi Controller on a Windows 2012 Server with 3 APās connected to it.
Best, Jay
Actually the RPI is not as straightforward as one would think and I learned the hard way. You need to have at least the RPI 3 due to the requirement of having a 64-bit cpu for the installation. It has to do with mongo db which is initially required during the install and fails without the right cpu (even though mongo later on is actually not required and even removed). I heard that there are people who got it working with older RPIs but I didnāt.
The following page Installing Ubiquity Unify Controller on a Raspberry PI finally solved my problem and saved me hours. Since then it works flawlessly.
cheers
Stefan
I have an issue where android devices change their mac address after every rebootā¦ any way to track them?
And is there a final release of this binding ?
what? how? 
this is not normal 
No, the latest can be found here: https://jenkins.otr.mx/job/openhab2-unifi-binding-v2/lastStableBuild/
Itās very stable and reliable. I have been using it for months/years
Check the android forumsā¦ Even some Samsung models do itā¦
What would work is 802.1x identityā¦ but that is probably not in the binding 
flash everything with custom f/w from xda
Not an optionā¦ and the binding requires a MAC address 
What would help is listing online devices as a list of things ā¦
you have faulty phones. fix them.
itās not normal to have the MAC changing all the time.
and donāt expect a developer to enhance the binding (to add 802.1x support and/or extra listings) for only 1 user who is experiencing device faults 
1 Like
MAC address change might not be caused by faulty device, but related to data privacy as MAC address can be used to track the user (this what unifi binding try to do as well 
).
Editā¦ https://source.android.com/devices/tech/connect/wifi-mac-randomization
most of the threads online discussing this (real) issue result to the user sending the unit back to RMA (cause itās faulty mainly due to firmware problems)
if this was related to data privacy, the user could willingly disable such feature
Itās not device faultsā¦ Or atleastā¦ Nothing I can fix. Itās 100.000 or more android only phones that do the same thing. But I am more than happy to adapt the code to work for me
If Iām allowed to.
the project is on github
I think that the owner would be happy to see contributions
That link says āA different randomized MAC address is used per SSIDā, so surely the MAC address would always be the same on your SSID, unless you changed your SSIDā¦
a bit further down, it writes:
Verify that forgetting a network and re-associating to the same SSID generates a new random MAC address.
so it seems that it will generate a different MAC even when connecting to the same SSID.
Itās not clear to me if you donāt forget the network and reconnect what will happen
btw, we are going way off-topic now
Anyway, this feature is disabled by default and the developer must provide for a user option.
As this would be my first OH project I dive into and really want this ā¦ Who can help me compiling the project ?
1 Like
the best way forward would be to
- Read https://www.openhab.org/docs/developer/contributing/contributing.html
- Fork https://github.com/mgbowman/openhab2-addons/tree/unifi-binding-v2/addons/binding/org.openhab.binding.unifi
- Get in contact with the original author @mgbowman for additional help
- Check the history also on: https://github.com/openhab/openhab2-addons/pull/3387