Aeotec Smart Home Hub/2018/2015 Model Hub Firmware Release Notes - 0.56.9

[Johnnybegoode (John)]

On Saturday, here in Spain.

[TapioX]

Two of my three v3 hubs have been updated to a new version 56.9

@SmartThings

Reduce popcorning when controlling multiple Zigbee lights at once by using Zigbee groups

• Popcorning refers to when controlling a group of lights at once there is sometimes a visible delay before individual lights respond
• This feature will be slowly rolled out after the release so you may not notice immediate changes

@nayelyz @Itati
How is it possible to know that this feature is enabled in the hub?

[nayelyz (SmartThings Developer Support)]

@TapioX

Two of my three v3 hubs have been updated to a new version 56.9

Hi, @TapioX
I asked the engineering team and they mentioned that so far, this feature has been enabled very shortly after the hubs get the update so any of your hubs that have 56.9 should be running with it.

[orangebucket (Graham)]

@orangebucket

Yes, one of my V3 hubs has been updated this afternoon (about 16:50 UTC).

Curiously the health status of that hub is now showing a last update three days previously, even though I used it to determine the time I quoted above (which was consistent with my checks). All my V2 hubs have been updated and there is one V3 to go, which was my last hub to be (re-)installed.

[jaidank (Aidan Killian)]

Please correct me if I have this wrong but, whenever my (V2) hub goes offline or online, I get an SmartThings app notification.
It would be a good idea if the SmartThings app were to notify that my hub had its firmware updated. This way, I could check if my critical devices are correctly connected (they alway have been in the past).
Just a thought.

[Kand]

My hub got the update today at some point.
I also noticed there is a new Z-wave thermostat driver. “2025-03-17T20…..”
That seems to have corrected or at least improved the issue I had with my Z-wave thermostats.

[TheHundredthIdiot]

My hub updated last night at some point and I now have 27 devices off line spread across device types…

[jkp]

reboot the hub on the Advanced Web App

[TheHundredthIdiot]

@jkp

reboot the hub on the Advanced Web App

Done this with no difference whatsoever, currently working through either a reboot or rediscovery of the devices themselves…

[JohnRichard (John Nadeau)]

@TheHundredthIdiot

Done this with no difference whatsoever, currently working through either a reboot or rediscovery of the devices themselves…

As good measure, did you try pulling the power plug (and removing batteries from bottom of v2 Hub if applicable) for say 2 minutes and perform a replenishing power-cycle of the hub?

As well, power-cycle “all” of the devices. I’ve had scenarios where a z-wave mesh network was not playing nice until I power-cycled all of the z-wave devices. Even a z-wave repair didn’t help.

For what/it’s/worth, we have four hubs/locations that all updated and all devices came back online without a hitch. (devices consist of many z-wave locks/sensors, some wi-fi cams, and some zigbee devices Hubs are v2 and v3 Aeotec).

[Paul_Oliver (PCO)]

Overnight my 2nd v2 hubs updated to 56.09. No problems have been seen.

[JDRoberts]

Just a note: The “power cycle the whole house” method has turned out to be unsuitable for matter fabrics, because certain devices have to complete their initialization sequence before other types of devices can do theirs. If you do things out of sequence, you end up with a broken mesh.

If all you have are Z wave devices, this won’t affect you. But if you are also using matter devices, it likely will.

Essential Tips for a Stable Matter over Thread Network

[JohnRichard (John Nadeau)]

@JDRoberts

unsuitable for matter fabrics, because certain devices have to complete their initialization sequence before other types of devices can do theirs. If you do things out of sequence, you end up with a broken mesh.

Good to know @JDRoberts, thanks! Great link/overview too!

[Beno951]

Great update. I can already see way less popcorning with light groups. It works for most functions (on, off, dim…) But if I use function “turn on or turn off” (toggle) for a light group, then it’s still popcorning. If I divide it into 2 on/off routines, then it works.

A fix for “turn on or turn off” would be appreciated. Thanks.

[TheHundredthIdiot]

@JohnRichard

As well, power-cycle “all” of the devices. I’ve had scenarios where a z-wave mesh network was not playing nice until I power-cycled all of the z-wave devices. Even a z-wave repair didn’t help.

All my devices with issues were Zigbee, mains and battery powered. I think it may have been exasperated by some mains powered repeaters loosing connection (Aurora aone sockets). These particular devices often do drop off-line after firmware updates. I have never lost so many devices in one go though.

[jkp]

@TheHundredthIdiot

All my devices with issues were Zigbee, mains and battery powered.

The same happened to me a couple of weeks ago when my hub updated to one of the 56.x betas. Rebooted the hub and power cycled the main powered repeaters but it took a couple of hours before they all were online again.

[marcos.scheffler]

I´m still seeing popcorning with only 2 smart bulbs in a group

[Andrew_Bartlett]

Only difference I have noticed is before driverMemoryLimitStatus was HardLimit and now it is SoftLimit.

Edit. I spoke too soon, now HardLimit.
Edit. Now SoftLimit again.

[MPHDodgeDaytona]

One of my 5 hubs so far has updated to 56.10. Which I find odd as that is supposedly the Beta verison of this firmware and I’m not in the Beta program (I’ll post in that discussion as well, as I’m kind of confused why this is). Anyway, all my hubs are built in hubs without Z-wave, but it was only one of my 2 Stations that has updated so far.

[Paul_Oliver (PCO)]

@MPHDodgeDaytona

I am also not in the beta firmware program and both of my ST Stations have updated to 56.10, both my v2 are still on 56.9.

They never announce Firmware updates for the ST Stations like they do for the v2 & v3 hubs.