UniFi WiFi AP: download

kw123 · Post by **kw123** » Tue May 31, 2016 10:55 am

Korey · Post by **Korey** » Tue May 31, 2016 11:18 am

Fantastic!

Thanks Karl!

kw123 · Post by **kw123** » Wed Jun 01, 2016 3:15 pm

posted v 0.2.1

fixed:
- menu/configuration input now checks for empty fields
- removed some early debugging parameters
- worked on synchronizing the different inputs ( log files from x APs and the Dicts from the x APs) depending on timing devices could go up/down within 21-2 seconds (e.g. log file states down, while dict read about 1 second later still states up). Now there is a timer that watches the timings and should make sure that that will not happen.

added:
- added fingscan support (requires FS v >=4.19.1) Enable through an option in configuration
- added states:
== last StatusChange = time stamp when device went from up->down/expired or down/expired --> up
== txRate besides rxRate shown in Kbit units, eg 24000 is 24 Mbits
== better debug selections in config

Karl

kw123 · Post by **kw123** » Wed Jun 01, 2016 5:29 pm

posted v 0.2.2

fixed:
for SHORT ip numbers the error test was a false positive, now each test does a real test if each number is an integer and if we have 4 integers.
10.0.0.10 did not pass
192.168.1.3 did

Karl

this should do the right thing for all ip (version4) numbers

Code: Select all

   def checkIP(self, ip0):
        ipx = ip0.split(".")
        if len(ipx) != 4:
            return False
        else:
            for ip in ipx:
                try:
                    int(ip)
                except:
                    return False
        return True

kw123 · Post by **kw123** » Thu Jun 02, 2016 4:41 pm

posted v 0.2.5

added:
=you can change the Notes filed in device edit after the ip-number to anything you like. if empty it will be overwritten by the info from the APs
=option to send the log output to a file in ~/documents/unifi.
to switch on: enable log file to file at bottom of config

This is handy when you would like to understand how this thing works.

the following files will be created:
unifi.log -- out put from regular log file and system log file output from APs. when the log file is > 10MB it gets renamed to unifi-1.log and a new log file gets created. Two log files are kept.
dict-AP-x-Seq-y.txt <-- these are the dicts from the APs, each time a new dict gets read y gets incremented put to 10. then it starts again form 1

you can check the log file out put in a terminal with e.g.
cd ~/documents/unifi
tail -f unifi.log
tail -f unifi.log | grep ">>>" <-- this will only list the connect/ disconnect messages
tail -f unifi.log | grep " ---" <-- this will only list the system messages
tail -f unifi.log | grep "dict" <-- this will only list the log entries for dict retrieves

etc.

Karl

examples:

Code: Select all

 for ">>>"
 >>>> Jun  2 17:23:22 5-gameR daemon.info hostapd: ath1: STA 74:c2:46:b9:1a:7a IEEE 802.11: sta_stats
   >>>> Jun  2 17:23:22 5-gameR daemon.info hostapd: ath1: STA 74:c2:46:b9:1a:7a IEEE 802.11: disassociated
   >>>> Jun  2 17:23:22 5-gameR daemon.notice hostapd: AP-STA-DISCONNECTED 74:c2:46:b9:1a:7a

or for "  ---"

  ---- Jun  2 17:36:20 5-gameR authpriv.info dropbear[22732]: Exit (karlwachs): Disconnect received
   ---- Jun  2 17:37:20 3-Study authpriv.info dropbear[22837]: Child connection from 192.168.1.136:63721
   ---- Jun  2 17:37:22 3-Study authpriv.notice dropbear[22837]: Password auth succeeded for 'karlwachs' from 192.168.1.136:63721
   ---- Jun  2 17:37:22 3-Study authpriv.info dropbear[22837]: Exit (karlwachs): Disconnect received
   ---- Jun  2 17:37:22 4-kons authpriv.info dropbear[22837]: Child connection from 192.168.1.136:63726
   ---- Jun  2 17:37:24 5-gameR authpriv.info dropbear[22910]: Child connection from 192.168.1.136:63729
  

    dict from:192.168.1.5 hostname:5-gameR MAC:44:d9:e7:f9:c5:43 GHz:5  essid:5 channel:36  nStations:0  tx_power:23  radio:na
    dict from:192.168.1.5 hostname:5-gameR MAC:44:d9:e7:f9:c5:43 GHz:2  essid:2 channel:1  nStations:2  tx_power:30  radio:ng
    dict from:192.168.1.5 name:client-18:fe:34:a6:4d:5b MAC:18:fe:34:a6:4d:5b GHz:2 ip:192.168.1.177  txRate:52000 rxRate:1000  signal:-53  name:ESP_A64D5B  powerMgmt:True
    dict from:192.168.1.5 name:client-00:bb:3a:4f:8e:87 MAC:00:bb:3a:4f:8e:87 GHz:2 ip:192.168.1.138  txRate:19500 rxRate:1000  signal:-44  name:  powerMgmt:True
    getting dict for #3
    getting dict for #4

wiery · Post by **wiery** » Sat Jun 04, 2016 5:35 am

Amazing work Karl, looking forward to installing later

Sent from my iPhone using Tapatalk

kw123 · Post by **kw123** » Sat Jun 04, 2016 9:16 am

v 0.5.1 posted

fixed:
if your device name in the notes field started with a "-" it replicated the name every minute (_name_name_name..) not likely a common problem

