-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Create a new entity from the "hostname" field #119
Comments
Hey, @Oligarch, I would need a bit more explanation of what exactly you mean by "name" for this feature. Currently, the
This priority list is built with the following thoughts:
So, what other option do you see to improve the naming? Does it not work this way for you? |
Unfortunately, this data is not available in any of the API endpoints with device information. The only way to get it - directly read So if I add the possibility to read this value, the integration will have to do 2 different requests (NVRAM read + get everything else from API - those requests cannot be merged), - this would take twice more time and may significantly influence the performance of some slower Asus models. Also, if any of the 2 requests fail, part of the data will be missing - should it then be:
For now, I am not sure this feature will be as useful, as it would influence the performance. But, in any case, I am not completely denying the idea. Just need to find a way to not make anything worse for XX% of users, who don't use this optional field. |
The problem
Can we have possibility to choose whether new device_tracker entities are created from the name or hostname field? If I'm not mistaken, the AsusWRT integration with hostname value known to the router creates object names from it. That would be much more convenient.
Specific device(s)?
No response
Firmware type
No response
The text was updated successfully, but these errors were encountered: