homebridge-plugins / homebridge-meross

Homebridge plugin to integrate Meross devices into HomeKit.
MIT License
202 stars 32 forks source link

Error message: mqtt connection closed #566

Open levnetet opened 9 months ago

levnetet commented 9 months ago

What issue do you have? Please be as thorough and explicit as possible.

An endless error message entry of the meross plugin: mqtt connection closed/reconnecting

Details of your setup.

Please paste any relevant logs below.

[Meross_log.docx](https://github.com/bwp91/homebridge-meross/files/14356870/Meross_log.docx)
SemoTech commented 8 months ago

Same here with latest Meross plugin version 10.3.0

image

How do we stop these?

jordanwmcdonald commented 8 months ago

Additional Data Point

I also receive these messages. From my experience, it seems to occur if another part of my network infrastructure updates/restarts (e.g., an Access Point, Switch, Router/Firewall/Security Appliance). The workaround is to restart the plugin.

Configuration Details

Thank you, Ben @bwp91

SemoTech commented 8 months ago

@afroeagle it makes no difference for me. The moment homebrige restarts the mqtt messages start and don’t stop. Do not think this is related to infrastructure as no other plugin does this. There should be an option to hide these mqtt messages in settings.

roboterm commented 8 months ago

Set connection type to Hybrid solved this issue for me.

SemoTech commented 8 months ago

Set connection type to Hybrid solved this issue for me.

Brilliant @roboterm worked for me too, log flooding with mqtt messages has stopped! Thank you.

Interestingly the "Hybrid" connection option is marked as "Recommended" but still not enabled by default. Maybe in the next version it can be set a default, especially since it is recommended?!?

brimco commented 5 months ago

I've been having this problem for the past few weeks, and my Meross devices are either unresponsive or very sluggish to Apple HomeKit commands (e.g., the logs will say [<device>] sending update failed as the request timed out.).

Restarting the Homebridge-Meross child bridge didn't help. The connection type is already set to Hybrid and has been for a while.

Any other solutions that might help fix this problem? The Meross devices are pretty much un-usable from Apple HomeKit without a fix.

Config: