No Pairing: Scan failed wifi networks

[brunosso]

Hi Alberto!

I'm italian and i trying to pair some MSS305 Smart Plug.

I follow all the setup, now i'm at the moment of pairing device.

I've installed the app on 3 Android Device (Android 13, Android 9)

I have the same problem. When i'm in the device pair section, no device shows, and if i force the update i receive baloon error "Scan failed wifi networks"

What can i do?

[gitgoober]

Same here. I have a recent MSS310 Samrt Plug. Looks like these will only pair via bluetooth with the official app.

[Eleven44p]

I encountered the same issue with my new Meross MSS310 smart plugs. Here’s a bit of background:

Initial Setup:

• I purchased new Meross MSS310 smart plugs.
• I set up the Meross Local Addon in Home Assistant and also installed a custom pairer app on my Android device (Samsung Galaxy Fold 3).
• At this point, I hadn't registered or installed the official Meross app, and these were my first Meross devices.

First Attempt:

• I turned on the smart plugs and ensured they were in pairing mode.
• Using the custom pairer app, I connected to the Meross Local Addon in Home Assistant. Everything seemed fine in the web UI.

Pairing Issues:

• When I tried to pair the devices with the custom pairer app, nothing was found, and I received an error message stating "Scan failed wifi networks."
• I reset the devices and tried again multiple times with no success.

Using the Official App:

• the same issue occurred—devices were not pairing.
• I initially thought the devices were faulty until I noticed an error message indicating the need to allow Nearby devices.

After allowing Nearby devices permission, the smart plugs paired and worked perfectly.

Current Issue:

I found that the permission for Nearby devices on the Pairer app was also enabled. However, this did not change anything, i.e. device discovery on Pairer app. Issue persists

[tbosnjak]

Hi,

I suspect that I have the same issue as the others in this thread. Meross device is the smart plug MSS305 and 2 phones one with android 13 and one with the android 14.

Additionally I can't allow the 'Nearby devices' permission to the pairer app.

[albertogeniola]

Hi @tbosnjak ,

I've just issued a new version of the pairer, v0.0.11. It should be available anytime soon from playstore. Can you please update and test if the new version works as expected? I've added the missing piece of logic that handles the NEARBY-DEVICES permission.

[tbosnjak]

Hi @albertogeniola,

thank you for the fast reaction. I updated the pairer app to 0.0.11 and I could add permissions for NEARBY-DEVICE, but it didn't help with pairing this device. I'm no sure if it will be of help or not, but there is no visible WiFi for this device that I can manually connect like it is the case with shellys. I verified that deice works as expected by connecting it into Meross app and putting it back into pairing mode.

Some of symptoms are: failed network scan, scan rate limited wait xx seconds...

Hope this helps a bit.

Cheers,
Tihomir

[albertogeniola]

Hi there!

Can you please report the wifi-ssid name you see when scanning "manually" with other APPs?

The current meross-pairer filters wifi names with specific ssid-naming rules. Maybe this class of devices is using a ssid-name that gets filtered out...

[tbosnjak]

That's the point, there is no wifi visible to pair to. Here are the WiFis that I see when I plug-in the device in pairing mode:

I'm very fresh in Meross and after a bit of reading I got feeling that Meross changed their way how they pair devices. I suspect that they first use some discovery protocol to which device responds with connection parameters. As already said even if, there were no new WiFis visible, the device popped up in the official app.

I tried to use the CLI tool to setup the device, but it proved to be useless since I can't connect manually to the device.

Pls don't take my rant as fact or pointed to you.

Thanks for you great work.

Cheers,
Tihomir

[tbosnjak]

A small update. If I connect to a bluetooth device MBRL_8110, then my smart socket doesn't show up in the official app. And the official app explicitly states that it requires bluetooth.

[albertogeniola]

I was going to suggest you that. IMHO, Meross is now using Bluetooth to discover the device, then they probably instrument the pairing phase via hidden SSIDs.

Unfortunately I haven't studied this new feature yet, so I cannot implement a new pairing mechanism in the short term...

[tbosnjak]

This is what I expected. Thanks anyway.