Setup does not work for newer MSS310 about meross HOT 8 CLOSED

@jluixjurado

What i've found is that new plugs doesn't seem to communicate through wifi but through bluetooth (in fact, when scanning for bluetooth devices you can find something like MRBL_XXXX, where XXXX are the last four digits of the plug MAC address.

That poses an issue of these new plugs. What I would recommend is to pair using the Meross app, then once it's on your network, reconfigure it using the tools.

@M0NsTeRRR

PS : I've tried with the rewrite branch at beginning but I can't get it worked as their is works to do

Sorry, I continued working on it and I pushed the changes because I needed to move to a new machine. I have time off now, so I'll endeavour to get this into a working state before New Year.

Sure no worries, it's how open source works 😁. Thanks for your amazing job ;)

from meross.

I have published a new release that includes #75

from meross.

Is there any information in the verbose output that would be helpful?

Also you used double quotes on your WiFi ssid, so try replacing with single quotes.

I wonder if the device ssid is hidden

from meross.

if you want to try it, there's an experimental branch that I started which allows you to send only parts of the setup.
https://github.com/bytespider/Meross/tree/feature/rewrite it's not very well documented at the moment so I will try my best to help.

from meross.

Hello, tested today with two MSS315, firmware 9.5.31 and hardware 9.0.0. It seems that the SSID is hidden maybe it's the same for you @fritut08.

My setup with home assistant :

1. Install official meross app
2. Setup the plug with meross app (it will configure wifi)
3. On home assistant install https://github.com/krahabb/meross_lan, connect meross cloud account. Add devices and get key from one device.
4. Install bytespider project and comment out line 95 to 102 (as we don't change wifi settings only MQTT) in bin/meross-setup
5. Get IP address of the plug from your DHCP and do npx meross info --verbose -g <IP> --key <KEY>, you should see plug configuration, it means everything is ready and you can go below (step not required)
6. Reconfigure meross MQTT plug npx meross setup --gateway 'IP' --wifi-ssid 'wedontcare' --wifi-pass 'wedontcare' --mqtt mqtts://<IP or HOSTNAME of MQTT> --wifi-cipher 3 --wifi-encryption 6 --wifi-channel 6 --verbose --key 'KEY'
7. Do step 5, it should display your new MQTT broker :)
8. Remove the plug on meross app, delete your account and delete the application

PS : I've tried with the rewrite branch at beginning but I can't get it worked as their is works to do. Old function not renammed like setSystemTime() to configureSystemTime(), missing an await keyword on _send function for got library and still after that I got a ECONNRESET. Much simpler to comment out wifi settings :)

Thanks for your library I can keep my privacy away from third parties cloud :)

from meross.

Hi there. I've got the same problem with my new mss310. What i've found is that new plugs doesn't seem to communicate through wifi but through bluetooth (in fact, when scanning for bluetooth devices you can find something like MRBL_XXXX, where XXXX are the last four digits of the plug MAC address. That's why CUSTOM PAIRER can't find the new plugs!

from meross.

@jluixjurado

What i've found is that new plugs doesn't seem to communicate through wifi but through bluetooth (in fact, when scanning for bluetooth devices you can find something like MRBL_XXXX, where XXXX are the last four digits of the plug MAC address.

That poses an issue of these new plugs. What I would recommend is to pair using the Meross app, then once it's on your network, reconfigure it using the tools.

@M0NsTeRRR

PS : I've tried with the rewrite branch at beginning but I can't get it worked as their is works to do

Sorry, I continued working on it and I pushed the changes because I needed to move to a new machine. I have time off now, so I'll endeavour to get this into a working state before New Year.

from meross.

@jluixjurado

What i've found is that new plugs doesn't seem to communicate through wifi but through bluetooth (in fact, when scanning for bluetooth devices you can find something like MRBL_XXXX, where XXXX are the last four digits of the plug MAC address.

That poses an issue of these new plugs. What I would recommend is to pair using the Meross app, then once it's on your network, reconfigure it using the tools.

@M0NsTeRRR

PS : I've tried with the rewrite branch at beginning but I can't get it worked as their is works to do

Sorry, I continued working on it and I pushed the changes because I needed to move to a new machine. I have time off now, so I'll endeavour to get this into a working state before New Year.

As referenced here krahabb/meross_lan#346 (comment) I've created a small pull request to allow for mqtt setup only, which fixes this issue #75

from meross.