@Hank21 This is NOT a reassuring response from TPLink.

1. If it is incompatible with Omada 4 then Omada 4 should not have done an automated update or even allowed a manual update.

2. Your support team has already told me that it should still work with Omada 4 - but instead it breaks the AP. This is a MAJOR bug and this firmware needs to be withdrawn immediately until it is fixed.

3. If you are intentionally going to introduce incompatible versions, which is what you have just implied, then you need to communicate this IN ADVANCE with a major communications campaign so that people can plan for the upgrade (and protect their networks from you in the mean time).

@Protopia-PT Hi, The same at my site.

The Software SDN 4.2.4 does or try to update the 6 AP's to version 5.0.7.

The APs then hung in a boot loop and could only be reached again after a PowerCycle.

A manual downgrade to Firmware Version 5.0.5 eliminated the boot loop.

After upgrading the software SDN controller to version 5.0.29, this problem no longer occurred.

Regards,

Juergen

  @Protopia-PT  OC200 in 4.1.5 version and the bug. TP-LINK may upgrade download page to avoid problem. And if you work in IT from a long time you always know that by default, don't let computer or device upgrade automatically !!!!!!! That's the base of IT :if it's work don't touch !!!!!!!!!

@plavielle As someone who spent several decades in IT (including senior management) then (of course) I would agree with this sentiment in principle. But where the user does not have an IT department and support is only available on an ad-hoc basis, you have to make a judgement about whether it is better to risk issues from bugs and security holes in older versions because you don't automatically update or to risks issues that result from automatic updates - sometimes these choices are not as black and white as you might think.

So, on 13 January I reported this to tp-link including providing details of my Omada version and the previous firmware version, and after a brief exchange of emails I was told explicitly that they would pass this to the appropriate department who would "do some tests according to your feedback".

But their reply to my chasing email today was to ask again what versions of software and firmware I was running, saying that they would pass it to the appropriate department and saying that there were no other reported instances of this problem (whereas I found at least 4 other instances in my search of the forums earlier).

Just what conclusion are we supposed to draw from this regarding the quality anmd trustworthiness of tp-link technical support?