Yea.. Totally missed it on this .. Never occurred to me there would be a use case here.. But I'll have an update shortly in a few minutes here..
1 Like
Changelog:
Updated 2020-04-30
- Updated CCT Range
1 Like
@beddini update pushed.. This will allow you to set the range of your CCT leds
2 Likes
@bcopeland You da man!
2 Likes
I pulled down the latest, and updated the driver. I could not see any updates to the prefs gui (tried switching between CCT and RGBW a few times). FWIW I double checked your code and could see the new "Cold White Temperature" pref that was conditionally populated for deviceModel == 1 . I modified one of the button names just to make sure I was reading the updated driver, and I can see the change.. just can't see the new cold white temp pref. Any thoughts that's an obvious screen grab above.. so I know its working from your end.
Also, I have repaired the zwave network about 6 times, factory reset the unit and re-paired, and then done a mesh repair again.. some minor improvement but now its unresponsive. I have a zwave outlet about 5 feet away that responds in under a half sec, and an outdoor outlet that's probably a hop or two that is under a sec as well.
1 Like
can you screenshot your preferences, and device data sections?
@bcopeland thanks for looking into this..
I've flipped the pulldown between RGBW and CCT and force refreshed the browser several times. No population of the CW field:
Here are the details.. I've only changed the device type name to have a version so you knew you were seeing I got the correct driver installed off GIT:
thanks!!!
1 Like
FWIW this is the first time I've played with a driver that can switch the pref fields. Should I expect certain fields to go away (like enableGammaCorrect) when I switch from RGBW to CCT? I've never seen the populated fields change when switching between the two Device Types.
best,
A
1 Like
Here is your problem..
It won't display those options until the device accepts the change and responds back with the accepted change..
It is only available when the device is in CCT mode
getDataValue("deviceModel") == "1"
Which is z-wave config parameter 4
cmds.add(zwave.configurationV2.configurationSet(parameterNumber: 4, size: 1, scaledConfigurationValue: deviceType.toInteger()))
cmds.add(zwave.configurationV2.configurationGet(parameterNumber: 4))
Yes.. Fields are only available to you that are related to the device type (which is configurable via parameter 4)
Can you enable debug logging and change to CCT and hit save and send the logs?
I've been seeing this error with the previous version too:
dev:3232020-05-01 12:59:30.833 pm errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 256 (updated)
dev:3232020-05-01 12:59:30.756 pm debugdeviceModel: 2 Updated setting: 1
dev:3232020-05-01 12:59:30.722 pm warndebug logging is: true
1 Like
Checking
Well.. this is embarrassing .. Not sure how I missed this one.. I'll have an update shortly..
@beddini Update pushed.. This should work for you now.. After updating, refresh device page, then click save again on the preferences section...
1 Like
just updated.. I can see the new power fail state field. but no updating between device 2 to 1:
dev:3232020-05-01 02:05:54.702 pm errororg.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object '243' with class 'java.lang.Integer' to class 'java.util.List' on line 259 (updated)
dev:3232020-05-01 02:05:54.679 pm debugdeviceModel: 2 Updated setting: 1
dev:3232020-05-01 02:05:54.637 pm warndebug logging is: true
Doh 
Man.. I am off my game apparently ..
Ok.. one more time @beddini fix pushed
