@Vincent-TP 

So, i have been totally re-factoring all my host and remote networks - i needed to add some vlans and change IP and naming schemes as well as tidying up some historical stuff that just gets added or changed on the fly.

What i have noticed is that Client Names, auto-type-identifiaction, and their associated type,vendor,model informations as set by me, easily get set into some kind of "locked" state where the controller either refuses to actually remember what they are set to, or just doesn't actually save the change when i make them even though it gave the successful message.  Client history also seems to stop working as well.

What i think caused this

So I could do all my re-working without interrupting network functions, i created a copy of each site.  On each copy, i made all the changes i wanted to over a period of time.  When ready, i simply "moved" all devices from original site to the new copy, had everything readopt, forced reprovision on everything.   Function wise this worked well, but i think this caused the issued with client data, because once moved, this is when it all started to go wonky.  I could edit a client name and type/vendor/model, but after a while, the controller would reset them to the generic icon.  Client history from this point also ceased - the last data being up to the point if moved hardware to the new site.

turning off client history data to clear it and back on again made no difference.

How i fixed this

I disconnected controller from the network, directly connected it to my laptop and logged into its GUI, went into "known clients" and deleted every single entry.  all of them.

When i rebooted the controller and reconnected it to the network, al client info was reset (as expected) but from this point on i could properly set names and type/vendor/model and it would properly save it.  Client history now also worked correctly from this point.  Auto detection of client types (eg wifi clients) also started working again.

I had to do this for every site that i re-worked.  Bit of a pain, but in a way nice to clear out the old client data as well.

this is mostly just a heads up for TP-Link that maybe they can optimize this in future controller versions.