I use node-red-node-pushover quite a lot, and find it frustrating that instead of the node saving it's credentials in a store (like most other nodes), I have to log into the pushover website and copy and paste the user-key and api-token from my user account, even if the new node it in the same tab as other pushover nodes.
The credentials can't be copied from one node to another because the api-token is hashed...
We don't have to do this with pushbullet, dropbox, darksky etc....
Any chance of a node update?
Paul
Or use a link node to feed them all into one node ?
I've created a subflow containing the pushover node + input and replaced all pushover nodes by the subflow.
Both good ideas, but it would mean prefixing each link node/subflow with a change node to set the priority, device etc, unecessarily increasing the node count.
Also, from a security perspective, shouldn't credentials be encrypted and safely saved in the store?
I assume they aren't at the moment.
No they are stored in the store. It's just that the node doesn't use a config node - that can then be shared between others.
