# Aeotec Smart Home Hub/2018/2015 Model Hub Firmware Hotfix Notes - 0.48.05

**URL:** <https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614>\
**Category:** Hub Firmware Release Notes\
**Tags:** hub\_firmware\_update\
**Created:** [June 30, 2023, 5:29pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614 "2023-06-30T17:29:07Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![kingsfan](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kingsfan](https://community.smartthings.com/u/kingsfan)\
**Post date:** [July 11, 2023, 9:47pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/21 "2023-07-11T21:47:04Z")

</div>

Through @nayelyz and per the instructions provided earlier in this thread, I have given Samsung access to my Hub for troubleshooting purposes. It’s been a day or so and I will be patient for 2-3 more days. This lack of QA before release of a firmware update is just not right and not something I expect from Samsung, who have an otherwise decent reputation.

---

<div class="post-metadata">

**Author:** ![kingsfan](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kingsfan](https://community.smartthings.com/u/kingsfan)\
**Post date:** [July 11, 2023, 11:08pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/23 "2023-07-11T23:08:26Z")

</div>

@nayelyz , Hopefully you can advocate for us suffering here. Is there an escalation path you can use to expedite resolution?

Z-wave is broken not just for 4 or 5 people. If 4 or 5 are chosing to report the issue, you can bet there are potentially hundreds more who are not and are simply giving up on the platform.

---

<div class="post-metadata">

**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\
**Post date:** [July 11, 2023, 11:14pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/24 "2023-07-11T23:14:25Z")

</div>

> [@\[Wi-Fi Hub\] Devices went offline and not responding](https://community.smartthings.com/t/wi-fi-hub-devices-went-offline-and-not-responding/265770/60):
>
> It all happened during the same rollout.

Hi, @John_Goering  
Per your description, I think you have a Wi-Fi Hub which is not related to this thread, is it correct? In those hubs Zigbee devices went offline and are not recovering but, in the case of @kingsfan, who was a V3 Hub, they are Z-Wave (or Zigbee) devices that go offline but **come back** at some point.  
If that’s the case, @John_Goering, I’ll move you to the correct thread.

@kingsfan, the update about this is that this has been escalated for the team’s investigation, I don’t have further info, sorry.

---

<div class="post-metadata">

**Author:** ![John\_Goering](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/john_goering/32/94786_2.png) [@John\_Goering](https://community.smartthings.com/u/John_Goering)\
**Post date:** [July 11, 2023, 11:17pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/25 "2023-07-11T23:17:33Z")

</div>

It all happened from the same update.  
Yes we have different hardware but you did one update that affected a HUGE amount of users of all sorts of things.

---

<div class="post-metadata">

**Author:** ![kingsfan](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kingsfan](https://community.smartthings.com/u/kingsfan)\
**Post date:** [July 11, 2023, 11:17pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/26 "2023-07-11T23:17:41Z")

</div>

@nayelyz , thanks for the response and the escalation. I am uncomfortable giving access to my Hub “Until turned off”. If you can get any estimate of an ETA for resolution, it’ll be great and I can then close access. I’m sure Samsung is as concerned about Privacy and Data Access as I am, if not more!

---

<div class="post-metadata">

**Author:** ![MarkTr](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/marktr/32/76583_2.png) [@MarkTr](https://community.smartthings.com/u/MarkTr)\
**Post date:** [July 11, 2023, 11:19pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/27 "2023-07-11T23:19:28Z")

</div>

> [@John\_Goering](#):
>
> It all happened from the same update.  
> Yes we have different hardware but you did one update

There is one firmware update that came out but there are other changes happening independently relating to the Edge migration. So the timing of the issues may be similar / the same but that doesn’t mean they’re all connected to the same change, as JR explained in another thread.

---

<div class="post-metadata">

**Author:** ![kingsfan](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kingsfan](https://community.smartthings.com/u/kingsfan)\
**Post date:** [July 11, 2023, 11:22pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/28 "2023-07-11T23:22:09Z")

</div>

Controlling too many changes is always a problem - thus the concept of “Change Control” - engineering 101 🙂

---

<div class="post-metadata">

**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\
**Post date:** [July 11, 2023, 11:24pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/29 "2023-07-11T23:24:22Z")

</div>

> [@John\_Goering](#):
>
> It all happened from the same update.

Actually, they have different versions, Wi-Fi Hubs are in 47 and, V2 and V3 are in 48. Also, Wi-Fi Hubs work significantly differently from the V2 and V3 Hubs (they aren’t updated at the same time or from the same source either). That’s why we treat each issue separately. Sorry for the confusion.  
So, I’ll move your posts to the other thread.

---

<div class="post-metadata">

**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\
**Post date:** [July 11, 2023, 11:36pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/30 "2023-07-11T23:36:19Z")

</div>

You can close the support access, if the team wants to check something else directly in your account, we’ll ask you to enable it again, we mostly require it to get device IDs, generate Hub logs, or see any other property (capabilities, driver in use, etc.) depending on the issue being investigated.  
Just as a clarification, the access is mostly read-only, we can’t do any changes to your setup without your written approval and we cannot access any camera/video devices, they are blocked for privacy purposes.

---

<div class="post-metadata">

**Author:** ![kingsfan](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kingsfan](https://community.smartthings.com/u/kingsfan)\
**Post date:** [July 11, 2023, 11:54pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/31 "2023-07-11T23:54:31Z")

</div>

@nayelyz , Thanks for the clarification. I will close the access. Do you know when any updates on resolution will be available? I’d rather not keep this open-ended. Any way to get updates on what the Support team is looking at/into with the data alrerady in their hands?

---

<div class="post-metadata">

**Author:** ![John\_Goering](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/john_goering/32/94786_2.png) [@John\_Goering](https://community.smartthings.com/u/John_Goering)\
**Post date:** [July 12, 2023, 1:08am UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/32 "2023-07-12T01:08:59Z")

</div>

Okay so the most basic development principles aren’t happening. Make a single change after good testing then back out if bad things happen. Instead we just throw changes at users and ignore the fact we cant tell what happened.

---

<div class="post-metadata">

**Author:** ![kingsfan](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kingsfan](https://community.smartthings.com/u/kingsfan)\
**Post date:** [July 12, 2023, 8:20pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/33 "2023-07-12T20:20:50Z")

</div>

@nayelyz , I have been rather patient with this saga and now my patience is understandly running out. Z-Wave devices continue to cycle on and offline to the extent that I have had to turn off automations that are wrecking havoc with lights turning on and off in the middle of the night!

This platform is becoming unusable for me now. **Is there any other escalation path to expedite resolution?** I would rather see positive closure of this issue rather than letting it slowly sink into a black hole.

Thanks for your assisatnce.

---

<div class="post-metadata">

**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\
**Post date:** [July 12, 2023, 9:49pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/34 "2023-07-12T21:49:23Z")

</div>

> [@kingsfan](#):
>
> Is there any other escalation path to expedite resolution?

I pinged the team again and they are taking a look at it. They asked me to separate random offline issues based on the protocol affected (Zigbee or Z-Wave).

Is there any other user here that has this issue only with Z-Wave devices? Most users have issues with Zigbee and the discussion about that is in this thread: [Aeotec Hub will not stay connected to zigbee devices - #47 by nayelyz](https://community.smartthings.com/t/aeotec-hub-will-not-stay-connected-to-zigbee-devices/265272/47)

---

<div class="post-metadata">

**Author:** ![kingsfan](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kingsfan](https://community.smartthings.com/u/kingsfan)\
**Post date:** [July 12, 2023, 10:15pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/35 "2023-07-12T22:15:02Z")

</div>

@nayelyz , I do not have any Zigbee devices. Most of what seems to be impacting me are Dome Z-Wave sensors. I have occasional issues with Be-Sense and Zooz Z-Wave sensors as well since that latest firmware update, but nothing to the level of the Dome sensors cycling on and off line every few hours.

---

<div class="post-metadata">

**Author:** ![John\_Goering](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/john_goering/32/94786_2.png) [@John\_Goering](https://community.smartthings.com/u/John_Goering)\
**Post date:** [July 13, 2023, 2:22am UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/36 "2023-07-13T02:22:41Z")

</div>

KingsFan,  
Strangely zigbee devices old and new seem to be the most affected.  
I have a 7 or so zwave and none had an issue.  
Still the overall response to the single wost update of SmartThings history has been like watching the hindenburg explosion in slow motion.

Apologize from VP of development please?

---

<div class="post-metadata">

**Author:** ![kingsfan](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kingsfan](https://community.smartthings.com/u/kingsfan)\
**Post date:** [July 13, 2023, 4:21pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/37 "2023-07-13T16:21:09Z")

</div>

@nayelyz ,  
I had to shut off more automation routines as other Z-wave sensors - Zooz and BeSense started cycling connectivity.  
As a last resort, I power cycled the Hub this morning. When may I expect updates from Samsung? This is not a good look for Samsung - please let any folks who still care about Customer Support and perception of Samsung know this.  
I am formally requesting Samsung to fix this issue and issue an apology.

---

<div class="post-metadata">

**Author:** ![Dean\_Crowe](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/dean_crowe/32/27158_2.png) [@Dean\_Crowe](https://community.smartthings.com/u/Dean_Crowe)\
**Post date:** [July 13, 2023, 9:27pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/38 "2023-07-13T21:27:05Z")

</div>

Well, thanks Smartthings. Every one of my Aeotec RGBW bulbs now has a SWITCH device driver, and all of my Aeotec Smart Switches now have ENERGY MONITOR drivers. Literally everything has failed and no longer works. The old drivers cannot be re applied and none of the devices if removed and re-added are detected as the device type they should be.

Well done Not So Smartthings!! Not impressed.

Goodbye Smartthings, Hello Home Assistant.

---

<div class="post-metadata">

**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\
**Post date:** [July 13, 2023, 10:21pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/39 "2023-07-13T22:21:36Z")

</div>

> [@Dean\_Crowe](#):
>
> Every one of my Aeotec RGBW bulbs now has a SWITCH device driver, and all of my Aeotec Smart Switches now have ENERGY MONITOR drivers.

Hi, @Dean_Crowe  
I think I heard about this issue, if you are willing, I can mention you’re also involved. But, if you’ll move to another platform I don’t think we will be able to gather the corresponding data.  
Sorry you’ve experienced this issue.

---

<div class="post-metadata">

**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\
**Post date:** [July 13, 2023, 10:26pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/40 "2023-07-13T22:26:56Z")

</div>

> [@kingsfan](#):
>
> When may I expect updates from Samsung?

I have been sharing all your comments with the team and they mentioned this is under investigation. I don’t have information about when they’ll have a final answer about this.  
I understand your frustration, that’s why I’m pending on everyone that can also provide their information to help with the investigation.

---

<div class="post-metadata">

**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\
**Post date:** [July 13, 2023, 10:40pm UTC](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614/41 "2023-07-13T22:40:30Z")

</div>

@kingsfan, can you enable access to your account again, please? The team needs to gather more information about the behavior of your devices.

[Previous page](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614.md?page=1)

[Next page](https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-hotfix-notes-0-48-05/265614.md?page=3)
