That is correct. I use to run HA core on nexus 5x for a year. Than i switch to unused laptop for better stability (and convenience).
Iāve got some non-HomeKit Meross smart bulbs on the way that Iām going to be giving a try. I have also found, with some digging that both the mss550 & msg100 non-HomeKit versions can still be found on Amazon. Iāve still got on my list to pickup another HomeKit compatible device for some snoopy/testing but Iām half tempted to just try setting up the HomeKit compatible devices directly in HA using the built-in HomeKit functionality, since HomeKit is a local protocol anyways.
Ok some mild progress.
Today i manage to connect mss210 to HA via MQTT (latest version 6..).
I even cut internet connection to make sure it works offline.
But after ~1hour connection was down and i cant reconnect anymore. Should do as suggested: add mqtt mqtts://192.168.0.2 twice
With my mss710 i made no progress.
In MQTT explorer i see no subscribe, only publish.
I canāt add them to HA (error if i enter key or cloud retrive loop).
@fajrstartr is your mss710 a HomeKit compatible version by any chance? I know that currently both my mss550 & msg100 devices are newer with HomeKit compatible firmware and neither of them with pair via MQTT. I do however have mss510, mss110, and msl120 devices that I was all able to successfully pair to MQTT. The mss550 & msg100 devices are all paired with Meross LAN but only via IP/HTTP polling, and I have had them get disconnected but a few presses of the reset but reconnected the device.
One of them yes (i have 3 of them).
I didnāt even bother to try homekit one, just the other two.
It bothers me because i setup them the same way (mss210 & mss710)
Which ones gets disconnected in your case?
Edit: all fine for the last three hours.
All the switches and plug are working (not homekit one offcourse).
When you finish pairing switch you must unplug it for few seconds. When you plug it again it shows different entry in integration.
I have āmeross LANā which are not working.
The right ones are āMeross 710ā or whatever type you own. They connect whitout device key.
Thanks everybody for your help.
A week after update: mss 210 is rock stable so far, mss 710 switches not so much.
They went offline randomly and come back after day or two.
One of them came back on scheduled router reboot (at 3 am) other at random hour.
What could caused this? Tapo and tuya plugs are allways stable.
@fajrstartr I think it would be best to raise this at Issues Ā· krahabb/meross_lan Ā· GitHub , to help others who may have the same problem.
Ok i did some research. Apparently there are issues with meross switches an asus routers.
I changed some settings on asus router recomended in some forums. Not good results so far.
My switches went offline randomly even when paired with official meross app, so integration shouldāt be a problem.
Some forums recomended to connect 2,4ghz switches to separate router. I have old linksys 54gl lying around at home.
Maybe iāll try that.
So I would advise, if you can, to steer clear of the HomeKit compatible devices if you really want local-only control through MQTT. As it is right now I have 3 devices that are newer HomeKit compatible devices(3-way switches & garage door opener) and they are basically stuck in an IP only local mode that makes state updates very slow and delayed. I have found that with some searching I can find the older non-HomeKit devices on Amazon so Iām going to try to buy only those as long as they are available. I might remove and reconnect the HomeKit compatible devices and maybe just configure them in HA using HomeKit, that might give me a better experience than with the IP-only Meross LAN integration.
Hi there!
Iām pretty new to this whole environment, but I managed to set a local MQTT broker and get my 3 MRS100 roller shutter switches working in HA via the āmeross_lanā integration.
However, I noticed something wrong with them - after performing an action (up/down/stop), the device might become unavailable, and other devices will lag in responding too (all devices in the MQTT network btw, not only Meross).
When looking through my MQTT explorer, I notice that a single action (up or down and stop) can trigger several thousand subscribe/publish messages, thus flooding my broker. Eclipse MQTT shows some āoutgoing messages are being droppedā and many reconnects for the device from which the action was performed.
Any ideas why that would happen?
I noticed that integrating the switches via MQTT added a kind of āpositionā tracker to the devices in HA (that I can also see in Alexa btw), I donāt know if this might have something to do with itā¦
Any help is much appreciated!
Thanks in advance
Closed at the request of the thread owner.