14291 GE In-Wall Smart Switch


#1

I’ve recently installed a bunch of the new 14291 GE Switches and I’m having an odd behavior that makes me wonder if SmartThings compatibility has some bugs.

  • Raw Description: zw:L type:1001 mfr:0063 prod:4952 model:3036 ver:5.20 zwv:4.05 lib:03 cc:5E,56,86,72,5A,85,59,73,25,27,70,2C,2B,7A role:05 ff:8700 ui:8700
  • When the hub is rebooted all interactions through SmartThings app work properly. Status stay correct throughout the SmartThings app and the “Recently” tab shows on and off events.
  • As soon as a switch is manually operated, the status in SmartThings becomes hung on the old status prior to the physical button press. Once this happens even changing the status in the app only temporarily changes the status, changing screens reports the device is actually still in the previous state. The “Recently” tab also stop showing any new status changes. All of this behavior persists until the hub is rebooted or the device is removed and added.
  • When the switch is manually pushed on or off to cause the problem there are no corresponding events in the IDE “Live Logging”
  • A zwave repair has no affect nor does resetting the breaker of the switch.
  • I don’t think it is a range problem since I have the older 12722s in the same gang boxes and all of them work flawlessly. Also the 14291s always respond to physical presses as well as wireless commands, there are never lost commands or delays, only the reported status in SmartThings is affected.
  • Followed all of the advice I could find on the forums for similar sounding problems with no luck.

I’d love to hear if anyone else has had this problem or if it is just me. Any more diagnostics I could perform? Maybe I just need to box all of these up and return them (UGH!).


#2

OK… I decided to go a bit further with the diagnostics, I’m terribly new to SmartThings so bare with me…

In the IDE, I copied the original “Z-Wave Switch” device handler to add some diagnostics to the parse like so:
log.debug “Parse description $description”
(Lifted that from the API documentation)

So now I do get some logging in the IDE’s “Live Logging”:
5e154298-34a3-4da9-bc26-bee0c1cb343e ‎10‎:‎48‎:‎11‎ ‎PM: debug Parse returned null
5e154298-34a3-4da9-bc26-bee0c1cb343e ‎10‎:‎48‎:‎11‎ ‎PM: debug Parse description zw device: 10, command: 5601, payload: 25 03 FF 79 58
5e154298-34a3-4da9-bc26-bee0c1cb343e ‎10‎:‎48‎:‎04‎ ‎PM: debug Parse returned null
5e154298-34a3-4da9-bc26-bee0c1cb343e ‎10‎:‎48‎:‎04‎ ‎PM: debug Parse description zw device: 10, command: 5601, payload: 25 03 00 67 A8

The 10:48:04pm event is turning the switch on, the 10:48:11pm event is turning the switch off.

Unfortunately the command and payloads are greek to me.

Interested if anyone has any ideas what to look at next.


#3

Well it looks like this switch uses Crc16Encap, and the default ZWave Switch device handler doesn’t support it. I added an event to handle Crc16Encap and unwrap it and everything started working.

Any official Device Handlers that handle Switches with Crc16Encap?


(Alex) #4

Well… that explains my issues too.

On an unrelated note, the listing for these has been removed from amazon.


(Alex) #5

There was a reference to Crc16Encap in the last update (Z-Wave Library Changes Feb 2017)


#6

No doubt this has a few issues that I am not aware of, but “it works for me”. I am far from a Groovy or Smartthings developer… maybe they will have a more official solution soon.


#7

Does the actual push-button switch feel different than the 12 series? I have one of the 26 series (motion+dimmer+zwaveplus), and it has a really nice, different, feel than the 12 series.


(Jim) #8

I had the same problem after installing a GE 14291 in a three way configuration. Your custom device handler solved the problem! Great fix, thanks.