# \[APP\]\[Pro\] WhatsApp, Signal, Telegram, Facebook messenger

**URL:** <https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374>\
**Category:** Apps\
**Created:** [June 12, 2021, 5:59pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374 "2021-06-12T17:59:51Z")\
**Posts on this page:** 20\
**Page:** 13

<div class="post-metadata">

**Author:** ![Tomas\_Severa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tomas_severa/32/33929_2.png) [@Tomas\_Severa](https://community.homey.app/u/Tomas_Severa)\
**Post date:** [August 24, 2023, 9:14am UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/246 "2023-08-24T09:14:04Z")

</div>

Did, you solved it?  
Have same error message.  
If i send a push notification in Homey app that works, but with call me bot to Signal or Messenger get the error  
Have Homey 2023

---

<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:** [August 24, 2023, 3:36pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/247 "2023-08-24T15:36:36Z")

</div>

Is it working by using the test URL?:

> ![Screenshot from 2023-08-24 17-34-47](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/a/0a5abbb5d99e8647516ca4daeed9fbb852b33dc2.png)

---

<div class="post-metadata">

**Author:** ![Tomas\_Severa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tomas_severa/32/33929_2.png) [@Tomas\_Severa](https://community.homey.app/u/Tomas_Severa)\
**Post date:** [August 24, 2023, 4:04pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/248 "2023-08-24T16:04:24Z")

</div>

> [@Peter\_Kawa](#):
>
> [https://signal.callmebot.com/signal/send.php?phone=[phone\_number]&apikey=[your\_apikey]&image=[url\_image]](https://signal.callmebot.com/signal/send.php?phone=%5Bphone_number%5D&apikey=%5Byour_apikey%5D&image=%5Burl_image%5D)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/9/9905c8df7381c6affae536091207df0b24a17119.jpeg)

How to find out the URL it is the one if i open the picture and the one in the searching bar? Like this one ([https://192-168-0-254.homey.homeylocal.com/api/image/090b358d-0ae7-4618-bff0-d594741b4594?\_r=0.10605115494978978](https://192-168-0-254.homey.homeylocal.com/api/image/090b358d-0ae7-4618-bff0-d594741b4594?_r=0.10605115494978978))

If its so i get this message

Apikey Correct.  
Error: Image format not recognized.  
Only image formats are allowed (.jpg .gif .png .etc)

---

<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:** [August 24, 2023, 4:24pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/249 "2023-08-24T16:24:47Z")

</div>

Ah, my bad, I didn’t realize they aren´t plain pictures 🫣 🤔

But when you pic an online pic, you can test if your signal account still can send pictures. You can use this one:  
[https://www.callmebot.com/wp-content/uploads/pinguin.jpg](https://www.callmebot.com/wp-content/uploads/pinguin.jp)

---

<div class="post-metadata">

**Author:** ![Tomas\_Severa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tomas_severa/32/33929_2.png) [@Tomas\_Severa](https://community.homey.app/u/Tomas_Severa)\
**Post date:** [August 24, 2023, 4:43pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/250 "2023-08-24T16:43:11Z")

</div>

Yes this work . it send the picture to Signal

---

<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:** [August 24, 2023, 4:51pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/251 "2023-08-24T16:51:07Z")

</div>

There’s more users having issues with sending pictures by apps with the Pro 2023.  
It is not just one app which is affected  
You should report your issue also to support imho [https://homey.app/support](https://homey.app/support)

> [@\[Homey Pro 2023\] Problems, issues and bugs](https://community.homey.app/t/homey-pro-2023-problems-issues-and-bugs/77502/17):
>
> since Homey2023 I have a problem with sending pictures  
> with email sender or callmebot incorrect  
> and I’m not sure if it’s up to callmebot or the source of the images  
> I send a picture from a camera (onvif app) via signal and get an error 403 Forbidden
> 
> if I send the same picture via email sender app then the attachment is a xx.bin  
> this is probably the reason for the error
> 
> with the homey 2019 no problems with both apps
> 
> the xx.bin is a jpg with bad name extention

---

<div class="post-metadata">

**Author:** ![Tomas\_Severa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tomas_severa/32/33929_2.png) [@Tomas\_Severa](https://community.homey.app/u/Tomas_Severa)\
**Post date:** [August 24, 2023, 4:55pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/252 "2023-08-24T16:55:59Z")

</div>

But in the Homey push notification is the picture present. So Homey can handle it.  
It guess when i write to support i guess they will say that is the problem from the Callmebot app itself, because casting pictures to Google chromcast devices work also…

---

<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:** [August 24, 2023, 5:09pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/253 "2023-08-24T17:09:50Z")

</div>

> [@Tomas\_Severa](#):
>
> So Homey can handle it.

True, but the push service is not an (community) app, Athom probably adjusted the push service as well, or it is some other difference between the push service and community apps.

> [@Tomas\_Severa](#):
>
> i guess they will say that is the problem from the Callmebot app

They can´t I think, Email Sender is also affected:

> [@\[Homey Pro 2023\] Problems, issues and bugs](https://community.homey.app/t/homey-pro-2023-problems-issues-and-bugs/77502/17):
>
> problem with sending pictures  
> with email sender or callmebot incorrect

> **[Email sender](https://homey.app/en-us/app/email.sender/Email-sender/)**
>
> Send email using Homey

---

<div class="post-metadata">

**Author:** ![riiskongen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/riiskongen/32/34733_2.png) [@riiskongen](https://community.homey.app/u/riiskongen)\
**Post date:** [September 19, 2023, 1:40pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/254 "2023-09-19T13:40:08Z")

</div>

Are there any news regarding this issue. Still cant send images with signal using the CallMeBot app. The imgage is on the Homey but will not be sent…

---

<div class="post-metadata">

**Author:** ![Bert\_Wissink](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bert_wissink/32/30075_2.png) [@Bert\_Wissink](https://community.homey.app/u/Bert_Wissink)\
**Post date:** [October 16, 2023, 10:42am UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/257 "2023-10-16T10:42:10Z")

</div>

Just send Stop via Whatsapp to the bot. You will get a message that the bot has been put on pause and all future API calls will be ignored.

---

<div class="post-metadata">

**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\
**Post date:** [October 22, 2023, 11:01am UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/258 "2023-10-22T11:01:39Z")

</div>

@riiskongen Many thx for your kind donation! 🥰

---

<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:** [October 30, 2023, 7:08pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/259 "2023-10-30T19:08:32Z")

</div>

Smart move 🤪 😉 😉

> ![Screenshot from 2023-10-30 19-58-19](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/d/fd6b6a17e696548045fbed2e7251aba90b63682b.png)

---

<div class="post-metadata">

**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\
**Post date:** [November 3, 2023, 9:00am UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/260 "2023-11-03T09:00:51Z")

</div>

@Michael_Ridzewski many thx for your kind donation! 🥰

---

<div class="post-metadata">

**Author:** ![Munnikie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/munnikie/32/31427_2.png) [@Munnikie](https://community.homey.app/u/Munnikie)\
**Post date:** [November 11, 2023, 10:50am UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/261 "2023-11-11T10:50:30Z")

</div>

Should be resolved with the latest Homey update.

---

<div class="post-metadata">

**Author:** ![riiskongen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/riiskongen/32/34733_2.png) [@riiskongen](https://community.homey.app/u/riiskongen)\
**Post date:** [November 15, 2023, 9:34am UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/262 "2023-11-15T09:34:10Z")

</div>

Yes indeed the last update 10.1.0 solved the problem!!!

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [January 25, 2024, 6:34pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/263 "2024-01-25T18:34:06Z")

</div>

Anyone recognizing this message;  
(“Waiting for message” sorry for the Dutch screenshot))

 ![1000006836](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/7/c752782f2d33a1a226c8f0ad1f907bed0dc9e230.jpeg)

When I click “more info”, the Whatsapp website tells me it has to do with encryption and that the senders phone is not online, see [link](https://faq.whatsapp.com/3398056720476987#:~:text=This%20might%20be%20because%3A,online%2C%20the%20contact%20was%20offline.)

Have not received earlier messages from Callmebot, so can’t have to do with rate limits. It’s status in Whatsapp is “online” too…

---

<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:** [January 25, 2024, 9:30pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/264 "2024-01-25T21:30:51Z")

</div>

You can run a test at this page, Henk:

> **[Test Whatsapp API from Web Browser](https://www.callmebot.com/blog/test-whatsapp-api/)**
>
> Complete the form to test the API WhatsApp Phone number: ApiKey: Text Message to Send: Complete the Form URL to use:

I have no issues sending WhatsApp messages from Homey

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [January 25, 2024, 9:50pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/265 "2024-01-25T21:50:03Z")

</div>

Thanks for the tip, @Peter_Kawa.  
That does work. Still the first one is not being delivered.  
Tested messages from Homey again and that gets delivered too:

 ![1000006840](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/6/2633379fc498c55358c07bf0e73e1c46d29c6174.jpeg)  
Do you, or someone else have any idea how this works in Callmebot?  
Perhaps a network glitch?  
I couldn’t find a server status history as well. Perhaps a short downtime?

---

<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:** [January 25, 2024, 9:57pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/266 "2024-01-25T21:57:09Z")

</div>

I think it was a temporary glitch or hickup.

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [January 25, 2024, 10:01pm UTC](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374/267 "2024-01-25T22:01:12Z")

</div>

Hope so, just installed this app yesterday, so I hope I was just unlucky to get an erreor so quickly then… 😉

[Previous page](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374.md?page=12)

[Next page](https://community.homey.app/t/app-pro-whatsapp-signal-telegram-facebook-messenger/48374.md?page=14)
