Why haven't all my GE Z-Wave switches been converted to Edge drivers?

I have almost 40 GE Z wave switches and dimmers in my house. They were all installed around the same time so there shouldn’t be many differences in the model numbers. Why have only some of my switches and dimmers been converted to Edge? There doesn’t seem to be any rhyme or reason for ones that have converted versus ones that haven’t.

2 Likes

Be patient. The migration is not being forced on all devices at once but it being handled in small batches. I would not worry about the pace with what has vs what has not been migrated at this point.

5 Likes

At the rate they are being converted, it doesn’t seem like they will hit the advertised end of 2022 conversion period- unless we all have a big Christmas present or white elephant gift in the offing.

I agree. I just thought it was odd that only some of my switches have been converted. Why not convert all of the same switches on the same hub at the same time? It just struck me as odd.

I get what your saying. Just doesn’t make sense to me to convert some devices and not others since they are the same type of device and on the same hub…

None of my Zwave devices have been converted yet. You’re lucky!

Frankly I am getting worried. I have 82 Z-Wave and Zigbee devices. So far SmartThings has converted a total of 8. I have converted a few but there are over 60 devices left to be converted. I imagine ST will do a massive changeover during the Christmas holidays and then pull the plug while some people are on holiday and away from home. Then there will be a mad scramble to fix/replace devices that were not converted.

I know in one post, @nayelyz said that SmartThings was ahead of schedule on the changeover. So why can’t they do a massive changeover now with all the drivers that are available and give us time to sort out the remaining ones.

do these use stock ST device handlers or do you use any custom device handlers? Only mention this as ST will start migrating custom device handlers to Edge Drivers on Dec 12th.

Most are stock drivers. I have very few devices using custom drivers. I migrated most of those myself.

Same. I’ve had 11 of 19 ZigBee devices auto-migrated and nothing else. Nothing new for several days. My devices are 100% stock DTHs on a V2 hub.

No issues with the things that have migrated, but mildly concerned about how slowly it seems to be proceeding.

It also seems the “simpler” stuff is getting migrated.

1 Like

Hi, @damohabir
Sorry for the delay. You must check which devices were officially supported in the SmartThings Platform, to know which will be ported to a compatible driver.
In the case of those using a custom driver, they will be migrated to the closest driver available, that’s why we suggest you install one that would support your device.
But, devices not migrated yet won’t stop working overnight.

@nayelyz, based on the list published by SmartThings, I do not have any devices which wont be supported. My concern is based on the pace at which ST is converting devices. I have over 80 Z-Wave and Zigbee devices, and ST has converted a total of 9 so far. Very few have custom DTH’s. So it seems ST is waiting until the last possible moment to do a massive conversion, and if anything goes wrong, a lot of people will not be home to resolve any issues, because of the holidays. I am using some devices in a non-conventional way and would like to see everything converted ASAP so I can fix any issues that arises.

1 Like

I think most of us are in the same boat. I’ve had 5 devices converted so far, would love to manually convert the rest if we had a tool to do so.

2 Likes

Hello, I have over 20 older GE switches/dimmers (ZW3005) that just went offline on Christmas. The newer models are working fine and seemed to be ported over.

To be clear, the older ones are “OFFLINE” and have no interaction with the hub. I tried to exclude them, nothing. Deleted one after a reset, and then try to add it back to the hub, with no effect. Now they are not even listed.

I have search this forum, but most solutions say, remove and add, but it seems once I remove them, there is no coming back.

Thanks in advance.

Have you done a factory reset on the device(s) before trying to pair them?

Yes. Specifically, pull the tab out (device lose power), put the tab back in, tap 10 times up.

Isn’t odd that 35 devices all become “offline” on Christmas?
If an device is offline, can it be excluded?

No, not really. Exclusion is supposed to tell a Z-wave device to forget the id of its controller.

Some devices remember their controller even after a factory reset. So there’s that.

@JDRoberts has deep expertise on this stuff.

Do you have any other Zwave devices on the network? To me, it sounds like your Zwave radio is dead.

Sure, “offline” isn’t part of the Z wave specification, it’s something that smartthings made up, which has to do with whether or not your cloud account has a record of the device having communicated recently.

As long as the zwave device has power and is within range you should be able to exclude it whether it was ever connected to your network or not.

You do this by issuing a “general exclude” from your hub, and then any Z wave device which is within range and which has been individually put into exclusion mode. (usually by a specific tap pattern on the device) should hear it and act on it. (That’s included in the specification because they knew that you might not always have the hub that the device had previously been connected to.)

To initiate the exclusion, open the smartthings app, find your hub on the “devices” list, and then look on its details to see “Z wave utilities.”

The following video from Inovelli, a different Z wave device manufacturer, shows the app steps. Those are the same regardless of brand.

Now to physically getting the switch to accept the exclusion command…

The first rule of home automation definitely applies here: “the model number matters.”

I’m not sure where you got the idea to tap 10 times, but for the ZW 3005, you only need to tap once, on either the top or the bottom of the switch. (This information is in the user manual.)

If you want to pull the air gap first, you can, but you need to make sure it is pushed all the way back in so that the switch is back on power before you then issue the exclude through the app.

So the steps are

  1. (optional) pull the air gap tab on the bottom of the switch all the way out. Wait 15 seconds. Push it all the way back in. Wait two minutes before continuing. This wait is important so that the switch can fully cycle after the power loss/restore and be ready to do the exclusion.

  2. open the Smartthings app and run the zwave exclusion utility

  3. immediately after selecting zwave exclusion in the app, definitely within 10 seconds, tap either the top or the bottom of the switch once. Then wait. The app should eventually tell you that one exclusion took place.

——
And, yes, this means that you need to do each switch One at a time, re-issuing the exclusion from the app each time. The ZW 3005 is an old model and doesn’t have some of the convenience features of the newer lines.

So far all you’ve done is exclude it and get it ready to add back.

———

BTW, there is a possibility that these switches needed one of your other switches as a repeater to get their messages to the hub and the process of moving those switches to the new architecture has somehow left these particular switches out of range. It would be weird, but it could happen.

Have you run a zwave repair recently? And if so, did you get any error messages?

If somehow that’s part of the issue, you may need to temporarily move the hub closer to each switch so that it can speak to them directly without needing a repeater.

@HalD

1 Like