Account details for TAPO control node (tapo-new-api)

I'm testing the node-red-contrib-tapo-new-api node (to replace my Python script) and entering my email and password each time I want to add a node to the flow - this is fine but I will have a fair number of nodes over different flows and both the email and password is long (and complex in the case of the password).

Looking at the help text, it states:

email string
If set this property overrides the one specified in the configuration node. It specifies the username of the Tapo account...
password string
If set this property overrides the one specified in the configuration node. It specifies the password of the Tapo account.

It would be really handy to set these values in the configuration node but I have zero idea where this 'configuration' node is as the picker only shows the 'actions' node.

I have looked at the examples (the email / passwords are blank) and there does not seem to be a way to raise an issue on GitHub so I thought I would try here.

My Node Red is out of date (v3.1.0) and I could update (fair amount of work TBH) if that fixes things.

This refers to an input passed in as msg.email, or maybe it's msg.config.email

And this refers to the email and address fields in the TAPO actions node (which will be blank until you fill them in!)

You could setup environment variables for the TAPO email and password.

To use these put eg $(TAPO_EMAIL) in the email field of the TAPO node.

Maybe its the way I'm reading it but I feel there should be a config node somewhere that sets these up :slight_smile: possible 'node configuration' would have been a better way of describing it in the help text?

TBH - I'll experiment with the environment options as I may end up sharing these flows and do not want my password floating around...

Could be a good chance to try the newest version as well.

With some nodes, eg MQTT-in & out, dashboard widgets etc there is indeed a config node created and if you delete the node that uses it the config node gets left over unused.
The TAPO node does not seem to behave like this though.
Yes "node config" would be better wording.