fix(config): correct valueSize for param 15 on GE/Jasco 26931 / ZW4006

[crxporter]

I have 3 of these switches (I don't have any of the dimmer type). The motion timeout setting has not been working, finally realized this should be a valueSize of 2. Additionally it accepts values outside of the options, so I've removed the limit on manual entry and added a description. Tested and working well for my 3 of these devices.

[crxporter]

Note: I would guess this error is in all of the Jasco switches and dimmers with motion detectors.

Links to potential other files with this same setup:

https://github.com/zwave-js/node-zwave-js/blob/75097b35fd3327fb7d4803710a51745e591d7a1e/packages/config/config/devices/0x0063/24770_zw4006.json

https://github.com/zwave-js/node-zwave-js/blob/0966efcd4993fa6ecd7a694e8afc28580c886aef/packages/config/config/devices/0x0063/26932_26933_zw3008.json

[AlCalzone]

Please put the description below the label.

Any chance you've measured some of these? 😅
If I assume 5 is 60s, 6 is 75s, etc. then 108 is 27 minutes, 109 is 27m15s and 110 is 27m again? Seems odd.

[crxporter]

So ... they come out at 15 seconds after the first two.

1 -> 10 seconds
2 -> 20 seconds
3 -> 30 seconds

and 15 second steps from there. So actually 110 is 27 minutes plus 15 seconds. ((110*15-15)/60=27.25)

for values 3 and higher the equation for how many seconds is (value*15)-15

It's accurate for values of 2, 8, and 9 at least. The description of this one at z-wavealliance.org shows it best - confirming how it actually works...

I'll change it to that wording "15 second intervals, starting at 60 seconds" like it is in that link.

[crxporter]

Just "for science" I've run some tests.

First at 2 minutes setting (value=9)

// Initial trigger 7:48:05 AM
{"node":12,"nodeName":"AtticLight","nodeLocation":"SensorSwitch","event":"VALUE_UPDATED","timestamp":1649162885500,"object":{"commandClassName":"Notification","commandClass":113,"endpoint":0,"property":"Home Security","propertyKey":"Motion sensor status","newValue":8,"prevValue":0,"propertyName":"Home Security","propertyKeyName":"Motion sensor status"}}
// 2 minutes no motion 7:50:06 AM
{"node":12,"nodeName":"AtticLight","nodeLocation":"SensorSwitch","event":"VALUE_UPDATED","timestamp":1649163006375,"object":{"commandClassName":"Notification","commandClass":113,"endpoint":0,"property":"Home Security","propertyKey":"Motion sensor status","newValue":0,"prevValue":8,"propertyName":"Home Security","propertyKeyName":"Motion sensor status"}}

Now running with the 110 value (27.25 minutes)... I'll update this comment once it goes back to idle.

// Trigger for 27.25 minutes 7:50:57 AM:
{"node":12,"nodeName":"AtticLight","nodeLocation":"SensorSwitch","event":"VALUE_UPDATED","timestamp":1649163057307,"object":{"commandClassName":"Notification","commandClass":113,"endpoint":0,"property":"Home Security","propertyKey":"Motion sensor status","newValue":8,"prevValue":0,"propertyName":"Home Security","propertyKeyName":"Motion sensor status"}}
// 27.25 minute setting back to idle 8:18:18 AM :
{"node":12,"nodeName":"AtticLight","nodeLocation":"SensorSwitch","event":"VALUE_UPDATED","timestamp":1649164698287,"object":{"commandClassName":"Notification","commandClass":113,"endpoint":0,"property":"Home Security","propertyKey":"Motion sensor status","newValue":0,"prevValue":8,"propertyName":"Home Security","propertyKeyName":"Motion sensor status"}}

With the little bit of "continued motion" at the start event, this comes out to be very close to 27.25 minutes, as expected. So now "yes" I've tested various situations including the maximum. Also tried setting to greater than 110, it does not take anything over 110.