P110 firmware 1.4.6 Build 260309 Rel 093810 issue

[andy0503]

Hello,
One of my P110 plugs has autoupdated firmware from 1.4.0 to 1.4.6 and will no longer communicate with the library.
I am using the tapo-rest api by ClementNerma which i understand is built using your library.

The tapo-rest api has been updated to include the latest revision of your library but still no luck.

this is the log file from this app

Now launching server...
Attempting to connect to the 2 configured device(s)...
Device url: http://192.168.140.15/app
Testing the AES protocol...
Component negotiation request: {"method":"component_nego","params":null}
starting new connection 'Some("192.168.140.15")'
Device url: http://192.168.140.16/app
Testing the AES protocol...
Component negotiation request: {"method":"component_nego","params":null}
starting new connection 'Some("192.168.140.16")'
shouldn't retry!
! Failed to connect to device 'sp1': Failed to connect to P110 plug 'sp1': error sending request for url (http://192.168.140.15/app)
shouldn't retry!
Device responded with: TapoResponse { error_code: 1003, result: None }
Not supported. Setting up the KLAP protocol...
Performing handshake1...
shouldn't retry!
Handshake1 OK
Performing handshake2...
shouldn't retry!
Handshake2 OK
Established a connection with device 'sp2'!
|> Device sp2 connected successfully!

The plugs are online and both respond to pings.
Any ideas how to fix it ?

[andy0503]

i have completed a port scan on my two devices. I looks like the new version of software 1.4.6 doesn't have an open port 80 anymore

[mihai-dinculescu]

Hi @andy0503,

Firmware 1.4.6 is supported and should continue to work with the library.

The most common issue is that Third-Party Compatibility is not turned on in the Tapo app. If it's already enabled, try switching it off and then back on again. You can find this option by navigating to Me → Third-Party Services in the app.

Let me know how it goes.

[andy0503]

Hello,
I can confirm that Third-Party Compatibility mode is switched on. I have tried turning off and then back on.
As a quick test, I have use a chrome browser to nagivate to a device with firmware 1,4.0 i.e http://192.168.140.16/app, i get 200 OK in the window. If i do the same test with a device on firmware 1.4.6 the browser returns "time out". Using Port scan (nmap) for these two devices, the old version of firmware returns an open port on 80 (http), the new version doesn't have an open http port.

[mihai-dinculescu]

The device not responding to HTTP requests at all is the smoking gun. It should continue replying 200 OK after the upgrade.

I have a large number of plugs working on this firmware version, and so do many other users of this library. So the issue must be with that particular device itself rather than with firmware 1.4.6 in general.

I'd suggest resetting the device to factory settings and setting it up again in the Tapo app.

[fberndl]

I have the same problem, could you resolve it?

[andy0503]

Yes, i had to factory reset the plug that was having issues. It went back to the original firmware that was installed. Removed from the app, then added the device again (with the same name), it picked up the events/schedules and reapplied these. Then remeber to toggle 3rd party integration. All other devices upgraded ok, without needing to be factory reset. Dont know why this one device had trouble.

…

Sent from my Galaxy

-------- Original message -------- From: Florian Berndl ***@***.***> Date: 01/07/2026 12:01 (GMT+00:00) To: mihai-dinculescu/tapo ***@***.***> Cc: andy kennerley ***@***.***>, Mention ***@***.***> Subject: Re: [mihai-dinculescu/tapo] P110 firmware 1.4.6 Build 260309 Rel 093810 issue (Issue #577) [https://avatars.githubusercontent.com/u/22743272?s=20&v=4]fberndl left a comment (mihai-dinculescu/tapo#577)<#577 (comment)> I have the same problem, could you resolve it? — Reply to this email directly, view it on GitHub<#577?email_source=notifications&email_token=ANHCX3IFMTFLBNQYCG5CR635CTVM3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBVGM3DCOBRGQ22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4853618145>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANHCX3LQ5EPF4BEIRYMPYKD5CTVM3AVCNFSNUABFKJSXA33TNF2G64TZHM2TAMBWGI2TANJXHNEXG43VMU5TINRTGM2TONJUHAY2C5QC>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/ANHCX3LANA4IQEMKCONMSO35CTVM3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBVGM3DCOBRGQ22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/ANHCX3MILG4K63B5JJLWKX35CTVM3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBVGM3DCOBRGQ22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[pobkac]

See Degix's sollution
https://gist.github.com/Degix/9d9e30850f39428c99853f5be1d3c8be
my understanding that the key symptom is that the webserver on the plug http:\DeviceIP:80 is not running.
Degix has identified this and has a script that fixes it.
In my case I was just able to rescan from the Tapo app and this activated the devices webserver so it started working again.

[mihai-dinculescu]

@pobkac Thank you for the contribution, and thanks to @Degix for the script. That's a very useful finding.

Worth pointing out: if sending the discovery traffic is what brings the device's web server back, then running the tapo_discover_devices.rs example should fix it as well, because it sends the very same discovery packet.

[mihai-dinculescu]

Thank you all for the investigation and contributions!

This has now been documented in the new Troubleshooting guide, including the symptoms, the cause, and the recovery steps.

Closing this as resolved.