My experience on this release cycle has been Wi-Fi matter devices connecting and reconnecting quite regularly. Several times a day.
The Hue dimmer switch problem with buttons 2,3 and 4 not responding is back after the .14 update.
Also, all of my Hue devices moved to the room where my hub is.
Hi @Francois_Venter
Could you please provide more details? Any additional info would help us investigate further.
Hi @Itati ,
I tried to do a logcat for the Hue driver today from the CLI to send through to you and then saw that the problem disappeared. I then checked the hue edge driver and saw that it was updated a few days after this firmware version release. I assume the the update of the Hue driver solved the problem.
1 Like
Is this UPDATE responsible for the SONOS OFFLINE problem I am experiencing since yesterday ?? We had problems two years ago that took months to resolve 
SONOS driver now changed to 2025-06-09T19:06:57.951558407 and the Hub firmware 000.057.00014
Hi, @glowworm
Checking the driver from the Production channel, I see it was last updated in April. So, I’m guessing you’re using the Beta version, right?
We saw there were reports about this and the engineering team mentioned the offline issue shouldn’t be present in the Production version of the driver, can you go to this invitation and install the Sonos driver to start using it and confirm if the issue is solved, please?
Reference post: Sonos status reporting and control issues (loss of)
Note: I see you already solved the issue here: Have SMARTTHINGS cocked up SONOS again? - #6 by glowworm
I went to the Production Version … Which I guess I was using before the Beta version was installed last night … It would be nice if SMARTTHINGS informed me when they were going to install a new version (Beta or otherwise) . I am also amazed that SMARTTHINGS have installed a BETA with known problems with my configuration … Pretty poor and not very SMART .
@glowworm I don’t think a beta release will overwrite an installed production driver, it will just update a pre-installed beta driver.
I posit that at some point you (as did I) subscribed to the beta channel and installed the beta Sonos driver and have been running on it ever since. In my case I did this right at the start of the edge migration before a production driver was released as an alternative to a community written driver.
Now you have the production driver installed beta channel releases will not have any effect unless you manually switch back.
1 Like
@TheHundredthIdiot is right, @glowworm. The Beta version isn’t installed on its own since it belongs to a different channel. So, even if the engineering team pushes a new update, it will only reach those enrolled in such channel.
To identify from which channel the driver you’re using comes from, you can:
- Enter the device’s details
- Select the menu (three-dot symbol in the upper-right corner) and tap on “Driver”.
- You’ll see details such as driver name, channel, version, etc.
1 Like
Yes .. I may have had a BETA driver installed from 2 years ago when ST had many issues with the EDGE migration . It was the only way we could get SONOS to work … But doesn’t answer my question "WHY INSTALL BETA DRIVER ON MY SYSTEM WITH KNOWN FAULTS " ???
I’ve previously stated the version of the Driver ST have “pushed” on to my hub , last night !!!
Being enrolled in the Beta channel for any driver means you might experience weird behavior because it is “like a filter” before releasing the driver in the Production channel.
It’s not like the engineering team released a new version with known issues; we’ve seen in the past that they come to the surface until it is released to the public, (which happens in the Beta Channel) since users have different setups that could be affected.
Once an issue is reported, the engineering team starts working on it and doesn’t release this version in Production until the issue is solved.
That’s why we all pay close attention to the reports about driver updates in this forum, to solve them as soon as possible, and we provide alternatives (if applicable). You were on the right path when you posted here.
4 Likes
Hello. I am wiht the 000.057.00014 in a aeotech Hub v3. Now, I can add my smartlife matter hub but no devices are discovered… It has worked fine in the past, with 70 devices discovered and working fine… seems to be something with the new firmware… any idea to fix it?
Hi @Sergio_A
Was this integration working before the firmware update? If so, why are you trying to reinstall it now?
Hello. I have 3 identical curtain motors. Two of them worked fine but 1 no (all worked fine in smartlife) and 1 llight switch allways showed a wrong state… I though that perhaps, after aeotec hub update was a good idea delete the other matter hub and sync all again. Badt dea, nothing is showed as connected in the matter hub (except if I bind a new device, that new is showed, but I can not unbind 77 devices and bind again)
And the aeotec hub doesn’t downgrade to the public releaae
Could you enable support access to your account so I can check its details, please?
- 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.
- Enable support access to your account:
- Go to the SmartThings Web (my.smartthings.com)
- Log in to your Samsung Account
- Select Menu (⋮) and choose Settings
- Toggle on Account Data Access
- 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.
More info about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support
Hello. Yes, theemail account registered in the forum is the same one you use for SmartThings. Acces updated
Hi @Sergio_A
I see that your account has a Matter bridge named “The Matter Wired Gateway by MOES.”
Is that the one you’re referring to — the one that isn’t discovering any devices?
You can try removing the Matter bridge and reinstalling it using your own account (Sergio Alonso) to rule out any issues related to ownership.
We noticed it was initially installed by another member of your location, which could be a contributing factor.
This is just to confirm and eliminate that as a possible cause.
Hello. Yes, the issue is with "The Matter Wired Gateway by MOES.”. I have deleted and sync again with smartthings this matter gateway (The Matter Wired Gateway by MOES.”) several times (and factory reset the Aeotec hub several times to)
