Well… I´m a Beginnger! But: Do i understand you right?! I have to delete the configuration.yaml with all his content? Sorry for this maybe stupid question.
Please give me a view more words! As a Beginner i think, i have to integrate these code to track my devices and to controle a coming home function or what else.
Ok, now I can follow you. Please excuse my unnecessary questions, I still don’t have the perspective. I had no idea, that this part is outdated. I was forwarded from Hass to this manual. I haven´t see that is from china. And i haven´t see, that is outdated. Sorry!
Well there are a new question for me as a beginner: If it was in the past required to insert these part of code, how is it possible for Hass to detect my devices who are connected to my Unifi Controller and why dosn´t it work for me?
i’m having the same problem as you and i have been looking for answers the past three days
all the replies i found is go check that page and go read this page.
no one is giving a clear answer to what’s wrong with our code and what to type exactly : (
this is not the answer for why the code we wrote is not working, that’s a different solution
the integration page is so simple and buggy even though in option two i selected the client i want to monitor but in the end it brought all the client in the network
but in confguration.yaml you have more option and gave you more control
like track_new_devices, detection_time, interval_seconds, consider_home
and i can just paste the mac addresses for the devices i want to monitor without searching and clicking in long checkbox list and when something get wrong you can’t copy your configuration easly
i just want to do it via configuration.yaml like everyone else but the home assistant log don’t show any details why it won’t work.
please i just want a working code or at least i want an answer in what’s wrong in our code : (
The path to configure the unifi integration through the configuration.yaml has been removed.
With the new integration there are multiple options to disable different types of entities to not be added. You can also disable specific entities in the entity registry
Thank you for your clear answer and time, i whished it was written in the documentation that’s the old way is no longer working so people don’t waste their time.
The Home Assistant Community is known as the biggest community in this area. And the reality shows exactly what you say: You have to invest many hours and days in research and in forums, get frustrated and simply lose interest because the answers are always the same: You can find that in the instructions. If you get an answer at all… I’m already dealing with the IOBroker because the acceptance and willingness to support beginners disturb me. I don’t know if it’s better there. But in this way I definitely do not come to a sustainable result. So I don’t learn adequately either. That frustrates me and takes my joy away.
What device? By default all network devices as well as network clients should be loaded. Device tracker entities are not visible in love lace but you can see them in the states view
@Robban How do you propose to define consider_home parameter? Unifi is now customizing via GUI, but it doesn’t provide “consider_home”. In the meanwhile the HA offsite propose to use this parameter:
Hint : When you use multiple device trackers together, especially stationary and GPS trackers, it’s advisable to set consider_home for stationary trackers as low as possible see device_tracker).