# \[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:** 16\
**Page:** 23

<div class="post-metadata">

**Author:** ![Eddy\_Poot](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eddy_poot/32/9878_2.png) [@Eddy\_Poot](https://community.homey.app/u/Eddy_Poot)\
**Post date:** [August 3, 2025, 8:00am UTC](https://community.homey.app/t/app-pro-telegram/66622/450 "2025-08-03T08:00:34Z")

</div>

Thanks for the fast respons.

I was already afraid of that.

---

<div class="post-metadata">

**Author:** ![MozartSailor](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@MozartSailor](https://community.homey.app/u/MozartSailor)\
**Post date:** [December 23, 2025, 1:39pm UTC](https://community.homey.app/t/app-pro-telegram/66622/453 "2025-12-23T13:39:00Z")

</div>

I have installed this app on my Homey Self-Hosted (SHS) on Synology.  
My previous HP23 had no issue sending images together with a message. But I am unable to do the same on the SHS. I had installed a new Telegram Bot on the SHS.

Would you be able to help see whether it is an app issue or SHS issue?  
Thank you.

e6b98dc8-aafd-4d1f-995a-e69e4c0d1e86

---

<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:** [December 23, 2025, 2:00pm UTC](https://community.homey.app/t/app-pro-telegram/66622/454 "2025-12-23T14:00:28Z")

</div>

```auto
[err] GrammyError: Call to 'sendPhoto' failed! (400: Bad Request: IMAGE_PROCESS_FAILED) 
payload: { chat_id: REDACTED , photo: 'attach://REDACTED', caption: REDACTED, parse_mode: undefined, message_thread_id: undefined, disable_notification: false }, ok: false, error_code: 400, description: 'Bad Request: IMAGE_PROCESS_FAILED', parameters: {} }

```

The API Returns a 400 error. Looks like the format of the “attach” url won’t work. I don’t know what changed Athom did to the SHS platform. Telegram needs full HTTPS Url. In the code I convert the Image tag to a Local or a Homey Cloud URL. I don’t know why it will tries to send the image like this.

Maybe I find some time to install a SHS Server if Athom gives us free access…

---

<div class="post-metadata">

**Author:** ![Seinuh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/seinuh/32/16357_2.png) [@Seinuh](https://community.homey.app/u/Seinuh)\
**Post date:** [December 27, 2025, 3:47pm UTC](https://community.homey.app/t/app-pro-telegram/66622/455 "2025-12-27T15:47:38Z")

</div>

confirmed image sending tested from home assistant Self hosted server homey

 ![Schermafbeelding 2025-12-27 164431](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/2/d2422aa96c7abc7740d208b3c7ae401a0fee5bca.png)

---

<div class="post-metadata">

**Author:** ![Riccardo\_Ancona](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/riccardo_ancona/32/103880_2.png) [@Riccardo\_Ancona](https://community.homey.app/u/Riccardo_Ancona)\
**Post date:** [January 8, 2026, 10:28am UTC](https://community.homey.app/t/app-pro-telegram/66622/456 "2026-01-08T10:28:34Z")

</div>

Hi! I need a tutorial to start using the bot.

I followed these steps:

> **[Telegram | Homey](https://homey.app/en-it/app/com.spkes.telegramNotifications/Telegram/)**
>
> Effortlessly control your smart home with Telegram

1. Install the app on your smart home hub.  
2. Create a Telegram bot by searching for @Botfather in the Telegram search bar and selecting the @Botfather bot@Botfather  
3. Start the @Botfather b@Botfathert by click@Botfatherng the “Start” butt@Botfathern or by sending@Botfatherthe /newbot command@Botfatherto create a new bot.  
4. (Optional) To ensure privacy, set the bot to private by entering /setjoingroup DISABLED and set the privacy to DISABLED by entering /setprivacy.  
5. Enter the token in the app settings.  
6. Start the bot by sending the /start command in Telegram, and follow the instructions. Each user must also send the bot the /start command. You can share the bot with others by searching for it in Telegram or by sharing the profile link.  
7. Enjoy controlling your smart home from Telegram!

And I was able to add my bot to two private groups (done many months ago).

Now I added to one of the groups the “Topics” from Telegram, and it immediately stopped working and now I don’t know how to restore it to simple group or how to make it work with topics.

Is there a well written and clear tutorial on how to do that? I think a tutorial with screenshots would be perfect, this bot is quite complex to configure (i did in the past and now I don’t even know how to do it for one simple group).

If a donation is needed, I will be happy to do it

---

<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:** [January 8, 2026, 10:42am UTC](https://community.homey.app/t/app-pro-telegram/66622/457 "2026-01-08T10:42:03Z")

</div>

You have to re-register the group, since you probably upgraded from a group to a supergroup.  
use /start again and fix your flows with the new group

---

<div class="post-metadata">

**Author:** ![Riccardo\_Ancona](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/riccardo_ancona/32/103880_2.png) [@Riccardo\_Ancona](https://community.homey.app/u/Riccardo_Ancona)\
**Post date:** [January 8, 2026, 10:56am UTC](https://community.homey.app/t/app-pro-telegram/66622/458 "2026-01-08T10:56:59Z")

</div>

Many thank you for your reply! /start where should I type it? If I type it inside the bot’s chat, does not do anything.

Edit: I stopped the bot, changed API Token, updated API Token but still to no avail

---

<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:** [January 8, 2026, 11:22am UTC](https://community.homey.app/t/app-pro-telegram/66622/459 "2026-01-08T11:22:59Z")

</div>

When the App Settings says it’s running. It running. But somehow you manged to use the API twice.  
`terminated by other getUpdates request; make sure that only one bot instance is running`

And as I said, the old group chat was upgraded. Make sure /setprivacy is set to false/DISABLED  
Make sure the Bot is the the group AND has rights to read/write. Supergroup has permissions.  
And then use /start. It should register… Then update the flows  
`Bad Request: group chat was upgraded to a supergroup chat`

---

<div class="post-metadata">

**Author:** ![Seinuh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/seinuh/32/16357_2.png) [@Seinuh](https://community.homey.app/u/Seinuh)\
**Post date:** [February 19, 2026, 3:34pm UTC](https://community.homey.app/t/app-pro-telegram/66622/460 "2026-02-19T15:34:35Z")

</div>

@spkesDE

Did you think there’s a solution for the image sending issue on homey SHS :

Diagnostic report:

775d6ab5-44bb-4a9a-a61c-e26023de1645

---

<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:** [February 19, 2026, 3:47pm UTC](https://community.homey.app/t/app-pro-telegram/66622/461 "2026-02-19T15:47:43Z")

</div>

No error in the diag. report.

As long Homey doesn’t provide free SHS access for Devs, I can’t work on that.

---

<div class="post-metadata">

**Author:** ![Seinuh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/seinuh/32/16357_2.png) [@Seinuh](https://community.homey.app/u/Seinuh)\
**Post date:** [February 19, 2026, 4:04pm UTC](https://community.homey.app/t/app-pro-telegram/66622/462 "2026-02-19T16:04:06Z")

</div>

I understand, hopefully they will support it for devs…

Error : ECONNREFUSED is the problem 🤷‍♂️

---

<div class="post-metadata">

**Author:** ![Seinuh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/seinuh/32/16357_2.png) [@Seinuh](https://community.homey.app/u/Seinuh)\
**Post date:** [February 23, 2026, 1:02pm UTC](https://community.homey.app/t/app-pro-telegram/66622/463 "2026-02-23T13:02:06Z")

</div>

After homey SHS update it’s fixxed 💯🫡

---

<div class="post-metadata">

**Author:** ![Rett\_Pop](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rett_pop/32/69805_2.png) [@Rett\_Pop](https://community.homey.app/u/Rett_Pop)\
**Post date:** [May 17, 2026, 6:42pm UTC](https://community.homey.app/t/app-pro-telegram/66622/464 "2026-05-17T18:42:49Z")

</div>

Today I have found that in the users list of the app on my Homey Pro 2023 there several (4 or 5) users I have never added. Unfortunately, I didn’t think to make a screenshoot and just immediately removed them and restarted the app. One of them was like “I’m broken”. I do not know how to check for any presense of those users. Checked logs in the app configuration UI. There are only errors from different times. How could it happen? What kind of treat could it bring? What should I reset?

---

<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 17, 2026, 7:05pm UTC](https://community.homey.app/t/app-pro-telegram/66622/465 "2026-05-17T19:05:13Z")

</div>

Use a password 🙂

It shouldn’t make any dangerous stuff.  
Since the bot is outgoing and only monitoring stuff that you registered and use in a flow

---

<div class="post-metadata">

**Author:** ![Rett\_Pop](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rett_pop/32/69805_2.png) [@Rett\_Pop](https://community.homey.app/u/Rett_Pop)\
**Post date:** [May 17, 2026, 7:36pm UTC](https://community.homey.app/t/app-pro-telegram/66622/466 "2026-05-17T19:36:52Z")

</div>

I also do not see any possible danger. But the fact that there are unknown users…

---

<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, 2026, 9:38pm UTC](https://community.homey.app/t/app-pro-telegram/66622/467 "2026-06-28T21:38:19Z")

</div>

# [Version 2.17.8 Bug Fixes & Dependency Updates 🐛](https://homey.app/a/com.spkes.telegramNotifications)

Hey,

This update focuses on improving reliability when sending Telegram notifications from Homey.

### 🎉 What’s New in Version 2.17.8:

> - Improved handling for blocked Telegram users.
> - Automatically removes stale chats when Telegram reports that the bot was blocked or forbidden.
> - Fixed unhandled promise rejections when sending questions or notifications.
> - Updated npm dependencies.
> - Fixed reported security issues in dependencies.

If you still see Telegram delivery errors, please check whether the target chat/user is still registered and has not blocked the bot.

### 💡 Support My Development:

If you appreciate my work and want to help out, consider buying me an energy drink ⚡ or a beer 🍺.  
You can donate via [PayPal](https://www.paypal.com/paypalme/spikes022). Your generosity helps keep this solo project moving forward!

### 👩‍💻 Calling All Developers!

Are you a developer? Want to contribute to this project? I’d love to collaborate! Feel free to send a pull request on GitHub and join me in making this app even better.

## 🙏 Thank you for your support!

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