GE Direct Wire Indoor/Outdoor smart switch (model 14285) zwave -- does not pair with hub

Devices & Integrations Connected Things
1

Hi there,
I just purchased two “GE Direct Wire Indoor/Outdoor smart switch” (model 14285) and I am unable to pair them with the smartthings hub via zwave. I worked with GE (jasco) support and Smartthings support but they were not able to get it working. Smartthings support tells me that this particular model is very new and that’s the reason it will not work.

Smarthings support suggest to exchange the device for a older model numbers (e.g. 14284) but removing these devices is a lot of work (electrical wiring) and I just paid an electrician to put them in. /-:

No word from Smartthings how long it will take them to work with GE to get this working.

This switch is marked as Smartthings compatible and I am not happy that it is not working .

2

OK, just going to ask a bunch of questions…

  • which hub do you have?
  • how far are the switches from your hub?
  • any z-wave repeaters between hub and switches?
  • do the live logs in IDE show any particular errors?
  • any custom device handlers in IDE? You may want to open each and Publish for Me again, then reset your switches and try to pair them again.
  • any way to move the hub close to the switches when pairing if there is a distance issue? If they pair, move it back to existing location.
  • have you tried pairing using both ST apps?
2 Likes
3

Yeah, I’m sorry but that’s just a crap response. @jkp has asked several good questions, so let’s see what you come back with. It could just be a simple general exclude you need to do on the device and then try rejoining. I suggest using the Classic app to exclude/join the switch, if you haven’t tried that already.

1 Like
4

The “very new“ part might be because it’s an S2 device. But you would see those issues in the log messages. :sunglasses:

1 Like
5

Thanks for your assistance. Here is the answer to your questions:

• which hub do you have?
Firmware Version 000.027.00009
Hardware Version hub v2, US customer Rev E

