Device key request from cloud fails.

[sgawne]

Having a weird problem with meross device keys. My device key is empty and the plugin takes me thru the action to get the device key from the cloud, but it fails with:

ConfigEntry.init() missing 1 required keyword-only argument: 'discovery_keys'

Some snippets from the log seem to indicate it is talking to the cloud...
2024-10-04 10:28:09.491 DEBUG (MainThread) [custom_components.meross_lan.api] CloudApiClient(): async_cloudapi_post:REQUEST url:https://iotx-us.meross.com/v1/Auth/signIn data:{'email': '#################0', 'password': '', 'encryption': 1, 'agree': 0} credentials:{}
2024-10-04 10:28:09.491 DEBUG (MainThread) [custom_components.meross_lan.api] CloudApiClient(): async_cloudapi_post:POST url:https://iotx-us.meross.com/v1/Auth/signIn request:{'timestamp': 1728052089491, 'nonce': '57262161fd5b41bfaba1f2e3af3c28a9', 'params': '', 'sign': 'ea1d767098df3fec92c4cd3ab7c8a01b'} headers:{}
2024-10-04 10:28:09.738 DEBUG (MainThread) [custom_components.meross_lan.api] CloudApiClient(): async_cloudapi_post:RECEIVE url:https://iotx-us.meross.com/v1/Auth/signIn response:
2024-10-04 10:28:09.740 DEBUG (MainThread) [custom_components.meross_lan.api] CloudApiClient(): async_cloudapi_post:RESPONSE url:https://iotx-us.meross.com/v1/Auth/signIn response:{'apiStatus': 0, 'sysStatus': 0, 'info': '', 'timestamp': 1728052089, 'data': {'userid': '@0', 'email': '#################0', 'key': '###############################0', 'token': '###############################################################0', 'domain': '#########################0', 'mqttDomain': '###################1'}}
2024-10-04 10:28:21.531 DEBUG (MainThread) [custom_components.meross_lan.api] CloudApiClient(): destroy
2024-10-04 11:09:41.869 DEBUG (MainThread) [custom_components.meross_lan.api] destroy

I have been poking around to see if I could understand it better, but its not clear why it is failing.

The version of the plugin is 5.3.1. The version of HA is 2024.10.1, also with 2024.10.0.

Not sure what I am missing.

[sgawne]

Seems my issue was that you needed to add a new meross setup (hub). While the devices were initially found without the hub, it was not possible to set them up. Adding the hub allows the cloud connection to start with and finds all the device keys. Then you have to go back and enter all the IP addresses manually :( But at least it is running :)

[boba51]

Hi @sgawne Are you saying I need to buy a Meross Hub to get my Smartplugs working with HomeAssistant?

[krahabb]

I think @sgawne refers to adding a configuration entry in meross_lan for 'cloud profile connection'...not the hardware hub ;)

[boba51]

@krahabb Thanks, does that means a fix will be forthcoming or I need to do the same, if I do, would anyone be able to provide details for me ?

[boba51]

I'm experiencing exactly the same issue, I've literally just install HomeAssistant in a VM on Synology NAS so have very little experience of HA yet, but happy to provide additional info if anyone can point me to what's needed and a simple guide on getting it.
I'm on the same versions as sgawne.

[krahabb]

@sgawne,
Therre should be some compatibility issues with HA 2024.10 cores...
I didn't have the time to test it so far so, beside apparently (and generally) working, there might be little fixes here and there that need to be implemented.

At any rate, I've opened #497 since this is likely a bug that need tracking

[Iggylights]

Just started with HA and of course I have a bunch of Meross stuff, of which only one device was discovered after getting a firmware update. Getting the same error:

'ConfigEntry.init() missing 1 required keyword-only argument: 'discovery_keys''

Should I wait for an update or is there a fix I can implement now? I'm on 2024.10 also...

Thanks! :-)

[krahabb]

I'm starting checking this issue..follow up tracking on #497 and hope for a quick patch ;)

[boba51]

Thanks

[boba51]

Installed the update, worked, thank you