Hub Firmware 57.14 and popcorning

Devices & Integrations
1

The previous firmware release was supposed to fix popcorning when controlling multiple devices with a routine, and to an extent I think it did.

However since my hub got 57.14 the popcorning (controlling 4 lights within a routine, 3 zigbee, 1 thread seems pretty bad, eg it can take up to 5 seconds to complete (or at least it feels like that, I didn’t time it).

Anyone else seeing this?

2

That’s not even popcorning (that would be fractions of a second), that’s something wrong somewhere, either the hub overloaded with stuff or an issue with the Zigbee network or Thread network adding latency.

In 56.x they added native Zigbee groups which is the only fix for actual popcorning, of course that doesn’t apply if there’s a group mixing Zigbee and Thread lights. Doesn’t apply either for routines individually controlling lights.

In 57.x they added native handlers so the “on” command sent to each light in the group is sent by the hub firmware instead of the driver, but we are talking about milliseconds unless the Zigbee driver is busy with stuff. Actually the “on” command being sent by the hub instead of drivers was introduced long time ago, in 57.x it was just native handlers for reports coming from the light which is not relevant in popcorning.

1 Like
3

Tried it again today, same sluggishness. Rebooted the hub, no real difference. Tried using a zigbee button to trigger the routine rather than Alexa and it might be slightly better but still not great.

Tried creating a manual routine (scene) to switch each device in turn rather than use the lighting group, might be slightly better but not massively so.

What I notice consistently though is that the devices in group being controlled by the routine the thread bulb is always the first to react and is pretty snappy, the others are variable with no pattern to which is slowest.

In terms of hub load I’m on “soft limit” with a notional 125 devices although a chunk of those are virtual or things like scenes from tuya integration.

This behaviour wasn’t anything like this slow until recently, so I’m inclined to suspect it’s linked to the hub firmware update.

4

Hi, @Declankh
So, based on your description, I think you’re seeing a delay instead of devices turning on/off repeatedly, right?
In that case, we would need to trace those events from beginning to end. To do so, we need the following:

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
  1. Share the name of the routine that has the delay issue
  2. If they are all Hub-Connected devices, open the logcat to listen to all the drivers in the hub:
  1. You need to set up the ST CLI and run the command below:
smartthings edge:drivers:logcat --all
  1. The CLI will start listening to all the drivers thanks to the --all flag
  2. Then, execute the routine so the events to all the devices involved are captured there
  3. Copy those logs in a file and share it with us, you can send it to build@smartthings.com.
  1. When you execute the Routine, take note of the current date and time and share it with us
  2. Then, let us know how long it took the Routine to complete.
5

Update on this: today I changed the driver on the zigbee bulbs …. I had been using zigbee light multifunction mc, and I changed it to zigbee switch. Controlling the lights is still sluggish when using a lightin group within st and a manual routine (scene) to turn the lighting group on and off. However if I changed the scene to switch each light in turn rather than use the group the lights reacted much more quickly. The original driver had no issue prior to the latest hub firmware update.

6

Also had huge delay problems, after 57.14 firmware update, with routines that turn on devices that use the light multifunction mc driver, till the point that the devices simply stopped to respond to on/off commands.
In my case, devices came back to “normal” after reseting the hub through AWA.

7

What do you mean by “resetting” the hub. If you mean rebooting I tried that multiple times without success. If you mean factory reset that’s not an option. There is a huge amount of configuration and rules in place and I’d not relish setting that up again, or even risking a restore.

8

Try power cycling it - unplug it for ten seconds.

2 Likes
9

I mean rebooting!

2 Likes