New plugin for Telegram

---

hello,
i cant bring the plugin to work properly.
everything works fine as sending messages etc.
but executing pimatic commands doesnt work…

i used:

WHEN: telegram received "temp"
THEN: send text telegram to sender “&$dht22.temperature $dht22.humidity”

but when i send temp to the bot it doesnt make anything…my useracc has admin permissions. any help?

Does it work after recreating the TelegramReceiverDevice -> open it, save it and then send “temp”.

@vincent-würzinger If @OrTiN 's suggestion does not work:
Could you enable debugging in both Pimatic and the Telegram plugin? The additional debug output may help us troubleshoot what is happening.

@vincent-würzinger said

WHEN: telegram received "temp"
THEN: send text telegram to sender “&$dht22.temperature $dht22.humidity”

but when i send temp to the bot it doesnt make anything…my useracc has admin permissions. any help?

Also I have not seen device attribute vars being preceded with an ampersand (&). Is this valid syntax?

i forgot to setup the telegramreceiverdevice. its working great. thanks.

@Dan I just discovered your plugin for the first time. What a great plugin and very useful!! A real value adding addon for Pimatic!

I was wondering if it’s also possible to markup the messages. At stackoverflow I read that this is possible for bots with the following setting:
Set the parse_mode to markdown and send bold
Set the parse_mode to html and send <b>bold<b>

Is this a nice to have feature yet to be developed? Or have I missed a setting?
Thank you for your great work!

@thijn-jacobs said in New plugin for Telegram:

I was wondering if it’s also possible to markup the messages.

Hello Thijn, Great to hear you enjoy the plugin!
I’ll make a quick update to allow for HTML in user-defined text in rule actions, e.g. "send text telegram to <user> "<b>The house is on fire</b>"
Per the Telegram API docs:

• Only <b>, <i>, <em>, <a>, <code> and <pre> are supported, for respectively bold, italic, emphasized, hyperlink, code block, and pre-formatted code block
• Tags must not be nested.
• All <, > and & symbols that are not a part of a tag or an HTML entity must be replaced with the corresponding
• HTML entities (< with <, > with > and & with &).
• All numerical HTML entities are supported.
• The API currently supports only the following named HTML entities: <, >, & and ".

Wow, that would be great!! Thank you very much for this super service!!
Please let us know when you’re ready…

1.1.11 is now available, with support for HTML formatted text as described earlier.
As it is relatively complicated to safely parse long messages (needed to preserve HTML markup per chunk) and the maximum message size is now 4096 characters, I have decided to disable the chunking of messages to allow unlimited length for now: Meaning the maximum length for text messages is now 4096 chars.

Enjoy!

Thanks a lot Dan!! I’m going to test tomorrow…

Thx for the update @Dan. I immediately change some rules where I was wishing the code-block format, but didn’t dare to ask about it…

@ortin said in New plugin for Telegram:

Thx for the update @Dan. I immediately change some rules where I was wishing the code-block format, but didn’t dare to ask about it…

ok ok, I’ve been told I can come across intimidating in real life, but I thought I was really friendly on the forum
Just kidding @OrTiN, dude you were one of the early adopters…you can always ask

it would be awesome to handle different Bots on one pimatic device. or is it somehow possible to let a specific message popup on my phone with a specific sound? for some events i need an alarm sound, for others the usual “ping” sound is enough (possible through botfather ai?)

@vincent-würzinger Hello Vincent, I have not seen options in the API allowing for custom notification sounds based on a message pattern. Implementing the ability to operate multiple bots requires associating the API token per-device, and then implementing a feature in the action provider so a user can define over which device (=specific bot) to send a message. On a mobile device you could then associate sounds per-bot. I’ll put this on the feature list, but currently I cannot give an estimate when this will be implemented.

Hey Dan,
I haven’t use the TelegramReceiverDevice function for a long time. In the past, maybe you remember I had problems to get a response from the bot. Now I observed the same behavior in the last days as before. After pimatic restart or recreating the device it works for a while (approx. one day) after this it stops to response.

I really have no idea, but from my knowledge the problem occurs the first time after the last functional update, where you’ve implemented the request of Zomer.

Can you please have a look to it. My config didn’t change since month regarding this function.

I still have the same problem. After a while (some days), Telegram stops responding. Is there a way to restart the Telegram service by rule or something?

@flop2006 said in New plugin for Telegram:

I still have the same problem. After a while (some days), Telegram stops responding. Is there a way to restart the Telegram service by rule or something?

Same here.

I found out that a “recreation” helps here. Means open the “TelegramReceiverDevice” and save it. The Telegram listener will be stopped and that started again. Now it will work for a while.
Maybe this restart of the listener can be achieved by an api command as well?

since today I have a problem starting pimatic with the telegram bot. Seems to be sth with the connection to telegram - or? Internet etc. is working fine… Some ideas here?

[bot.error.webhook] { [Error: socket hang up]
  code: 'ECONNRESET',
  __trace: 'Error: From connect\n    at TLSSocket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:55:29)\n    at Object.TLSSocket._init.ssl.onclienthello.ssl.oncertcb.exports.connect (_tls_wrap.js:1048:11)\n    at Agent.createConnection (https.js:79:22)\n    at Agent.createSocket (_http_agent.js:188:16)\n    at Agent.addRequest (_http_agent.js:157:23)\n    at new ClientRequest (_http_client.js:142:16)\n    at Object.exports.request (http.js:31:10)\n    at Object.socket.once.exports.request (https.js:189:15)\n    at Request.start (/home/pi/pimatic-app/node_modules/pimatic-telegram/node_modules/telebot/node_modules/request/request.js:747:32)\n    at Request.end (/home/pi/pimatic-app/node_modules/pimatic-telegram/node_modules/telebot/node_modules/request/request.js:1506:10)\n    at end (/home/pi/pimatic-app/node_modules/pimatic-telegram/node_modules/telebot/node_modules/request/request.js:560:14)\n    at Immediate._onImmediate (/home/pi/pimatic-app/node_modules/pimatic-telegram/node_modules/telebot/node_modules/request/request.js:574:7)\n    at processImmediate [as _immediateCallback] (timers.js:396:17)' }

Very strange but it works as expected, today. So by now it is fine