windkh / node-red-contrib-telegrambot

Telegram bot nodes for node-red.
Other
267 stars 119 forks source link

node registered twice - misconfig or only informative? #87

Closed ozett closed 4 years ago

ozett commented 5 years ago

i use one telegrambot, but i use one node with the bot-config in the upper half of my flows-page, and another node with the same bot-config further down. gives my flow-page more structure. better readable. but so i have the same bot as two nodes on my flow page.

and get a notification message. looks like a error-warning. can i get rid of this? is there a better way to configure this?

image

windkh commented 5 years ago

Normally you should not get this warning. But that could gappen when you do not a full deploy. You can ignore this message

ozett commented 5 years ago

i get this "registered twice" notification after importing example-flows from your github (as the links to the examples on npm-site are broken).

i.e. this: https://github.com/windkh/node-red-contrib-telegrambot/blob/master/examples/inlinekeyboard.json

if i import it, and aply changes, i get "registered twice" notification . if i than go into the bot-config and change only the name, and save this, than the message is cleared and goes away. (i also delete the imported heinzbot and any other bot-config, just leave my own bot-api in)

image

ozett commented 5 years ago

it seems to me, that duplicating a command-node has the same effect. if i change the name and save the one and only bot i have, the duplicate information is gone. no error anymore

ozett commented 5 years ago

unsolved before: https://github.com/windkh/node-red-contrib-telegrambot/issues/67

windkh commented 5 years ago

.... the warning clearly states that this can be ignored. I will remove the log as it only causes confusion

ozett commented 5 years ago

cant we find the duplicate? i will search as much as i can? 😃

my impression it, it comes from copying telegram-nodes or importing telegram-flows...

windkh commented 5 years ago

When a node is created it registers itself at the config node. The config node issues the warning when a node registers itself twice. That happens when you do not fully redeploy.

windkh commented 4 years ago

removed warning