New plugin for Telegram

---

The next release will include sending locations (GPS coordinates), which will show as a map in your telegram messaging client. Combined with the location or phone plugins this could yield some creative solutions, such as “alert if a device is not at an expected location at a determined time”. Code is ready on a separate branch, but I am not sure when I will merge to master yet. Soon though

Version 1.1.13 has been released just now:

• new feature: send gps telegram ....... "<latitude>;<longutide>" which allows for sending GPS coordinates
• Fixed a number of bugs logged via the forum and Github and found through rigorous testing
• improvements on logging events

Late breaking known issue: After changing settings of the TelegramReceiverDevice, the rule commands defined by telegram received "rule_command" are lost by the listener. I am looking to make these persistent across recreation of the device (which happens on changes), or reload the rules defined with “telegram received” on recreation of the device, which then passes them to the listener
Workaround: Restart pimatic after changing settings on your TelegramListenerDevice

Hi,

i like the telegram plugin very much and change from pushover to telegram!
but i habe now one problem with the telegram plugin. I create a rule that sends me some datas out of variables, if i send a message to my bot. and it works fine. but my problem is, that the variables in the message don t updated. if i order the variables the first time, everything looks good. but every message after the first (same rule) include the same information like the first, although the variables changed in pimatic. only i restart pimatic the message includes the right data.
(pimatic version: 0.9.38 | telegram version: 1.1.13)
i hope somebody can help.

@flozen See the primary post on reporting issues on Github. This issue was logged previously and has been fixed. The fix will be included in the next release.

oh, now i see. sorry, i have to search better the next time and thanks for your very fast answer

1.1.4 has been released with bugfixes for Github issues:
#13: Telegram receiver rules are not applied for recreated telegram receiver device
#16: Bot sends old values

In short, when changing settings on the receiver device, Telegram now reloads rule commands when telegram received "<request>"
When sending variables, eg temperature, Telegram now sends the actual value at the time of sending the message

@flozen: No worries !

Hi. Not sure if i’m blind, or it’s not possible for now:
Is it possible to turn off the message sent, when activating rules by sending keywords (“Rule condition ‘XYZ’ triggered”)?

Thanks for your work!

Hi @sirhc,

Your eyes are still working The confirmation message is sent always. If needed I can look into making this a configurable option.

Can you say some more about your specific scenario? this helps determining the best option, as it may benefits others as well.

First, thanks for the great plugin
But i have a little problem.
The pluging should send me the actually temperature, but it only works once and after the pimatic send me always the same value.
If i send the value at the same time by email, then i receive a mail with the correct value.
At the Webinterface is the value also correct but telegram send me always the same value.

regards
Markus

@Dan
I’m relieved :P
I’m just using Keywords like “Licht aus” to switch off all 433mhz triggered lights. When done im sending a text message Via telegram with a custom text “Licht XYZ aus”, which i prefer over the rule condition triggered.
For other scenarios it’s even more “useless” to see the rule triggered: When sending “Temperatur” to my telegram bot i’ getting messaged with the current values of my temperature sensors (see my error report from 2 days ago); Therefore i’m sending a message with those values - if that rule hadn’t been triggered, i wouldn’t get any response, so there’s as well no need for this.
So an option for just turning on / off rule triggering would be nice: Those who don’t want to create customs responses can just use the automated rule answer, while the others can turn it off and send custom messages.

Thanks in advance!

@edhunter667 said in New plugin for Telegram:

Just upgrade to the new version, your error #13 was fixed there.

@sirhc said in New plugin for Telegram:

So an option for just turning on / off rule triggering would be nice: Those who don’t want to create customs responses can just use the automated rule answer, while the others can turn it off and send custom messages.

Thanks in advance!

This is the easy option :D, can implement in a few minutes really, I’ll see if I can get around to it today!

@sirhc
thanks, it works
sometimes the solution is so easy.

1.1.5 is ready for consumption, with two new features, configurable via the device config page:

• Telegram Listener can be turned on and off in the frontend (If you add the Receiver device to your webpages)
• Confirmation messages on executing rule and device actions can be turned off (feature request @sirhc)

Three new config options have been introduced to support these features:

stateStartup:
       description: "Start Telegram Listener at Pimatic start?"
       type: "boolean"
       default: true
     confirmRuleTrigger:
       description: "Should the receiver send confirmation upon executing rule actions?"
       type: "boolean"
       default: true
     confirmDeviceAction:
       description: "Should the receiver send confirmation upon executing device actions?"
       type: "boolean"
       default: true

And 1.1.6 is on the floor: Added send doc telegram ...... (request @Andi-Tudor)

• Included file checking, max allowed file size is 50MB

Thanks for sending the document option.

I have installed the plugin today but I have a problem…
When I send “help” to pimatic there came no answer. I have restart pimatic several times but it doesn’t work.

The debug says:

debug [pimatic-telegram]: Request ' help ' received, processing...
19:13:57info [pimatic-telegram]: Starting Telegram listener

So I can see that my “command” arrives in pimatic.

Here my config:

    {
      "apiToken": "xxxx",
      "debug": true,
      "recipients": [
        {
          "name": "ViperAdmin",
          "userChatId": "xxxx",
          "enabled": true,
          "admin": true
        }
    {
      "secret": "xxx",
      "auth_timeout": 5,
      "stateStartup": true,
      "confirmRuleTrigger": true,
      "confirmDeviceAction": true,
      "id": "telegram-receiver",
      "name": "Telegram_Receiver",
      "class": "TelegramReceiverDevice"
    }

Hi there,

I like the new feature that you can disable the telegram listening. But there is one thing that could be better

If you disable the listening and after that send some requests nothing happens (correct). But than if you aktivate the listening, every requests (in the “disable time”) get an answer. It would be better, that Pimatic doesn’t answers these “old” request.

@flozen you are correct. The message queue is maintained and kept on the Telegram infrastructure. There is something to be said for purging the queue, as well as maintaining it. I will consider this, but i am not sure if this is the correct approach. Some may want to keep it, others may want to purge.

@Dan
Can"t you help me? See my post above.