I don’t know what you mean, but before the new version all was working fine, but wanted to test new version (to reduce memory) but now ended up with a not working device, I have trust this will be solved, so keep up the good work…
1 Like
@Wout_van_den_Dool I understand, but the live version should still work.
And next to that, i already noticed this issue today and working on it.
Hope it’s clear now 
@Frekel I checked and see what you mean, unfortunately i cant change the text to a phonennumber as that will break the mention.
But the mention it self is already properly parsed so it does mention correctly.
So when you have a flow like: Message received - Send Whatsapp. (like when you reply back to the person)
For your use case it’s still relevant to check for the LID in the message as that;s the only way for now
@martijnpoppen New day, new changes 
I created the following report c2d3ebd6-7ea2-4579-bf15-ceb472e14bbe
This is the message in Whatsapp:
This is the flow:
and this is the result:
Notifications:
Whatsapp:
Two things:
- I have the card “text contains” that still returns true for the LID instead of the Phonenumber
- I do not get the last result message in Whatsapp. Even if the notification on the end is succesfully triggered.
If you want to chat on slack to debug this faster I am available all day
- Already replied to you, see post above yours.
- known issue, update is coming
@martijnpoppen
Sorry for the message. Didn’t see your earlier reply.
I will keep checking for the LID. No problem!
And for the second issue, I just need to wait.
Thanks again for the quick replies. I really appreciate it 
1 Like
New app update (
TEST: 1.35.0):
Changelog:
NEW:
1: NEW: update to SDK v7
2: NEW: add flowcard to check group link
3: NEW: add Poll flow card
4: NEW: memory improvementsFIXES:
1: FIX: parsing LID to phonenumber (v7) (phonenumbers were encrypted this fixes it)
2: FIX: Reduce Memory usage
3: FIX: various small fixes
4: FIX: properly parse group invite links with extra parameters (like ?mode=ems_copy_t…)
5: FIX: mentions for passing trough received messages
6: FIX: messages sometimes not handled
7: FIX: connection drops
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)
You can install the test version by clicking the link above and press install
Don’t want to be part of this test version? Install the live version → WhatsApp | Homey
@Frekel @Wout_van_den_Dool see above
Fixed got a crash, reboot and now i was able to repair the devices 0d9e2794-56c7-4f96-be05-c39209be9ae1
1 Like
@Wout_van_den_Dool nice 
Hope it stays like that, and repair should now be finally fixed aswell
@martijnpoppen I have a return messages so everything is fine for my issues.
1 Like
@Frekel Nice!
And maybe while we at it, can you also see if the memory of the app went down for you? (via insights on the homey web app)
This is the graph from this year:
And from last week:
Note: I am currently heavily using the app as I try to resurrect my AI agent (which communicates with my family thru whatsapp → homey → open ai)
1 Like
@Frekel thanks, i see the same behaviour, around 70-80.
Before it had around 100. So looks good to me
1 Like
@martijnpoppen “test” version looks good no issues after 24h testing 
1 Like
@martijnpoppen oops it’s chrashed ..
510fe41d-5d85-444e-86c6-c6be16d18e03
After chrashing it’s repairs itself.. 
@Seinuh please share the graph as well
@martijnpoppen also a flow running now to check if it’s chrashed.. did you see the crash in my report ?
@Seinuh yes i did, but the memory is quite high on your homey, mine runs around 70.
how many connections did you setup?
