I am following this Echo Bot Tutorial, and have gone through all of the basic steps regarding setup and registration. I am following the steps (near the bottom) regarding local testing, and have been using ngrok successfully.
I was able to add my Skype Bot as a contact, and I also have the latest version of the Skype app (Mac). When I send a message to the bot via the Skype app, I see the message appear in the debug notes in my terminal window. So I know that the messages I type are coming through.
I also see this:
skype-sdk.MessagingServiceClientV2 Sending message to 8:username with content Hey 8:username. Thank you for your message: "test".
However, I do not see any kind of reply in my Skype application. My expectation is that the bot would echo back my message to me.
My questions are:
1) When testing locally using the ngrok method described in the tutorial, should I be able to see activity from the Skype bot (in terms of messages to me)?
2) I am guessing this may be some an authentication issue? How can I best troubleshoot things, and get the Skype bot to actually respond in the Skype app?
I feel like I am incredibly close to getting this working, in that the messages I send are coming through... but the messages I expect from the Skype bot are not coming through. Any help or ideas greatly appreciated!
Found the fix, and posting it here should anyone else run into the same issue.
During the setup process, when I was using the Application Registration Portal, I selected the wrong string as my Application Secret.
Originally, I clicked on Generate New Key Pair, which resulted in a new entry appearing in the admin labeled Private Key. I used this string as my App Secret.
However, it appears that what I should have done was click on Generate New Password and used *that string instead**. Just gave it a try, and my bot is now responding back to me locally (in the Skype app), when testing with ngrok.
I think this particular distinction could have been made clearer in the documentation, as I lost a great deal of time due to this one oversight. Oh well, at least I can start developing now...
Related
I’ve been running a MS Teams bot without issues for about half a year now. It is written in Python, using the bot builder SDK, and connected to Teams/Azure via ngrok. Users use it by clicking on the link, which opens up the chatbot in their Teams app (desktop or mobile).
Out of a sudden, some time on 3rd Feb 2023, the bot started having issues sending replies out. And reports a “404 not found error” in ngrok. There’s been no changes to the chatbot’s code.
To be clear, the bot is able to receive the user inputs, but fails to send the replies out.
Would anyone know why?
Finally found the answer. The app secret value expired and simply needs to be renewed. I had suppressed the trackbacks, not expecting that I would one day miss this.
I am developing chatbot for Slack using Microsoft Bot Framework. The Web app is hosted on azure. We have few installations.
Everything worked fine before this morning when I saw that new bot just didn't respond (the old one is still working).
We've been experimenting on permissions and auth keys on slack, so I thought that was the reason. But I tried to reinstall the app, bot user, auth keys etc from scratch and it didn't help. My configured endpoint just don't hit.
I think the issue is in communication between Slack and Microsoft Bot Framework, 'cos when I'm testing from chatbot panel's web client everything is working fine. Also, Slack representatives confirmed that there's no problem from their side.
UPDATE: I re-checked all credentials again and seems like it's working, don't know what was the issue. But two side questions still actual:
1) Can I test this channel of communication somehow? Cos when my endpoint didn't hit I can't get any info on what is happening. I have 0 errors on Microsoft Bot Framework web console.
2) Docs on configuring slack channel have changed recently and now it suggesting to add "Subscribe to Bot Events", while everything worked w\o it. Can you elaborate on that? Also, it's not quite clear what is {YourBotHandle} docs referring to in https://slack.botframework.com/api/Events/{YourBotHandle}
Usually, the Bot Framework Portal is the place to see if any channel is reporting errors with your bot. You can also check https://github.com/Microsoft/BotBuilder/issues just in case there is a general problem with a channel.
Regarding the second question, {YourBotHandle} refers to the handle that you provided at the time of registering your bot, as explained here.
As far as why you need to subscribe to bot events, first I would recommend you to read the documentation about Events on Slack (here), but long story short, this allows the bot to subscribe to events and be notified when those happen instead of having the bot asking Slack if something happened or not.
One way to use the Events API is as an alternative to opening
websocket connections to the real time messaging API. Instead of
maintaining one or more long-lived connections for each team an
application is connected to, you simply set up one or more endpoints
on your own servers to receive events atomically in near real-time.
Firstly I want to say I am a novice to programming. But I want to learn. I do know logic and want to make things for myself using Node Red for IoT.
I was trying to figure out how do send messages to and from telegram through node red. So that once I can do that I can connect other devices that can listen to my messaged from telegram and be controlled via node red and vice-versa.
Here's what I have already done so far.
1. Installed both of the following modules in Node red
TelegramBot and Redbot(chatbot) via NPM and for this example I am using Redbot to send my message.
2. Setup a telegram bot successfully and got my API key for the bot
3. Got my API key and ChatID (which was really a Pita BTW)
4 I followed guide - https://www.npmjs.com/package/node-red-contrib-chatbot to setup my Node Red Flow. the basic flow which looks like this. NodeRed Flow
But my problem is when I send anything from my Telegram bot, NodeRed pick up something as I see the "Debug tab" updating. But it only says
"msg : string [44]Unable to find context().global in Node-RED"
When I click the error it takes me back to the instance of Telegram I setup already.
I know I am doing something wrong here but what is that I am just not sure. Can someone help. I am sure I am missing something very simple.
There is an open issue for this problem on the package's github page:
https://github.com/guidone/node-red-contrib-chatbot/issues/28
And a what looks like a pull request that will fix it:
https://github.com/guidone/node-red-contrib-chatbot/pull/29
Hi I got my bot approved and the app is live to the public, but it only sends responses to me. Please help. Im a beginner and not sure what's wrong
Update: Please see Messenger Bot Fails to Respond
Perhaps a bit late but perhaps this will help. I just got my bot approved today. In the App Review panel, I now see that 'pages_messaging' is enabled. Also, under the 'Messenger->Setting' I see 'Bot Ratings'. The bot appears to be open to the world as several people have accessed it.
http://messenger/t/dynamicmemorysolutions
please verify if your app is available to the general public.
Follow these steps:
Login to your facebook developer console.
In Basic settings provide an email.
In App Review switch to YES (general public)
In Roles section you can also define test users in order to verify that your Bot is working as expected.
Regards
I have been playing around with the Kik bot framework using Node and have a bot to chat with. I am using the onTextMessage event successfully, but have yet to get the onStartChattingMessage to fire. The docs are not very detailed, any idea when this gets invoked? I thought it would be when I start a new chat with the bot but that doesn't seem to be it. Or I am just holding it wrong. Code is on GitHub at https://github.com/jcapka/otherword/blob/master/server.js
Per https://dev.kik.com/#/docs/messaging#start-chatting this only happen
Under normal circumstances, you will receive this message once
when user that starts chatting with you for the first time.
If you are trying to get it to work but using the original username you have already chatted.
You'd have to make a new account to be able to get the first-time experience and have that StartChattingmessage
As an example I went and messaged your bot and I got this response `