ha-asusrouter: [Bug] Device trackers are stuck

There is a new version of the integration coming soon with a new backend. Hopefully, the issue will be solved already there, since the communication methods were completely changed. But there is still some more work to be done before it’s ready

The main issue, as already pointed here, is the fact that some routers themself do not show the connected devices properly.

E.g.,on the RT-AC66U I have partial access to, the devices are only coming online but not offline even in the Web UI. Unless, you manually open the device list menu (via the “full list” button) in the Web UI. Unfortunately, even mimicking this behavior from the integration side, I didn’t yet manage to solve the issue.

With some other devices the method of the guest networks does really help, but not all of them.

So, I hope, you can understand, when the issues are on the device side, it’s not as easy to be fixed (or even avoided) from the external integration

In any case, the work on fixing at least a part of issues with the device tracking is ongoing. As soon as there will be any news, I’ll let you know

P.S. As for the “I’ll never use AsusRouter again”, I am surely sad of hearing this, but AsusRouter is my hobby project, done by testing on a single device I have available. Please, try to understand this limitations. You can always use the default HA AsusWRT integration which will have quite the same problems. Or, for the devices you need to know exact location, you better use the proper way of monitoring - which is never a router - WiFi connection requires quite some time and you can actually cross all the WiFi coverage area before your device authenticate and the router (of any model and manufacturer) will report it

Some news here ?

@5a5cha, yes. Unfortunately, there is still an issue with the data mix between several devices. I hope to be able to solve it soon

@TeddyLafrite, I am working on the device tracking issues

@Vaskivskyi Can I buy you a few coffee, if you can solve this issue. This is main feature of this addon.

Hello, guys.

I am sorry for not replying - there were some matters not allowing me to work on AsusRouter lately. But from now on the work will continue as before.

Thanks for all the reports you have already posted. Even the small details might help with the whole picture of the problem core.

@contrasenda, that’s an interesting fact. Actually, all the time testing I was only directly disconnecting the device and never tried going out of range. Maybe, the device FW is processing this differently. I will try to check

Hi, with the latest update tracker seems to work for me to.

Hi @Vaskivskyi Installed this morning Tracker seems to work properly

Hi @Vaskivskyi Installing and tell you next days Thanks and happy Christmas 😃

have you tried running merlin firmware on the router and node(s). Unlikely to help as aimesh is all closed source but might be worth a try. Merlin’s firmware is way better than stock in my opinion anyway.

I think it is better, but still not perfect.

In screenshot, you can see attributes have correct information, but log doesn’t show correct information. Laptop was off whole day, but it had status home. I updated asus router component at 6:21 PM and somehow it got status home. Attributes show correct connected time. So, it should be set from Away to Home at the time shows in attributes.

Maybe it is not due to asus router. Maybe is something when parsing api response from router, that status is not correctly updated? As jata1 said, I checked router and connected devices attribute and shows correct information.

Hi there,

I’m testing for 24h the beta 0.23.0b1 and devices tracker seems to work :

AsusRouter vs AsusWRT :

As a reminder : ASUS model RT-AX55

I’m installing 0.23.0b3 and will post results here in 2 ou 3 days

Today I was tackling unrelated bug, it was a problem with rendering the default Overview dashboard, and stumbled upon a thread that pointed out about bug that didn’t treat properly entities that had space at the end of the name. I chased down one entity created by another integration that had extra space at the end, and once I fixed that, after the reboot, the trackers started working as intended in both AsusRouter and AsusWRT integrations. I can’t confirm yet if that was the culprit, but so far everything seems to work as intended. Will see in a few days.

I found some Asus threads where others also had issues with devices not showing up in the device list eventhough they were connected. The fix was to create a guest wireless connection (feel free to hide it) for your router. You dont have to connect anything to the guest ssid, but just create it. Then the bug of not all devices showing in Asus device list is fixed. Now that all my devices are showing in the router list, the state is being passed to this Integration correctly (and no daily reboots or reloading of the integration are needed).

I tried this. I created a guest wifi network. Then I rebooted the router. Now, three days later, my Deco integration reports that one person is home and three are not. (Two Iphones and one Android, if that matters). The Asusrouter “integration” reports all four at home.

The add-on is unusable, so I am removing it and will rely on the perfectly working Deco integration.

Signing-off.

Any news from development?

Hi,

Just chiming in here that with the RT-AC66U I’m not seeing a lot of issues. I have noticed that immediately after rebooting the Home Assistant offline devices go “Unavailable” instead of “away” until they return. Looks like between boots the integration maybe forgets about previously tracked devices?

In any event, no major complaints from me right now.