Same Device, Same Device Type, Different Result

zip · February 13, 2016, 3:01am

I have two Jasco 45602 Lamp Module Plugs. I have two small children who have a habit of turning their bed lamps on after we put them to bed, so I want to be able to control the on/off status of the lamps after bedtime. However, I do want them to be able to turn them on in the middle of the night if they need to get up to go to the bathroom or something.

So what I need is a Load Sensing feature on the device, which I confirmed is a feature of the 45602. After I purchased them I learned that the Load Sense is set to off as default and that I need to have the Load Sensing parameter 29 set to 1 in order for the Load Sensing to work.

Having zero experience with device handlers (or writing code for that matter), after a few hours reading the forums, I found some guys who wrote the device handler to do this in this thread https://community.smartthings.com/t/modify-ramp-rate-on-ge-jasco-dimmers/11893/32

I copied the code, published it to myself and then modified one of the devices (Device A) to use the handler. And it worked perfectly.

Tonight I went to set the second device (Device B) up the same way, but it doesn’t work. I’ve checked and rechecked everything and think I have it right. But when I try to turn the lamp off when the device is in the OFF state, it doesn’t turn on. It still works perfectly on the first device.

Then I discovered something. On Device B, when in the OFF state, I try to manually turn the lamp off it of course doesn’t come on. But if I slide the dimmer bar in the ST app in either direction, the bulb comes on!

Can anyone think of what might cause this behavior?

zip · February 13, 2016, 4:26am

Update:

The dimmer bar movement causes the same behavior in both devices. If Device A is off and I simply move the dimmer bar the bulb turns on. So the dimmer bar is just acting as a second method to turn the lamp on from the ST app. I assume this is expected behavior.

I’m still unable to get Auto Sense to work on Device B.

Fuzzyligic · February 13, 2016, 10:30am

@zip

I am presuming the configuration options on the devices are set to different values. These pretty easy to set and list. Have a look at my previous posts. I wrote a Popp plug device type for someone and created a configuration sections at the bottom of the code to both set and list the parameters that are set.

You could strip these functions out and put into your device type easy enough. If you really cant do it. Please send me a link to the manual and I will update it for you…it wont be today though as I have a lot on

zip · February 13, 2016, 4:20pm

@Fuzzyligic

Thanks! I found your code, add a line to set paramater 29 to 1 and added the new device handler to both devices. I get the exact same result. Device A works exactly as it should. Device B still doesn’t Load Sense.

zip · February 13, 2016, 4:27pm

Here’s a link to the manual. If you’re willing to help I’d appreciate it!

Also here’s the lines of code I added to yours:

cmds << zwave.configurationV1.configurationSet(configurationValue: [1], parameterNumber: 29, size: 1).format()

and

cmds << zwave.configurationV1.configurationGet(parameterNumber: 29).format()

Fuzzyligic · February 13, 2016, 4:55pm

ok if when you use the listCurrentParams command and both show the same configuration for Parameter 29 then i am unsure. the only other thing i can think is, are you testing with the same Lamp? i.e is one of the lamps an LED bulb…i can envisage Load sensing would have an issue with an LED bulb due to the reduced load an LED bulb would give

zip · February 13, 2016, 6:55pm

I am using different lamps and different bulbs and different wall outlets. But I’ve tried every permutation and combination of all the variables with identical results.

I’ll try all the combination again and double check, but I don’t think that’s the issue.

zip · February 15, 2016, 3:18am

You said something that I don’t understand. How do I use the listcurrentparams command?

zip · February 15, 2016, 3:27am

I just discovered another anomaly. When I show the devices in the IDE, Device A (the one that works) shows an endpointid of 0. Device B does not show one at all.

Secondly, Device A has a “Raw Description” of 0 0 0x1101 0 0 0 7 0x26 0x27 0x73 0x70 0x86 0x72 0x77. Device B has none.

Device A was included to the network before Device B. Not sure if any of this is material.

