@Kevin_Z   I do not detect if there is a disconnection and connetion in milliseconds of any of the devices, which may be cause for notification. II do not know the cause.

@Kevin_Z I don't have 'proof' of the notifications received for the same device at the same time at the moment, I was to late and the timestamps changed to yesterday and I deleted them. If I encounter it again, I will post it!

To be fair, with previous firmware/updates this wasn't an issue and I can assume TP-Link has far greater resources to test these kind of bugs .

It happend occasionally on previous updates though, but this is insane. Luckily it is only in the app itself and it doesn't give me push notifications to my phone (which is weird because I have it turned on). 

@Derek_76 

Ah ok no I can't select. Never used that before. I'm on android.

Come on tplink. I think it's about time you release a rollback 1.41 firmware whilst you spend some time fixing and then actually doing some proper QA before you release.  I mean we have waited 8 months since the last firmware so really you've had more than enough time to properly release the updated code.  Pretty disappointing tbh

If I were you I'd open up a beta line of fw updates for those who want to test and let them have the ability to rollback the firmware to previous builds if needs be.

@thefunkygibbon agreed - this firmware is horrendous - should never have been released. Has there been any testing?

@Kevin_Z 

Unfortunately only have Android devices in house.  Any time frame on when the issue will be fixed?  The update doesnt look to be very well tested.

@Kevin_Z works for me now. YAYYYYYYYYYYYYYYYYYYYYYY. Will observe if there are any other issues.