Hello,
I wanted to look at devices connected to my UniFi AP. I have added the requested lines to my configuration.yaml, but I don’t see anything showing up. Any ideas?
device_tracker:
- platform: unifi_direct
host: 192.168.1.5
username: myusername
password: mypassword
interval_seconds: 10
consider_home: 180
You shouldn’t have to do that, just use the unifi integration.
I am aware of the unifi integration and I am actually using the one for Protect, but this other one just doesn’t seem to work and the directions are not spot on or I am missing something. Either way if UniFi AP does not work why has it not been pulled?
You need to use the UniFi integration as the access point does not track devices, but the UniFi controller.
Not opposed to using the Unifi Integration based on experience with the one for Protect, but can someone just give a reasonable explanation (without side step criticizing the person behind WiFi AP add-on) as to why this should be an integration inside HA. Why not throw it into HACS or remove it all together? Just saying clean up stuff that is obsolete, lacking instruction or does not work. Only so saying so many hours in day, man.
I gave you the right answer. Use the Unifi network integration.
The Unifi AP integration with device tracker (like you are trying to do) was broken when they made that change to break all the rest of the device trackers.
Honestly, I didn’t even know what that integration does (unifi AP). Seems pretty useless to ONLY get that information when you have a lot more info available to you - info that works, too. LOL
so your an advocate of leaving broken integrations published? I am only trying to prove a point, but how many other integrations are busted but not removed? Clean the dirty house (Home Assistant)
dude. that’s all.
No one here cares for your bitching. The devs generally don’t read the forum.
The integration is ancient by HA standards. It has no codeowner. It does not comply with ha’s current coding standards. In due course it’ll be deprecated and removed.
Nevertheless some kind soul contributed it back in 2017. Good on him.
But please don’t demand change “Clean the dirty house”. Or call people dude. Have respect.
Since your nit picking my sentences let clarify. the people who replied I am not calling dude. Its a sad state if devs don’t read the forums, but if that is what is so be it. I am not sure how old the integration is and yes I am disappointed it don’t work. I was speaking to HA as a whole not specifically calling someone a dude, certainly not the repliers. But how many other “ancient” integrations are out there that are deprecated but sitting around? No idea but based how often HA is updated I thought the obselete ones would be gone. So don’t twist my words to prove a point.
The Unifi Direct / Unifi AP integration does work. I use it exclusively as I only want to track a small number of devices and don’t see a need to be running the controller 24/7.
thanks for offering to help @silvrr. That was my thought too. Eventually I might add in the full UniFi Network integration but I only have a very small pool of IP’s than can be statically assigned and would like to monitor the few I do allow to be assigned. Happen to believe in setting static IP’s wherever possible.
To answer your question I did not see a known_devices.yaml in the config directory.
What about the logs?
Logger: homeassistant.components.device_tracker
Source: components/unifi_direct/device_tracker.py:85
Integration: Device tracker (documentation, issues)
First occurred: 1:45:10 PM (1 occurrences)
Last logged: 1:45:10 PM
Error setting up platform legacy unifi_direct
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/device_tracker/legacy.py”, line 282, in async_setup_legacy
scanner = await hass.async_add_executor_job(
File “/usr/local/lib/python3.10/concurrent/futures/thread.py”, line 58, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/homeassistant/homeassistant/components/unifi_direct/device_tracker.py”, line 39, in get_scanner
scanner = UnifiDeviceScanner(config[DOMAIN])
File “/usr/src/homeassistant/homeassistant/components/unifi_direct/device_tracker.py”, line 57, in init
self._connect()
File “/usr/src/homeassistant/homeassistant/components/unifi_direct/device_tracker.py”, line 85, in _connect
self.ssh.login(
File “/usr/local/lib/python3.10/site-packages/pexpect/pxssh.py”, line 386, in login
raise ExceptionPxssh(‘Could not establish connection to host’)
pexpect.pxssh.ExceptionPxssh: Could not establish connection to host
Is SSH enabled on the AP?
Was disabled in UniFi, but enabled it. Restarted HA but still not able to putty to it. Will need to keep digging. Do I use the ssh user id and pw or the user I create in Unifi with my own pw?
It’s been working fine for me over the four months I’ve been using the UniFi integration!
I have the same issue!
I had the same thing. The entity names are confusing. You should search in entitys: device_tracker. The integration makes a single tracker for every device thats connected to the unifi AP
