@cpadil If you are having no issues, you should be fine.  The reference to a version 1.6, is probably a typo since there is not a v1.6 listed as released.  This new firmware should show on the support site in the next day or two.

@JoeSea thank you, I also thought the same about v1.6 or maybe a new revision coming(?)

btw, I just noticed a relevant reduction of the CPU usage of the EAP670 with this new firmware.... it's weird that with few clients / traffic the CPU was jumping all over the place...

  @cpadil I have the 650, and it does a similar pattern of CPU usage, and it too has a new firmware from yesterday so it'll be nice if the CPU use goes down too.  I'll find out in a few days, since I wait about a week after new firmware comes out before upgrading.

  @cpadil 

This firmware does have bugs and issues.

We're all waiting for a new firmware release for 650/670 EAPs.

  @cpadil my 650 and 670 updated to 1.0.6 as well. Strange I'm not seeing anything on it.

It was updated through the controller software.

(Is the hardware version able to be seen in omada controller software??)

Seeing an ip missing from a connected device, not sure if it's cosmetic only. I think this behavior is new.. only been up and running like 2 weeks.

  @JS_racer People are upgrading to the new 1.0.6 firmware, but no one is mentioning any bugs.  I just updated mine today, with no issues other than a big decrease in CPU usage, and Dropped and Error packet statistics have fallen to almost zero (maybe they aren't being counted correctly?).

As far as no IP on one client, I have a couple of clients that do that, they don't really have an interface for it and just pass through traffic, so they just show as MACs.  As long as the MAC is there, the client can talk in and out.  Some things to try if you think there should be a an IP, do a hard reload of the webpage (Ctrl + F5 on most browsers), if it's been awhile since the last controller reboot (couple of months), give it a reboot, or perhaps that client's OS is doing something funky.

  @JoeSea 

Got ya... thank you.

The client is a samsung s22 ultra phone. My wife's.. she didn't yell from upstairs it wasn't working,  so I'll chalk it up to cosmetic.  

Everything has been going since the beginning of the month.  Eap have been restarted for different reasons.  Router and controller have yet to be restarted.

Since I'm new, and learning.  If things need restarting, is it the software controller,  and 605 router ?? My first venture into anything like this. Always had an asus router, with a big reboot button in the software.  Heh.  Lots to learn, that's for sure.

Thanks so much for your time 

  @JS_racer What I've learned is that if the network is working and computers are getting the internets, but the Omada UI is showing something odd, then it's good to start by hard reloading the webpage, and then if still not showing, to reboot the controller.  Over the past year, I've seen that software controllers need rebooting more often, and hardware controllers can usually go a couple of months or more.

The router, switches, and APs almost never need rebooting unless something is really weird, especially after a firmware update.

TPLink has also been increasing the firmware update rate, so that also resets things more often, so anymore I don't find myself doing an intentional reboot.  But my first switch (an SG3428MP) went almost 9 months before a reboot, due to firmware update.

  @cpadil 

Hello,

The version numbering strategy on TPLink products is a quite common question ; you will find a lots of threads dealing with it.

You can check this one : https://community.tp-link.com/en/business/forum/topic/515726?replyId=1028626 where a TPLink employee answers the question relative to the R605 ; but I far as I know, the same goes for all products.

As long as the major number matches (digit before the .), there should not be any issue.