I spent the whole weekend working on it and I found what the problem was. My WhatsApp within Homey was still linked to my old WhatsApp number. I removed it and set up WhatsApp again with the new number, and then it worked again. I did have to set everything up again (my flows), but I’m sure I’ll manage that today as well.
Hey!
To whom it may concern.
From the 3rd of may i was experiencing a high cpu load (x2 up to x5), could not understand where from. Sent in a ticket to homey and the diagnostic report showed “Error on the WhatsApp App that there are over 2000 future messages before the App crashes”.
But i couldn’t see that anywhere as i only use whatsapp for a couple of things, and still dont understand the 2000 messages haha. I send maybe 4 per week as max.
And today i tested it out, but it just failed, not clear why.
So i removed the linked device and repaired it, and now it seems to be working.
Hope this helps dev and/or anyone that might be experiencing issues.
Hey @j_wak !
You’re not the only one seeing this, it’s a known issue related to the underlying WhatsApp SDK (Baileys). What you’re describing (high CPU, the “2000 future messages” in the diagnostics, and re-pairing the linked device fixing it) matches the pattern exactly.
The “2000 messages” isn’t messages you sent: it’s an internal buffer in the SDK that fills up when the session gets out of sync, which then spikes the CPU until the app crashes. Re-pairing resets that
But with this info I might be able to figure something out ! Thanks
Awesome! Team work yey!
If i can help in any way, just holla! 
Hi! I’m running into a problem where I’m trying to use Homey to send an automatic reply to WhatsApp messages when I don’t have my phone with me. I’ve set up the flow so that when a message comes in that isn’t a group message, Homey sends a reply back to the “sender number”. This is automatically generated by the first card “when a new message has been received”. However, this number is very often incorrect. I found this out because I have a notification sent to myself with that same “sender number” variable. There you can see really strange numbers showing up. Does anyone know if I’m doing something wrong here myself, or if this is a bug in the app?
@NSchooneveldt correct that’s a LID instead of a phone number. That’s new in WhatsApp. Already implemented in the test version of the app. Which stays in test until there’s a official SDK update
So you can install the test version and try that out
@martijnpoppen question about sending a poll, I noticed all 8 optionals are marked as required but I would like to create a poll with just two options could that be fixed?
@Sre yes check the test version of the app
Cool it works, thanks
Test build crashes within minutes after pairing
Crash id: a5fae865-a836-4e82-9123-a6b176628208
Yeah but polls with less then 8 options are broken in the stable version 
@Sre not broken. Never implemented. But I’m not going to do multiple release only for this poll change. So it will be released together with the new SDK
no problem I dont mind cherry picking and backporting changes on old versions and creating a local build for myself, but I noticed you havent pushed to github in the last 6 months, could you please push your changes? Many thanks!
@Sre you can’t as you need to cherrypick the library as well
New app update (
TEST: 2.2.0):
Big stability release. Updated to the final WhatsApp SDK release candidate (rc10) — first SDK update since November, packs 5+ months of upstream work. Combined with internal fixes targeting the high-CPU and “future messages” crashes some of you have been reporting since last releases.
Changelog:
NEW:
1: NEW: WhatsApp SDK update to 7.0.0-rc10 (final release candidate)
2: MAJOR: Update app to NodeJS 22 (requires Homey v12.9.0+)FIXES:
1: FIX: high CPU usage and crashes caused by “future messages” pile-up
2: FIX: reconnect storms with overlapping reconnect attempts
3: FIX: device store filling up over time
4: FIX: 30 second delay on sending messages when the device was reconnecting
5: FIX: stale state surviving a logged-out / clear-session event
6: FIX: infinite query timeout causing memory growth
7: FIX: pre-key cleanup at startup could crash on installs with very large stores
8: FIX: parsing LID to phonenumber (SDK v7) (phonenumbers were encrypted this fixes it)
9: FIX: Poll card now only has 2 required items
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
@Sre new update above 
(also pushed to git)
For me 2.2.0 doesn’t show a pairing code
on web I see this in the console:
De bron van ‘https://192-168-1-107.homey.homeylocal.com/manager/drivers/assets/css/deprecated-pincode.css’ is geblokkeerd vanwege een niet-overeenkomend MIME-type (‘text/html’) (X-Content-Type-Options: nosniff). pair
TypeError: can’t access property “split”, data is null
https://192-168-1-107.homey.homeylocal.com/pair/ line 2 > injectedScript:7
_onPairMessage https://192-168-1-107.homey.homeylocal.com/js/homey.drivers.js:194
@Sre will check. No need to send console as that won’t help
Should repair the device work? I have got a red triangle with a exclamation mark.
But repair does not work. Adding a new device gives a time out.
The app has worked for me, till the update today.
