What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Release RT-AX58U 3004.388.9_2 and device binding problem

ILampa

New Around Here
Hi everyone. I have a strange problem with device binding since upgrading to 3004.388.9_2 on my RT-AX58U. The topology is in an AI mesh with the 58U as the main node and an RT-AC66U B1 running 3004.386.14_2 as the secondary. At some point in the past after upgrading the main node I decided to bind a few devices, which are in the "gray" area distance wise, to the main node. After some time I discovered that ALL devices are now bound to the main node! Trying to unbind them does nothing, both in the WebUI and Asus app on my phone. In other words, impossible to reconfigure binding. Hitting the optimisation for nodes or devices does nothing either.

Has anybody else seen this? Is there a command line option to unbind? Some of the devices are so close to the secondary that they will connect to that node, but show the orange exclamation and hitting unbind does nothing, as mentioned.

1754733608767.png

1754733665860.png
 
Update: After searching a bit better I found an article pertaining to binding and how to "reset".

Command: nvram set sta_binding_list="<AA:AA:AA:AA:AA:AA>1>"
reboot

That cleared the binding list and I can now assign bindings in the UI, both web and app.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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