Yup, your driver... When I switched the dimmer to your driver, it will not control the device... Seems to report the device status but will not change level, turn on or turn off the dimmer... Just tried again. Each time I have to switch back to the generic driver for it to work again.
OK. put it in debug logging and let me know what the logged messages say. I'll see if I can't figure it out.
Here is the log. Again its showing the commands sent but no change on the device...
dev:8822019-06-05 18:09:14.291 debugParse returned null for zw device: D3, command: 2603, payload: 00 , isMulticast: false
dev:8822019-06-05 18:09:14.288 infoDimmer Family Room Lights was turned off [digital]
dev:8822019-06-05 18:09:14.278 debug---SwitchMultilevelReport V3--- Dimmer Family Room Lights sent SwitchMultilevelReport(value:0)
dev:8822019-06-05 18:09:14.271 debugcmd: SwitchMultilevelReport(value:0)
dev:8822019-06-05 18:09:14.245 debugparse() >> zwave.parse(zw device: D3, command: 2603, payload: 00 , isMulticast: false)
dev:8822019-06-05 18:09:11.026 debugsetLevel(value, duration) >> value: 0, duration: 0, delay: 3000
dev:8822019-06-05 18:09:11.023 debugsetLevel(0, 0)
dev:8822019-06-05 18:09:11.015 debugTurn device OFF
dev:8822019-06-05 18:07:44.259 debugParse returned [[name:, value:, displayed:false]]
dev:8822019-06-05 18:07:44.256 debug---CONFIGURATION REPORT V2--- Dimmer Family Room Lights sent ConfigurationReport(configurationValue:[0, 3], parameterNumber:10, size:2)
dev:8822019-06-05 18:07:44.252 debugcmd: ConfigurationReport(configurationValue:[0, 3], parameterNumber:10, size:2)
dev:8822019-06-05 18:07:44.233 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 0A 02 00 03 , isMulticast: false)
dev:8822019-06-05 18:07:43.212 debugParse returned [[name:, value:, displayed:false]]
dev:8822019-06-05 18:07:43.182 debug---CONFIGURATION REPORT V2--- Dimmer Family Room Lights sent ConfigurationReport(configurationValue:[1], parameterNumber:9, size:1)
dev:8822019-06-05 18:07:43.179 debugcmd: ConfigurationReport(configurationValue:[1], parameterNumber:9, size:1)
dev:8822019-06-05 18:07:43.169 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 09 01 01 , isMulticast: false)
dev:8822019-06-05 18:07:42.158 debugParse returned [[name:, value:, displayed:false]]
dev:8822019-06-05 18:07:42.154 debug---CONFIGURATION REPORT V2--- Dimmer Family Room Lights sent ConfigurationReport(configurationValue:[0, 3], parameterNumber:8, size:2)
dev:8822019-06-05 18:07:42.151 debugcmd: ConfigurationReport(configurationValue:[0, 3], parameterNumber:8, size:2)
dev:8822019-06-05 18:07:42.140 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 08 02 00 03 , isMulticast: false)
dev:8822019-06-05 18:07:41.157 debugParse returned [[name:, value:, displayed:false]]
dev:8822019-06-05 18:07:41.153 debug---CONFIGURATION REPORT V2--- Dimmer Family Room Lights sent ConfigurationReport(configurationValue:[1], parameterNumber:7, size:1)
dev:8822019-06-05 18:07:41.150 debugcmd: ConfigurationReport(configurationValue:[1], parameterNumber:7, size:1)
dev:8822019-06-05 18:07:41.137 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 07 01 01 , isMulticast: false)
dev:8822019-06-05 18:07:40.126 debugParse returned [[name:inverted, value:false, displayed:false]]
dev:8822019-06-05 18:07:40.124 debug---CONFIGURATION REPORT V2--- Dimmer Family Room Lights sent ConfigurationReport(configurationValue:[0], parameterNumber:4, size:1)
dev:8822019-06-05 18:07:40.120 debugcmd: ConfigurationReport(configurationValue:[0], parameterNumber:4, size:1)
dev:8822019-06-05 18:07:40.107 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 04 01 00 , isMulticast: false)
dev:8822019-06-05 18:07:39.132 debugParse returned [[name:indicatorStatus, value:when off, displayed:false]]
dev:8822019-06-05 18:07:39.127 debug---CONFIGURATION REPORT V2--- Dimmer Family Room Lights sent ConfigurationReport(configurationValue:[0], parameterNumber:3, size:1)
dev:8822019-06-05 18:07:39.118 debugcmd: ConfigurationReport(configurationValue:[0], parameterNumber:3, size:1)
dev:8822019-06-05 18:07:39.080 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 03 01 00 , isMulticast: false)
dev:8822019-06-05 18:07:36.790 warndescription logging is: true
dev:8822019-06-05 18:07:36.787 warndebug logging is: true
dev:8822019-06-05 18:07:36.784 infoupdated...
dev:8822019-06-05 18:07:11.292 infoconfigure triggered
OK. so what did it actually do when you did that? It shows it turned the light off (level=0), and the device reported back it was off?
It didn't turn off the light... They are still on...
Interesting...
Switched back to the generic smart dimmer driver and its able to control the lights again...
Could it be a firmware issue within the dimmer switch? I just got these and replaced them within the last two weeks... The box says 14294-3 for the model... Is the 3 a revision?
OK.
I'll have to think about this. I'm guessing that is a lot newer version of the hardware than I have. Obviously something in the new version doesn't like how I set it up for the old versions. Typical Jasco/GE...
Does the box say it is S2 capable, perchance?
In any case, ya better stick with the in-box driver for now....
I don't see an S2 on the box anywhere... I'll keep looking... Just got these from Lowes... Says In-Wall EZ Smart Dimmer Z-Wave Plus....
OK. Weird.
One outside chance thing to try. Here's a test driver. It likely won't work either, but there are a couple changes that the newer firmware versions I'm looking at should prefer...
IF you feel like trying it - great, if not that is fine too. If you do make sure debug logging is on when you try a command and post the logs.
Here you go sir... Didn't work either but I captured some logs... Hit the command to turn the lights off, but no go still..
dev:8822019-06-05 18:29:07.168 errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.parse() is applicable for argument types: (java.lang.String, java.util.ArrayList) values: [zw device: D3, command: 2603, payload: 00 , isMulticast: false, ...]
Possible solutions: parse(java.lang.String), parse(java.lang.String, boolean), parse(java.lang.String, java.util.Map), parse(java.lang.String, java.util.Map, boolean), wait(), any() on line 108 (parse)
dev:8822019-06-05 18:29:07.129 debugparse() >> zwave.parse(zw device: D3, command: 2603, payload: 00 , isMulticast: false)
dev:8822019-06-05 18:29:03.947 debugsetLevel(value, duration) >> value: 0, duration: 0, delay: 3000
dev:8822019-06-05 18:29:03.944 debugsetLevel(0, 0)
dev:8822019-06-05 18:29:03.940 debugTurn device OFF
dev:8822019-06-05 18:28:55.469 errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.parse() is applicable for argument types: (java.lang.String, java.util.ArrayList) values: [zw device: D3, command: 7006, payload: 0A 02 00 03 , isMulticast: false, ...]
Possible solutions: parse(java.lang.String), parse(java.lang.String, boolean), parse(java.lang.String, java.util.Map), parse(java.lang.String, java.util.Map, boolean), wait(), any() on line 108 (parse)
dev:8822019-06-05 18:28:55.431 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 0A 02 00 03 , isMulticast: false)
dev:8822019-06-05 18:28:54.441 errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.parse() is applicable for argument types: (java.lang.String, java.util.ArrayList) values: [zw device: D3, command: 7006, payload: 09 01 01 , isMulticast: false, ...]
Possible solutions: parse(java.lang.String), parse(java.lang.String, boolean), parse(java.lang.String, java.util.Map), parse(java.lang.String, java.util.Map, boolean), wait(), any() on line 108 (parse)
dev:8822019-06-05 18:28:54.405 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 09 01 01 , isMulticast: false)
dev:8822019-06-05 18:28:53.422 errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.parse() is applicable for argument types: (java.lang.String, java.util.ArrayList) values: [zw device: D3, command: 7006, payload: 08 02 00 03 , isMulticast: false, ...]
Possible solutions: parse(java.lang.String), parse(java.lang.String, boolean), parse(java.lang.String, java.util.Map), parse(java.lang.String, java.util.Map, boolean), wait(), any() on line 108 (parse)
dev:8822019-06-05 18:28:53.386 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 08 02 00 03 , isMulticast: false)
dev:8822019-06-05 18:28:52.397 errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.parse() is applicable for argument types: (java.lang.String, java.util.ArrayList) values: [zw device: D3, command: 7006, payload: 07 01 01 , isMulticast: false, ...]
Possible solutions: parse(java.lang.String), parse(java.lang.String, boolean), parse(java.lang.String, java.util.Map), parse(java.lang.String, java.util.Map, boolean), wait(), any() on line 108 (parse)
dev:8822019-06-05 18:28:52.356 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 07 01 01 , isMulticast: false)
dev:8822019-06-05 18:28:51.381 errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.parse() is applicable for argument types: (java.lang.String, java.util.ArrayList) values: [zw device: D3, command: 7006, payload: 04 01 00 , isMulticast: false, ...]
Possible solutions: parse(java.lang.String), parse(java.lang.String, boolean), parse(java.lang.String, java.util.Map), parse(java.lang.String, java.util.Map, boolean), wait(), any() on line 108 (parse)
dev:8822019-06-05 18:28:51.337 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 04 01 00 , isMulticast: false)
dev:8822019-06-05 18:28:50.379 errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.Zwave.parse() is applicable for argument types: (java.lang.String, java.util.ArrayList) values: [zw device: D3, command: 7006, payload: 03 01 00 , isMulticast: false, ...]
Possible solutions: parse(java.lang.String), parse(java.lang.String, boolean), parse(java.lang.String, java.util.Map), parse(java.lang.String, java.util.Map, boolean), wait(), any() on line 108 (parse)
dev:8822019-06-05 18:28:50.335 debugparse() >> zwave.parse(zw device: D3, command: 7006, payload: 03 01 00 , isMulticast: false)
dev:8822019-06-05 18:28:48.016 warndescription logging is: true
dev:8822019-06-05 18:28:48.013 warndebug logging is: true
dev:8822019-06-05 18:28:48.009 infoupdated...
That's what I needed. Thanks.
Last question - and thanks for your help - you don't happen to have the Basic Z-Wave Tool driver installed, do you? It would be handy to get a version report off of the device.
If not, don't worry about it.
here you go sir... I'm guessing this is what you need...
dev:8822019-06-05 18:34:16.604 infoVersionReport- applicationVersion:5.29
dev:8822019-06-05 18:34:16.598 infoVersionReport- zWaveProtocolVersion:4.34
dev:8822019-06-05 18:34:16.591 infoVersionReport- zWaveLibraryType:Enhanced Slave
And BTW, thank you... I'm always impressed with the work you guys do!
Thanks. Yes, as I thought - yours is a newer firmware than all of mine... I've tried multiple times to get one of the new firmware, but keep getting the old ones. lol.
Let me think on this, maybe I'll figure it out without a device. Is a lot harder, but we'll see.
Ok, but if you need anything from me, let me know... I can try out what you need.
1 Like
Out of curiosity. Did you try any other commands? ON, set level, etc? I assume yes - and I assume none of those worked either?
yes, last night i tried on, off and set level.. Nothing would change the lights from the state they were in.. the device page reported that the changes happened, but in reality they didn't.
OK. Got it.
This is the firmware on my switches... I checked two of them and they are the same... Don't want to check all 30... But if this helps, the switch driver is working great.
dev:2892019-06-05 18:56:36.640 infoVersionReport- applicationVersion:5.22
dev:2892019-06-05 18:56:36.611 infoVersionReport- zWaveProtocolVersion:4.54
dev:2892019-06-05 18:56:36.604 infoVersionReport- zWaveLibraryType:Enhanced Slave
Any progress on this yet? I jut looked at the firmware for all my devices... Mostly all the same but a few devices have older firmware... Anyway, the plugin dimmer has the same software and firmware as the wall mount models... Just interesting. 
