I think you are a real hero, trying this new option with 110 devices connected.
I really don’t have the guts, and may only do this after having a failing hub.
At one of my locations I have a nearly “empty” v3 hub, next to a v2 with 40 devices, but I will ony try after many over here declare being succesful.
I have a v2 and addes a new v3 to account. It shows up in smartthings and I’ve attempted the hub swap feature but the attempt fails with a “try later” message. I try later and get a "successful " message but the devices don’t actually move over to the new v3 hub. Any ideas?
They suggested I “uninstall and reinstall the SmartThings and also try rebooting both the Hubs and then try replacing the Hub and check how does it goes.” I did as instructed but it did not help.
I am getting less confident in the success of the process…
I have a v3 that I constantly get memory errors on. Debating powering the v2 back up and seeing if I can move it back to the hub with more memory.
What are some of the symptoms of your memory errors? I also have a Aeotec V3 that has seems to have daily issues (non responsive devices, slow/delayed routines running, items that go offlline, then come back online after rebooting, etc.) that I need to reboot the hub several times a day. On the advanced webpage the “driverMemoryLimitStatus” is constantly in “Hard limit” and “Soft Limit” status and I’m wondering if it is a memory issue.
I was delighted to see this new feature for the Hubs introduced. A huge step forward and long awaited feature I thought. Then I read the whole topic and I am more than happy that I changed years ago to Home Assistant and left all these failed release attempts behind. It is just a usual Samsung/SmartThing…
Yup, all those symptoms. Additionally adding devices sometimes produces memory errors and sometimes unable to add devices. But the real problem is the issues like non responsiveness and delayed routines.
Here is an update on communications with ST support regarding the use of the Hub Replace feature to transfer my setup from my ST v2 hub to the Aeotec/v3 Hub…
My contact at SmartThings relayed the following information:
SmartThings team took a deep dive and made a few notes below:
The V2 is definitely using more memory than the V3 hub currently which is part of the issue.
There are 51 unique drivers installed in the V2, they definitely advise any cleanup that can be done to reduce the number of unique drivers.
(as an example, if you have multiple switch drivers (individual Smart Switch 7, Smart Switch 6 drivers individually), it may be worth consolidating them into a single Z-Wave Switch driver which would save considerable amount of memory)
Remove any unused drivers as before.
If there is still not enough memory, they suggest removing the community virtual edge driver device (as it uses the most memory in terms of resources) which should be enough for the hub to successfully use the replace hub feature.
In reply, I responded to my SmartThings contact as follows:
As of last evening removed five additional unused drivers and I also deleted five or six driver channels which I had installed for which I was not using any of the drivers contained in these channels. I then rebooted both hubs and I found that that error was gone, that I was free to begin the hub replacement process. I have not begun to execute the hub replacement yet as I am a little tentative due to the fact that my YouTube channel is based on demonstrating the capabilities of the ST platform. I am fearful of encountering issues when transferring my setup. Perhaps you can clarify some things for me? I assume there has been testing of the Hub Replace feature? Is the success rate of the transfer of devices, settings and routines constantly at 100 percent or should I expect some failures?
My support contact stated that he…
“tested the Replace Hub 2x times between my hubs and haven’t had any failures of any of my devices being lost. But in my own setup, i only have ~30 unique edge drivers, and roughly 35 devices in my network. So my environment may differ and i’m not sure if there is a higher chance of failure in transferring. Let me check in with SmartThings in this case to see if they have any data points on their testing to determine if failure can happen at all.”
I am currently holding off on doing the transfer until I get this additional data.
I was a little bit afraid for that. As you are a power user. Lots of extra drivers.
Keep us informed.
p.s: Smartthings support doing well this way.
Did you make a decision on trying out the v2 with the increased memory? Besides Thread capability, is there anything else we would be losing by going back to a v2?
The response you got from ST support bugs me. I have nowhere near the number of devices and drivers that you have. I only have 16 drivers loaded in each of my V2 (18 devices) and Aeotec (22 devices) hubs . BUT, 7 of those 16 are drivers I did not load nor need. I assumed they came with one of the firmware updates. Those drivers are: bose, Harmon Luxury, JBL, Philips Hue, SamsungAudio, Sonos, and Wemo.
If at some point a user could run into memory issues, why does the system load you with extraneous stuff that you didn’t ask for?
More info:
I noticed the same set of drivers mysteriously installed as well.
These are lan drivers apparently and if you uninstall them they will reappear in a day or two.
Yep. It’s the same principle as “super LAN connect” on the old Groovy platform (which I personally hated, but that’s another story). It adds itself whether you want it or not. And if you delete it, it adds itself back again pretty quickly.
Yes, I found this out as well when I was testing the Hub Replace.
As an update on my attempt to use the Hub Replace feature, I was finally able to get past the “Not Enough Memory” error on the Aeotec Hub once I reduced my driver count down to 39 and my driver channel count reduced to 13. I then rebooted both the v2 and the Aeotec hub, and as you mentioned, I subsequently found the bose, Harmon Luxury, JBL, Philips Hue, Samsung Audio, Sonos, and Wemo drivers on both hubs. I deleted these drivers and attempted the Hub Replace. The Hub Replace process started but then errored shortly thereafter. The message I received stated: “Couldn’t transfer the devices below because something went wrong with the server. Try resetting the devices and then manually add them to the new hub.” (see screenshot below):
There were no devices listed below the error. As it turns out, I found that only one device and all drivers and driver channels were resident on the Aeotec hub. I removed the single device from the Aeotec Hub, deleted the hub from SmartThings and restored it to factory settings. I then reinstalled the hub within the ST app and tried the Hub Replace several times only to find the original error stating that there was insufficient memory on the Aeotec hub.
I have been corresponding with Chris Cheng, Field Application Engineer for Aeotec. Chris has confirmed that he has tested the Replace Hub 2x times between his hubs and did not have any failures of any of his devices being lost. He stated that his setup contains 30 unique edge drivers and roughly 35 devices. As a result, I am guessing that you will likely be able to use “Hub Replace” with a smaller number of devices and drivers.
I recorded a live demo of my attempts to use the Hub Replace feature an it will publish on my YouTube channel this coming Saturday.
Anyone care to speculate about how likely it is that the hub-replace feature will become available for SmartThings WiFi hubs? I was initially quite optimistic and bought a Aeotec hub soon after the announcement to have it ready to go because it was briefly on sale. However, I’ve become increasingly pessimistic, and I just realized that I can still return the new hub (I have another week).
I realize that no one knows for sure, but I’m curious what others think. On the one hand, I could see them being anxious to get users of older hubs to migrate to newer devices. But, on the other, I could see them deciding that there aren’t enough SmartThings WiFi hubs still in active use to justify the resources necessary to support it…
I wouldn’t hold my breath. There hasn’t been a release for the Wifi hubs since late July.
Someone in the facebook group was successfully with ~70 devices. So the memory issues must crop up somewhere between 70 and 100 devices.
