[RELEASE] GE 26931 Motion Switch

Pieced things together from another post on here. The current built-in Jasco/GE DH doesn't support the Occupancy/Vacancy modes via custom commands.

This exposes the Occupancy and Vacancy Modes. You can create custom commands in RM for use in your rules so you can switch occupancy() and vacancy() or even manual() if you like. I exposed most of the other parameters except I did nothing on the ramp rates(so if someone would like to fix those). I also added a debug text switch and a descriptive logging. The descriptive logging will just tell you on/off & active/inactive.

Thanks to Matt lebaugh for the original Smartthings DH

1 Like

When operating the switch have you seen if Crc16Encap() is being called? If so, are appropriate values being passed to it?
Thank you

We have native support for this device in the next release.
I didn't need Crc16Encap in the driver i wrote.

Mike are you referring to the motion dimmer? I use the stock driver for the motion switch already.

Nice! With or without the extra functionality?

Extra, we updated the switch as well.

1 Like

Awesome! Then the above can be ditched entirely! I'm not complaining. I'd rather it be officially supported than hacker supported :wink:

@mike.maxwell

What device type is the native driver now in 2.0?

**edit: I see a Jasco Motion Dimmer...NVM

1 Like

Is anyone else having issues with the Motion Switch (not dimmer) after the 2.0 upgrade? Ever since I upgraded my switch will not turn on or is extremely delayed in turning on with occupancy mode set. Motion is detected and logged as an event but the switch won’t turn in immediately like it did prior to the update.

Change the DH to the "Basic Zwave Configuration Tool" and check parameter number 3. If it's NOT 3...then Occupancy is turned off which would be my guess. When it's on there is no waiting for the hub to turn the light on. It's done in the switch. My guess is it's set to 1 which is Manual.

BTW you can use that tool to set it back to occupancy if you want.

ConfigurationValue: 3, parameterNumber: 3, size: 1

That was it, the value was set to 1 even though I had the Operation Mode preference set to Occupancy in the driver. Once I changed it to 3 it is working again.

@mike.maxwell it appears there is a bug with the new Jasco Z-Wave Motion Switch driver where the preferences for occupancy mode aren't updating the device. I had previously set it to occupancy after the 2.0 upgrade and clicked configure but it stayed on manual.

you don't click configure, you make the preference change then click save preferences.

After the upgrade it defaulted to manual, I changed it to occupancy, clicked save, then out of habit clicked configure. The device showed it set to Occupancy but after following @jrfarrar's suggested I used the Configuration Tool to view the setting and it was still set to 1 even though the preference on the device was set to Occupancy. So the preference save didn't update my switch.

Yes, its certainly possible that the device didn't receive the command, but I can tell you the driver sent it.

1 Like

updated DH in original post

I'm thinking about purchasing this switch, does it support double tap? Thanks

1 Like

Are these switches natively supported by Hubitat now?

They have been for a long while. Not every feature is implemented thus need for a custom driver if you want to change settings not supported by stock driver.

1 Like

Yes and you will find them listed under Jasco, not GE in the device list.

I would suggest using the built in one unless you need the other features.

1 Like

Does anyone know how to expand the reset time on the motion sensor for GE 26931?

I'm using the built-in DH, but the Auto-off field appears to control the light, not the motion sensor. I'm using the switch as a standalone in-wall motion sensor with no lighting directly attached. All motion-drive events are controlled by HE. But I need to extend the reset time of the motion (i.e., a motion event keeps the sensor in an active state for, say, 15 mins). I've tried all the Modes, and nothing works. I can create a virtual device that shadows the motion sensor, but that seems like overkill. Ideas?