Slow switch on/off events

[albertogeniola]

Slow switch on/off events

[albertogeniola]

Hi Davide,
As you would imagine, the library is not the only actor here. There are a number of parameters like network speed/latency, wifi coverage of the plug and the Meross server-side mqtt broker.
If you want to speed up the library, there is always space for improvement, but the point is that it might cost reliability and usability.

Why don't you explain to us what's your use case?

[DavideCannizzo]

I'm developing a website for managing my house's lights remotely. I've got several Google Home's and Meross devices. Google Home app is nice, but it is very slow. Meross app is terribly ugly. However, it is immediate when turning on/off lights. So, my website is a nicer alternative to the Meross app. It also offers a feature that is useful for my house, and here events come useful: I have some three-gang wall switches and none of them has all its gangs connected to a light (often they have only one gang connected). I want the unconnected gangs to toggle some lights, so my server (which hosts my website) listens for those buttons to be pressed, and then it toggles the proper light. This feature is the one I call 'Linked devices' and is an important part of my website. However, the delay isn't a pleasure. It's not a network problem: even though my network is very complicated (a server acts as a router, then there are a few of other routers and my ISP modem, and I've got three networks - LAN, DMZ, and Management, along with my ISP's WAN), I managed things to get everything extremely fast, e.g. a ping to 'google.com' takes an average of 16 milliseconds. I guess the problem is all about Meross' MQTT broker, because, as you pointed out, I know it's not an issue of your library and it is only part of the whole mechanism, so, excluding a hypothesis at a time, just the broker remains.

I wouldn't care if you close the issue (as it's not exactly an issue, though).

Thanks for the interest in people's complainings :)

[albertogeniola]

HI Davide,
well, in that case, why reinvent the wheel? There are plenty of home-automation libraries, such as Home Assistant. Moreover, I've developed a custom component to support Meross devices (using this library as part of the Home Assistant custom component). You should check that out!

[DavideCannizzo]

Thank you for the support, really.
However, I like reinventing the wheel (it is also part of a software developer's job, though), and the 'Linked devices' feature looks like to has been only an idea of mine. I didn't find anything akin that, yet. That's necessary for me to address some wall switches' gangs to lights I couldn't connect them to by cables.
At the moment, I'll stay with the slow events, as I find them the only one way. I think that one day, though, I'll develop my custom MQTT broker to replace the Meross', using my private DNS server to make devices think their broker is my server, hoping that it could handle things faster.
Now, thanks again, and I guess this issue could be closed. Indeed, I'm just closing it.