Single Tapo P100 not working, another works fine, both work with app

Add-ons Bindings
1

Running openHAB 4.2.1 with Tapo binding 4.2.1 from the add-on store, on Raspberry Pi. I have multiple Tapo smart plugs, including two P100s. Both work perfectly in the Tapo app, but one (which worked fine until about a week ago) gives a permanent " COMMUNICATION_ERROR device offline (9009)" in openHAB. Nothing showing about it in the log at all except “Thing ‘tapocontrol:P100:c43d71e9f9:d9b5e80f42’ changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): device offline (9009)”.

Both P100s have identical firmware version (1.2.5 build 240411). IP address is correct and protocol for both is set to Secured KLAP HTTP Protocol. Problem has persisted through removing and installing binding and updating the entire operating system.

Any suggestions? At my wits end!

EDIT TO ADD: Upped logging for the Tapocontrol binding to Trace, only got the following:

2024-09-14 14:24:02.619 [TRACE] [l.devices.wifi.TapoBaseDeviceHandler] - (tapocontrol:P100:c43d71e9f9:d9b5e80f42) schedulerAction
2024-09-14 14:24:02.621 [DEBUG] [l.devices.wifi.TapoBaseDeviceHandler] - (tapocontrol:P100:c43d71e9f9:d9b5e80f42) check if logged in but is not
2024-09-14 14:24:04.624 [DEBUG] [rol.internal.api.TapoDeviceConnector] - (tapocontrol:P100:c43d71e9f9:d9b5e80f42 / DeviceConnector) no ping while login '192.168.1.207'
2024-09-14 14:24:04.626 [DEBUG] [rol.internal.api.TapoDeviceConnector] - (tapocontrol:P100:c43d71e9f9:d9b5e80f42 / DeviceConnector) handle error '@text/error-binding-device-offline [ "9009" ]'
2

The plot thickens - I’ve tried just pinging the plug and every other device in the house can ping it except that Raspberry Pi, which in turn can ping every other device except this plug. I genuinely have no idea how that can be the case. Nothing set on the router that could be causing it, they’re both connected by wifi to the same router. Guess this probably isn’t an Openhab issue but if anyone’s got a suggestion I’m happy to hear it!

3

I face the same problem since two or three days. I think it comes from firewalling - I need to investigate why the ping done in code is blocked.

The code implied is this one : openhab-addons/bundles/org.openhab.binding.tapocontrol/src/main/java/org/openhab/binding/tapocontrol/internal/api/TapoDeviceConnector.java at 0e1b4481a55d8e5cf6d80f000f2b1e09c047e397 · openhab/openhab-addons · GitHub

4

I sorted my issue by doing:

sudo setcap cap_net_raw=+ep $(readlink -f $(which java))

This let java issue ICMP packets without being root.

5

I’ve got the same problem. I have two P100 sockets; one works, the other doesn’t. I then checked via the Tapo app. The one that wasn’t working was up to date, and the one that was working needed an update. I installed the update, and now neither of them works anymore. I found the solution here. Tapocontrol Communication Error - COMMUNICATION_ERROR invalid http-response (9001) - #12 by stefan13

6

Thanks for the tip -I had the same problem after updating an L530 lamp.

7

I’m getting an error for P115 after doing the upgrade from 1.4.0 to 1.4.6.

COMMUNICATION_ERROR cant create handshake (1100)

I already enabled the 3rd Party Service option - and bounced the option as well - but without success.

P110 and P115 with 1.4.0 are working fine, but 1.4.6 are failing to connect.

Any idea?

8

I have two P300 power strips and also ran into the COMMUNICATION_ERROR problem after FW update. I use OpenHAB 5.1.4

I tried the 3rd party support workaround with the Tapo App on my Android smartphone: did not help. Then I installed the Tapo App on an iPad, enabled the 3rd party support from there – and voilà: the power strips went Online in OpenHAB.

Not sure if this is just coincidence or pure luck, but since then both P300 are Online in OpenHAB.

Hope that helps.

Regards,
Dietmar

9

Did work for me unfortunately. I disabled the 3rd Party option in the Tapo App in my iPad. After some seconds all Tapo Things in OH5 went in error condition.

Then I enabled the option again and waited for the Things to become online. This worked for all, except the P115 with 1.4.6 software running.

@glhopital any idea?

10

No, sorry, last time I has this issue, I disabled/reenabled 3rd party option and things went back ONLINE.

11

I found this bug report, with a workaround to get the device temporarily working again. I will check it. Maybe the link is useful for users.