You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While some of my devices work, other get timeouts on discovery e.g.
meross_iot.manager WARNING: Device myDev (123456) is online, but timeout occurred when fetching its abilities.
I tried to find the problem and discovered that after login my http_api_client lists only one mqtt domain e.g. http_api_client.cloud_credentials.mqtt_domain": ["mqtt-eu-5.meross.com"]
All devices that are working normally also got this mqtt domain.
But some of my devices got another mqtt domain e.g. mqtt-eu-4.meross.com.
I assume that the timeout is a result of the wrong authentication used by the mqtt client for this domain.
Am I doing something wrong? Is there any way to reauthenticate to get access to all needed mqtt servers?
The text was updated successfully, but these errors were encountered:
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.
While some of my devices work, other get timeouts on discovery e.g.
I tried to find the problem and discovered that after login my http_api_client lists only one mqtt domain e.g.
http_api_client.cloud_credentials.mqtt_domain": ["mqtt-eu-5.meross.com"]
All devices that are working normally also got this mqtt domain.
But some of my devices got another mqtt domain e.g.
mqtt-eu-4.meross.com
.I assume that the timeout is a result of the wrong authentication used by the mqtt client for this domain.
Am I doing something wrong? Is there any way to reauthenticate to get access to all needed mqtt servers?
The text was updated successfully, but these errors were encountered: