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 P110 does not work after firmware upgrade #38

Open
taaning opened this issue Nov 27, 2023 · 14 comments
Open

Tapo P110 does not work after firmware upgrade #38

taaning opened this issue Nov 27, 2023 · 14 comments

Comments

@taaning
Copy link

taaning commented Nov 27, 2023

Tapo P110 does not work after firmware upgrade from Version 1.2.3 Build 230425 Rel. 142542 to Version 1.3.0 Build 230905 Rel. 152200

News for Version 1.3.0 Build 230905 Rel. 152200
Modification and Bug Fixes:

  1. Improved stability and performance
  2. Enhanced local communication security

Here is the output from the Status Node on the new version:
27.11.2023 17.15.43[node: debug 2]
msg.payload : Object
object
result: false
errorInf: "Error: Unexpected Error Code: 1003 (undefined)"

@einfach113
Copy link

Unfortunately I have the same problem. I have already deactivated the autoupdate of the firmware and hope that this can still be fixed?

@joside
Copy link

joside commented Nov 29, 2023

There is a new encryption protocol used, found this here: https://community.openhab.org/t/single-tapo-p100-suddenly-stopped-working-error-code-1003/149740/3

@joside
Copy link

joside commented Nov 29, 2023

BTW, possible duplicate of #33

@einfach113
Copy link

Hi joside, sorry i dont´t use openhab or any other Smarthome-System. i work only with node red and the node-red-contrib-tplink-tapo-connect-api file. Can you help me integrate these changes into my palette? Unfortunately, I'm not a programmer and don't know much about it

@joside
Copy link

joside commented Nov 29, 2023

Hey @einfach113,

Sorry, I am also just a user of this plugin. But I found out, that this firmware change is the reason for it. And that there is a duplicate ;-)

I hope that there will be a fix soon, I am using it for my washing machine to notify me when ready...

@einfach113
Copy link

Ok, i also use it to check if my car is laoded and to see how much cost i have

@taaning
Copy link
Author

taaning commented Nov 29, 2023

I have moved everything to Home Assistant for now, but i like to keep it in Node-RED because i just like Node-RED, and find it easier to use than HA, so i really hope there will be an update, but this repo hasn't been updated for a long time, so i has not much hope, if i could i would be happy to help, but i am not a programmer.

@paul-thomas1964
Copy link

I’ve got the same problem following the firmware update. I also have an integration of tapo into hubitat and this has failed too.

@ValeGreenEnergy
Copy link

Same problem, The p110 doesn't work after the update.
Are there already any solutions?

@taaning
Copy link
Author

taaning commented Dec 16, 2023

Same problem, The p110 doesn't work after the update. Are there already any solutions?

There is a workaround, i have not tried it myself, as i have moved all the Tapo P110 functions from Node-red to Home Assistant.
#33 (comment)

Hoping this will be fixed.

@paul-thomas1964
Copy link

If you have hubitat, and you still want to use the devices in nodered there is a solution.
You can install the hubitat to nodered app, this can make the selected devices in hubitat (including the tapo devices) available to nodered.
I have a nodered app which graphs power usage from my p110’s, it was easy to change over to the hubitat version of the devices.

@Goulash667
Copy link

I have same issue, some of my P110 plugs are updated and not working via Nodered... I´m using energy monitoring and ON/OFF function. I´ll try workaround, but this node was just perfect.

@joside
Copy link

joside commented Jan 20, 2024

I switched to this fork now, after updating my node version it works again:
https://github.com/mbserran/node-red-contrib-tapo-new-api

Thanks for the work!

@anttiryt
Copy link

It seems the new-api interace requires node-15.0 since 0.45. Has anyone tested 0.40 with node-14 ? I'd like to know if the node-15 dependency was forgotten in 0.40 or if it is only needed 0.45 onwards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants