Meross MSS310 setup

[marcocattaneogotam]

Meross MSS310 setup

[moviedan]

Amazing @donavanbecker - worked like a charm. I’m going to work through and set the other plugs up now. Thanks for your help.

[donavanbecker]

Just released Version 1.1.0, if you want to give it a try.

[marcocattaneogotam]

Thanks. I've updated the plugin, the config (with the right model), but no, it doesn't work.

This is the current config:

{
"model": "MSS310",
"name": "presa",
"deviceUrl": "192.168.1.141",
"channel": 0,
"messageId": "d8a5c2e967c923bd80014df179bbfb59",
"timestamp": 0,
"sign": "82aec8a0295bd874e12ab2c3f31f77",
"accessory": "Meross"
}

This is what I get:

[4/28/2020, 8:51:08 PM] [presa] Set succeeded: {
header: {
messageId: 'd8a5c2e967c923bd80014df179bbfb59',
namespace: 'Appliance.Control.ToggleX',
method: 'ERROR',
payloadVersion: 1,
from: '/appliance/1912249200127825188148e1e9146f24/publish',
timestamp: 1588107068,
timestampMs: 670,
sign: '2487c9d69692f34d4bed1c79ca1d59e8'
},
payload: { error: { code: 5001, detail: 'sign error' } }
}
[4/28/2020, 8:51:08 PM] [presa] setOnCharacteristicHandler: false
[4/28/2020, 8:51:08 PM] [presa] calling getOnCharacteristicHandler for MSS310 at 192.168.1.141...
(node:374) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'digest' of undefined

[4/28/2020, 8:51:08 PM] [presa] calling getOnCharacteristicHandler for MSS310 at 192.168.1.141...
(node:374) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'digest' of undefined
at Meross.getOnCharacteristicHandler (/usr/lib/node_modules/homebridge-meross/index.js:297:34)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:374) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)

Thanks again

[donavanbecker]

@marcocattaneogotam what are you using to get your timestamp, messageId, and sign?

Can you provide the request body? from the /config.

[moviedan]

I’m having a similar issue. I originally used Charles Proxy on the device to sniff traffic to the plug, and retrieved similar time stamp, messageID, and Sign values to @marcocattaneogotam.

I don’t think they’re right though. My understanding is we’re supposed to grab these as a result of the call to /config, but in Charles I keep getting a 503 when calling that end point. Any ideas?

[donavanbecker]

Hey @moviedan, can you update to 1.1.0? And then can you try these steps and let me know if it works?

Downlod HTTP Catcher! It is going to be a little different then my instructions on the credentials wiki, but it works.

• Hit Configure in the top right.
• Enable VPN.
• Hit Start to start collecting.
• In "Search URL", search for your IP of the meross plug.
• You will see a Post to /config with a 200 Response with application/json.
• Click into that and hit Response header.
• From there you will find the sign,timestamp, and messageId.

[marcocattaneogotam]

It worked for me too. Thanks!

[donavanbecker]

@marcocattaneogotam good to hear!!

[IsonCode]

Hello, I have the same problem with MSS310 plugin version v5.0.1, homebridge v1.3.4.
I have successfully set up 2 MSS210 plugs, but I have tried to set up with the same exact method a MS310 plug and it does not work.
I know how to proceed te setup (because I have already successfully setup 2 plugs).