Meross device pairing error (com.meross.meross)

[FauconSpartiate]

Please answer the following questions for yourself before submitting an issue.

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

AdGuard version

V4.1

Environment

- OS: Android 13
- Device: Oneplus 8T
- Firmware: KB2003_13.1.0.581(EX01)

Root access

• Yes, I have it.

What filters do you have enabled?

No filters enabled

What Stealth Mode options do you have enabled?

/

Issue Details

Steps to reproduce:

• Open app
• Add new device
• Select device that does pairing over WiFi and not bluetooth

Expected Behavior

Pairing succeeds flawlessly

Actual Behavior

Setup fails unless AdGuard is turned off

Screenshots

Screenshot 1:

Additional Information

Original issue in AdguardFilters repository: AdguardTeam/AdguardFilters#160557

[maxikuzmin]

@FauconSpartiate unfortunately I don't have the devices to connect to Meross to reprodece this.
It would be nice to get your logs.

• Enable debug logging:

Settings -> General -> Advanced -> Logging level -> Debug

• Reproduce the issue related to the button behaviour, then remember the exact time when it happened

• Collect logs:

Settings -> General -> Advanced -> Export logs and system info

• Sent this file to devteam@adguard.com:

mention the 4989 number in the subject
specify the exact time when the issue occurred

[maxikuzmin]

@FauconSpartiate any news? I didn't get your logs in the mail

[FauconSpartiate]

@maxikuzmin I don't have the device near me right now, I'll do it as soon as I do.

[maxikuzmin]

@FauconSpartiate any news?

[FauconSpartiate]

@maxikuzmin I just sent the logs per email

[maxikuzmin]

@FauconSpartiate we need some more time. Please wait

[maxikuzmin]

@FauconSpartiate does the app filtering exception help you?
Go to App management -> Merross app -> Route traffic through AdGuard -> off switch

[FauconSpartiate]

Yes, like mentioned in the original issue: AdguardTeam/AdguardFilters#160557 (comment)

[maxikuzmin]

@FauconSpartiate could you temporarily remove the exception for the Merross app, repeat the steps, and see what requests are blocked in the filtering log? Please send screenshots to devteam@adguard.com. Blocked requests should be opened and screenshot the detailed information of the blocked request

[maxikuzmin]

@maxikuzmin any news?

[FauconSpartiate]

@maxikuzmin
Sorry for the delay.
I've just tried, and don't see anything obvious. The only requests that get blocked are ones to a stat server, but these occur also when having the app open normally, not while trying to pairthe device.
I also tried overriding this rule and still allowing it, but it didn't fix the bug.

So disabling filtering entirely doesn't solve the problem, but disabling the routing through Adguard does.
So it's probably a problem with the path the packets take, not the filtering having some false positives...

[maxikuzmin]

@FauconSpartiate great, we've decided to add a default to the exclusions for Meross filtering. This will be implemented in the next updates