Trigger message from "external"

[guidone]

Trigger message from "external"

[guidone]

You have to use a Conversation node, you have to specify the chatId, every conversation bot-user has a unique chatId, you can discover it with the Debug node

Yes a tutorial about that would be useful

[ScuttleSE]

Hrm... seems to need something more than Conversation.

This is the flow I just created:

I get the error "This node is not available for transport: null" and it seems to be attached to the Message-node

[guidone]

You're right, it doesn't get the right transport anywhere.
I'm fixing it

[guidone]

OK @ScuttleSE grab version 0.5.10, you can select the transport with a drop down in the conversation node configuration

[ScuttleSE]

Worked just fine.

[marcostrullato]

Hi, I still have the same issue. I'm using 0.6.24.
Is it maybe a regression?

Thanks

[guidone]

It should work fine, there are tests for this

https://github.com/guidone/node-red-contrib-chatbot/blob/master/test/conversation-node.js

Is it possible that in your flow there's a function node that strips away this information?
Is it a flow that you can export here so I can look at it?

[marcostrullato]

Hi, I exported a test flow: it might be I'm wiring the nodes incorrectly.. let me know :-)

Thanks

[{"id":"3eee808b.b2679","type":"chatbot-telegram-send","z":"d7d606ad.3dd17","bot":"","track":false,"outputs":0,"x":1004.0079905192058,"y":469.714243888855,"wires":[]},{"id":"ff020ecc.28235","type":"function","z":"d7d606ad.3dd17","name":"alert via telegram","func":"msg.payload = 'Internal temperature reached X degrees!';\nreturn msg;","outputs":1,"noerr":0,"x":560.7143046061199,"y":379.99997901916504,"wires":[["a7fc7867.cc4928","838af521.57fb"]]},{"id":"838af521.57fb","type":"debug","z":"d7d606ad.3dd17","name":"","active":true,"console":"false","complete":"payload","x":803.0952402750652,"y":505.23806858062744,"wires":[]},{"id":"19b1e786.460328","type":"chatbot-telegram-receive","z":"d7d606ad.3dd17","bot":"","x":148.83332061767578,"y":295.6666564941406,"wires":[["f648f9c6.855dd8"]]},{"id":"f648f9c6.855dd8","type":"chatbot-conversation","z":"d7d606ad.3dd17","name":"conversation","chatId":"xxxxx","transport":"telegram","x":347.50000508626306,"y":333.3333088556925,"wires":[["ff020ecc.28235"]]},{"id":"a7fc7867.cc4928","type":"chatbot-message","z":"d7d606ad.3dd17","name":"","message":[""],"answer":false,"track":false,"parse_mode":"","x":809.1666475931804,"y":411.66664028167725,"wires":[["3eee808b.b2679"]]},{"id":"1e4700ac.2e9ba7","type":"inject","z":"d7d606ad.3dd17","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"x":163,"y":460.33331298828125,"wires":[["f648f9c6.855dd8"]]}]

[guidone]

Just remove the first empty text of the text node

TL;DR

The message node uses the input payload only if the message field in the configuration panel is empty, the bug is that a list with just an empty element is considered not empty.

I've already fixed the bug in 0.6.25-beta-1, but you don't need to install this, just remove the empty element

[marcostrullato]

Great! it works!

Thank you