Cannot get MSS110 (hardware:7.0.0 firmware:7.3.46) to switch from Meross cloud to local MQTT server #88
Comments
|
Hello, Did you try the option |
|
Also, are you sure you are using the latest version of meross ? I know your folder is named with the latest version, but some options seem to be missing. Can you show us the output of |
|
Tried --use-wifi-x but no change unfortunately. |
|
lawrence@lawrence-PC: I appreciate the thoroughness. I set up this Ubuntu install only a few days ago, and made sure I was using the latest version of meross-info/meross-setup from this repo. As you can see from the log I attached to my first message, I also tried the 2.0 beta to see if that worked. So far, I've managed to get a bunch of older revision mss110 plugs to work fine - along with a variety of switches - it's just this newer one (and a mss510xr light switch, but that will be a separate case) that are giving me any problems. |
|
Sorry, the beta deprecated the option Why do you use the option |
|
At that point, I was basically just trying anything I could think of - including if it worked after the device was connected (hence giving it the IP of the device on my AP). This is my first time using this utility and modding Meross stuff, so I didn't want to make any assumptions about what would work and what wouldn't (in case I overlooked something silly). |
|
So you successfully connected the plug to your Wi-Fi using this utility or the official Meross app ? |
|
For now, it's connected to the Meross cloud using their app. Hoping to get this one bound to my local MQTT server, as I got everything else on it. All I got left are just 4 of this particular version of the mss110 and 1 of the mss510xr light switches that are still connected to the Meross cloud. |
|
Can you show me the output of |
|
Sure. I just quickly removed it from Meross app, connected to the wifi ap that appeared (Meross_SW_4534) and ran that command (substituting in the real wifi details, of course): Setting up device with IP 10.10.10.1
{ Error Unable to connect to device |
|
Sorry, I will have to go to bed, but here are some leads:
|
|
Unfortunately neither of those options worked. However I did discover something potentially interesting. I happened to have another MSS110 in a box here, and meross-info confirms it is the same hardware version (7.0.0) but a slightly older firmware (7.3.19 instead of 7.3.46). meross-setup still fails with the same error when trying to get it to connect to my MQTT server but I can use meross-setup to connect to my wifi AP (whereas the one on the newer firmware won't even do that with meross-setup). This leads me to believe that Meross has probably changed something in a recent firmware that is breaking things. |
|
I wonder if this may be something related to the HomeKit version of these devices, as these newer MSS110 support Homekit. Whereas the ones I have that work, don't support it. I've ordered a 4 pack of both from Amazon, and am expecting them to be delivered on the 13th. Unless anyone has any other ideas, I will follow up next week and let you know my findings. |
|
@lcwsoft Can you please try again with Node 20? |
|
unfortunately no dice with node 20 either (I used the latest LTS version available via nvm, 20.18.1). meross-setup 1.0.15 fails with: Error Unable to connect to device The 2.0 beta fails with a "socket hang up" error it seems. I'm not familiar with Node, so I'm not sure if that's just a different error for the same underlying issue. The output is a bit more verbose than 1.0.15 and may provide more info: lawrence@lawrence-PC:~/Downloads/meross-bak/Meross-1.0.15/bin$ npx meross@beta setup --wifi-ssid 'XXXX-iot' --wifi-pass 'XXXX' --verbose RequestError: socket hang up Node.js v20.18.1 |
|
If you need any additional information, please feel free to ask. While I'm not familiar with Node, I am a pretty quick learner and eager to help. |
|
Hi sorry for the delay. We have had some trouble with HomeKit and Bluetooth devices in the past, so I wouldn't be surprised if that's related. Based on your previous messages, I will assume that the device can be pared via WIFI as it previously responded to Could you try the following steps?
|
|
No worries :) The device that could be paired with Wifi is an MSS110 with the same hardware version, but older firmware. I am using Ubuntu 24.04 LTS (not in a VM) with Node 20 as you asked earlier, and followed those steps. Here's the result: lawrence@lawrence-PC: That's all I got . |
|
In Ubuntu what is the output of |
|
I'll follow up on this later today or tomorrow. |
|
Please make sure you use the latest version when you follow up. |
|
Updated to the new 1.0.16 version and tried again, but no luck. I connected to the wifi offered by the mss110, ran meross-setup --version, then the ip addr show, then meross-setup with both NODE_OPTIONS set and not set, as well as --use-wifi-x (mostly just to rule it out). lawrence@lawrence-PC:~/Downloads/meross-1.0.16/Meross-1.0.16/bin$ ./meross-setup --version
1.0.16
lawrence@lawrence-PC:~/Downloads/meross-1.0.16/Meross-1.0.16/bin$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 30:85:a9:8f:49:7e brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ac:5a:fc:55:fe:92 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.100/24 brd 10.10.10.255 scope global dynamic noprefixroute wlp4s0
valid_lft 7146sec preferred_lft 7146sec
inet6 fe80::794e:9f94:c4a4:fb7f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
lawrence@lawrence-PC:~/Downloads/meross-1.0.16/Meross-1.0.16/bin$ ./meross-setup --wifi-ssid '<XXX>-iot' --wifi-pass 'XXXXX' --verbose
Setting up device with IP 10.10.10.1
> POST undefined
> Host: 10.10.10.1
> Accept: application/json, text/plain, */*
> Content-Type: application/json
>
{
header: {
from: '',
method: 'GET',
namespace: 'Appliance.System.All',
messageId: 'c0f2c368ce1e5b4460a00cba42442931',
timestamp: 1736948201,
sign: '27bd0bdea9ad722a686439fb7e723999'
},
payload: {}
}
< 200 OK
< content-type: application/json
< connection: close
<
{
header: {
messageId: 'c0f2c368ce1e5b4460a00cba42442931',
namespace: 'Appliance.System.All',
method: 'GETACK',
payloadVersion: 1,
from: '/appliance/2307069048441951200148e1e9cf4546/publish',
uuid: '2307069048441951200148e1e9cf4546',
timestamp: 425,
timestampMs: 625,
sign: 'a28a56be11e48e33957251c7947e394b'
},
payload: {
all: {
system: {
hardware: {
type: 'mss110',
subType: 'un',
version: '7.0.0',
chipType: 'rtl8710cm',
uuid: '2307069048441951200148e1e9cf4546',
macAddress: '48:e1:e9:cf:45:46'
},
firmware: {
version: '7.3.46',
homekitVersion: '6.3',
compileTime: '2024/08/21-10:15:09',
encrypt: 1,
wifiMac: '',
innerIp: '10.10.10.1',
server: '',
port: 0,
userId: 0
},
time: { timestamp: 425, timezone: '', timeRule: [] },
online: { status: 2, bindId: '', who: 0 }
},
digest: {
togglex: [ { channel: 0, onoff: 1, lmTime: 0 } ],
triggerx: [],
timerx: []
}
}
}
}
┌─────────────┬───────────────────────────────────────────────────────────────────────────────┐
│Device │mss110 un rtl8710cm (hardware:7.0.0 firmware:7.3.46) │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│UUID │2307069048441951200148e1e9cf4546 │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│Mac address │48:e1:e9:cf:45:46 │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│IP address │10.10.10.1 │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│Credentials │User: 48:e1:e9:cf:45:46 │
│ │Password: 0_8737bd6ae86640ba6e396e20b0bf4bbd │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│MQTT topics │Publishes to: /appliance/2307069048441951200148e1e9cf4546/publish │
│ │Subscribes to: /appliance/2307069048441951200148e1e9cf4546/subscribe │
└─────────────┴───────────────────────────────────────────────────────────────────────────────┘
> POST undefined
> Host: 10.10.10.1
> Accept: application/json, text/plain, */*
> Content-Type: application/json
>
{
header: {
from: '',
method: 'SET',
namespace: 'Appliance.Config.Wifi',
messageId: '5e0f1a3d757b56ef2fb1069528b8e58e',
timestamp: 1736948201,
sign: 'a4445ffcbe6574e38041a7ffe30d23b1'
},
payload: { wifi: { ssid: '== REDACTED ==', password: '== REDACTED ==' } }
}
Error Unable to connect to device
Are you connected to the device's Access Point?
lawrence@lawrence-PC:~/Downloads/meross-1.0.16/Meross-1.0.16/bin$ NODE_OPTIONS='--insecure-http-parser' ./meross-setup --wifi-ssid '<XXX>-iot' --wifi-pass 'XXXXX' --verbose
Setting up device with IP 10.10.10.1
> POST undefined
> Host: 10.10.10.1
> Accept: application/json, text/plain, */*
> Content-Type: application/json
>
{
header: {
from: '',
method: 'GET',
namespace: 'Appliance.System.All',
messageId: '3758a36437e3c269db43d56c0c06c970',
timestamp: 1736948213,
sign: '45615a027a328ea0c11a305b98f1a67e'
},
payload: {}
}
(node:6709) Warning: Using insecure HTTP parsing
(Use `node --trace-warnings ...` to show where the warning was created)
< 200 OK
< content-type: application/json
< connection: close
<
{
header: {
messageId: '3758a36437e3c269db43d56c0c06c970',
namespace: 'Appliance.System.All',
method: 'GETACK',
payloadVersion: 1,
from: '/appliance/2307069048441951200148e1e9cf4546/publish',
uuid: '2307069048441951200148e1e9cf4546',
timestamp: 437,
timestampMs: 451,
sign: '22262ad813f421875a9c68b4d9d9219d'
},
payload: {
all: {
system: {
hardware: {
type: 'mss110',
subType: 'un',
version: '7.0.0',
chipType: 'rtl8710cm',
uuid: '2307069048441951200148e1e9cf4546',
macAddress: '48:e1:e9:cf:45:46'
},
firmware: {
version: '7.3.46',
homekitVersion: '6.3',
compileTime: '2024/08/21-10:15:09',
encrypt: 1,
wifiMac: '',
innerIp: '10.10.10.1',
server: '',
port: 0,
userId: 0
},
time: { timestamp: 437, timezone: '', timeRule: [] },
online: { status: 2, bindId: '', who: 0 }
},
digest: {
togglex: [ { channel: 0, onoff: 1, lmTime: 0 } ],
triggerx: [],
timerx: []
}
}
}
}
┌─────────────┬───────────────────────────────────────────────────────────────────────────────┐
│Device │mss110 un rtl8710cm (hardware:7.0.0 firmware:7.3.46) │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│UUID │2307069048441951200148e1e9cf4546 │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│Mac address │48:e1:e9:cf:45:46 │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│IP address │10.10.10.1 │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│Credentials │User: 48:e1:e9:cf:45:46 │
│ │Password: 0_8737bd6ae86640ba6e396e20b0bf4bbd │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│MQTT topics │Publishes to: /appliance/2307069048441951200148e1e9cf4546/publish │
│ │Subscribes to: /appliance/2307069048441951200148e1e9cf4546/subscribe │
└─────────────┴───────────────────────────────────────────────────────────────────────────────┘
> POST undefined
> Host: 10.10.10.1
> Accept: application/json, text/plain, */*
> Content-Type: application/json
>
{
header: {
from: '',
method: 'SET',
namespace: 'Appliance.Config.Wifi',
messageId: '90dec92089ad047350f063af37b8c8d9',
timestamp: 1736948213,
sign: 'e0995968b7ec7f9bb0a923184c79ab7c'
},
payload: { wifi: { ssid: '== REDACTED ==', password: '== REDACTED ==' } }
}
Error Unable to connect to device
Are you connected to the device's Access Point?
lawrence@lawrence-PC:~/Downloads/meross-1.0.16/Meross-1.0.16/bin$ NODE_OPTIONS='--insecure-http-parser' ./meross-setup --wifi-ssid '<XXX>-iot' --wifi-pass 'XXXXX' --verbose --use-wifi-x
Setting up device with IP 10.10.10.1
> POST undefined
> Host: 10.10.10.1
> Accept: application/json, text/plain, */*
> Content-Type: application/json
>
{
header: {
from: '',
method: 'GET',
namespace: 'Appliance.System.All',
messageId: '06d06ed4f69f01543f12bd5ce3b4329e',
timestamp: 1736948226,
sign: '7229c30d9831711fa7b35b23cd9e51ea'
},
payload: {}
}
(node:6716) Warning: Using insecure HTTP parsing
(Use `node --trace-warnings ...` to show where the warning was created)
< 200 OK
< content-type: application/json
< connection: close
<
{
header: {
messageId: '06d06ed4f69f01543f12bd5ce3b4329e',
namespace: 'Appliance.System.All',
method: 'GETACK',
payloadVersion: 1,
from: '/appliance/2307069048441951200148e1e9cf4546/publish',
uuid: '2307069048441951200148e1e9cf4546',
timestamp: 450,
timestampMs: 754,
sign: '9b9ae24ef91de563d0ad87e6fbbae53c'
},
payload: {
all: {
system: {
hardware: {
type: 'mss110',
subType: 'un',
version: '7.0.0',
chipType: 'rtl8710cm',
uuid: '2307069048441951200148e1e9cf4546',
macAddress: '48:e1:e9:cf:45:46'
},
firmware: {
version: '7.3.46',
homekitVersion: '6.3',
compileTime: '2024/08/21-10:15:09',
encrypt: 1,
wifiMac: '',
innerIp: '10.10.10.1',
server: '',
port: 0,
userId: 0
},
time: { timestamp: 450, timezone: '', timeRule: [] },
online: { status: 2, bindId: '', who: 0 }
},
digest: {
togglex: [ { channel: 0, onoff: 1, lmTime: 0 } ],
triggerx: [],
timerx: []
}
}
}
}
┌─────────────┬───────────────────────────────────────────────────────────────────────────────┐
│Device │mss110 un rtl8710cm (hardware:7.0.0 firmware:7.3.46) │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│UUID │2307069048441951200148e1e9cf4546 │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│Mac address │48:e1:e9:cf:45:46 │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│IP address │10.10.10.1 │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│Credentials │User: 48:e1:e9:cf:45:46 │
│ │Password: 0_8737bd6ae86640ba6e396e20b0bf4bbd │
├─────────────┼───────────────────────────────────────────────────────────────────────────────┤
│MQTT topics │Publishes to: /appliance/2307069048441951200148e1e9cf4546/publish │
│ │Subscribes to: /appliance/2307069048441951200148e1e9cf4546/subscribe │
└─────────────┴───────────────────────────────────────────────────────────────────────────────┘
> POST undefined
> Host: 10.10.10.1
> Accept: application/json, text/plain, */*
> Content-Type: application/json
>
{
header: {
from: '',
method: 'GET',
namespace: 'Appliance.System.All',
messageId: '98cd9247adac5d91c82c8a8f322f3ad6',
timestamp: 1736948227,
sign: 'c1fded88afebc9d1c1c0446e9ed00616'
},
payload: {}
}
< 200 OK
< content-type: application/json
< connection: close
<
{
header: {
messageId: '98cd9247adac5d91c82c8a8f322f3ad6',
namespace: 'Appliance.System.All',
method: 'GETACK',
payloadVersion: 1,
from: '/appliance/2307069048441951200148e1e9cf4546/publish',
uuid: '2307069048441951200148e1e9cf4546',
timestamp: 450,
timestampMs: 101,
sign: '74f0037d91fc2883fb206468bffd9fe1'
},
payload: {
all: {
system: {
hardware: {
type: 'mss110',
subType: 'un',
version: '7.0.0',
chipType: 'rtl8710cm',
uuid: '2307069048441951200148e1e9cf4546',
macAddress: '48:e1:e9:cf:45:46'
},
firmware: {
version: '7.3.46',
homekitVersion: '6.3',
compileTime: '2024/08/21-10:15:09',
encrypt: 1,
wifiMac: '',
innerIp: '10.10.10.1',
server: '',
port: 0,
userId: 0
},
time: { timestamp: 450, timezone: '', timeRule: [] },
online: { status: 2, bindId: '', who: 0 }
},
digest: {
togglex: [ { channel: 0, onoff: 1, lmTime: 0 } ],
triggerx: [],
timerx: []
}
}
}
}
> POST undefined
> Host: 10.10.10.1
> Accept: application/json, text/plain, */*
> Content-Type: application/json
>
{
header: {
from: '',
method: 'SET',
namespace: 'Appliance.Config.WifiX',
messageId: '95f5e3ccc881d29caf40c715986c7c5b',
timestamp: 1736948227,
sign: '89a5c946eb3a3c4cf0465558ce1bd5ba'
},
payload: {
wifi: {
ssid: '== REDACTED ==',
password: '== REDACTED == '
}
}
}
Error Unable to connect to device
Are you connected to the device's Access Point?
lawrence@lawrence-PC:~/Downloads/meross-1.0.16/Meross-1.0.16/bin$ |
|
I updated your comment to add formatting 10.10.10.1 does seem to be the IP of your device as it correctly manages to get the device info and promptly dies when we try to submit the WIFI credentials. Okay a couple of things:
|
|
Sorry about the formatting :) To answer your thoughts:
--include-wifi doesn't work on the current firmware either: I do seem to recall that --include-wifi worked on the original firmware for the version 7.0.0 of the MSS110 (7.3.19). I've since managed to get a new in box one (with those specs) to connect to wifi using the earlier meross-setup command on 1.0.15 with just wifi details, and then link up with HomeAssistant using their HomeKit integration. It's not what I hoped, but it's a decent enough compromise to accomplish my original goal (which was to get off Meross cloud). That leads me to think that they've changed something in a firmware update that prevents meross-setup from working as intended. I've spent a fair bit of time tinkering around with these plugs and don't know if there's anything else I can do. Unfortunately between work and life, it might be quite some time before I can get deeper. In the meantime, I'm going to reach out to Meross as I've heard that they will remotely downgrade firmware and see if I can get my remaining plugs down to an older firmware and get up on Homekit to at least resolve this for me. If I find another of these plugs laying around and don't have a need for it, would you be open to having me send it to you? I tried ordering 2 packs of these plugs from Amazon over Christmas, and ended up with a newer hardware version (8.0.0) that used Bluetooth instead of wifi for setup, and ended up returning them. I don't know if version 7.0.0 is readily available anymore, but would gladly offer one if I can and it would help out. |
|
Thanks for the updates. I'll try to delve into the android app and see of there is anything specific for the MSS110 + version 7.3.46 firmware and respond back if I discover anything. If you do find a spare device I'll happily accept it for science. You can email me to arrange. |
|
Hi, just for recording keeping I am also having the same issues with the same device (homekit enabled) ┌─────────────┬───────────────────────────────────────────────────────────────── best of luck on this :) |
|
I've added some field to the header of the messages. I couldn't see anything else in the source that's missing. |
|
I'm off today, so I had a chance to give that updated version with one of the MSS110 plugs running firmware 7.3.46 (hardware version 7.0.0). Unfortunately no luck: |
|
meross-info output: |
|
Thanks for trying. Looking further into the code and the responses you provided, I have noticed a flag regarding encryption. It's possible the device expects the Homekit data to be passed encrypted to the device before it's willing to continue. I don't have the time to look into this currently but maybe towards the weekend. |
I am in the process of getting my MSS110 plugs 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 the plugs (hardware version 2 and firmware version 2.x), however I got 4 of a newer version (hardware:7.0.0 firmware:7.3.46) 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.
The Meross app has no issues setting up this plug, and your utility has no issue with older version MSS110 plugs that I have, so 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.
mss110 version 700 debug data.txt
The text was updated successfully, but these errors were encountered: