If I have the list sorted by signal or anything that makes the list jump around and and the same time change a name of a client device it will change the name of the device moved to that row - and not the intended one…
This happens 9 times out of 10… please have a look at this!
Can you take a video to demonstrate this more clearly?
Got it
Im testing to rename a device called “test” with MAC ending with …63ed but ending up changing a samsung tablet with Mac ending with …6810… instead. You can see I have both “testae” (samsung tablet) and “test” (the intended client to change the name of).
It happens all the time if the clients are jumping around and when selecting it and pressing enter it renames the client that is on the current row where it was initiated…
just did a screen-recording and that happened on the first try…
I didn’t check the video but from the description I believe I have came across the same thing also for the very less frequent updates for the IP sort order.
Anytime you open up a device’s Name attribute to change it, it is actually the object/device at the same row at the time of submit that receives the change, not the object/device corresponding to the opened form.
The update frequency for the devices list is likely once per second, so sorting on Signal on a network with a high count of wireless devices will get close to 100% chance of hitting this bug for an attempt to change a device’s name.
I’m able to reproduce this on my local controller. In the meantime, click the device’s icon to the left of its name to edit without risk of the device moving.
This has been resolved on the cloud controller, and the local controller will receive the fix soon, as well. Sorry for the troubles, and thank you for the report!
