Are there any changes for zigbee device recently?

Developer Programs Writing Edge Drivers
1

We have two independent SmartThing Hubs working on different networks.They have been working normally all along.
But today I suddenly found that adding Zigbee devices in the SmartThing APP failed(There is no any display). We tried three different Zigbee devices.

Excuse me, have there been any updates recently added to Hub regarding Zigbee devices?

2

which model hubs do you have?

3

I am having the same issue. I have a V3 hub and I am not able to add any zigbee devices. I do have over 65 zigbee devices but also have a few hardwire zigbee switches and plugs. I am also experiencing delays on zwave devices. My firmware still not updated but these issues have been happening for a few days already.

4

I see now that my hub shows driverMemoryLimitStatus “HardLimit”. I have been using the same drivers for months. I had a combination of 205 devices that were working fine (wifi, zwave, zigbee and virtual). I deleted many to see if this would solve the issue but still can’t add devices. Now I have 185 devices and 23 drivers. I am trying to change drivers for zigbee bulbs back to the stock driver but it won’t let me. I am at a loss, I think might be time to migrate to a different platform.

1 Like
5

Thanks! Here is the info about one of our hubs:

1729127713076
17291277130761414Ă—712 38.8 KB

6

After a night, the two hubs have returned to normal. It’s really strange.

7

Hi, @jlatis
Did you add more devices to such drivers? The suggestion to avoid having memory issues is:

  1. Have installed only the drivers that you’ll use
  2. Check if a single driver can support most of your devices. There are some that offer several features which increase their size, if you have several “big” drivers active, the memory limit will be reached.

Note: A driver is active when it has at least a device connected to it.

8

Hi, @chenjun. The firmware update for the Hub recently finished, it might have been a factor in your case. Please, let us know if you experience this issue again.

1 Like
9

@nayelyz I am in a similar situation, without having changed my configuration, I’m am now unable to add any new thread, zigbee, z-wave devuce. I tried removing several drivers and devices, but the memory status is still “hard limit”. I have 175 devices (many of which are virtual, LAN devices or Samsung appliances) and 45 drivers installed (may of which are pre-installed).

Any advice on how to overcomer this issue?

Thanks.

10

I have added devices but I have not added any new drivers. When I delete drivers that are forced on to us (Wemo, JBL, etc), then the status goes back to soft limit. Also, why are we forced onto these drivers? I un-enrolled my hub from the driver channel and I still get these drivers. I have Sonos speaker but I don’t want it on my Smartthings hub, every time I scan to add something else, the speaker appears again. Is there a different way to stop these drivers from being added?

11

Hi, @sulisenator. Sorry for the delay, we were checking with the engineering team and as I mentioned above:

  1. Have installed only the drivers that you’ll use.

Note: @jlatis, I’m checking the part of pre-installed LAN drivers. AFAIK, they’re there to facilitate the discovery of devices supported by them since they don’t work with fingerprints and during discovery mode, they cannot be matched with a driver to download it as a Zigbee, Z-Wave or Matter device

  1. Check if a single driver can support most of your devices. There are some that offer several features which increase their size, if you have several “big” drivers active, the memory limit will be reached. So, having one driver per device could consume your memory faster.
  2. Ultimately, get a new Hub. However, it’s important to note that Routines across hubs (meaning 1 device from Hub A and another from Hub B in the same routine) would make it to run in the Cloud instead of local. So, you could join the devices in the Hub depending on which ones you want in the same routine to keep the “local” execution.

The engineering team is aware of the struggles with memory in the Hub and we’ve provided all your comments related to that.

12

Inactive drivers occupy storage but should have a minimal memory footprint. However I guess the difference between a soft limit and a hard limit could be as little as one byte.

Although other types of Edge drivers are installed on demand, apparently it takes too long with LAN drivers. So they need to be pre-installed just in case.

I never really bought into that explanation. I can’t see why the required driver can’t be pre-installed as part of the onboarding process. There are bazillions of supported devices listed in the mobile app, many with bespoke installation processes, so what’s so precious about these LAN devices?

The default channel doesn’t require enrolment so that isn’t going to help.

It’s a lot worse when you have more than one hub, and it was particularly bad when they weren’t in sync.

No. I doubt they are your biggest problem though.

13

Thank you for the response. I just don’t think I have that many drivers. 22 drivers and that is already consolidated. That is why I keep deleting the sonos driver since that is the one I don’t mind not having. Having different device types will very quickly add up.