I have ~10 GE/Honeywell/UltraPro dimmer switches and 3 were migrated a few weeks ago. Since they were migrated, they have almost no functionality and when actions do actually execute they are significantly delayed. I have tried both the ST generic z-wave switch driver as well and a driver for this switch built by Philh30 and am still having issues. The only time I can get them to work is immediately after the hub (v2, running 045.00011) is rebooted, then they seem to work as expected for <10 min before becoming useless. Is this an artifact of running the two architectures simultaneously and will work once groovy is fully retired? Any tips or insight would be helpful. Thanks!
A little more info on your environment please:
- Total number of devices on your hub
- Total number of drivers loaded on your hub
- Fingerprint of the device(s) that are not working well
- What does “almost no functionality” mean? Are there missing settings for either/both drivers? Are your devices just unresponsive or slow to respond?
- Have you tried deleting and re-adding any of the affected devices?
Thanks for the response. I’m not sure how to get the the total number of drivers or device fingerprints. If you could point me in the right direction I can get that information. I have 109 devices. What I meant by “almost no functionality” is that they are un responsive or extremely slow to respond. Settings for the drivers appear to be present and correct. I have deleted and re-added one of the migrated switched but this didn’t result in any noticeable improvement.
Easiest way to see total drivers and fingerprints is to use the API Browser from @TAustin. You will find the total drivers by selecting Locations->Hubs->“Your Hub”->Installed Drivers. To see the fingerprint of a device, select Devices->Devices->“Your Device”->Details.
Thanks for that. 109 total devices, 70 total drivers installed. Fingerprints for the switches are all 0039-4944-3235
As Im writing this, the switches seem to be working right now if I toggle them in the app, Im not sure why… However, Immediately after I tried executing a routine containing the switches, they did not respond during scene execution (all other devices ran as expected) or by toggling individually. Not sure if this is just coincidence but thought Id mention it.
That’s… a lot of drivers. What model hub? It’s possible you’re running low on memory. There have been reports of that on V3 and Aeotec hubs.
You also might want to run a Z-wave repair.
1 Like
Yeah, it is haha and I dont use them all either. I had dropped a bunch in to try them out. I will remove the ones I am not using. I have tried ruining the z-wave repair but haven’t had a noticeable change in performance. Is there a way to check memory utilization? I am running a V2 hub.
I haven’t heard of anyone having memory issues with a V2, but there’s a first for everything and that’s certainly a lot. I think what matters though is the number running, so if you have any drivers that aren’t assigned to devices then they might not be hurting you.
In the app, try going to Add Device → By Device Type → Generic Z-Wave Device and proceed through the prompts until the step where it asks you to pick a hub and room. Does it show a warning about memory being full or almost full underneath the hub selection box? There’s also a way to query the API to see if these memory warnings are being triggered if that’s in your wheelhouse.
Alternatively, if you install the CLI you can start logcat running on all drivers, and then watch to see if you’re hitting periods of sluggish behavior or if drivers are frequently rebooting.
1 Like
Thanks - I tried adding a generic z-wave device and did not receive any error messages. I found the thread to install the CLI but might take me a bit (not a programmer 
)
There are binaries available for all the major operating systems so you don’t have to be a programmer to install.
1 Like
I have reduced the numbers of drivers to 13. Looking through the logs, it seems like the commands for the switches running the edge drivers are last in the queue for transmission when running a scene containing actions for these switches. Is there a way to see all items in the radio transmission queue (both edge and DTH)? I think that might help me track down the issue. I didn’t see any evidence of drivers rebooting or anything but there is sluggish behavior when these switches are sent commands. Let me know if there are any log excerpts that may help.
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!