Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tapo P300: Smart Plugs Not Syncing in HA #796

Open
KleMic123 opened this issue Aug 28, 2024 · 17 comments
Open

Tapo P300: Smart Plugs Not Syncing in HA #796

KleMic123 opened this issue Aug 28, 2024 · 17 comments
Labels

Comments

@KleMic123
Copy link

I am using a Tapo P300 with the latest firmware and the current version of Home Assistant. For a while now, I have been unable to control the smart plugs correctly via Home Assistant. They are shown as ‘on’ even though they are ‘off’. When I switch them to ‘off’ in HA, it automatically reverts back to ‘on’. What should I do?

@cauchy49
Copy link

cauchy49 commented Sep 9, 2024

I can confirm, I have the same problems.

@hyprodos
Copy link

hyprodos commented Oct 4, 2024

I have the same problem, where can I find the log so we can help to discover where the problem is?

@hyprodos
Copy link

hyprodos commented Oct 4, 2024

To solve the problem, at least momentarily, you can downgrade to v2.14.0. The bug started in v3.0.0. I hope this will help to pinpoint where it was introduced.

@millenniumy2k
Copy link

Same problem, switches don't update state

@acamar80
Copy link

Same problem here. Waiting for a fix.

@KleMic123
Copy link
Author

downgrade to v2.14.0

Downgrading to v2.14.0 didn’t work because all Tapo sockets could no longer be controlled. I think this is because v2.14.0 doesn’t support the current Tapo firmware.

@Ninfus
Copy link

Ninfus commented Nov 9, 2024

Same problem with Tapo v3.1.2 😢

@TheSpoon98
Copy link

Just adding to the confirmation - though I have a TP25 (outdoor plug) that has the same issue.
Tapo Device: TP25
Hardware Version: 1.0
Firmware Version: 1.1.3 Build 240604 Rel 150844

Tapo Integration Version: 3.1.2

HA Version: 2024.11.3

@freire-nuno
Copy link

I Have the same problem with my P300.
Any expectation to fix this?

@Orishas
Copy link

Orishas commented Dec 20, 2024

Same here P300, does not work anymore

@TheSpoon98
Copy link

Running it lately - I've noticed that it only gets stuck in the "on" state. If I reset HA, the initial read is correct - if it's on, I can't turn it off - if it's off it can turn on.

Currently on HA 2024.12.5

@psm-psm
Copy link

psm-psm commented Jan 2, 2025

Same issue. HA 2024.12.5, P300 V1.0.16, Tapo 3.1.2.

The state of each socket being reported in HA is the state it was in when the device is seen by HA when it connects. It will be reported correctly in HA initially. If any socket state is changed by pressing a switch on the P300, HA will not report the change. If a socket state is changed from HA, it will activate the socket and display the change for 2 seconds in HA, then HA reverts to reporting the initial state.

E.g. Restart HA with Socket 1 off, Socket 2 off and Socket 3 on. HA will show S1 = off, S2 = off, S3 = on.
If I change S2 from HA, then S2 will physically turn on, then HA will show it as on for 2 secs, then it will show it as off (s2 will still physically be on). Turning on S2 again from HA will change the indication in HA to on for 2 seconds before it reverts to showing off with no change in the physical state of the socket. However (still with S2 physically on and HA showing off) , turning on S2 again from HA, HA will show on and if I turn it immediately off from HA while HA is showing it as on (in the 2 second window before it reverts to showing off), the device will turn off.

The same, but in reverse, happens with a socket that was initially on when first connected to by HA. In the example above, S3 will always revert to showing as on, even when it has been turned off.

I also have P110 and P110M plugs and they work perfectly.

@KleMic123
Copy link
Author

Same issue. HA 2024.12.5, P300 V1.0.16, Tapo 3.1.2.

The state of each socket being reported in HA is the state it was in when the device is seen by HA when it connects. It will be reported correctly in HA initially. If any socket state is changed by pressing a switch on the P300, HA will not report the change. If a socket state is changed from HA, it will activate the socket and display the change for 2 seconds in HA, then HA reverts to reporting the initial state.

E.g. Restart HA with Socket 1 off, Socket 2 off and Socket 3 on. HA will show S1 = off, S2 = off, S3 = on. If I change S2 from HA, then S2 will physically turn on, then HA will show it as on for 2 secs, then it will show it as off (s2 will still physically be on). Turning on S2 again from HA will change the indication in HA to on for 2 seconds before it reverts to showing off with no change in the physical state of the socket. However (still with S2 physically on and HA showing off) , turning on S2 again from HA, HA will show on and if I turn it immediately off from HA while HA is showing it as on (in the 2 second window before it reverts to showing off), the device will turn off.

The same, but in reverse, happens with a socket that was initially on when first connected to by HA. In the example above, S3 will always revert to showing as on, even when it has been turned off.

I also have P110 and P110M plugs and they work perfectly.

It's the same for me. It would be great if there were a solution for this soon.

@psm-psm
Copy link

psm-psm commented Jan 3, 2025

After some more digging, I found the inbuilt TP-Link Smart Home integration
and added the P300 to that one rather than the Tapo integration from HACS.
The P300 is now working as expected.

@KleMic123
Copy link
Author

After some more digging, I found the inbuilt TP-Link Smart Home integration and added the P300 to that one rather than the Tapo integration from HACS. The P300 is now working as expected.

Thanks for the tip, it works 🙂

@acamar80
Copy link

acamar80 commented Jan 3, 2025

Same here. It works. Thanks 😉

Copy link

github-actions bot commented Feb 2, 2025

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

10 participants