• how far are the switches from your hub?
• About 30-50 inches
• any z-wave repeaters between hub and switches?
• no
• do the live logs in IDE show any particular errors?
• No (but just to confirm you mean these logs --> https://graph.api.smartthings.com/ide/logs?)
• any custom device handlers in IDE? You may want to open each and Publish for Me again, then reset your switches and try to pair them again.
• No I don’t use any device handlers
• any way to move the hub close to the switches when pairing if there is a distance issue? If they pair, move it back to existing location.
• Not really … also they are max 30 inches from the hub
• have you tried pairing using both ST apps?
I can only use classic. I tried the new app but this hub does not show up in the new app

6

So another update. As I mentioned I have two of these switches and they are both next to each other and close to the hub. While trying to look at the log one of them successfully paired with the hub, following the simple pairing instructions which I have been trying for the last couple of days. Not sure why it suddenly decided to pair but I am now able to control the device via the app.

Then I tried the second device but I am unable to get it to pair (following the same instructions).

Here is the device info from the one which paired:

Z-Wave Metering Switch Device A. Z-Wave Metering Switch

Name Z-Wave Metering Switch
Label A. Z-Wave Metering Switch
Type Z-Wave Metering Switch
Version Published
Device Network Id 08
Status ONLINE
Hub Timber Hill Hub
Last Activity At 2019-09-29 1:24 AM MDT
Date Created 2019-09-29 12:47 AM MDT
Last Updated 2019-09-29 12:48 AM MDT
Data * networkSecurityLevel: ZWAVE_S2_FAILED
* MSR: 0063-4F44-3032
Raw Description zw:L type:1001 mfr:0063 prod:4F44 model:3032 ver:5.55 zwv:6.02 lib:03 cc:5E,25,85,59,5B,70,2C,2B,32,55,86,72,5A,73,9F,6C,7A role:05 ff:8700 ui:8700
Current States * switch: on
1 Like
7

Ok update #2 … I was able to get the second device working as well. Once I saw the logs i realized that the pairing process goes through a loop, so I pushed the pairing button of the device after each iteration and at some point it paired successfully .

extract from the log:
25a53e30-9274-4e6a-a973-955d8aa04ecf 4:23:25 AM: debug no encapsulation supported for command: MeterGet(scale: 2, reserved202: 0, reserved00: 0)

25a53e30-9274-4e6a-a973-955d8aa04ecf 4:23:25 AM: debug no encapsulation supported for command: MeterGet(scale: 0, reserved202: 0, reserved00: 0)

25a53e30-9274-4e6a-a973-955d8aa04ecf 4:23:25 AM: debug no encapsulation supported for command: SwitchBinaryGet()

25a53e30-9274-4e6a-a973-955d8aa04ecf 4:23:25 AM: debug refresh()

524c42e2-1063-47d3-93d6-c44365a5f2d3 4:23:02 AM: debug motionOrContactHandler(Living Room motion:inactive)

524c42e2-1063-47d3-93d6-c44365a5f2d3 4:22:41 AM: info SHM isActiveSensor(motion:active, app: off, location: off) = false, locationId: e4acead3-fef9-4cd8-917a-e981768ef5b6, ISA: 524c42e2-1063-47d3-93d6-c44365a5f2d3

524c42e2-1063-47d3-93d6-c44365a5f2d3 4:22:41 AM: debug motionOrContactHandler(Living Room motion:active)

524c42e2-1063-47d3-93d6-c44365a5f2d3 4:22:25 AM: debug motionOrContactHandler(Living Room motion:inactive)

524c42e2-1063-47d3-93d6-c44365a5f2d3 4:22:11 AM: info SHM isActiveSensor(motion:active, app: off, location: off) = false, locationId: e4acead3-fef9-4cd8-917a-e981768ef5b6, ISA: 524c42e2-1063-47d3-93d6-c44365a5f2d3

524c42e2-1063-47d3-93d6-c44365a5f2d3 4:22:11 AM: debug motionOrContactHandler(Living Room motion:active)

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:20:06 AM: debug 'zw device: 09, command: 7205, payload: 00 63 4F 44 30 32 ’ parsed to [[descriptionText:Z-Wave Metering Switch MSR: 0063-4F44-3032, isStateChange:false, linkText:Z-Wave Metering Switch, displayed:false]]

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:20:06 AM: debug msr: 0063-4F44-3032

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:20:06 AM: debug parse() - description: zw device: 09, command: 7205, payload: 00 63 4F 44 30 32

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:02 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:02 AM: debug updated called

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:02 AM: debug updated called

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:01 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:01 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:01 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:01 AM: debug scheduled run, numberOfRuns: 11

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:01 AM: trace in discovery

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:01 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:01 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:01 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:01 AM: debug scheduled run, numberOfRuns: 11

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:20:01 AM: trace in discovery

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:56 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:56 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:56 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:56 AM: debug scheduled run, numberOfRuns: 10

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:56 AM: trace in discovery

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:41 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:41 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:41 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:41 AM: debug scheduled run, numberOfRuns: 9

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:41 AM: trace in discovery

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:26 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:26 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:26 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:26 AM: debug scheduled run, numberOfRuns: 8

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:26 AM: trace in discovery

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:19:24 AM: debug 'zw device: 09, command: 5B03, payload: 18 80 01 ’ parsed to [:]

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:19:24 AM: debug Z-Wave Metering Switch: Unhandled: CentralSceneNotification(sceneNumber: 1, keyAttributes: 0, reserved11: 16, sequenceNumber: 24)

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:19:24 AM: debug parse() - description: zw device: 09, command: 5B03, payload: 18 80 01

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:11 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:11 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:11 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:11 AM: debug scheduled run, numberOfRuns: 7

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:19:11 AM: trace in discovery

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:56 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:56 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:56 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:56 AM: debug scheduled run, numberOfRuns: 6

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:56 AM: trace in discovery

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:56 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:56 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:56 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:56 AM: debug scheduled run, numberOfRuns: 5

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:56 AM: trace in discovery

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:55 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:55 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:55 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:55 AM: debug scheduled run, numberOfRuns: 4

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:55 AM: trace in discovery

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:55 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:55 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:55 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:55 AM: debug scheduled run, numberOfRuns: 3

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:55 AM: trace in discovery

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:18:55 AM: debug no encapsulation supported for command: MeterGet(scale: 2, reserved202: 0, reserved00: 0)

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:18:55 AM: debug no encapsulation supported for command: MeterGet(scale: 0, reserved202: 0, reserved00: 0)

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:18:55 AM: debug Configure zwaveInfo: [zw:L, type:1001, mfr:0063, prod:4F44, model:3032, ver:5.55, zwv:6.02, lib:03, cc:[5E, 25, 85, 59, 5B, 70, 2C, 2B, 32, 55, 86, 72, 5A, 73, 9F, 6C, 7A], role:05, ff:8700, ui:8700, endpointInfo:]

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:18:55 AM: debug configure()

8a6bf9cb-1bd7-41ef-9029-a6412ac03f1f 4:18:54 AM: debug installed()

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:48 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:48 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:48 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:48 AM: debug scheduled run, numberOfRuns: 2

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:48 AM: trace in discovery

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:41 AM: debug No devices to add, verified devices: [:]

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:41 AM: debug detecting status for 74d35d20-c003-4a42-8be8-280a88f5d9ea : true

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:41 AM: trace in ssdpDiscover

4bad248f-96de-4d1c-bf24-013b2ba08b2f 4:18:41 AM: debug scheduled run, numberOfRuns: 1

1 Like
8

The the solution is to repeatedly keep pressing the “sync” button on the device while adding the hub is in “add a thing” (pairing mode). When the pairing is successful the green light on the device will light up.

Hope this helps others … (-:

3 Likes
9

This worked for me as well. I just kept pressing the pairing button while the percent circle was on the screen and in 2 seconds it asked me to scan the qr code again. Went “Processing” for a minute or more then it worked.

10

So are you able to control this easily in the new Smartthings app? I am thinking of getting one or two.

11

Yes they work fine.

—Frank

12

I have the same exact problem with my recently purchased GE 14285 & smart things hub. I’ve spent a long time repeatedly hitting the pair button & restarting everything multiple times - still no luck pairing the devices. Any other suggestions?

13

Maybe try to reboot the SmartThings hub and try the steps I described again?

14

Anytime a zwave device won’t pair, the first troubleshooting recommendation is usually to try excluding it. It may have been paired with a test controller at the factory and they didn’t clear the information, or one of your attempts may have partially succeeded, just enough to keep it from pairing fully… It happens.

So begin by doing a “general exclude.“ You will issue this from your smartthings hub. ( it’s fine that you never succeeded in pairing the device before: the general exclude is for the situation where the hub itself broke and you had to get a new one or you got a used device… It will work with any easy wave device nearby as long as you put that device into exclusion mode.)

You will have to look at the user manual for the smart plug to find out how to put it into exclusion mode. That’s usually a particular tap pattern, but it does vary from model to model.

Here are the instructions for issuing the exclude:

https://www.samsung.com/sg/support/mobile-devices/how-to-exclude-a-z-wave-device-that-is-not-connected-with-samsung-smartthings/

Once you have completed the exclude, that will clear out any old network information in the smart plug. And then you should be able to add it like usual. :sunglasses:

He may still run into some of the issues described above, but doing the exclusion won’t hurt anything, and it does give you a clean slate to start from.

Also, what hub model do you have? Because the GE switch is so new, it is going to try to add as an S2 device.

1 Like
15

I put the smart things hub into exclusion mode & did a factory reset of the GE switch (the closest thing the manual had to exclusion mode). No luck - it still refuses to pair. I followed all of the suggested steps in the prior messages: moving the hub about a foot away from the device, powering off both hub & GE switch, hitting the GE switch program button every minute or so. I also opened up the smart things live log and can see messages when I hit the GE switch program button … but it still doesn’t pair.

I believe my smart things hub is version 3 - the model number is IM6001-V3P01.