mss210 us rtl8710cf (hardware:6.0.0 firmware:6.1.12) unable to connect about meross HOT 9 CLOSED

Hi @platofan23 can you tell me a bit about your broker? Is it running via Home Assistant, and if so what version of the HA broker is it? V6.x is bad and you'll need to find a way to downgrade to 5.x.

from meross.

Hi @platofan23 can you tell me a bit about your broker? Is it running via Home Assistant, and if so what version of the HA broker is it? V6.x is bad and you'll need to find a way to downgrade to 5.x.

Iam running the broker just over ssh. Later i want to integrate this in homeassistant.

is there a site to download the 5.x firmware from meross for the plug?

from meross.

If you are on using Homeassistant there are a couple of options.
Harder: krahabb/meross_lan#63 (comment)

Simple: #28 (comment)

from meross.

If you are on using Homeassistant there are a couple of options.
Harder: krahabb/meross_lan#63 (comment)

Simple: #28 (comment)

That worked but i don't want my Raspberry Pi to bei Connect to the WiFi of the Plug all the time...

from meross.

If you followed the commands in the first option then the final step will cause the plug to reboot and connect to the WIFI details you provided.

from meross.

I didnt got that to Work. But i found an Other way. I connected the Plug via the meross app and Just Blocked the Internet Access with my Fritzbox. I still can use the meross LAN component for HA

from meross.

I didnt got that to Work. But i found an Other way. I connected the Plug via the meross app and Just Blocked the Internet Access with my Fritzbox. I still can use the meross LAN component for HA

It's a bit risky, because of blocked connection to meross mqtt, sometimes device will reboot itself.

Check if common name is the same in all your certificates

from meross.

The problem is not related to Meross directly. The device when it cannot find the broker will try the second broker defined before finally failing. You should choose the best option for you. Either your own broker or use the Meross ones.

We cater for your own broker setup.

from meross.

The problem is not related to Meross directly. The device when it cannot find the broker will try the second broker defined before finally failing. You should choose the best option for you. Either your own broker or use the Meross ones.

We cater for your own broker setup.

Later i solved the problem by adding the plugs with your HA-Integrations. That worked great =)

from meross.