Fuzzyligic · February 15, 2016, 6:40am

This is definitely a problem with the configuration, one is configured with multiendpoint encapsulation and the other has not.

Let me look at the device type you were using a little later today and I will see how the configuration is set.

FYI the ListCurrentParams command can be run from the IDE.

In the thread below I tell how you can run the ResetParams2STDefaults command but in the screengrab you can see the other command. But as I said leave it with me today and when I get a minute I will write sone instructions to enable you to resolve the issue.

Noob help please -- Popp dimmer (UK model 123603) Projects & Stories

Hi, we all have to start somewhere, yes you will need a custom device type to set the options, I have taken a look at the manual here and can see the options. I am not a coder either but I have knocked you up a custom device type that should work to install this just goto your Smartthings device handlers page here if you are in the US or here if you are in the UK and then click on [image] then choose the from code tab and paste in the code from my github page above and then click on Create you will see near the bottom of the code the resetParams2StDefaults() section, this contains all the parameters from the manual that are currently set to the default options for example below for parameter number 1, the default value is 3, just change any of the parameters values between the for…

JDRoberts · February 15, 2016, 6:41am

Four likely possibilities:

Device B is defective. It happens.
Device B is from a later model run after load sensing was no longer available. Many devices which offered load sensing prior to 2013 stopped offering it (or at least no longer made it the default) after it was found to mostly aggravate people. It just doesn’t work the way people expect it to. Load sensing does only one thing: turn on the lamp if the pocket socket is in the off state and someone turns the manual switch on the lamp to on. However, if the person then manually turns the lamp to off, the network won’t be able to turn it on again, hence the frustration.
Device B did not get correctly configured to enable load sensing.
Device B is on a differently wired circuit than Device A, or being used with a different type of lamp. For example, GFCI plugs can be problematic with load sensing devices. So can 3 way lamps. This one is easy to test: just put device A in the socket you were using for device B and vice versa.

You’ve gotten good advice for possibility 3) above, but if that’s not working, you might consider the other possibilities.

JDRoberts · February 15, 2016, 7:22am

This does not describe what auto sense is supposed to do on this Jasco device.

Instead, when you try to turn the lamp on (not off) manually on the lamp itself but the pocket socket is in the off state, the lamp should turn on.

On many table lamps this requires turning the manual switch twice to activate load sensing. The first turns it off, the second turns it on. But on other table lamps, it’s a momentary, and you only have to press once.

Did you try putting device B into the same socket with the same lamp that was working with device A?

zip · February 15, 2016, 1:56pm

@Fuzzyligic Thanks for your help. I do see now how to use the ListCurrentParams command.

Also the earlier link I posted to the manual is really just the quick start guide. Here’s the link with the manual that has the parameter settings. https://buy.dmp.com/dmp/products/documents/45602-UsersGuide.pdf

zip · February 15, 2016, 1:59pm

JDRoberts:

Four likely possibilities:

Device B is defective. It happens.

Device B is from a later model run after load sensing was no longer available. Many devices which offered load sensing prior to 2013 stopped offering it (or at least no longer made it the default) after it was found to mostly aggravate people. It just doesn’t work the way people expect it to. Load sensing does only one thing: turn on the lamp if the pocket socket is in the off state and someone turns the manual switch on the lamp to on. However, if the person then manually turns the lamp to off, the network won’t be able to turn it on again, hence the frustration.

Device B did not get correctly configured to enable load sensing.

Device B is on a differently wired circuit than Device A, or being used with a different type of lamp. For example, GFCI plugs can be problematic with load sensing devices. So can 3 way lamps. This one is easy to test: just put device A in the socket you were using for device B and vice versa.

You’ve gotten good advice for possibility 3) above, but if that’s not working, you might consider the other possibilities.

I’ve been leaning to #1 or #2. And @Fuzzyligic is helping me narrow down #3. It’s not 4, as I can replicate the problem when I plug the lamp from Device A in to the questionable plug.

