Well, I can't really direct you to an easy solution, but if you are using meross-homeassistant the login api is hidden there and access tokens together with the key are retrieved for sure and saved somewhere (at least in code if not persisted)

Following https://github.com/albertogeniola/MerossIot/wiki/HTTP-APIs I still can get my login tokens. Just to recap I'm using this 'pseudo-coded' payload

POST https://iot.meross.com/v1/Auth/Login HTTP/1.1
Content-Type: application/json

{
    "params": base64({"email": "YOUR_EMAIL", "password": "YOUR_PASSWORD"}),
    "sign": md5("23x17ahWarFH6w29" + timestamp + nonce + params),
    "timestamp": 0,
    "nonce": "9123456789ABCDEF"
}

using the dummy fields provided it should go like this:

POST https://iot.meross.com/v1/Auth/Login HTTP/1.1
Content-Type: application/json

{
    "params": "eyJlbWFpbCI6ICJZT1VSX0VNQUlMIiwgInBhc3N3b3JkIjogIllPVVJfUEFTU1dPUkQifQ==",
    "sign": "192a561b2f5d06d096a2b9be3c3f02b1",
    "timestamp": 0,
    "nonce": "9123456789ABCDEF"
}

I've used some online tools to base64 encode and md5 hash the fields and then I'm using a vs-code plugin to send the POST but any curl like utility should do

Discovery OK but impossible to config mss310 #69

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions