Downgrade firmware for P110, new version buggy

A new firmware has upgraded some of my Tapo P110 plugs (1.3.4 Build 250403 Rel. 150504). The previous version was 1.3.1 Build 240621 Rel. 162048.
This version causes some problems in a specific case:
I have an automation process which detect a movement from a T100 captor and switch on for 5 minutes a solenoid valve. After this 5 minutes the valve is switched off.
Everything is ok with old firmware but, with the new one, the automation is executed, and few seconds later the T110 plug is reset and need to be reconfigured for the same result at the next execution. Hopefully I've found a plug with the old firmware without this bug. I disabled auto updates for all my Tapo modules.
I think you didn't test every cases. Why don't you begin by a beta test phase before crash our system by these bad upgrade.
Thanks for an urgent fix or a method to rollback my installation.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks for the informations. No these firmware aren't public and support has to affect them to your MAC Addresses to receive the update.
Mine is 1.3.4 Build 250520 Rel 153523.
- Copy Link
- Report Inappropriate Content
I continue to suffer random intermittent issues with the device losing configuration, which I then have to set up as a new device via the Tapo App.
This is after I've tried the different firmware releases TP-Link support has provided.
Using the power button on the left side of the smart plug seems to cause a random chance that the configuration will be lost. Most often when turning off, but I've had it at least once when turning it on.
I have been testing whether I get issues if I use the Tapo App to power on and off the P110 smart plug. And so far, that has been working fine, and the smart plug turns off and on without loss of configuration. I've passed this information, along with flashlog file, back to TP-Link technical support and am waiting for any update from them.
- Copy Link
- Report Inappropriate Content
TP-Link have supplied me with another new firmware (1.3.4 Build 250527 Rel.110651) which I've tested.
Testing the P110 v1.0 hardware smart plug's power on and off showed no issues with loss of configuration, and the button press itself was back to as before - just a short press to power off/on.
However, I cannot provide TP-Link support with the flashlog file, as any request to the embedded web server responds with a "200 OK" message. Suggesting something has changed or is not working for that element in this test firmware.
I think progress is being made, at least for my issue, but I can't quite confirm things are fully fixed.
- Copy Link
- Report Inappropriate Content
OK good news. For my part they provide me a debug firmware for one P110 Plug but I am unable to reproduce the bug I had 2 days ago on the 1.3.4 production version... It's a crazy random bug....
- Copy Link
- Report Inappropriate Content
TP-Link tech support has confirmed to me that they removed the flashlog function in this latest firmware because they have identified the root cause of the problem and fixed it.
I've been asked to monitor my plugs to see if I see any further issues.
So far, for me on firmware 1.3.4 Build 250527 Rel.110651, everything seems to be working again.
I now need to apply it to the remainder of my P110 devices, as some are set not to automatically update the firmware as they're supporting key devices that are on 24/7.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Glad I found this thread, I have the same issue on my P110, I'll check the firmware version when I get home.
I hadn't noticed it was connected with switch off, but that makes sense, and certainly was the case this morning.
- Copy Link
- Report Inappropriate Content
MazzaUK wrote
Glad I found this thread, I have the same issue on my P110, I'll check the firmware version when I get home.
I hadn't noticed it was connected with switch off, but that makes sense, and certainly was the case this morning.
What appliance is connected to your P110? If the problem is replicable and persistent, please send me the Mac address of the plug through a private message.
- Copy Link
- Report Inappropriate Content

For the issue reported in this thread, the relevant optimizations are planned in the next official firmware.
- Copy Link
- Report Inappropriate Content
Ok thank you for the information. So finally you managed to reproduce the case?
- Copy Link
- Report Inappropriate Content

Information
Helpful: 7
Views: 2920
Replies: 37
Voters 1
