@Chillout this is a whatsapp update issue i guess. I’m still waiting for the SDK to update which should resolve these things.
What might help is opening the whatsapp app on your phone and a additional whatsapp web connection
@Chillout this is a whatsapp update issue i guess. I’m still waiting for the SDK to update which should resolve these things.
What might help is opening the whatsapp app on your phone and a additional whatsapp web connection
Ah no worries. Then my housemembers are lucky (for now) that I’ll be the only one getting the notifications for the washing machine
Thanks for the great work you’re doing!
So maybe this will help? Still beta so i will wait.
https://community.homey.app/t/homey-pro-2016-2019-firmware-updates/54910/185?u=mike1233
@Mike1233 No that’s the Homey SDK. waiting for Whatsapp SDK
→ [APP][Pro] WhatsApp - Simple. Reliable. Private - #2030 by martijnpoppen
→ Releases · WhiskeySockets/Baileys · GitHub
@martijnpoppen Ok, excuses me. Sorry.
How did you make the message with 2 flows met kapotte variabelen?
Nice! Can you help me with that and tell me in a private message? It is not for here in the topic
- or if you want to help more peope ![]()
Changelog:
NEW:
1: NEW: Update whatsapp SDK to version 7.0.0-rc-9 (BETA!)
2: MAJOR: Update app to NodeJS 22 (requires Homey v12.9.0+)FIXES:
1: None
If you find any issues, send a diagnostic report
Note: Before sending a report make sure to reproduce the issue so the issue will be visible in the report
Via Homey Mobile app:
More - apps - WhatsApp - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)
Via Homey Webapp:
Settings wheel bottom left - Select WhatsApp - Click on send diagnostic report
You can install this version by clicking the link above and press install (do not remove the app, only press install)
Don’t want to be part of a test version? Install the live version → WhatsApp | Homey
Hi, lost homey whatsapp sinds yesterday. endless repair attempts….
9e92cbfc-6f69-4f5d-ab49-0da067243990
best regards, Luc
@Onyx i just put a test version out. It’s above your post. please try that.
Hi Martin
When I try to repair my device, the app always crashes. Vers. 2.0.1
3e8549af-0967-4316-be7a-c0575d1047d2
thanks, test version did load but the card new message received wasn’t working. however installing the latest standard version did work after that. probaly just a glitch somewhere.
@Asterix yes still a known issue unfortunately.
Can you try piaring it as a new device? (remove before that)
Flow can be fixed wth: [HOW-TO][Pro][Cloud] - Tool to FIX (advanced) flows after removing and re-adding devices
Hi @martijnpoppen, first of all really great App! I tried an advanced flow with the latest official version and the “Message received” card. It didn’t worked. I updated to the Beta release 2.0.1 that fixed it for a few tries but it broke again. I downgraded to the official version again and since then its working fine. Why am I telling this. For me it seems homey is able to read the messages from a specific chat.
But I have an issue to show this messages in the dashboard widget. I deleted and added the device several times but that didn’t help. The dashboard widget is only showing the messages that homey sent, even I have set the two toggles (show messages I sent, show messages others have sent) in the config to yes. Do you have an idea why incoming messages are not shown?
Thanks and regards, Jan
Hi @Jan_Tendahl
Yes the behaviour between live and test version is known and expected unfortunately. the test/beta version still has some quirks but so does the live version. I really hope there will be stable SDK released soon ![]()
Oh that’s interesting, is it a group app or a specific 1-1 chat?
Thanks for the reply!
The widget should show a group chat.
Hello martijnpoppen
I deleted the existing device and added the new one, so far no crash ![]()
If there is a crash again in the coming days, I would get in touch.
Ps: I tried the script, but I’m too stupid for it, but it would certainly be practical…
Is the issue regarding not beiing able to repair and the crash still active / worked on? Or is it unsolveable?
@JvdMeulen when the SDK version is final the issue will be addressed until now waiting for that version