zip · February 15, 2016, 2:01pm

I had a typo. I meant to say when I try to turn the lamp ON.

I also understand the need to turn the lamp switch off/on to trigger the load sense on the device.

I did try putting device B into the same socket with the same lamp that was working with device A.

zip · February 15, 2016, 2:16pm

@Fuzzyligic
Here are the logs I get when I run the ListCurrentParams command. The first device is the one that works; the second is the one that doesn’t.

DEVICE A:
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:25 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:25 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 54, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:25 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 36 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:25 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:25 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 53, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:25 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 35 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:24 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:24 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 52, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:24 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 34 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:24 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:24 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 51, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:24 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 33 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:23 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:23 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 29, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:23 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 1D 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:23 AM: debug Parse returned Dimmer Switch Brooke indicator status is when off
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:23 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [3], parameterNumber: 20, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:23 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 14 01 03 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:22 AM: debug Parse returned Dimmer Switch Brooke indicator status is when off
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:22 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [3], parameterNumber: 19, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:22 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 13 01 03 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:21 AM: debug Parse returned Dimmer Switch Brooke indicator status is when off
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:21 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [3], parameterNumber: 18, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:21 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 12 01 03 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:21 AM: debug Parse returned Dimmer Switch Brooke indicator status is when off
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:21 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [3], parameterNumber: 17, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:21 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 11 01 03 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:20 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:20 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 9, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:20 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 09 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:19 AM: debug Parse returned Dimmer Switch Brooke indicator status is when off
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:19 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [3], parameterNumber: 8, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:19 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 08 01 03 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:19 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:19 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 7, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:19 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 07 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:19 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:19 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 6, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:19 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 06 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:18 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:18 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 5, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:18 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 05 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:18 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:18 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 4, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:18 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 04 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:17 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:17 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 3, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:17 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 03 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:17 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:17 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 2, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:17 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 02 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:16 AM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:16 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 1, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:16 AM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 01 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 8:52:16 AM: debug Listing of current parameter settings of Dimmer Switch Brooke

DEVICE B:
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:18 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:18 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 54, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:18 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 36 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:18 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:18 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 53, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:18 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 35 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:17 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:17 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 51, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:17 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 33 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:16 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:16 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 29, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:16 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 1D 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:16 AM: debug Parse returned Dimmer Switch Audrey indicator status is when off
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:16 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [50], parameterNumber: 20, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:16 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 14 01 32 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:15 AM: debug Parse returned Dimmer Switch Audrey indicator status is when off
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:15 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [50], parameterNumber: 19, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:15 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 13 01 32 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:15 AM: debug Parse returned Dimmer Switch Audrey indicator status is when off
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:15 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [50], parameterNumber: 18, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:15 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 12 01 32 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:14 AM: debug Parse returned Dimmer Switch Audrey indicator status is when off
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:14 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [50], parameterNumber: 10, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:14 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 0A 01 32 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:13 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:13 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 9, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:13 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 09 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:13 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:13 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 8, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:13 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 08 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:12 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:12 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 7, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:12 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 07 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:12 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:12 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 6, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:12 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 06 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:11 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:11 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 5, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:11 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 05 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:11 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:11 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 4, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:11 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 04 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:10 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:10 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 3, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:10 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 03 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:10 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:10 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 2, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:10 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 02 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:09 AM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:09 AM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 1, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:09 AM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 01 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 8:53:09 AM: debug Listing of current parameter settings of Dimmer Switch Audrey

Fuzzyligic · February 15, 2016, 2:36pm

ok we can see that option 29 is the same on both devices, however following the manual you do not have all the supported parameters as per the manual listed.

The device from my reading about it does not support command encapsulation so we can rule that out, but i am left wondering if one of the devices has not associated correctly.

I have created a device type that will give us the correct info we need which is below, please install this device type for both Dimmers and then please do nothing else other than choose the ListParameters command. please then post the results in this thread.

