You assumed right
I also have the same problems.
If you send a message to the callmebot number +34 644 52 74 88 on Signal, it doesnât get deliverd anymore. I didnât get any reply yet. Callmebot is run by only one person, so it might be a while before this gets fixed, if it gets fixed at all.
Yeah, thatâs where i got the email addresses from. Itâs the first time i received notifications that an email could not be sent with possible causes:
- Typo in email-address (I used copy /paste)
- Verify email address exists
- The recipient is refusing you (what really?)
So thatâs why i formulated it like that ![]()
Iâve got slight understanding for refusing a known Simple Login domain. I find it harder to believe that an email address from a custom domain would be refused.
But this is getting more offtopic now. Glad to see you and Norbert could send an email ![]()
Itâs started working again for me this afternoon.
Yes over here as well ![]()
Confirmed. Case closed I hope ![]()
![]()
Keep in mind CallMeBot is a one-person-project ![]()
I got this mail:
Hi Bert,
*Iâve started the year with problems everywhere. I canât wait for it to end!!!
I have been experiencing some issues with the API due to changes on Signal side but I have been working on them and they are now solved.
Thank you for your patience and I apologize for the inconvenience.
Best regards,
Borja*
Why doesnât Homey send emoticons to WhatsApp anymore? I still see them in Homey. I havenât received an update.
Edit anwser.
I got a response from callbot. The server crashed frequently due to too much information.
Thatâs why there are no more emoticons in whatsapp messages. Not problem from Homey.
@Ralf_Huelsmann Thank you for your kind donation. Much appreciated! ![]()
![]()
@Gruijter Hi there! App the whatsapp connection crashed and is not working. Last message I received was on 25 february and the whatsapp device in homey says last seen on 27 february 23:59. Restart doesnât work. Worked for years and payment is done too. What can I do?
In the logging I see this:
Haha thanks! The solution was too simple, which made me think that wouldnât be it. Itâs working again.
Hopefully it wonât come back, it took me a month now to notice that I didnât get the messages. Do you know if there is a possibility to make/get a notification when the bot is paused again?
Feedback here. Requesting to change a couple of lines in readme / text:
The text below is on both forum and github see [APP][Pro] WhatsApp, Signal, Telegram, Facebook messenger - #2 by Gruijter and GitHub - gruijter/com.gruijter.callmebot: Let Homey send messages to your Whatsapp, Signal, Telegram and Facebook messenger ¡ GitHub
See instruction below; that instruction is incorrect.
I would change it (because it did cost me time to figure out the issue).
At method signal you should not include your âphone numberâ. You should directly use âphone IDâ or âphoneâ.
So i tried to enter:
- my phone number
- APIKEY received from signal
Getting error:
there was an error!!! Error Num:2Error Text:Trying to access array offset on value of type null
So use the full long phone=xxx (what is 36 char in my case) ; you need to fill in the xxx as the âAPI keyâ
So part:
fill in your phone number and apikey
Full text from the links:
Add the phone number +34 603 21 25 97 into your Phone Contacts. Name it âHomey CallMeBot Signalâ.
Send this message âI allow callmebot to send me messagesâ to the new Contact created (using your Signal Messaging of course)
The bot will answer you with your personal apikey.
Add the Signal device in Homey and fill in your phone number and apikey. You can now start sending messages from a flow.
Thx! Will update the docs.
v2.0.0 is ready for testing:
-
Complete app rewrite.
-
Updated README.
-
Added all translations.
-
Many fixes and stability improvements.
This is a massive rewrite of the entire app. It makes use of the latest Homey and NodeJS features. Many stability improvements were implemented, and errors in image and voice messages tackled (I hope).
Please test the new version and let me know if you find any issues. If all is good I will push it to stable release.
Maybe you need to use âCallMeBotâ instead of âcallmebotâ?









