Solved Help - Asus ZenWiFi CT8 - Specific device not roaming properly.

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

santiagojlouise

New Around Here
Hi everyone,

Just for the background first:
  • I'm using the latest firmware 3.0.0.4.386_23003
  • I have the 2-pack Asus ZenWiFi CT8.
  • 2.4GHz and 5GHz are separated
  • I have tried switching the nodes as a main router.
So I am getting these logs for my specific device OnePlus 7 Pro. Other devices are roaming fine.

Code:
Apr 23 10:44:50 roamast: determine candidate node [3C:7C:3F:45:D8:B0](rssi: -61dbm) for client [FA:56:FF:71:A2:98](rssi: -85dbm) to roam
Apr 23 10:44:53 roamast: Roam a client [FA:56:FF:71:A2:98], status [1]
Apr 23 10:45:09 roamast: determine candidate node [3C:7C:3F:45:D8:B0](rssi: -61dbm) for client [FA:56:FF:71:A2:98](rssi: -86dbm) to roam
Apr 23 10:45:12 roamast: Roam a client [FA:56:FF:71:A2:98], status [1]
Apr 23 10:45:24 roamast: determine candidate node [3C:7C:3F:45:D8:B0](rssi: -61dbm) for client [FA:56:FF:71:A2:98](rssi: -85dbm) to roam
Apr 23 10:45:27 roamast: Roam a client [FA:56:FF:71:A2:98], status [1]
Apr 23 10:45:44 roamast: determine candidate node [3C:7C:3F:45:D8:B0](rssi: -66dbm) for client [FA:56:FF:71:A2:98](rssi: -86dbm) to roam
Apr 23 10:45:47 roamast: Roam a client [FA:56:FF:71:A2:98], status [1]
Apr 23 10:45:49 roamast: determine candidate node [3C:7C:3F:45:D8:B0](rssi: -65dbm) for client [FA:56:FF:71:A2:98](rssi: -89dbm) to roam
Apr 23 10:45:52 roamast: Roam a client [FA:56:FF:71:A2:98], status [1]

It seems to be constantly looking at a candidate node to switch to but it's not establishing. I'm literally directly above the mesh system on our second floor. Other devices are in the same location but switched flawlessly.

So, I just need some help or confirmation if my mesh system is working fine and it's my specific device that has an issue?

EDIT: I did factory reset a couple of times with the latest firmware and it keeps happening so I decided to downgrade to 3.0.0.4.386.22245 and the device now switches node seamleslly. Sent feedback to Asus via Web GUI
 
Last edited:

RogerSC

Part of the Furniture
EDIT: I did factory reset a couple of times with the latest firmware and it keeps happening so I decided to downgrade to 3.0.0.4.386.22245 and the device now switches node seamleslly. Sent feedback to Asus via Web GUI

Good luck with that, I've sent Asus several bugs that way and they've not acknowledged anything. Either they don't read the reports that they get, or they play their cards very close to their vests *smile*.
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top