added
+++new mode for the wifi clients:
== besides the regular mode with expiration timer to go to DOWN then to EXPIRED after a set time if no message (can now also be set individually for each device in device edit)
== "fastDown" mode. Device goes UP after a connect message received. it ONLY goes down after a "disconnect" message received. any info from the dicts is ignored for this mode.
this can be used to for switches and devices that do NOT go to sleep. you can test it on you phone by turning wifi on/off/on (must be 1 second apart) and see the reaction in the the status field.
+++ added new states:
== noise ( in dBm) should be compared to signal (signal - noise is ~RSSI)
== idle time gives you the # of seconds since last transmission from the device only updated with the dicts (i.e. 1/minutes depending on your setting in config)
+++ added some more features to the log file writing.
=== now the latest dict file is aways -0. 9 files are kept # 8 is the last
=== a little bit more management around what always goes to the indigo log file (basic start/ stop)

Karl

kw123 · Post by **kw123** » Sat Jun 04, 2016 4:00 pm

v 0.6.1 posted

fixed
-

added:
added neighbor wifi router info. It shows most of the available parameters in the AP- DICTS. If you have 2 or more APs they should show up too as neighbors.
Shown in the notes field with their SID

This gives you a good indication of the frequencies used and which things are around on a continuous basis. the RSSI value should be as low as possible from your neighbors. If they are > 15 you likely have a problem. (RSSI=10 is Signal/noise =10, 20=100, 30=1000, 1=1)

Karl

Found out that 2 of my neighbors have UNIFI equipment too. (the model and and model_display parameters are not blank)

kw123 · Post by **kw123** » Sun Jun 05, 2016 6:00 am

posted 0.6.2

fixed:
error: uniFiAP in Line '689' has error=''key ipNumber not found in dict''

added
== option to ignore new neighbors
== added some info to the notes field for neighbor routers

Karl

howartp · Post by **howartp** » Sun Jun 05, 2016 7:25 am

Cool.

Just bought a 3-pack of non-AC's for church on the back of the zero handover thread.

If they go well, I'll be getting one or two for home.

One of the church ones will accidentally come home for a month as its for an extension that doesn't exist yet

Sent from my iPhone using Tapatalk

DaveL17 · Post by **DaveL17** » Sun Jun 05, 2016 8:56 am

howartp wrote:Cool.

Just bought a 3-pack of non-AC's for church on the back of the zero handover thread.

If they go well, I'll be getting one or two for home.

One of the church ones will accidentally come home for a month as its for an extension that doesn't exist yet

Sent from my iPhone using Tapatalk

One of the Commandments 11-15: "Thou shalt not covet thy church's APs."

howartp · Post by **howartp** » Sun Jun 05, 2016 9:38 am

Haha!

I best bring home all my equipment that the Church has coveted then ;-

Sent from my iPhone using Tapatalk

kw123 · Post by **kw123** » Sun Jun 05, 2016 9:44 am

posted v 0.7.1

added:
== symbols in status column for up=green, down= grey, expired= red
== added state "adhoc" in device types: neighbor = other wifi routers. This is to distinguish between regular router and you e.g. chrome cast that starts its own wifi for peer to peer communication
== expanded the parameter print in menu. now prints all parameters AND all devices with props and states

Karl

kw123 · Post by **kw123** » Sat Jun 11, 2016 10:21 am

posted v 0.8.1

fixed:
some inconsistent state definitions (mac MAC etc)

changed:
device types are now
- WiFi
-DHCP
-Neighbor
-gateway
-Device-AP
-( in the future SWITCH + ..)

"Client" was replaced by "Wifi". When you upgrade the plugin the old "CLIENT" devices will still be there but inactive (dead) and new WiFi ones will be created. You need to rename them to your liking and delete the old "client" devices.
As there a more devices available now and more coming and they are all "clients" it made sense to distinguish them
Hope that is not too much trouble

added:
= "full" support for gateway with DHCP client info available (ip, uptime, "age", name, ..)
= added lookup for MAC number device vendor name (/usr/bin/curl http://api.macvendors.com mac# returns the vendor name) . This is done at startup, so the first time you load the plugin it might take a little bit longer to start.
= reduced the number of logins to AP and Gateway by doing a continuous loop on the AP and GW within EXPECT.
= reduced # of bytes send from AP and GW by removing leading spaces for the DICT dump with an sed filter (*)
= added besides fast down idleTime and AGE to trigger UP--> down. You now have a variety of options to check if a device is NOT up expiration time (common or individually) fast down/idletime/age. You need to figure out what works best for you.

Wifi devices will show up twice: once as a WIFI device and as a DHCP device and they behave differently as the information sources are different.

Wifi devices that stay connected even when they are asleep ( iPhones) can use either fast down (you turn off wifi) or expirationTime ( after xx seconds when nnot visible to wifi device)
another example are amazon dash buttons: When pressed to come alive send some packages and wait, still connected but don't send any more packages. you can use idleTime to trigger down

What is missing is the SWITCH info. ( If you have a unify switch) In my setup not all traffic comes by the gateway. Only internet Broadcasts and DHCP request. So a lan device might be not visible
to the Gateway if it only talks internally, besides requesting an IP number from the DHCP server. When I get the unify switch I will add that info.

Karl

(*)removing leading spaces for database formatted json dump with:
mca-dump | sed -e 's/^ *//'
>50% reduction, in my case 25k-40k --> less than 7k

kw123 · Post by **kw123** » Sun Jun 12, 2016 6:49 am

posted v 0.8.4

this should fix the error "'Device' object has no attribute 'updateStateOnServers'"

Karl

ps
suggest to enable write logs to file in config. This gives a nice tool to check how the thing communicates and does not flood your indigo log file.
to open up the log file double click on on ~/documents/unifi/unifi.log

Indigo Domotics

UniFi WiFi AP: download

UniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download

Re: uniFi WiFi AP: download