Would it be possible to check the bots access token and throw an error if the token is wrong?
If you want, I could develop this little extension and submit it as Pull request.
Are you interested?

I noticed you removed the stream parameter from the multipart method. Filepath as parameter is more user friendly but I am missing the stream parameter since I download files and forward it to Telegram.

I quick and dirty patched it like this for now:

//    var file = options.files[key]
//     , filename = path.basename(file)
//      , stream = fs.createReadStream(file);

var file = options.files[key];
var stream = file.stream;
var filename = file.filename;

A nicer way to handle stream as parameter would be great

There is a problem with _poll when messages are edited before being read.

msg.message is missing when a message is edited, msg.edited_message is available

I've provided a very quick fix. But you might want to do something more comprehensive.

Bot.prototype._poll = function () {
  var self = this;

/* Some Code */
              if (self.parseCommand) {
////////////////////////////////////////////////////////////
// QUICK FIX HERE
////////////////////////////////////////////////////////////
// a quick fix because msg.message is missing when a message is edited, ...
// but msg.edited_message is available
// put this where you think it makes sense
if (!!msg.edited_message) {
  msg.message = msg.edited_message;
  console.log("Monkey Patch for Edited Messages:", msg);
}
////////////////////////////////////////////////////////////
                if (msg.message.text && msg.message.text.charAt(0) === '/') {
                  /**
/* Some Code */

Here's what a msg.edited_message looks like:

   { message_id: 869,
     from: { id: 179442020, first_name: 'xxx', username: 'xxxx' },
     chat: 
      { id: 0000,
        first_name: 'xxx',
        username: 'xxxx',
        type: 'private' },
     date: 1463978414,
     edit_date: 1463978429,
     text: 'f' },

Is it still possible to use streams instead of the file path when sending images/videos/etc?
I get the images off another server, which is why I need it :/

bot.sendPhoto({
  chat_id: USER_ID,
  caption: 'Telegram Logo',
  files: {
    photo: {
      filename: './examples/logo.png',
      stream: fs.createReadStream('./examples/logo.png')
    }
  }
}, function (err, msg) {
  console.log(err);
  console.log(msg);
});

Hi !

I try to send a message with custom keyboard as reply.

bot.sendMessage({chat_id: myid,
                             text: "Who to write ?",
                             reply_markup: {
                                 keyboard: [ ["hello"], ["world"] ],
                             }
                                    }, function(err, ret) {
                                        if(err) return console.error(err);
                                    })

I get the message "Who to write ?" and I see that the client is waiting a command but none of the options are shown.
Am i doing something wrong ?

Moving from Q to native promise by node v4

On line 218 it should be self.emit(command, msg.message, arg);
Now it's self.emit(command, msg.message, arguments); and is doing crazy things.

I'm still at 0.1.2 and can't upgrade to latest version.
I have 2 servers which share the same token and use pulling.
From time to time they get 409 error.
with 0.1.2 the pulling continues.
with 0.1.9 pulling stops on 409 error.

If dir is not set on getFile method the returned url is null.

Apparently the url is only set inside the options.dir conditional.

Compared to Q which we are using now, bluebird has better performance and compatibility.

Some times my bot fails with the following error:

Error: read ECONNRESET
    at errnoException (net.js:905:11)
    at TCP.onread (net.js:559:19)

PS: I do not work with network using some libraries exception node-telegram-bot.

Hello,
thank you for your library, I need help about the use of the method sendPhoto because I see that there's only one parameter, but, how can I use photo option?
Thank you.

Trying to send a PNG image, getting a timeout message:

504 Gateway Time-out

The URL is:
https://api.telegram.org/BOT_API_KEY/sendPhoto

Any idea why this happens?

I do as said in one of closed issues:

bot.sendPhoto({
    chat_id: message.chat.id,
    files: {
        photo: {
            filename: 'test.jpg',
            stream: fs.createReadStream('test.jpg')
        }
    }
});

 if (options.filename || value.path) {
                                 ^
TypeError: Cannot read property 'path' of undefined

What am I doing wrong?

Hello I want to send a gif file like this:

bot.sendDocument({
    chat_id: id,
    document: request(original_url).pipe(fs.createReadStream("image.gif"))
});

But I keep getting this message:

.../node_modules/node-telegram-bot/lib/Bot.js:700
    if (options.files.stream) {
                     ^

TypeError: Cannot read property 'stream' of undefined

When an audio message is received, how do you save it or open it or do anything with it? The JSON message just has meta data like duration, mime, file_id, file_size.

I have a problem with app which was deployed on the OpenShift (node-telegram-bot version 0.0.16):

TypeError: Cannot call method 'split' of undefined
    at /var/lib/openshift/55a967bc500446e3a9000060/app-root/runtime/repo/node_modules/node-telegram-bot/lib/Bot.js:90:44
    at Array.forEach (native)
    at Request._callback (/var/lib/openshift/55a967bc500446e3a9000060/app-root/runtime/repo/node_modules/node-telegram-bot/lib/Bot.js:87:21)
    at Request.self.callback (/var/lib/openshift/55a967bc500446e3a9000060/app-root/runtime/repo/node_modules/node-telegram-bot/node_modules/request/request.js:197:22)
    at Request.emit (events.js:98:17)
    at Request.<anonymous> (/var/lib/openshift/55a967bc500446e3a9000060/app-root/runtime/repo/node_modules/node-telegram-bot/node_modules/request/request.js:1050:14)
    at Request.emit (events.js:117:20)
    at IncomingMessage.<anonymous> (/var/lib/openshift/55a967bc500446e3a9000060/app-root/runtime/repo/node_modules/node-telegram-bot/node_modules/request/request.js:996:12)
    at IncomingMessage.emit (events.js:117:20)
    at _stream_readable.js:944:16

Hi!
Love the library.
Could you make some sort of config parameter to enable/disable command parsing?
I'm currently handling this on my own, and if for every message you parse it, it would allow for a loss in performance.
If needed I can contribute with a pull-request for this.
Thanks.
Sebastian

Hi there,

I started bot from example:

var Bot = require('node-telegram-bot');

var bot = new Bot({
  token: 'bla bla token'
})
.on('message', function (message) {
  console.log(message);
})
.start();

Every time I send msg to bot I got .on fired twice;

{ message_id: 12,
  from: 
   { id: 000,
     first_name: 'first',
     last_name: 'last',
     username: 'usr' },
  chat: 
   { id: 135648167,
     first_name: 'first',
     last_name: 'last',
     username: 'usr',
     type: 'private' },
  date: 1453575130,
  text: 'test' }
{ message_id: 12,
  from: 
   { id: 135648167,
     first_name: 'first',
     last_name: 'last',
     username: 'usr' },
  chat: 
   { id: 135648167,
     first_name: 'first',
     last_name: 'last',
     username: 'usr',
     type: 'private' },
  date: 1453575130,
  text: 'test' }

The test suggests something that looks like:
App api_id:App api_hash

However, with this I get a 401 error.

Telegram was under DDOS yesterday and my bots got this error:

{ [Error: socket hang up] code: 'ECONNRESET' }

I think the best place to handle this is in your library. Maybe retry until connectable again? Is there a on-error event?

Bot.prototype._poll is used to poll message to the bot.

the HTTP response in most cases is 409 (timeout).
New code (0.1.4) is raising an error for that.

works perfectly with 0.1.2

Code:

    }).on('stats', function (message) {
    // do something
    }).on('message',function(msg){
        send(msg.chat.id,'unprocessable command: '+msg.text);
    }).start();

Request
/stats@myBot
Response:
unprocessable command: /stats@myBot

Can someone confirm this is a bug? I'm running V0.1.2

Hello!
I`m a developer of the analytics service for telegram bots https://github.com/botanio/sdk

I want to offer integrate our sdk to this wrapper, so bot developer can get some analytics without much efforts. Is anyone interested in such enhancement?

Hi, I'm new here (also started to learn how to code a few weeks ago) and I have a doubt (maybe newbie question, but still):

How can I set my bot to answer group chat commands? Because when I send a command /help on a private chat it works correctly, but when my bot is in a group with another bots, the message is sent as: /help@MyBotUsername, and it doesn't answer.

Any help or explanation would be appreciated, thanks and sorry for any mistake. :)

Got this error when trying send photo in telegram -> bot

/home/ubuntu/workspace/FacebookBot/node_modules/node-telegram-bot/node_modules/q/q.js:155
throw e;
^

TypeError: Cannot read property 'destination' of undefined
at callback (/home/ubuntu/workspace/FacebookBot/facebookbot.js:95:83)
at /home/ubuntu/workspace/FacebookBot/node_modules/node-telegram-bot/node_modules/q/q.js:2031:17
at runSingle (/home/ubuntu/workspace/FacebookBot/node_modules/node-telegram-bot/node_modules/q/q.js:137:13)
at flush (/home/ubuntu/workspace/FacebookBot/node_modules/node-telegram-bot/node_modules/q/q.js:125:13)
at doNTCallback0 (node.js:417:9)
at process._tickCallback (node.js:346:13)

When sending stickers to bot app is crashing with the below error. I guess the problem occurs when there is not text in message.

var command = msg.message.text.split(' ')[0]; TypeError: Cannot read property 'split' of undefined at Array.forEach (native) at /app/node_modules/node-telegram-bot/lib/Bot.js:90:43

When you send "/error" the bot crashes with following error message:

Error: Uncaught, unspecified "error" event. ([object Object])
    at Bot.emit (events.js:144:17)
    at /home/tobias/gem-dev/node_modules/node-telegram-bot/lib/Bot.js:238:24
    at Array.forEach (native)
    at Request._callback (/home/tobias/gem-dev/node_modules/node-telegram-bot/lib/Bot.js:216:23)
    at Request.self.callback (/home/tobias/gem-dev/node_modules/node-telegram-bot/node_modules/request/request.js:198:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (/home/tobias/gem-dev/node_modules/node-telegram-bot/node_modules/request/request.js:1035:10)
    at emitOne (events.js:82:20)
    at Request.emit (events.js:169:7)

When the server sends a message like (personal information redacted and user id modified):

{ update_id: 404781694,
  edited_message: 
   { message_id: 11,
     from: 
      { id: 152564221,
        first_name: 'REDACTED',
        last_name: 'Redacted',
        username: 'redacted' },
     chat: 
      { id: 152564221,
        first_name: 'Redacted',
        last_name: 'Redacted',
        username: 'redacted',
        type: 'private' },
     date: 1471044047,
     edit_date: 1471044102,
     text: '/asignatura ean',
     entities: [ [Object] ] } }

The following error is raised:

/home/fcanela/workspace/lab/silly_motivational_bot/node_modules/node-telegram-bot/lib/Bot.js:221
                if (msg.message.text && msg.message.text.charAt(0) === '/') {
                               ^

TypeError: Cannot read property 'text' of undefined
    at /home/fcanela/workspace/lab/silly_motivational_bot/node_modules/node-telegram-bot/lib/Bot.js:221:32
    at Array.forEach (native)
    at Request._callback (/home/fcanela/workspace/lab/silly_motivational_bot/node_modules/node-telegram-bot/lib/Bot.js:216:23)
    at Request.self.callback (/home/fcanela/workspace/lab/silly_motivational_bot/node_modules/request/request.js:187:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/home/fcanela/workspace/lab/silly_motivational_bot/node_modules/request/request.js:1044:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:188:7)
    at IncomingMessage.<anonymous> (/home/fcanela/workspace/lab/silly_motivational_bot/node_modules/request/request.js:965:12)

This behaviour can be reproduced this way:

1. Sending a command using Linux client
2. Pressing up key in the text area, an "Edit message" label will appear
3. Resending the command or writing a new one

A dirty and quick fix that solved my issue was referencing msg.message to msg.edited_message. Starting from line 216:

          body.result.forEach(function (msg) {
                        if (msg.edited_message) msg.message = msg.edited_message;

There should be probably a better option, but I have no time to validate it right now. I hope this help.

Thanks for the library.

events.js:85 │·······················
throw er; // Unhandled 'error' event │·······················
^ │·······················
Error: read ECONNRESET │·······················
at exports._errnoException (util.js:746:11) │·······················
at Pipe.onread (net.js:559:26) │·······················

i mean ,sending a photo from url like : "http:......./host/goal.png" instead of a file on local server

Hi everyone.
Am I the only one getting a ton of 409 errors from Telegram?
It's stated somewhere on the web that this is probably when trying to use multiple bots at the same time, but the case is I'm only running one instance of each one that I have.
Every couple of minutes I get this error and restart the polling.

I did find a probable bug on the Bot, that in the polling the getUpdates gets a 60 seconds timeout, but the actual request call is only 6 seconds (6000ms). I increased to 70000ms to make sure Telegram times out first, but I still get the same problems.

I run at least 10 bots at the same time.

Anyone else having this problem?
Seba

Hi there, me again.
I have your library running 24x7 with a couple of bots on a server.
Last week I updated to your latest revision and some crashes started to appear.
Sure enough are easy to fix. Seems like the response object is null on some cases.
Here are two different errors:

First reported issue

TypeError: Cannot read property 'statusCode' of undefined
File "/node_modules/node-telegram-bot/lib/Bot.js", line 203, in Request._callback
} else if(res.statusCode === 401){
File "/node_modules/request/request.js", line 198, in self.callback
self._callback.apply(self, arguments)
File "events.js", line 107, in Request.emit
File "/node_modules/request/request.js", line 877, in Request.onRequestError
self.emit('error', error)
File "events.js", line 107, in ClientRequest.emit

Second reported issue
TypeError: Cannot read property 'statusCode' of undefined
File "/node_modules/node-telegram-bot/lib/Bot.js", line 159, in Request._callback
console.log("Failed to set webhook with code" + res.statusCode);
File "/node_modules/request/request.js", line 198, in self.callback
self._callback.apply(self, arguments)
File "events.js", line 107, in Request.emit
File "/node_modules/request/request.js", line 877, in Request.onRequestError
self.emit('error', error)
File "events.js", line 107, in ClientRequest.emit

Any extra help I can provide, let me know!

https://core.telegram.org/bots/api#getfile

Hi. Are you planning to add channel support and new Chat field type in Message?

/node_modules/node-telegram-bot/node_modules/q/q.js:155
throw e;
^
TypeError: Cannot read property 'file_id' of undefined
at /commands/dl.js:36:56
at /node_modules/node-telegram-bot/node_modules/q/q.js:2031:17
at runSingle (/node_modules/node-telegram-bot/node_modules/q/q.js:137:13)
at flush (/node_modules/node-telegram-bot/node_modules/q/q.js:125:13)
at process._tickCallback (node.js:355:11)

This is an absolute must have!

https://core.telegram.org/bots/inline

Telegram new updates :

• Added support for self-signed certificates: upload your certificate using the certificate parameter in the setWebhook method.

Is there any way I can use self-signed cert? Thanks.

Hello,

I am trying to use the Library to be able to Stop the BOT app from Node if needed.
However next time when I start the bot again it fails to start up.

Here is a code snippet:

case message.text == '/stop':
      bot.sendMessage({
        chat_id: message.chat.id,
        text: 'Goodbye',
      });
      bot.stop();
    break;

This inside the command parser instantiated by:

// Attach event on every received message 
bot.on('message', function (message) {
  parseMessage(message);
});

Where parseMessage(message) is the function that is used to interpret the message as a command.

The package is running normally when there is no /stop command sent.
However ones this is sent from Telegram it causes the BOT to stop.
Next time when I try to start the application it does not allow the BOT application to start.

Kindly help regarding this.

Warm Regards,
Boseji

Currently webhook is not attached to a http server to receive request.

Hi there!

I am running this bot on my Raspberry Pi and it always just stops pulling the messages after a period of time.

I am running it with nohup to daemonize it like this:

nohup node app.js &

The nohup.out never throws an error, it just stops pulling the messages until I kill and restart the bot. Then it processes all missed messages and goes on for a few hours.
My Raspberry Pi is running rock solid for more than 120 days straight now.

Any idea?

I see here that it's possible to parse commands with this library, but there are no documentation/examples of it. Can you please provide some detailed doc?

The example only mentions .on('message', function (message) { ... } where message.text has the command and the text. Is it possible to do something like .on('start', function (message) { ... } or .on('help', function (message) { ... }?