Hub Firmware and Edge Driver Release Notes - 0.61.6

As a experiment I have reset and re-added the 3 problem Zigbee devices at my Home location. 30 min. later 1 device (tuya contact sensor) is already offline.

Update: An hour later all 3 devices (2 leak & 1 contact sensors) are marked offline again.

Interesting. That sounds very plausible. Pretty sure changed my from from the default under advice from smartthings team. Mine is currently 20, so if thats the default I think it’s been reset with the firmware update.
When I changed it last time it was the tuya devices that needed repairing :thinking:

EDIT looked back at the messages and it seems I changed it from 24 to 20. Dunno how it was at 24 if that wasn’t the default. I don’t recall changing it prior to that :man_shrugging:

Never changed the channel and it’s 11. Read through about 50 comments mentioning “Zigbee channel” and it looks like that this is the default. Someone said that the hub chooses a random channel when it’s set up, but 11 seems to be standard.

I do think there’s an optimum channel to pick which has the smallest or zero overlap with your wifi channel frequency , so “best” can vary based on your environment

Thanks for this insight!

Yes mine was set to 14

Very very odd.

Resetting devices, most light switches… the devices will connect and then they drop off the network with 2-3 mins. ( i have 3A nue light switch devices, which are also bricked from any normal actions during this time, cannot even turn light off at switch it will not respond)

I have reset channel to 11 and will do a reboot/ 20 min zigbee network bebuild and try again.

Any other thoughts/ suggestions?

I have 3A light switches, when the SmartThings hub connected about 6 work manually and the other 20 are frozen. When the hub is disconnected they all work manually after turning the CB off and back on. Power points also only work manually.

Hi,

Sounds like we have the same issue.

What firmware version and hub are you running.

Im on V2 2015 model, and on v 61.6.

Im seeing others are on 000.061.00006.

I have had to completely remove the hub from network to get lights working manually for now.

( cytrently in supporting ticket queue with Samsung for a new welcome code to re-pair my hub)

Hi all,

I noticed a couple of other people are suddenly having issues with their multi-gang switches, and I wanted to add my data to the pile.

Following the automatic rollout of Hub Firmware version 000.061.00006 (0.61.6) on my Aeotec SmartThings Hub, my entire home lighting network has been rendered completely unusable. The hub is triggering a massive background network loop that is physically paralysing my wall hardware.

My Setup:

  • Hub: Aeotec SmartThings Hub (Firmware: 000.061.00006 / 0.61.6)
  • Devices: Multiple 2-gang, 3-gang, and 4-gang Nue (3A Smart Home) Zigbee in-wall switches.
  • History: These switches have operated with absolute stability on this exact hub for years without a single dropout or hardware lockup until now.

The Symptoms (Started Morning of Friday, 19th June):

  1. Within 60 seconds after my Aeotec Hub finishes booting and connects to the Zigbee mesh, every single multi-gang wall switch in my house physically freezes up. The glass touch buttons stop working, and the physical factory reset buttons on the units become entirely unresponsive.
  2. The Isolation Proof: If I completely unplug the Aeotec Hub from power and flip my house lighting circuit breaker off and on, the wall switches boot up and function 100% perfectly as standalone, manual wall switches indefinitely. The exact second I plug the hub back into power and its radio links up, the data flood occurs, and every wall plate seizes up again within 60 seconds.

Troubleshooting Completed:

  • Completely Driver-Independent: I have thoroughly tested multiple driver profiles via the Advanced Web Dashboard, including shifting the parent devices completely over to the generic stock Samsung Zigbee Switch driver and fully purging/deleting all custom community Edge drivers from my hub’s memory cache.
  • The Root Cause: The selected driver profile makes no difference. The moment the hub links to the switches under firmware 0.61.6, the core hub radio aggressively broadcasts background network routing packets or configuration clusters that the older Nue firmware cannot handle. This creates an infinite command loop / broadcast storm that overloads the switch microcontrollers until the physical hardware crashes.

Current Status:

The only way I can currently turn the lights on in my house is to leave my Aeotec Hub completely unplugged and sitting in a drawer.

I have already submitted a direct ticket to the SmartThings Developer Support Team and explicitly enabled “Support Access” in my account settings so they can pull the network traffic logs starting from the morning of June 19th.

Has anyone else managed to find a temporary fix for this, or found an alternative to Edge/Mariano’s drivers? I am looking for any custom driver profile from other developers (or specific configuration settings) that actually work to stabilise multi-gang gear on this new firmware without triggering the hardware lockup. Please let me know if you’ve found a workaround!

@nayelyz @Itati


Smartthings v3 hub and 000.061.00006.

Hi @nayelyz ,
I am also having the similar issue after my Aeotec hub got updated version (000.061.00006). I have even tried to reset the hub and manually added my devices again but after some time they all freeze and go offline.
As you can see 56 devices are showing offline


Can someone please help?

Has this been escalated as a bug yet?

Ive raised a ticker to samsung too but nothing else yet.

I have also been having a mix of issues I see others posting here since the update with my V2 hub

Presence sometimes doesn’t work, or flaps home/away

Devices show offline

Devices show online but do not respond to routines or manual changes in the app. Or, respond erratically. Or respond 10 minutes later.

Routines do not fire

All of this is random and intermittent. Most of the time the system does not work reliably anymore, occasionally it works and I hope it’s resolved but then it doesn’t work again

I have enabled support access as well as submitted a ticket.

Hub has been power cycled a few times, and I cycled the power on the whole house to restart everything. No change.

Any suggestions or advice would be appreciated, but it seems there may be a firmware issue

Hi, @deantatt
Our engineering team contacted you directly, please check your inbox.

Hi, @nickdahiya
Sure. Can you follow the steps below, please?

My Zigbee network largely fails with recent versions. Devices disconnect unpredictably, and routines run slowly—sometimes after minutes.

AI search suggests changing the channel, but attempting this through the Advanced web app triggers error 500.

Hi, @veonua
Can you also open support access so I can add your hub’s info to the current report, please?

I note that the update period has been relatively quietly extended by four days to the 26th.

As I’ve commented before, it would be handy to have some idea when to expect the updates for each hub. Anything that will allow users to be at a higher state of readiness when it matters would help. A notification when the update begins would be useful too. The same applies to beta releases.

Hi @nayelyz , I have enabled the data sharing for my account for the support but I am not able to find the right place to raise a support ticket as my account is for Australia. May i know how do i send you a DM as my email is different for samsung account? I don’t see any place to send you a DM

It’s open and available.