Telegram Notifications Plugin (discourse-telegram-notifications)

Perhaps a dumb question, but what notifications should I expect to see via Telegram? The bot is up and running, I send it a message and get a Chat ID, I put that ID into my user profile, but despite having gotten a couple of email notifications since that time, I haven’t seen anything on Telegram. Should I have, or is there someplace else I need to set up those notifications?

If logs are needed to help figure this out, I’m fine with posting them, but I’ll need some guidance on where to look for them.

Proofreading always helps–turns out I’d (apparently, though I never saw the error) entered the Chat ID incorrectly. Now that it’s re-entered, notifications work as expected. Cool!

3 Mi Piace

Hi. I’m trying to get this configured but I’m stuck on trying to get the Bot to send me the Chat ID. No matter what i type, I get no response.

First I created the bot following the directions.
Then I created a Group in Telegram and add the bot as a member.
Then i try to send a message, even tagging the bot and still no response.

I even try to create a channel and message the bot but still no response.
I even tried doing it through the desktop pp and through my mobile phone app, still no luck.

Im not sure what else to do.

Also, Do i need both, discourse-chat-integration and discourse-telegram-notifications installed?

I don’t see anywhere in the docs that it says to create a group, and in fact I see a recommendation to disallow the bot from being added to a group. Send a message directly to the bot, not to a group that includes the bot.

According to the OP (it’s even in a shaded box at the top), they do different things:

1 Mi Piace

thanks for the input, ill try again.

Can I use Chatroom Integration Plugin & Telegram notification plugins at the same? I have integrated chatroom integration plugin successfully and its working fine, but Telegram notification plugin is not notifying users. The bot just show me this!

testbot, [28.12.19 15:58]
Hi Administrator, I'll message you when you have new notifications on Engineer's Asylum. 
Replying to a notification will post a reply on Engineer's Asylum.
To disable, visit your user preferences.

From the OP:

I haven’t done it myself, but that appears to answer the question.

1 Mi Piace

I found where i went wrong, i was putting the access token in the chat integration plugin area, i found the one in the plugins settings area for telegram, messaged the bot and I got a response!

Blockquote Im still not getting the bot to respond and provide me the chat id via telegram. I tried to send a message to the bot itself. i tried to create a channel via telegram and tag the bot with a message. still i got nothing

Have you found a fix for this? I got this issue too.

I have just opened this PR to the plugin:

It adds support for that string, and also for the Discourse Follow Plugin
I hope staff merges it soon

Looks great, I just merged it - thanks @barreeeiroo :smiley:

4 Mi Piace

If you plan to expand this to offer Viber and SMS notifications, look at my project GitHub - Sprachprofi/notifications_sample: Demonstrating how to cleanly handle opt-in/opt-out and notifications via a variety of platforms

1 Mi Piace

@david
Very useful plugin, Thank you! :blush:

Can I use {name} instead of {username} in translations?

Unfortunately not, that would require a change to the code of the plugin

4 Mi Piace

Hey @david, my bot sometimes not working … Checked the token and site SSL, all ok… Any ideas?

I had checked the logs and those all about private messages:
Failed to send Telegram message. Message data= "… private message …"

/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/logster-2.5.1/lib/logster/logger.rb:112:in `report_to_store'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/logster-2.5.1/lib/logster/logger.rb:103:in `add_with_opts'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/logster-2.5.1/lib/logster/logger.rb:54:in `add'
/usr/local/lib/ruby/2.6.0/logger.rb:543:in `error'
/var/www/discourse/plugins/discourse-telegram-notifications/services/discourse_telegram_notifications/telegram-notifier.rb:46:in `doRequest'
/var/www/discourse/plugins/discourse-telegram-notifications/services/discourse_telegram_notifications/telegram-notifier.rb:7:in `sendMessage'
/var/www/discourse/plugins/discourse-telegram-notifications/plugin.rb:234:in `execute'
/var/www/discourse/app/jobs/base.rb:232:in `block (2 levels) in perform'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rails_multisite-2.0.7/lib/rails_multisite/connection_management.rb:63:in `with_connection'
/var/www/discourse/app/jobs/base.rb:221:in `block in perform'
/var/www/discourse/app/jobs/base.rb:217:in `each'
/var/www/discourse/app/jobs/base.rb:217:in `perform'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:196:in `execute_job'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:164:in `block (2 levels) in process'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/middleware/chain.rb:138:in `block in invoke'
/var/www/discourse/lib/sidekiq/pausable.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/middleware/chain.rb:140:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/middleware/chain.rb:143:in `invoke'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:163:in `block in process'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:136:in `block (6 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/job_retry.rb:111:in `local'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:135:in `block (5 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq.rb:37:in `block in <module:Sidekiq>'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:257:in `stats'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/job_logger.rb:13:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/job_retry.rb:78:in `global'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:124:in `block in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/logger.rb:10:in `with'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/job_logger.rb:33:in `prepare'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:123:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:162:in `process'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:78:in `process_one'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/processor.rb:68:in `run'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/util.rb:15:in `watchdog'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.4/lib/sidekiq/util.rb:24:in `block in safe_thread'

Greeting.
Same problem with installation of this plugin…

Problema e Soluzione:

Problema:
Ero molto confuso tra due plugin, due bot di Telegram, due chat di Telegram (canale di Telegram e gruppo di Telegram). In questa confusione, mi veniva sempre richiesto un campo denominato ‘Token di Telegram’ o qualcosa di simile, ma continuavo a fare confusione tra i due.

Soluzione:
Alla fine, ho scoperto che nelle Impostazioni di Discourse esistono due campi diversi, con etichette/nomi molto molto simili e situati molto vicini l’uno all’altro, ma che, beh, NON SONO LA STESSA COSA.

Quindi, vi prego di notare che si tratta di due cose diverse e hanno scopi differenti:

Ho notato che le chat di canale/gruppo di Telegram non rispondono più al comando /getchatid. Non possiamo più far sì che rivelino il loro ID chat in modo normale. In precedenza, ogni volta che creavamo un nuovo bot, questo comunicava automaticamente il proprio ID non appena iniziavamo una chat con esso. Ma ora non si comporta più così.

Sarebbe possibile implementare una notifica quando un post è in attesa di approvazione?

Ehi @david!

Per prima cosa, grazie per il plugin. È tutto configurato, funziona e non vedo l’ora di annunciarlo alla community.

Tuttavia, ho un paio di domande:

  1. Come posso tradurlo nella mia lingua per rendere le cose ancora più semplici per la nostra community?

  2. C’è un modo, tramite Telegram o Discourse, per controllare l’aspetto dei messaggi su Telegram? Il font non è molto gradevole e ci sono doppi spazi tra le parole del testo del messaggio effettivo inviato da Discourse (i testi del plugin sembrano invece perfetti).

Anch’io. Non mi piace molto com’è fatto.

È bello sentire che funziona ancora. Penso di provarlo sulla mia community.