Also created a new report: 8e7c964e-baec-44a9-b57f-73f12d71949c
@Frekel sorry i can’t see what is wrong in that flow. can you explain the screenshot so i know what i’m looking at?
Edit: Sorry i checked the logs, but i think the issue you describing is not clear to me, what exactly is not working?
Mentions are changed in the latest update, if that’s what you mean,
Maybe you can also share the real data to me in a DM as the striked trough images makes it really hard to understand
Problem:
Normally I get the correct phonenumber from the Homey device (10 digit number prefixed with @), now I get a 15 digit number with also prefixed with a @ sign)
What if you remove the homeyscript? I think that’s causing the issue you’re seeing as that’s now part of the app code
Hi,
So I have two problems:
- The mention in the Text are not returning the correct phonenumber of the user.
So instead of the @31612345673161234567 (10 digit), I got this @256789123456789 (15 digit)
Even if I run the latest (1.34.0) test version - When I use the “Text contains” card in the flow, I never get a match. If the text is “Hello Lily” and the card is “if Text contains Lily” it always returns False.
Edit: The second issue is only when I do a test run in the Flow. If I use Whatsapp, it continues the flow as expected (except I now check if the 15 digit number is in the text)
- The 256577672065109 is a LID. Which should be fixed in the latest update. So think the homey script is the culprit here, but if you can check it without let me know
- This i can’t see in your logs, can you make sure to test that so i can see it coming back in a report? → Edit: yes correct test flow works different as it really checks a message and i cant get that to work with testing, so testing is not reliable at all.
I have removed that step in the code. Great addition in the code 
@Frekel awesome!
Yes i found it yesterday when i was testing mentions if they were parsed correctly from LID to Phonenumber and then i did fix this 
@Frekel can you run it again and send a new report, it’s not visible in the last one you send. HOmey caps of to 100 lines
f3776236-3324-4181-a425-9516714964b5
@Frekel the example from your screenshot is not in the logs.
@martijnpoppen I will create a new one tomorrow morning. I also see that my messages don’t get send to the group. Some do and some don’t.
I will create a new user/device tomorrow so I can test with a brand new clean slate 
Thanks for the quick replies!!!
Hmm on my end the test version resulted in a broken device whatsapp (and repair keeps showing a white screen with spinner) adding a new device didn’t work out with the code to connect… Diagnostic report: d743afce-77ea-49a0-a018-39c3a5088441
@Wout_van_den_Dool and the live version? Also noticed this, working on it 
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…
@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 
