Watching - I’m having this exact issue. I’m running V2. but I just bought an Aeotec in hopes of fixing this issue. Is the Aeotec worse than V2?
I guess I’m slightly different, but not for the material things - all devices that “upgraded” to edge have stopped working completely. They all show as “off” in the app and on my.smartthings.com, and when I try to turn them on, on the app, I get a network or server error, on my.smartthings.com I get nothing. they have nothing in their logs, no history.
I have 146 devices, the vast majority of which are GE Zwave switches or dimmers. A very few (maybe 5) of the devices seem to have been spared the upgrade, and are therefore still working. Those devices appear to have a fingerprint of 0000-0000-0000.
I have 2 drivers. (zwave sensor and zwave switch). There seem to be several different fingerprints (e.g. 0063-4944-3235, 0063-4944-3038, 0063-4952-3135) - I can’t go through them all. I’m running V2 Hardware.
Repairing the network does not fix the problem. I cannot delete the devices - when I try, the app just spins - I did not try force deleting yet.
I do not have a memory error when I try to add a new device.
I’ve installed the CLI on my windows machine. when I type smartthings.exe edge:drivers, I get “no items found”
Any advice would be greatly appreciated - my wife is pretty unhappy with her non-working house!
The Aeotec hub is the same as the 2018 V3 Samsung hub. It has less memory than the V2 hub.
If it were me, I would not go thru the pain of replacing the 7+ year old V2 hub with 4+ year old V3 hub.
1 Like
I was debating this as well if I had to rebuild my entire network after migration is done. Thanks for the insight. Is there any outlook on an upgraded Aeotec hub?
There haven’t been any leaks or rumors so far as I know. But you’ve gotta think that 5 years is pretty long in the tooth for any electronics these days. Even if it did get a new case recently.
If you have GE switches and dimmers, I would suggest using @philh30’s drivers that provide more capabilities than the standard drivers. Install the driver(s) to the hub and change the driver in the ST app by selecting the device and using the “Change Driver” option in the dropdown menu.
In addition to using the CLI, I would suggest checking the status of your devices using the API Browser from @TAustin. In addition to checking status, you can delete devices and manage several other aspects that were formerly available in the IDE.
If you have GE switches and dimmers, I would suggest using @philh30’s drivers that provide more capabilities than the standard drivers. Install the driver(s) to the hub and change the driver in the ST app by selecting the device and using the “Change Driver” option in the dropdown menu.
This worked (at least for my test case)! thank you. Is there a way to batch update them, or do I need to do them one at a time?
In addition to using the CLI, I would suggest checking the status of your devices using the API Browser from @TAustin. In addition to checking status, you can delete devices and manage several other aspects that were formerly available in the IDE.
I have been using this - saw it above in the thread!
I don’t know of a way to batch update them, but just remembered it’s quicker and easier to change drivers via the API Browser than using the ST App.
Devices->“Your Device”->Change Driver
select next device, rinse and repeat
This is much faster, working on this now.
Given that I already received it and started to set it up - is there any problem with having a second hub? I’ve got both of them on the network, but have added nothing to the aeotec yet. My V2 seemed to take a long time doing things (eg. turning off everything seems to take several minutes. so I was wondering if there was a performance benefit to splitting them up. Now, that group is from Alexa, so it may be slow there).
Not something I have any experience with but there are others who do. @JDRoberts : any words of wisdom in running multiple hubs?
Depends what you mean by “problems.” The smartthings architecture has never really been designed for multiple hubs, but over the years has gotten better at it.
The integration isn’t seamless. You can create a routine that includes a device attached to each hub, but when you do, then that routine Has to run in the cloud, which can slow things down.
There’s also the issue of network backbones: they don’t share a Network, they each have their own, so you have to have enough Zigbee and zwave repeaters for each.
Historically people usually ran two hubs in one building because they were having difficulty getting signal between floors, typically in a cement or adobe house. But now we are seeing more people running Zigbee on one hub and Z wave on the other, in part because then they are not duplicating edge drivers on the two hubs so they have more resources on each. 
There are a few community members who are running multiple hubs: I’m sure they would have something more helpful to say.
Tagging @orangebucket @csstup
2 Likes
No issues with two hubs in a single location. Each has their own set of drivers installed. Routines can run across hubs in a location but always require the cloud, even if the hubs are on the same subnet.
When you pair a new device using the mobile UI, it will ask you which hub you’d like to bind it to.
1 Like
Argh. Spoke too soon. Now it’s much more like the OP’s problem. It worked at first, but when I ran my “Goodnight” automation from Alexa, it didn’t work and everything is no longer working again - had to run around my house turning off all the lights.
Ok, I think I have a better idea of what’s happening. Until I ran that script last night (from Alexa), everything was working well - I could turn lights on and off from Alexa and from the app, and from the web page. After that, the app no longer correctly shows the status of any of the edge switches, shows no history of the edge switches, and those switches are unusable. All the other components (e.g. switches that didn’t get upgraded, buttons, etc) show history, correctly show status and work. But when I run a script that executes a command, the non-edge devices correctly respond, but the edge devices do not.
So it seems like the edge subsystem, in the hub (not the individual systems) has crashed completely - I just rebooted the hub, and the edge devices are not working. However when I update the driver (to the old one, away from the @philh30 one), it works correctly. Somehow rebooting the hub is not resetting the status of the edge subsystem. Interestingly (after updating only one device to the old driver) I ran my goodnight script and it turned successfully turned off the one updated device. The device was then working afterwards.
So to summarize, everything starts out working fine, I then run a Routine from Alexa (goodnight) that turns off most of the switches in the house. That routine does not complete (it may turn off some , and following that, all edge devices are inaccessible. I see two possibilities - either that script runs and hits an individual device that somehow kills the edge subsystem (so aggressively that it can’t be restarted with a reboot), or the script somehow overloads the queue (since it’s running ~140 commands from Alexa, rather than using the Smartthings own automation), and that queue keeps anything in it that is using the driver that was in place at the time of the script being run.
Coincidentally, every time I try to do anything on the app, I get a network delay as it’s trying to find a path to the server. This happens regardless of whether I’m on the local wifi or no wifi at all.
Are you using the reboot button in the old IDE? I’ve usually found it takes power cycling the hub to recover when it’s truly hosed.
Your V2 is beefier than the V3, but the specs still fall short of a Raspberry Pi. You’re probably overloading it with that routine. I’d suggest running logcat on all drivers when you kick off that routine to get a better idea of what’s happening to the hub.
Agree with @philh30 that you’re probably overloading your network or hub if you’re blasting that many commands with no pauses.
My Alexa “lights out” routine has an Alexa “wait” for 5 seconds about every dozen devices. For what it’s worth, I’m mostly triggering scenes from Alexa with each scene setting the lights in one room off. Then wait 5 seconds before triggering the next scene. Repeat until the whole house is done.
No - power cycling it.
What are your opinions on Hubitat?
I actually have a “room” in Alexa with all the devices and the script just turns that off.
I am going to try putting scenes in Smartthings and trigger those as you suggested.
Curious why this would overload the new system, but has worked for years before now.
I had all sorts of issues when I tried to turn off more that 15 or 20 devices at once. Delays on some and some devices didn’t turn off. In fact, my Alexa routine repeats each scene because of those issues.
As best as I can tell my problems were from having too many Z-wave devices in one physical room. We’ve got a great room that incorporates kitchen, dining, wet bar, entry, and living room. Aside from lights in the room there are controls for two hallways and all the exterior lighting on two sides of the house. All told there were something like 30 Z-wave switches and dimmers around the perimeter of this one room. I ended up replacing about a third of them with ZigBee and my Z-wave mesh issues went away.
For what it’s worth it seems like you’re having mesh issues. I don’t recall if you’ve mentioned doing a Z-wave repair recently. Or if you’ve checked for “ghost” devices.