@sparke,
The connected_devices
sensor has a list of all the devices as an attribute device
, including the IP addresses of the active clients.
In principle, it would be easier to watch (and don’t forget to enable it first in the integration configs) the HA event asusrouter_device_connected
(new connections) and asusrouter_device_disconnected
(device connects again after being disconnected). This events hold some basic info about the client, including MAC, name and assigned IP
@h3llrais3r,
Can you please add a comment to this issue ([Bug] My device (client) gets dis-/reconnected regularly or not tracked well · Issue #792 · Vaskivskyi/ha-asusrouter (github.com)) and give more info on your router (including model and FW) as well as the switch / AP info you are using and with which you are experiencing tracking issues. Please, also specify the make and models of the devices which are disconnecting and reconnecting.
@boheme61,
The troubleshooting of the connected clients issue is switching to the per-client basis. Please, use the issue by the link above to add the details about connected devices that bother you in the integration
@rorynolan
You can easily use the asusrouter_device_reconnected
as a trigger and check whether it’s triggered by a device with a specific MAC address. But that would require the cleaner to use a static MAC address when connecting to your WiFi (so, not the anonymous IP
as defaults in the modern Android / iOS phones).
In this case, it might be easier to just watch the device_tracker
for this exact MAC, which would be even easier. Just set an automation triggered by device_tracker
getting state home
.
@dl3,
Can you please open an issue in the GitHub of the integration (if you haven’t yet). Unfortunately, I have a rather limited amount of time lately and don’t regularly check the forum.
P.S. If you already opened an issue and I haven’t replied to it yet, this will be done as soon as possible.
@jhummel,
Integration works with 2 out of 3 types of parental control rules - block
and allow
. The time
rules are not supported (yet). Please, make sure that the rules not showing properly in the integration are not in the time
state (when you select the schedule for the internet access)
@boheme61,
AsusRouter is creating device entries in the registry only in a way as described in the HA documentation for the Link
device type - which means it only says how the device is connected to your network. Home Assistant takes this into account to provide the connected via
and other link functionalities. The integration shown as the main in the UI is the one defined as Primary
in the docs. If the HA web UI is showing AsusRouter as a primary integration - this only means either there is an issue with HA itself, or the other integration (which has to be primary
is not implementing it up to the docs).
Link to the docs: Device Registry | Home Assistant Developer Docs (home-assistant.io)
Moreover, AsusRouter does not create devices without user explicitly marking it (block switches for the internet access or on the MANUAL enabling of the disabled trackers) in the configs or HA doing it as it is designed to do.
Device trackers come to the second group. They are bound to existing devices because HA is doing this. All the trackers that do not have the same MACs as known by HA are not even enabled by default.
If you would like to suggest changes to the HA architecture, feel free to create a new discussion in the corresponding repo. But this has nothing to do with the AsusRouter. You can check that out using the in-built AsusWRT integration or any other integration for any other router - they will all work in the same way