# \[APP\]\[Pro\] Telegram

**URL:** <https://community.homey.app/t/app-pro-telegram/66622>\
**Category:** Apps\
**Tags:** app, flow, homey-pro\
**Created:** [July 28, 2022, 1:34pm UTC](https://community.homey.app/t/app-pro-telegram/66622 "2022-07-28T13:34:36Z")\
**Posts on this page:** 20\
**Page:** 13

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [April 23, 2023, 11:22pm UTC](https://community.homey.app/t/app-pro-telegram/66622/243 "2023-04-23T23:22:55Z")

</div>

> [@spkesDE](#):
>
> Added “I Fucked up menu”

🎯 😉

---

<div class="post-metadata">

**Author:** ![Felho](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/felho/32/38916_2.png) [@Felho](https://community.homey.app/u/Felho)\
**Post date:** [April 25, 2023, 9:17am UTC](https://community.homey.app/t/app-pro-telegram/66622/244 "2023-04-25T09:17:07Z")

</div>

> [@johan\_maillot](#):
>
> Hello,
> 
> I have a problem at the token stage.
> 
> I put the token in the Telegram settings of the Homey app.
> 
> And from there it loads continuously.
> 
> Where is my mistake?

Me to same problem the last version. and after close and reopen app I see online token but no have user or group in group page

---

<div class="post-metadata">

**Author:** ![Felho](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/felho/32/38916_2.png) [@Felho](https://community.homey.app/u/Felho)\
**Post date:** [May 10, 2023, 9:24pm UTC](https://community.homey.app/t/app-pro-telegram/66622/245 "2023-05-10T21:24:29Z")

</div>

Hi why not showing my user pickup telegram? diagnostic report f3d3b4f4-1485-42a0-b774-109a0d1bdd66

thanks someone help

---

<div class="post-metadata">

**Author:** ![Felho](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/felho/32/38916_2.png) [@Felho](https://community.homey.app/u/Felho)\
**Post date:** [May 10, 2023, 10:19pm UTC](https://community.homey.app/t/app-pro-telegram/66622/246 "2023-05-10T22:19:44Z")

</div>

I think I fix it. thanks

---

<div class="post-metadata">

**Author:** ![Phil\_Bro](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phil_bro/32/78156_2.png) [@Phil\_Bro](https://community.homey.app/u/Phil_Bro)\
**Post date:** [May 29, 2023, 2:17pm UTC](https://community.homey.app/t/app-pro-telegram/66622/247 "2023-05-29T14:17:58Z")

</div>

Hi there!

Started implementing the app in the advanced flows I have for 2 locations. All ok except the [delete message with ID] option, which is in fact very handy.

Assume I sent a system message stating the solar panels yield is below the power required by batteries to properly charge and the grid power is to expensive. After rechecking this with a delay of max. 10min, I want to delete this message and resubmit the remark with updated info. If the delay runs out of time, a new status update is send and the old message is just old, occupying the timeline in the chat.

How to delete the message senT by the bot, in other words how do I determine the message ID?

Thanks,

Phil

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [May 29, 2023, 2:33pm UTC](https://community.homey.app/t/app-pro-telegram/66622/248 "2023-05-29T14:33:46Z")

</div>

Well, it’s complicated.

You have to use the “When a Message is Received” card to get the message ID as a token. Save it or use a timer to delete it.

There is no nice way for me to save the message data inside Telegram.

Also keep in mind after 48h(or72h, i can’t remember) you can’t delete the message anymore

---

<div class="post-metadata">

**Author:** ![Phil\_Bro](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phil_bro/32/78156_2.png) [@Phil\_Bro](https://community.homey.app/u/Phil_Bro)\
**Post date:** [May 29, 2023, 3:00pm UTC](https://community.homey.app/t/app-pro-telegram/66622/249 "2023-05-29T15:00:55Z")

</div>

Many thanks!

So as I read it, the message ID is in fact data from the received message by the app itself, not the sent message ID. Obvious the same. I will do some testing with this and report back to the comm.

It is not that difficult to store the ID as variable and the timeslot of 48h is much longer than needed in this case.

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [May 29, 2023, 3:17pm UTC](https://community.homey.app/t/app-pro-telegram/66622/250 "2023-05-29T15:17:51Z")

</div>

Yeah, the message id will be given by telegram itself. so it’s not possible to attach a custom id or so.

---

<div class="post-metadata">

**Author:** ![Phil\_Bro](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phil_bro/32/78156_2.png) [@Phil\_Bro](https://community.homey.app/u/Phil_Bro)\
**Post date:** [May 29, 2023, 3:21pm UTC](https://community.homey.app/t/app-pro-telegram/66622/251 "2023-05-29T15:21:26Z")

</div>

There is a problem with this or more, a limitation. The [when message is received] or even [when message is received from chat], simply the last message is taken from the bot chat. This chat is used for many messages so if within the timeframe of my delay a message is sent by the bot, THAT message ID is taken in the dialog, and most probably wrongly deleted.

Is there any change to send an extra parameter with the telegram messages, like f.i. flow ID or another and even better option, send message to [user] with [custom id] this is not available. The delete message with [custom ID] is already available.

Thank you for your input, appreciate your work!

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [May 29, 2023, 3:27pm UTC](https://community.homey.app/t/app-pro-telegram/66622/252 "2023-05-29T15:27:42Z")

</div>

Sadly not. only with the question system possible

---

<div class="post-metadata">

**Author:** ![Phil\_Bro](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phil_bro/32/78156_2.png) [@Phil\_Bro](https://community.homey.app/u/Phil_Bro)\
**Post date:** [May 29, 2023, 3:33pm UTC](https://community.homey.app/t/app-pro-telegram/66622/253 "2023-05-29T15:33:53Z")

</div>

Last question. Is the app suitable for using 2 bots with the huge advantage of having 2 sets of vars to play with. I sent the messages to a group, stored in [type] as a name. Any chance with this?

If both are NO, I need to consider to split the messages based on prio or relevance , e.g. timeline, push and telegram… Sadly …

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [May 29, 2023, 3:45pm UTC](https://community.homey.app/t/app-pro-telegram/66622/254 "2023-05-29T15:45:47Z")

</div>

Two bots no.

But you can filter the messages using when a message is received card.  
Also you can use topics to split messages into “sub groups”

---

<div class="post-metadata">

**Author:** ![Phil\_Bro](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phil_bro/32/78156_2.png) [@Phil\_Bro](https://community.homey.app/u/Phil_Bro)\
**Post date:** [May 29, 2023, 4:20pm UTC](https://community.homey.app/t/app-pro-telegram/66622/255 "2023-05-29T16:20:12Z")

</div>

Settings topics did broke the group membership of 2 bot locations. Didn’t know that. Just restored all.  
I see no other options to play with, I will try to send the message as question and delete with response to that with a certain delay. Far from ideal, but it is something.

Thank you for the support!

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [June 28, 2023, 10:17am UTC](https://community.homey.app/t/app-pro-telegram/66622/256 "2023-06-28T10:17:28Z")

</div>

# [Version 2.7.0 is now in testing](https://homey.app/a/com.spkes.telegramNotifications/test/) 🎉

> ## Changes
> 
> - Added “A message from Topic is received”.
> - Thanks to enyineer / Nico for programming this!

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [June 28, 2023, 7:49pm UTC](https://community.homey.app/t/app-pro-telegram/66622/257 "2023-06-28T19:49:18Z")

</div>

# Big news!

Enyineer, aka @NicoEk, is currently actively contributing to this app! This means faster updates, new features, and maybe a better and more feature-rich app for you guys!

In the near future, we will show you changes and features that will improve your smart home experience via Telegram.

Also, for people who don’t like support on this forum, we created a community telegram group!  
Feel free to join there and ask for support. Join us [here](https://t.me/homeyCommunity), we’re exited to see you there!

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/e/6e857ecf5fec915f5aefe5d5598d22d8ab68f8c5.png)

---

<div class="post-metadata">

**Author:** ![JMH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmh/32/29230_2.png) [@JMH](https://community.homey.app/u/JMH)\
**Post date:** [July 25, 2023, 7:12am UTC](https://community.homey.app/t/app-pro-telegram/66622/258 "2023-07-25T07:12:06Z")

</div>

Will text styling (bold, italic, …) become available? I still use the other Telegram app for that, but would like to transfer completely to yours.  
Thanks in advance.

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [July 25, 2023, 8:44am UTC](https://community.homey.app/t/app-pro-telegram/66622/259 "2023-07-25T08:44:58Z")

</div>

It’s on our agenda for v3.0.0.

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [July 28, 2023, 8:02pm UTC](https://community.homey.app/t/app-pro-telegram/66622/260 "2023-07-28T20:02:53Z")

</div>

# [Test Version 2.8.0 is now testing…](https://homey.app/a/com.spkes.telegramNotifications/test/)

There are big changes with this version, but these are only under the hood.  
This is the first version of v3 of the Telegraf app.

> - Changed from Telegraf to Grammy.dev for better programming experience
> - It’s about 300kb bigger than Telegraf. RAM usage in our test was about 1MB more. Please give us feedback.
> 
> - Added Markdown support (HTML and MarkdownV2). Enable it in the settings.
> - It supports escaping characters using the backslash `\` to display special characters or prevent them from being interpreted as formatting.
> 
> - Added about page on the settings menu
> - Fixed an issue with URL validation when the redirects had a 30X code. (by [@andreasvikke](https://github.com/spkesDE/com.spkes.telegramNotifications/commits?author=andreasvikke))

* * *

# [Test Version 2.8.1 is now testing…](https://homey.app/a/com.spkes.telegramNotifications/test/)

> - Nearly everything can be found in translation (EN, DE, IT, NL).
> - Custom commands will no longer be overwritten.  
> ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/1/6174988c632a574858b3f07b2af4c98c4ba9bc52.png)

---

<div class="post-metadata">

**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\
**Post date:** [July 29, 2023, 9:33am UTC](https://community.homey.app/t/app-pro-telegram/66622/261 "2023-07-29T09:33:36Z")

</div>

I’m working on supporting all languages that are supported by Homey Pro (except RU).

If you speak one of these languages, please give me feedback.

| Language | Link | Help needed? |
| --- | --- | --- |
| 🇬🇧 English | [Here](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/en.json) | ☑ Done by @Twan_Veugelers and me |
| 🇩🇪 German | [Here](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/de.json) | ☑ Done by me |
| 🇳🇱 Dutch | [Here](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/nl.json) | ☑ Done by @Twan_Veugelers and @LRvdLinden |
| 🇮🇹 Italian | [Here](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/it.json) | ☑ Done by @ilpaolino and @pippo73 |
| 🇵🇱 Polish | [Here](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/pl.json) | 🆘 Yes |
| 🇪🇸 Spanish | [Here](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/es.json) | 🆘 Yes |
| 🇩🇰 Danish | [Here](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/da.json) | 🚧 In Progress |
| 🇸🇪 Swedish | [Here](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/sv.json) | 🆘 Yes |
| 🇳🇴 Norwegian | [Here](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/no.json) | 🆘 Yes |
| 🇫🇷 French | [Here](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/fr.json) | 🆘 Yes |

You can also find the translations [➡ here ⬅](https://github.com/spkesDE/com.spkes.telegramNotifications/tree/feature/moreLanguages/locales)  
For reference, the 🇬🇧:/🇺🇸 translation can be found [➡ here ⬅](https://github.com/spkesDE/com.spkes.telegramNotifications/blob/feature/moreLanguages/locales/en.json)

# Current status of this can be found [here](https://community.homey.app/t/app-pro-telegram/66622#feedback-bugs-5).

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [July 29, 2023, 6:06pm UTC](https://community.homey.app/t/app-pro-telegram/66622/262 "2023-07-29T18:06:34Z")

</div>

Nice to see some people already participating 🙂

> [@spkesDE](#):
>
> This is the first version of v3 of the Telegraf app.

As for version 3 - we are now on 2.8.1 - it is already the one we shall keep eye on re memory utilisation? It’s not much, 300kB difference but do you expect some issues?

[Previous page](https://community.homey.app/t/app-pro-telegram/66622.md?page=12)

[Next page](https://community.homey.app/t/app-pro-telegram/66622.md?page=14)
