Telegram Plugin stops receiving

---

I have some rules, that sends status messages with telegram. These rules always works well.
Additional i have some rules, which gets triggered when a telegram messages is received. But after some days these rules does ot trigger and telegram does not ask for the passphrase. After a restart of pimatic, these messages gets delivered and the plugin sends the messages to telegram.

Does anybody know this behaivor and found a solution or the cause of the problem?

Kind regards

@TeeS This might be caused by your ISP changing your external IP address.

@TeeS You may be able to check this via the management interface of your DSL router. It should show a timestamp about when the IP access connection has been established. At that point the IP address may have changed.

Either this is shown in the log or depending on the router you have there may also be status page for the internet connection (Fritzbox provides this at least).

Thanks for this hint. I get an Mail from my FritzBox when the IP changes. Does anybody have an idea who to implement an workaround for the telegram plugin? My only solution is to restart pimatic service manual.

I have the same behavior. After startup the receiver works, but after a certain time it stops reacting. I really missing this feature. Any workaround is welcome.

If time permits, I will look into replacing the communication interface for the Telegram API to see if this can improve stability. Otherwise I will see if I can implement a “restart” action for the rule engine so users can at least schedule regular refreshes of the receiver device.

Cannot make any promises on ETA though, could be weeks.

Have implemented a “reload <TelegramReceiverDevice>” action, to provide somewhat of a workaround
(e.g. when it is 23:00 then reload TelegramReceiverDevice)

Awaiting alpha test by one of our trusted users before packaging and releasing on NPM.

I have been able to do a quick and dirty change of the underlying messaging infrastructure, which should be more stable?! Requirement is node v10 though.
If you still experience the disconnect issue: a new action reload <TelegramReceiverDevice> is made available so you can reload at scheduled times, e.g. 23:00.

Also some minor bugs have been fixed such as the “help” bug.

Before I package and release on NPM, for the advanced users:

sudo systemctl stop pimatic
cd <pimatic-app>/node_modules/
rm -rf pimatic-telegram
git clone http://github.com/sentzu01/pimatic-telegram.git
cd pimatic-telegram
git checkout telegraf
npm install
sudo systemctl restart pimatic

If at any time you want to revert to the released version:

sudo systemctl stop pimatic
cd <pimatic-app>/node_modules/
rm -rf pimatic-telegram
sudo systemctl restart pimatic

Note: I have asked Lord Vader aka @OrTiN to Alpha test. So the issues he reports I will be “more responsive to” as my time is limited. Thanks everyone!

@dan said in Telegram Plugin stops receiving:

git clone http://github.com/sentzu01/pimatic-telegram.git

I tried it, but get this error messages, i am not very familiar with git. Can you understand what this messages mean?

@tees error in my instruction, I will update:
after:

git clone ......

you need to do:

cd pimatic-telegram

and then the rest starting with:

git checkout telegraf

@dan said in Telegram Plugin stops receiving:

git checkout telegraf

Hello, i tried this before an get the error, that there is no matching file.

Is checkout telegraf correct? Not telegram? But i tried both with the same error.

Pimatic-telegram 1.1.13 has been released. The telegraf branch has been removed from Github.
Just remove your pimatic-telegram directory including content and restart Pimatic. The latest version will be installed automatically. Installing a pre-release from github usually requires additional knowledge.