You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am in the process of getting my light switches to connect to my local MQTT server and removing them from the Meross cloud, with the goal of going fully localized. Your utility works fine with older versions of them, however I got 1 of a newer version (mss510xr hardware:4.0.0 firmware:4.3.2) that I cannot get to connect no matter what (using the same steps as you've documented).
To reproduce, I do the following under Ubuntu 24.04 LTS with npx installed via npm and NodeJS being managed via nvm (I tried several versions, including 22 and 23.5):
Remove the plug from Meross cloud using the app
Connect to its wifi ap
Run meross info to get the MQTT user and password details so I can add the needed user to my MQTT server (running version 6 provided with HomeAssistant).
Run Meross setup with my wifi ap details and MQTT server address, to no avail.
I ran both version 1.0.15 and the newest beta from npm, and in both cases, it seems that the requests fail with connection errors. I've attached my terminal output, with verbosity and only necessary redaction of sensitive details, to show what happens.
I'm guessing that newer versions of the device use different endpoints or require different requests to them - unfortunately that's a bit beyond my knowledge. However I will gladly try any suggestions that you may have or provide any details that you may need.
Please note that I did have to edit the shebang lines in your utilities, otherwise they would fail with "no such file" errors mentioning "nodejs --no-warnings"). Apparently that's a common issue and not specific to them.
Update: it looks like this switch and firmware version still work with having meross-setup configure only the WIFI AP settings. If I do that, it connects to my home network and I can then add it to HomeAssistant using HomeKit (with the 8 digit code printed on the front of the switch) without adding it via the Meross app. Probably not the ideal outcome, but it works for me for now :)
I am in the process of getting my light switches to connect to my local MQTT server and removing them from the Meross cloud, with the goal of going fully localized. Your utility works fine with older versions of them, however I got 1 of a newer version (mss510xr hardware:4.0.0 firmware:4.3.2) that I cannot get to connect no matter what (using the same steps as you've documented).
To reproduce, I do the following under Ubuntu 24.04 LTS with npx installed via npm and NodeJS being managed via nvm (I tried several versions, including 22 and 23.5):
I ran both version 1.0.15 and the newest beta from npm, and in both cases, it seems that the requests fail with connection errors. I've attached my terminal output, with verbosity and only necessary redaction of sensitive details, to show what happens.
I'm guessing that newer versions of the device use different endpoints or require different requests to them - unfortunately that's a bit beyond my knowledge. However I will gladly try any suggestions that you may have or provide any details that you may need.
Please note that I did have to edit the shebang lines in your utilities, otherwise they would fail with "no such file" errors mentioning "nodejs --no-warnings"). Apparently that's a common issue and not specific to them.
I've attached a log of the terminal commands and output.
mss510xr version 400 debug data.txt
The text was updated successfully, but these errors were encountered: