@Frekel Flow Utilities might be a nice app for that instead of Homeyscript ![]()
![]()

9af982a3-bceb-4697-9175-2d64241d8fb8
@Michael_Zimmer hmm it seems to break on a broadcast message. Can you:
- restart the app
- Try the widget again
- Send a new report
== offtopic ==
I did but it doesn’t allow for image recognition
App was restarted.
The same problem still exists:
3051d7ec-f2a9-4fed-92d0-d47f3c174206
@Michael_Zimmer can you please describe the steps you took?
I see a lot of things in the logs but I makes no sense to me in relation to the dashboard widget
New app update (
LIVE: 1.27.8):
Changelog:
NEW:
1: NoneFIXES:
1: FIX: widgets setup
If you find any issues, send a report via the mobile homey app
More - apps - Whatsapp - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)
Issue list: [APP][Pro] WhatsApp - Simple. Reliable. Private - #3 by martijnpoppen
@Michael_Zimmer fixed, see above ![]()
The widget is working now.
Thanks a lot for you help and very fast answer.
That’s how it makes fun with homey.
I’ve been having an issue with the Whatsapp on Homey, for the past few days. After the latest update, everything was still working fine, but now images are no longer being sent to WhatsApp, while text messages go through without any problems.
I’ve already tried re-pairing the phone number, restarting the WhatsApp app on Homey, and even restarting Homey itself, but the issue persists.
Has anyone else experienced this?
@JJJJ please send a diagnostic report after sending a image
aa97f2bc-e1c6-451a-9782-b539eb24c59b

@JJJJ youre sending a xml page as image
That’s not a image and can’t be downloaded
Now I see it indeed. I can see that the snaps from my doorbell are coming through again, which weren’t being delivered before. So the issue seems to be resolved. Thanks!
@martijnpoppen Strange bug: Sending an Email in the content field leads to this error, any idea? (Love that app 150%
Thanx!)

@Stefan_1 It’s not failing on the content field but failing on the number. There’s a E.164 number validator in there. So looks to me the number is not correct
Thanx @martijnpoppen so much, well the number receives every other text message. I just changed the text field to that email address. I just copy/paste the number with a E.164 number validator, the number also passes through. Then I tried another different number, same problem.
Can you experience that bug on your side?
No bug:

Bug:
