I am not getting tracker updates from this integration. Been that way for awhile. Devices never change to Away unless I reload the integration.
Any solution for this?
1 Like
Does toggling the LED entity write to NVRAM or does it only change the value in the NVRAM mirror? I have merlin so I can’t test it by rebooting.
Currently I have a cron job set up on the router to toggle the LED at night and in the morning, but I only write to the NVRAM mirror to avoid wear on the flash. But if this service doesn’t write to the NVRAM either then it would be better to set up an automation in HA.
Hello, @szerencl,
The integration uses the FW service ctrl_led the same way as the Web UI is doing (via this button in the AiMesh panel).
Snapshot
As far as I know, it writes the value to NVRAM directly and on the stock FW the LED state is staying the same even after reboot. At the same time, Merlin ignores this NVRAM value and does not load it on boot (because long ago Merlin implemented a different way to disable LEDs). To work around it, when the communication library notices a reboot and if the last state of the LED is “off”, it actually sends to Merlin (and only Merlin) an “on”/“off” sequence for the LED to restore the correct state. With the “on” value from before the reboot, nothing is sent.
Considering the fact that this is exactly the same behaviour as the Web UI has, I don’t think this should be a problem for the NVRAM wear. Especially considering the number of changes written to NVRAM constantly in any case. But this is up to you to decide what is better in your case.
@kramttocs, hello. I am constantly trying to improve the device tracking features. Unfortunately, the lack of any testing devices (except for the only RT-AX88U I have) and the fact that the issue might happen and not happen to the two identical devices with the same FW version is not helping in solving it fast.
But it will be solved eventually.
Can you please open an issue on GitHub with all the details about the problems you are experiencing, so that we can troubleshoot and solve everything properly.
To everyone else. If you are experiencing some issues and there is no such issue on GitHub yet, please open an issue. If the same issue already exists, please just comment on it with the device model and the FW version you are using.
With time it’s getting harder to track all the issues here and this can help with providing fixes much faster.
The new version is coming soon to AsusRouter. Please, stay tuned 
3 Likes
RT-AX88U stock firmware. I’m finding that the integration is corrupting my static IPs and the router is “forgetting” the name of my tracked devices and their statix ip management gets messed up. Only happens to devices tracked through the integration.
Anyone else?
Hello,
AsusRouter cannot directly access the DHCP server table and cannot change the IPs set to static. Please, check your device’s DHCP settings (available at https://YOURROUTERIP:8443/Advanced_DHCP_Content.asp). Are they changed from what it was?
As per the “forgetting the name of tracked devices”, I would need more context. How do you see this? When and how it happens? And what do you actually mean by the device name?
Thanks in advance for the provided info
What are your thoughts on adding a service to reload the integration? I see some integrations have this.
Just thinking that maybe reloading the integration on a daily basis may help with the device tracker issue. I know we don’t want to rely on it as a permanent solution.
Isn’t there a Service available in Core already that let’s you reload any integration? Why not just create an automation using that to do what you need…
Is there? I looked through them but didn’t see one that allowed you to pick an integration. Will look again. But yes, an automation using a service is what I am looking to do.
Something like this should work…(does for me anyway, tho not with this integration)
Obv add in your own entity_id and/or device_id
service: homeassistant.reload_config_entry
target:
entity_id:
- entity1
- entity2
device_id: device 1
data: {}
1 Like
Thanks! I’ll give that a try. I know it’s purely a workaround but interested to see if this helps.
Stumbled upon this integration after getting very frustrated with ASUSWRT. From what I can tell it’s FANTASTIC! I do have one question that I’m close to pulling my hair out over! I have an ASUS AiMesh setup in my house consisting of:
1x Main Router
2x Wired Nodes
1x Wireless Node
I mainly use the integration as a device tracker so I can trigger certain events when family members are home vs. away…However, my issue is that when a user (android or IOS) connects to the Wireless node (happens to live outside on the patio to cover the backyard), the entity state for that device shows as: AWAY even though they are still connected to the network. How do I tell this integration to over-ride also use the wireless node as part of the tracker?!
Thanks again for all the great community support!! Look forward to figuring out this small issue!
EDIT: I am running stock firmware and tried both Router and AP Access mode with no luck on either.
Hi Mark,
I also have an ASUS AiMesh AC set up in my house consisting of 3 units:
1 router
1 node (wired)
1 node (wireless)
My wireless node is also to provide coverage for the back yard however in still inside the house against the back wall. My wireless node only has the 5GHz radio turned on (2.4GHz disabled) as the backyard coverage I need is for family and guest cell phones. All my IoT devices (2.4GHz) connect to one of the two wired nodes either Ethernet of WiFi.
I too use this excellent AsusRouter integration to track which family members are visiting (adult children living away) as well as home residents (my wife & I) home or away via cell phones (combination of iPhones and Android devices). For me and my wife I also use geofencing apps to supplement the AsusRouter wifi presence.
I just tested the AsusRouter presence for myself by going into the backyard and confirming my iPhone was connected to the wireless node. My iPhone entity remained as ‘Home’ and did not switch to ‘Away’ when my phone WiFi connection roamed from the main router node to the wireless backyard node. I too am running stock firmware and the latest software release for the ZenWiFi AC hardware. Just thought I’d share my findings and experience in case it helps you and/or the integration developer.
The device tracker finicky-ness is a known issue but tough nut to crack. When you are seeing this behavior, if you reload the integration, does it immediately update to HOME?
1 Like
I just tried your suggestion and after reloading and rebooting it does not trigger as home. It seems to be just when I’m on the wifi mesh node. The wires backhail nodes appear to be fine. My router is an Asus XT8 with a second node and my two other nodes are Asus RP-55 repeaters. I feel like I have something not quite set right somewhere in my setup?!
EDIT: To further complicate matters, I’ve noticed that the Asuswrt integration is showing the same phone as Home on its entity while the Asus router integration shows away while on the wifi node?!
I’m currently running both while trying to get this figured out.
1 Like
Oh, that’s interesting that’s only the wifi one does it while the wired doesn’t. My setup is:
RT-AX86U Primary
RT-AC88U mesh with wired backhaul
RP-AX56 mesh with wired backhaul
So I don’t have a good comparison not having a wifi only node.
Sorry, wish I could be of more help but your note of the two integrations showing different values may give the dev something to look into though.
I have a setup with 2x RT-AX58U nodes using wireless backhaul and the integration is working correctly in terms of home/away status for devices I want to track.
Overall AiMesh is a bit flaky generally (nothing to do with this integration) and different combos of routers and different firmware have strange results.
I find running merlin’s FW on the main router and latest stock FW on the nodes works best for me (after many years of trial and error).
My advice would be to try to do a clean/fresh/manual install of the FW on the main router. Do a wps reset after flashing the latest firmware - do not restore any settings. Then do a wps reset on each node and add them as a mesh node one at a time. Do not make any further advanced/config to any settings.
Now test how the tracked devices roam across nodes and see how they look in the integration.
Hope this helps. I know it’s a lot of work but in my opinion, a clean/fresh install saves a load of time troubleshooting weird issues.
Thanks Jata, but I don’t think it’s the router/aimesh in this instance, since the ASUSWRT integration appears to be working semi-normally at this point for me in regards to the tracking feature. Hopefully someone else has experienced this and can point me in the right direction. Ugh! lol
How did you fix this? It used to work but now doesn’t.
I just spent time to get my asus router / mesh network working nicely. To do this I completed a full reset and manual reconfiguration. Made minimum changes to default config. Then I added the integration to HA and slowly got things working.
Got the integration to monitor the network and nodes.
Used connected devices entity to create the connected devices view - including node.
Then I used enabled device_tracker for the few devices I actually wanted to track home/away status for (family member iphones)
Then I linked those devices to people entities and it works perfectly - all family members are currently home…
2 Likes
Thanks! Were you able to sort the table by IP like your yaml suggested? For me it won’t expand and I get “flex-table-card.js?hacstag=156292058072:22 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘toString’)”.