I found and fixed the issue with Zwave Switch CS causing the issue with the setFanSpeed command. Its been released to my channel.
However, the same bug doesn’t exist for Zwave Fan CS and I just tested it locally with my Leviton fan switches and it works fine. Can you verify you’re seeing a similar issue with Zwave Fan CS?
Yes, I’m still seeing an error (log below) with Z-Wave Fan CS version 2022-10-06T11:06:10.924540761. I tried deleting the driver from hub and reinstalling from your channel to force an update, but I guess that’s still the latest version.
In fairness, with Z-Wave Switch CS working, I’m certain to use that over Z-Wave Fan CS as it can be controlled with my voice assistant. Still, if there’s anything else you need, I’ll be happy to help out as best I can.
2024-07-14T18:24:19.641697881Z TRACE Z-Wave Fan CS Received event with handler capability
2024-07-14T18:24:19.671062222Z TRACE Z-Wave Fan CS Z-Wave command(6686fa83) queued for radio transmission: CC:Switch Multi-level, CID:0x01
2024-07-14T18:24:19.679715088Z INFO Z-Wave Fan CS <ZwaveDevice: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [60] (Office Fan)> received command: {"args":{"speed":2},"capability":"fanSpeed","command":"setFanSpeed","component":"main","positional_args":[2]}
2024-07-14T18:24:19.694522738Z TRACE Z-Wave Fan CS Found CapabilityCommandDispatcher handler in zwave_fan -> Z-Wave fan 3 speed
2024-07-14T18:24:19.713614488Z INFO Z-Wave Fan CS <ZwaveDevice: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [60] (Office Fan)> sending Z-Wave command: {args={duration="default", value=66}, cmd_class="SWITCH_MULTILEVEL", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x42\xFF", src_channel=0, version=2}
2024-07-14T18:24:19.717966079Z ERROR Z-Wave Fan CS Office Fan thread encountered error: [string "st/dispatcher.lua"]:267: Error encountered while processing event for <ZwaveDevice: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [60] (Office Fan)>:
arg1: {args={speed=2}, capability="fanSpeed", command="setFanSpeed", component="main", positional_args={2}}
"\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x64\x69\x73\x70\x61\x74\x63\x68\x65\x72\x2E\x6C\x75\x61\x22\x5D\x3A\x32\x36\x37\x3A\x20\x45\x72\x72\x6F\x72\x20\x65\x6E\x63\x6F\x75\x6E\x74\x65\x72\x65\x64\x20\x77\x68\x69\x6C\x65\x20\x70\x72\x6F\x63\x65\x73\x73\x69\x6E\x67\x20\x65\x76\x65\x6E\x74\x20\x66\x6F\x72\x20\x3C\x5A\x77\x61\x76\x65\x44\x65\x76\x69\x63\x65\x3A\x20\x39\x31\x62\x38\x32\x35\x34\x33\x2D\x63\x32\x65\x34\x2D\x34\x33\x39\x62\x2D\x39\x65\x31\x63\x2D\x39\x35\x65\x65\x30\x37\x63\x35\x31\x31\x63\x65\x20\x5B\x36\x30\x5D\x20\x28\x4F\x66\x66\x69\x63\x65\x20\x46\x61\x6E\x29\x3E\x3A\x0A\x20\x20\x20\x20\x61\x72\x67\x31\x3A\x20\x7B\x61\x72\x67\x73\x3D\x7B\x73\x70\x65\x65\x64\x3D\x32\x7D\x2C\x20\x63\x61\x70\x61\x62\x69\x6C\x69\x74\x79\x3D\x22\x66\x61\x6E\x53\x70\x65\x65\x64\x22\x2C\x20\x63\x6F\x6D\x6D\x61\x6E\x64\x3D\x22\x73\x65\x74\x46\x61\x6E\x53\x70\x65\x65\x64\x22\x2C\x20\x63\x6F\x6D\x70\x6F\x6E\x65\x6E\x74\x3D\x22\x6D\x61\x69\x6E\x22\x2C\x20\x70\x6F\x73\x69\x74\x69\x6F\x6E\x61\x6C\x5F\x61\x72\x67\x73\x3D\x7B\x32\x7D\x7D\x0A\x22\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x7A\x77\x61\x76\x65\x5F\x66\x61\x6E\x5F\x68\x65\x6C\x70\x65\x72\x73\x2E\x6C\x75\x61\x22\x5D\x3A\x34\x33\x3A\x20\x61\x74\x74\x65\x6D\x70\x74\x20\x74\x6F\x20\x70\x65\x72\x66\x6F\x72\x6D\x20\x61\x72\x69\x74\x68\x6D\x65\x74\x69\x63\x20\x6F\x6E\x20\x61\x20\x73\x74\x72\x69\x6E\x67\x20\x76\x61\x6C\x75\x65\x20\x28\x6C\x6F\x63\x61\x6C\x20\x27\x64\x75\x72\x61\x74\x69\x6F\x6E\x27\x29\x22"
2024-07-14T18:24:19.777185299Z TRACE Z-Wave Fan CS Z-Wave command(6686fa83) transmit status: TRANSMIT_COMPLETE_OK
2024-07-14T18:24:24.431699685Z TRACE Z-Wave Fan CS Received event with handler unnamed
2024-07-14T18:24:24.440500625Z INFO Z-Wave Fan CS <ZwaveDevice: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [60] (Office Fan)> received Z-Wave command: {args={value=66}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="B", src_channel=0, version=1}
2024-07-14T18:24:24.449204975Z TRACE Z-Wave Fan CS Found ZwaveDispatcher handler in zwave_fan -> Z-Wave fan 3 speed
2024-07-14T18:24:24.457246702Z INFO Z-Wave Fan CS <ZwaveDevice: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [60] (Office Fan)> emitting event: {"attribute_id":"fanSpeed","capability_id":"fanSpeed","component_id":"main","state":{"value":2}}
2024-07-14T18:24:24.460595709Z INFO Z-Wave Fan CS <ZwaveDevice: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [60] (Office Fan)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-07-14T18:24:24.463408032Z INFO Z-Wave Fan CS <ZwaveDevice: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [60] (Office Fan)> emitting event: {"attribute_id":"level","capability_id":"switchLevel","component_id":"main","state":{"value":66}}
2024-07-14T18:24:24.466458598Z DEBUG Z-Wave Fan CS Office Fan device thread event handled
I’ll work on debugging it, as clearly its faulting, but the fanspeed attribute (and thus the control) should be reflecting the correct state as it does set the value in your log example:
2024-07-14T18:24:24.457246702Z INFO Z-Wave Fan CS <ZwaveDevice: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx [60] (Office Fan)> emitting event: {"attribute_id":"fanSpeed","capability_id":"fanSpeed","component_id":"main","state":{"value":2}}
Thanks for the bug report, I’ll see what I can see!
I was able to see the bug locally. When looking at the code it looked like it was already fixed - it was updated when I last synced the drivers against the base ST code. I didn’t notice that anything had changed since last packaged 2022-10-06.
Just repackaged the driver with the latest code and tested locally. Issue is fixed. Sent the update out to the main channel.
───────────────────────────────────────────────────
Driver Id 260eba86-b00d-45b4-a1d9-69e659bbd182
Name Z-Wave Fan CS
Package Key zwave-fan-cs
Version 2024-07-14T18:46:26.954474137
───────────────────────────────────────────────────
Thanks again for letting me know about the issue!
BTW, while clearing out unused drivers from my hub, I noticed SmartThings Z-Wave Sensor was updated earlier this month. I haven’t encountered any issues with Z-Wave Sensor CS nor I did I look at the repo, but thought I’d mention it. 
Cool, thanks for the info. Zwave Switch CS (oriignally PH) isn’t based on the stock ST Zwave Switch, even if the names are similar. Zwave Fan CS is just Zwave Fan with my tweaks so I take their mainline changes as needed.
I’m having an issue with a fan switch. The led indictor isn’t working no matter what. I think i traced it through the code on github - it’s one of the ge fan switches that uses the ‘fan-scene’ profile. On the scene profile both the led indicator and energy frequency are mapped to parameter 3. I’m guessing it’s causing a conflict.
How do i get that fixed?
What is the specific model number and/or fingerprint for the device?
55258 ge fan control
According to the Z-Wave Alliance certification, only parameter 4 is supported for inverting the switch.
@csstup curious if you were still looking at adding the LED color and intensity settings for the new 700 series switches?
I think what you’re referring to is this:
energyFrequency = {type = 'config', parameter_number = 3, size = 1},
ledIndicator = {type = 'config', parameter_number = 3, size = 1},
However that is a red herring. The profile for ge-fan-scene doesn’t contain a preference for the “energyFrequency” tag, so its ignored from the data set above. This allows multiple sets of parameters in code to match to different parameters based on the profile itself (ie, the GE_SCENE set is used for switches, dimmers and fans, and only the preferences listed in the actual profile used will map to a parameter_number, etc.)
As to your specific issue of why you can’t change the LED parameter settings on the 55258, more information is available here. The TLDR version: changing the LED operation is not supported on the 55258, either by zwave parameter nor by tap-sequence. For the future it might be helpful to do a search by model number to get any past history to help quicker.
Why have the ledIndicator parameter available on the profile used by the 55258 at all? The profiles in these consolidated drivers are fairly generic on purpose, most devices follow the same patterns of which parameters they support by generation. For whatever reason, the 55258 is an outlier and it wasn’t worth making an exception for just a single device.
I added it to several models of switches a bit ago.
- id: "0063/4952/3239"
deviceLabel: Enbrighten Switch 58433
- id: "0063/4952/3330"
deviceLabel: GE Smart Toggle Switch 58436
If there are other 700 series switches that need this support, i’ll need model numbers and fingerprints. I also remember that some 700 series dimmers could use support but I’ll need model numbers and fingerprints for those as well.
The ones I have are 0063-4952-3333. They are the Ultrpro ZWA4011ULT versions. On/off switches, not dimmers.
───────────────────────────────────────────────────
Driver Id 36e506d8-ce52-4ef4-b90b-6a5fe7c41b83
Name Z-Wave Switch CS
Package Key zwave-switch-cs
Version 2024-08-17T21:20:15.983735608
───────────────────────────────────────────────────
Sent out update for Zwave Switch CS to use the ge-switch-scene-led profile, which adds the additional params for this model. The update will appear within the next 12 hours if you already have the driver installed.
Thanks for your help, will let you know when it works.
Sorry,
Found another one. These are dimmers I just got delivered today.
0063-4944-3433
Model - UltraPro ZWA3016ULT
And another Jasco/UltraPro toggle switch
0063-4952-3334
ZWA4012
Looks like the product id is 59368 or 59374(2 pack)
It is recognized by the driver as a switch-binary with conditions on/off/on or off.
Is this correct or does it need a fingerprint added?
Thank you
Hello, I just replaced a GE Z-wave Switch (model ZW4005; manu code 0063-4952-3036) that failed.
The new switch is an Enbrighten Z-wave Switch (model ZWA4011DVENB; manu code 0063-4952-3331). The new switch is not recognized by this driver. I am limited to using the generic Z-wave Switch driver that does not support double taps. Can this code be added?
Thanks!
Can you give the Jasco part number (5 digits, likely 59xxx). The ZWAxxxx model numbers get reused across many different part numbers.