[question] what is the AMnual API Setup User Key?

[wsw70]

(apologises if this is not the right place for questions but I did not see a Discussion area open)

I have been using locally paired devices together with @krahabb meross_lan integraton for years (right from the start).

It worked so well that I did not come back to it after having paired everything I had and I now need to do pairings again. The problem is that I completely forgot how to do it.

Back in the day, I used both a Linux-based pairer and the Custom Meross Pairer. It changed a lot by now and I cannot find anymore how to configure Meross devices so that they talk to a local MQTT broker (all the ones I have do talk to it now, without issues - the problem is with the new ones).

Since I use a docker-based HA installation, I do not have Add-Ons. It seems the Meross Local LAN Addon is compulsory for the app (or not, I am not sure).

There is however the manual option, which requires two elements: the User ID and the User Key. What are they?

Or maybe there is a more straightforward way to do the pairing (ultimately I will use @bytespider Meross tool (excellent), but I will have to dual boot to Linux, not having a handy device around EDIT: ah wonderful! I can run it off npx and my shell history even had the command in memory (which is short of a miracle))

[donations-bot-prod]

Donation bot here. Supporters can mark their interest in this issue by adding a comment
starting with "+1" (without quotes) or adding the "#supporter_sponsor" keyword
(without quotes) in their comments.

You can become a donor by subscribing as Sponsor from the GitHub sponsorship page or from the BuyMeACoffee page.

Issues marked by donors will be labeled accordingly and handled with special care

[bytespider]

@wsw70 i'm glad you were able to find the original commands you used to get your devices paired to your HA MQTT broker.

If you're considering adding new Meross/Refoss devices you should be aware that the paring method has changed significantly and my tool will not work. For those devices its often better to pair using their App and then reconfigure the device once it's on your network. The Matter devices can be paired directly in HA using the built-in Matter support.

[wsw70]

adding new Meross/Refoss (...) my tool will not work

Ah. Thanks @bytespider for the information! I have however older devices that were at some point paired with your tool (or Custom Meross Pairer, or both). So this should be hopefully OK.

For those devices its often better to pair using their App and then reconfigure the device once it's on your network

Would you have a doc or advice on what exactly to reconfigure? My understanding is that once such a device is paired with the vendor cloud, it is on my WLAN but otherwise I have no control over it (outside of what the vendor app gives me of course). Is there a way to switch them at that point to HA (local control, not though the vendor cloud -- and not even because of security concerns, but rather delays or throttling)

---

In case you did not know, it seems that http://bytespider.dev/ does not work

[bytespider]

I can't quite remember the steps as it's been a while.

I certain you need to find the cloud account User ID and the Shared Key and then you can run
npx meross setup --nowifi --gateway {DEVICE IP} --mqtt {MQTT IP} --user '{CLOUD USER ID}' --key '{CLOUD SHARED KEY}'

Sadly I don't recall how to obtain the User and Key. @krahabb May recall a I think it was brought up in a discussion on the meross_lan integration.

[bytespider]

In case you did not know, it seems that http://bytespider.dev/ does not work

Thanks, I'll check it out.

[wsw70]

I can't quite remember the steps as it's been a while.

Same here :)

I certain you need to find the cloud account User ID and the Shared Key and then you can run npx meross setup --nowifi --gateway {DEVICE IP} --mqtt {MQTT IP} --user '{CLOUD USER ID}' --key '{CLOUD SHARED KEY}'

Sadly I don't recall how to obtain the User and Key. @krahabb May recall a I think it was brought up in a discussion on the meross_lan integration.

Thanks - I will browse the Issues/Discussions looking for that!