github.com

fuzzysb/SmartThings/blob/master/DeviceTypes/fuzzysb/Jasco_GE_Plug_In_Dimmer_Module/Jasco_GE_Plug_In_Dimmer_Module.groovy

/**
 *  Copyright 2015 SmartThings
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 */
metadata {
	definition (name: "Jasco GE Plug In Dimmer", namespace: "fuzzysb", author: "Stuart Buchanan") {
		capability "Switch Level"
		capability "Actuator"
		capability "Indicator"
		capability "Switch"
		capability "Polling"

This file has been truncated. show original

zip · February 15, 2016, 3:06pm

Awesome, thanks! I’ll try it when I get home tonight.

zip · February 16, 2016, 2:44am

@Fuzzyligic Welp, very close. Device A still works perfectly. Device B now turns on when Load Sense is triggered. The only problem is with Device B, it doesn’t always turn on fully lit. Sometimes it’s as low as 2%. Other times some other seemingly random low (less than 50%) dim level. Any way to change the device type to always start at 99 or 100%?

I see that parameter 5 can ignore the start level and use the level embedded in the command, but setting parameter 5 to 0 had no effect. Where in the handler is the start level embedded? Can we just set that to 99 or 100, then set parameter 5 to 0?

zip · February 16, 2016, 3:08am

Here’s the log for Device A:

17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:31 PM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:31 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 29, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:31 PM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 1D 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:31 PM: debug Parse returned Dimmer Switch Brooke indicator status is when off
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:31 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [3], parameterNumber: 12, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:31 PM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 0C 01 03 )
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:30 PM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:30 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 11, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:30 PM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 0B 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:29 PM: debug Parse returned Dimmer Switch Brooke indicator status is when off
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:29 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [3], parameterNumber: 8, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:29 PM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 08 01 03 )
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:29 PM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:29 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 7, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:29 PM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 07 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:29 PM: debug Parse returned Dimmer Switch Brooke indicator status is when on
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:29 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 5, reserved11: 0, size: 1)
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:29 PM: debug parse() >> zwave.parse(zw device: 03, command: 7006, payload: 05 01 01 )
17752f05-95e8-454c-aaa2-a4990bd9a804 10:06:26 PM: debug Listing of current parameter settings of Dimmer Switch Brooke

Here’s the log for Device B:
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:07 PM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:07 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 29, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:07 PM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 1D 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:06 PM: debug Parse returned Dimmer Switch Audrey indicator status is when off
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:06 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [3], parameterNumber: 12, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:06 PM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 0C 01 03 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:06 PM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:06 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 11, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:06 PM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 0B 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:06 PM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:06 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 8, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:06 PM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 08 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:05 PM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:05 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 7, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:05 PM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 07 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:04 PM: debug Parse returned Dimmer Switch Audrey indicator status is when on
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:04 PM: debug ConfigurationReport ConfigurationReport(configurationValue: [1], parameterNumber: 5, reserved11: 0, size: 1)
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:04 PM: debug parse() >> zwave.parse(zw device: 02, command: 7006, payload: 05 01 01 )
7b7361aa-342c-4e7d-bfd9-15931acfde26 10:08:02 PM: debug Listing of current parameter settings of Dimmer Switch Audrey

Topic		Replies	Views
GE Pluggable Light Switch - Enabling Load Sensing Step by Step Connected Things	69	11973	April 18, 2018
Jasco dimmers support minimum dim and true switch mode Writing Device Types	31	4612	June 13, 2020
Need help with Loadsensing for GE Plug-in Wireless Dimmer Connected Things	7	2148	March 12, 2017
Modify Ramp Rate on GE (Jasco) Dimmers Devices & Integrations	86	24327	March 13, 2021
[OBSOLETE] Zooz Zen22 v2 Dimmer Community Created Drivers dth_lighting	54	7718	March 15, 2019

Same Device, Same Device Type, Different Result

Related topics