Beiträge von matternj

Indeed, it's Eero's Multi-Link (MLO) feature that causes Shelly devices to constantly switch between routers on the network with the strongest signal, causing micro-drops between each new connection. After a few hours, the connection stabilizes and adjusts to optimal connections.

tvbshelly To stabilize the router, I connected the Shellys to Wi-Fi 1 on the router with the strongest signal and Wi-Fi 2 on another router, using the same IPv4 network settings. Eero controls this using the device's IPv6. Therefore, micro-drops no longer occur.

tvbshelly For now, I'm testing the Eero 7 Pro configuration with Multi-Link (MLO) functionality, where each Shelly device connects to multiple Eeero devices at once. It worked fine with 1.5.1. I'm monitoring its behavior to see if there are any disconnections. I'll have to test it without the Eero MLO feature later. Then I'll see if the problem persists, whether it's an Eero issue or a Shelly issue.

tvbshelly Yes, I have an eero 7 Pro Wi-Fi network, which is quite stable with all Shelly devices running firmware 1.5.1, but this isn't the case with 1.6.0, 1.6.0Beta1, or 1.60Beta2. I have about 40 Shelly devices installed, and I can see it. Except with the Shelly 1p gen2, where 1.6.0 doesn't fail.

Zitat

1.6.0-beta2 ahora admite cubiertas en el modo Materia para 2PM Gen3

tvbshelly

I've tried firmware 1.6.0-beta2 as a blind, but it's not fine-tuned.
Homekit recognizes it and works correctly.
Aqara (matter) also recognizes it and works correctly.
HA only recognizes the firmware, but doesn't recognize the buttons and doesn't work.

On all systems, including Shelly, the Wi-Fi network is unstable and suffers from interruptions, causing slow operation at times.

On firmware 1.6.0-beta2 as a switch, it's also unstable on the Wi-Fi network.

discostur In case you're interested: tested on the Shelly 1 Mini Gen 3, but not yet on the Shelly 2 PM G3. To sync with HomeKit again, you must perform a factory reset, which will reinitialize the ability to sync with Matter.

To reset firmware 15 on the Shelly 2 PM G3, once you've updated to firmware 16, you must delete the generic scripts. After that, you can deactivate Matter, and only then can you revert to the previous firmware.

There is no way for the Shelly 2 PM G3 or the Shelly 1 G3 to work with Matter; only the Shelly 1 Mini G3 works with Matter.

I believe the folks at Shelly are making a mistake here. More than half of all installed Shelly 2 PM G3 devices are used to control blinds, and very few users rely on scripts to operate them.

Improving compatibility would make the device truly versatile, and it would undoubtedly become the best blind control relay on the market. Replacing them with the Shelly 2 PM G4, once released, is neither economically nor operationally viable. This would simply open the door for other manufacturers to step in with competing products over time.

In any case, I think Shelly needs to seriously reconsider the Matter compatibility of the Shelly 2 PM G3—because right now, it doesn’t function properly as a blind controller, nor as a switch, and it doesn’t integrate with other Matter-based systems.

With the Matter protocol, the Shelly 2 PM G3 device is highly unstable. It causes interference with the Wi-Fi network, constantly connecting and disconnecting from it, even disrupting the connection of nearby Shelly devices due to this interference. This issue does not occur with Shelly 1 Mini Gen 3 devices, which work perfectly.

When using Matter, the Shelly 2 PM G3 is recognized by HomeKit only as a dual switch, not as a shutter or blind controller. While it appears to be integrated, the control buttons are completely unresponsive—so it doesn't actually work. Furthermore, it doesn’t integrate with other Matter networks like Aqara’s, which can integrate devices from other Matter-compatible brands.

If you attempt the initial pairing on an Aqara network, it accepts the pairing code and Shelly shows the device as paired. At first it seems to work, but Aqara fails to complete the pairing and ultimately doesn't recognize the device. This might be an Aqara issue, but it also seems to be a problem on Shelly’s end: once it considers the device "paired," it won’t provide the pairing code again—not even after a factory reset or reinstalling firmware version 16.0beta1. The device neither stores nor shows the pairing code again. It only prompts you to pair through the already-linked platform, even when it's not actually paired.

Therefore, the first integration must always be done through HomeKit before attempting to add the device to any other platform.

It’s strange, because with the Shelly 1 Mini Gen 3, you can first integrate it with Aqara, and then add it to HomeKit, Home Assistant, or any other platform in whatever order you prefer.

Saludos: