Network sluggish and freezing constantly

@nayelyz @Itati

Hey guys, ever since the latest update, my Hub V3 has been extremely sluggish and freezing constantly, especially with Matter devices.

At first, I thought the issue was with my Tuya Matter hub, since most of my devices are Tuya and are bridged to the V3 through it. To test this, I even swapped the Tuya hub for a spare one I had on hand, but the behavior stayed exactly the same. On top of that, the devices are frequently going offline. Another important point is that during the hub swap, I had a hard time pairing another device, as it threw the same error multiple times. See attached screenshot.

Routines and scenes are lagging and taking a long time to trigger. Since most of these delays happen with devices coming from Tuya via Matter, I’m leaning toward the V3 being the main culprit after this firmware update.

Is anyone else experiencing this, or does anyone have an idea on how to fix it? I could really use some help!

Colegas, após a última atualização, meu Hub V3 ficou extremamente lento e travando direto, principalmente com os dispositivos Matter.

No início, achei que o problema fosse o Hub Matter da Tuya, já que a maioria dos meus dispositivos são Tuya e são integrados ao V3 através dele. Para testar, cheguei a trocar o hub Tuya por um reserva que tenho aqui, mas o comportamento continuou exatamente o mesmo.

As rotinas/cenas estão lentas e demoram muito para executar. Como a maior parte dessas falhas ocorre com os dispositivos que vêm do Matter via Tuya, acredito que o problema principal esteja mesmo no V3 depois dessa atualização.

Alguém mais passando por isso ou tem alguma ideia de como resolver? Preciso de ajuda!

Hi, @Casa_Virtual_Automac

Is this happening only for Matter devices? I see you have more Zigbee devices. Or even more specifically, only for Tuya devices?
You mentioned the routines; have you checked if the events that trigger them are reflected on time in the platform? This is to make sure that the event is taking a while to come in, affecting the execution.

To check this further, we need your help to collect the following:

  1. Choose 3 devices that have this issue present
  2. Open the driver logs to see in real time if the events are received
  1. Trigger events on them that are involved in some routines.
  2. Check if there’s a delay and let us know in your description on what you did what you observed. For example:
    I tried to turn “x” device on to trigger a routine called “z” and the command took 10 seconds to appear in the driver logs.
  3. After testing all the devices, submit the hub logs as follows:
  1. In the Advanced Users app, enter the “Hubs” section
  2. Enter the corresponding Hub and click on “Dump Hub logs”
  3. Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
  4. You’ll get a green box at the top confirming the Hub logs were requested.

I’m seeing similar sluggishness on V2 after latest firmware.

Using Shelly Switches on Edge Drivers. Fixed IPs. The Shelly Switch input sensor responds immediately in the Native Shelly App, but very slow & inconsistent in the SmartThings app.

Prior to Firmware update, input sensors would show immediate in SmartThings

I’ve had sluggish network symptoms all over the place. Turns out it was this:

All my Echos and FireTVs have updated since, problem is gone.

Good morning! The issue only occurs with Matter devices brought over to the SmartThings (ST) hub via the Moes Matter hub. All scenes involving these bridged devices are failing. Additionally, I am also experiencing connection drops with Matter devices from other brands, but those are connected via Wi-Fi.

Bom dia! O problema ocorre somente com os dispositivos Matter integrados ao hub SmartThings (ST) por meio da ponte (bridge/gateway) da Moes. Todas as cenas que envolvem esses dispositivos replicados estão apresentando falhas. Além disso, também tenho perda de conexão com dispositivos Matter de outras marcas, porém estes estão conectados via Wi-Fi.

Ok, I also saw your DM, so help me get the info below before you reset the hub, since we don’t know that’ll help.
It’s the info I mentioned before, except for the driver logs: