Zwave Dimmer - Fan Control

kemotsysinc · February 19, 2022, 3:20am

When I set my fan between 30 and 50 percent in the UI, it jumps to between 80 and 100 for the fan speed. Other fans work correctly in the UI.

I’m on OH3.2 on RPi.
Aeotec Zwave Stick
Zwave fan switch

Fan code:

UID: zwave:device:d6d9befb8f:node5
label: Master Fan
thingTypeUID: zwave:ge_12730zw4002_00_000
configuration:
  switchall_mode: 255
  config_11_1: 0
  config_10_1: 0
  config_7_1: 0
  config_8_1: 0
  config_9_1: 0
  config_12_1: 0
  config_3_1: 0
  config_4_1: 0
  node_id: 5
bridgeUID: zwave:serial_zstick:d6d9befb8f

Fronttail:

kemotsysinc · February 19, 2022, 3:43am

Even if I create code to set the fan speed, it still changes it to 100. When I was on OH2.5, this was not an issue:

2022-02-18 22:42:08.437 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'MasterFan' received command 50
2022-02-18 22:42:08.443 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'MasterFan_Dimmer' received command 50
2022-02-18 22:42:08.450 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'MasterFan_Dimmer' predicted to become 50
2022-02-18 22:42:08.506 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'MasterFan_Dimmer' changed from 0 to 50
2022-02-18 22:42:10.133 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'MasterFan_Dimmer' changed from 50 to 100

kemotsysinc · March 5, 2022, 4:43pm

Things I’ve tried -

Removing the device and adding the device.
Changing browsers and updating speed in the UI
Writing code to change it via code
Running updates (still on version 3.2)

Any other suggestions?

JustinG · March 5, 2022, 6:12pm

Do you mean these other fans are connected to the same type of device, or are they controlled by different brands of devices?

Can we see the configuration of the item and channel link you have configured for this control?

kemotsysinc · March 5, 2022, 7:10pm

Other fans of the same brand/type controlled by OpenHAB work fine via Alexa, UI and code.

kemotsysinc · March 5, 2022, 7:11pm

I have also upgraded to 3.3 and have the same issue.

JustinG · March 5, 2022, 11:47pm

Ok, then there are some fairly simple things you can check. It can’t hurt to double check that the config you posted up above is consistent with the config from one of the devices that works.

Next, I would follow the instructions on toubleshooting laid out in the binding docs and check out the z-wave debug logs. Look at the logs when one of your working devices changes properly and then look at the logs when this device does it’s weird thing. See if there’s any obvious difference.

Also, how did you upgrade from OH2 to OH3?

kemotsysinc · March 6, 2022, 4:24pm

To go from 2.5 to 3.0, I flashed the SD card and “started over”.

I’ll see if I can find anything in the zwave logs. Thank you!

jswim788 · March 6, 2022, 5:27pm

To me this looks like the Zwave control side of it is working fine. The Item received a command of 50, 50 was predicted, and the device reported it changed to 50. But then 2 seconds later it reported a change to 100. My guess is that the issue is with the fan control device itself. I would be tempted to exclude it, reset it, and re-include it. But it doesn’t make sense that an upgrade caused an issue like this.

kemotsysinc · March 6, 2022, 6:06pm

I did an exclude and then an include, I’ll see if I can find out how to ‘reset’ it.

kemotsysinc · March 6, 2022, 6:13pm

Log commands from selection Dimmer level to ‘20’ via the UI:

2022-03-06 13:12:20.044 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'MasterFan_Dimmer' predicted to become 20
2022-03-06 13:12:20.048 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'MasterFan_Dimmer' changed from 63 to 20
2022-03-06 13:12:21.649 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'MasterFan_Dimmer' changed from 20 to 71

Here is the log from the DEBUG

2022-03-06 13:12:20.055 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Command received zwave:device:d6d9befb8f:node27:switch_dimmer --> 20 [PercentType]
2022-03-06 13:12:20.056 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 27: Creating new message for command SWITCH_MULTILEVEL_SET
2022-03-06 13:12:20.056 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: SECURITY not supported
2022-03-06 13:12:20.057 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Command Class COMMAND_CLASS_SWITCH_MULTILEVEL is NOT required to be secured
2022-03-06 13:12:20.058 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Adding to device queue
2022-03-06 13:12:20.059 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Added 225 to queue - size 5
2022-03-06 13:12:20.064 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 27: Sending REQUEST Message = 01 0A 00 13 1B 03 26 01 14 25 BB 53 
2022-03-06 13:12:20.069 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling initialised at 1800 seconds - start in 1500 milliseconds.
2022-03-06 13:12:20.088 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: sentData successfully placed on stack.
2022-03-06 13:12:20.090 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: TID 225: Transaction not completed
2022-03-06 13:12:20.112 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: SendData Request. CallBack ID = 187, Status = Transmission complete and ACK received(0)
2022-03-06 13:12:20.113 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: resetResendCount initComplete=true isDead=false
2022-03-06 13:12:20.116 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Response processed after 49ms
2022-03-06 13:12:20.117 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: TID 225: Transaction completed
2022-03-06 13:12:20.118 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: notifyTransactionResponse TID:225 DONE
2022-03-06 13:12:20.120 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2022-03-06 13:12:21.569 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling...
2022-03-06 13:12:21.572 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:d6d9befb8f:node27:switch_dimmer
2022-03-06 13:12:21.573 [DEBUG] [erter.ZWaveMultiLevelSwitchConverter] - NODE 27: Generating poll message for COMMAND_CLASS_SWITCH_MULTILEVEL, endpoint 0
2022-03-06 13:12:21.574 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 27: Creating new message for command SWITCH_MULTILEVEL_GET
2022-03-06 13:12:21.577 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: SECURITY not supported
2022-03-06 13:12:21.578 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Command Class COMMAND_CLASS_SWITCH_MULTILEVEL is NOT required to be secured
2022-03-06 13:12:21.579 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling skipped for zwave:device:d6d9befb8f:node27:switch_dimmer on COMMAND_CLASS_BASIC
2022-03-06 13:12:21.580 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Adding to device queue
2022-03-06 13:12:21.582 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Added 226 to queue - size 5
2022-03-06 13:12:21.586 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 27: Sending REQUEST Message = 01 09 00 13 1B 02 26 02 25 BC 41 
2022-03-06 13:12:21.602 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: sentData successfully placed on stack.
2022-03-06 13:12:21.603 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: TID 226: Transaction not completed
2022-03-06 13:12:21.627 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: SendData Request. CallBack ID = 188, Status = Transmission complete and ACK received(0)
2022-03-06 13:12:21.628 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: resetResendCount initComplete=true isDead=false
2022-03-06 13:12:21.630 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: TID 226: Transaction not completed
2022-03-06 13:12:21.638 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Application Command Request (ALIVE:DONE)
2022-03-06 13:12:21.639 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: resetResendCount initComplete=true isDead=false
2022-03-06 13:12:21.640 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Incoming command class COMMAND_CLASS_SWITCH_MULTILEVEL, endpoint 0
2022-03-06 13:12:21.641 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: SECURITY not supported
2022-03-06 13:12:21.642 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 27: Received COMMAND_CLASS_SWITCH_MULTILEVEL V1 SWITCH_MULTILEVEL_REPORT
2022-03-06 13:12:21.643 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 27: Switch Multi Level report, value = 71
2022-03-06 13:12:21.643 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2022-03-06 13:12:21.644 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SWITCH_MULTILEVEL, value=71
2022-03-06 13:12:21.645 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Updating channel state zwave:device:d6d9befb8f:node27:switch_dimmer to 71 [PercentType]
2022-03-06 13:12:21.646 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Commands processed 1.
2022-03-06 13:12:21.647 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@93fdfc.
2022-03-06 13:12:21.650 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@93fdfc.
2022-03-06 13:12:21.651 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: notifyTransactionResponse TID:226 DONE
2022-03-06 13:12:21.653 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

apella12 · March 6, 2022, 6:58pm

My guess is the command poll is happening before the device has a chance to get to the level you set. Increase it. If it is still at the default 1500, set at 4000.
As to the actual fan speed, do you see it increase when OH changes the percentage? Or is this just a reporting issue?

Bob

kemotsysinc · March 6, 2022, 7:02pm

Thank you all!!

I did a ‘reset’ of the device and an exclude/include and it seems to be working perfectly!