TKB TZ35D strange issues, help!

Add-ons Bindings
#1

Im having some strange issues with one of my TKB TZ35 double dimmers.
Running M5 on Ubuntu with Zstick.

Ok, its recognized as TZ55D Dual Paddle Wall Dimmer, but its the same thing.
@chris TZ55D DB entry has some issues

The problem is with the right paddle.
Can’t get any value in between (dimming), not sure if its supported, but as the name suggests it is supposed to be double-paddle dimmer.
Shouldn’t both channels be switch multilevel?

The bigger issue is when switching on (pressing on top) it sends 0 and when its switched off it sends 100.

And when I press left paddle I get 2 events, left set to X and right set to X.
Pressing right ON again sets it from X to 0.
I have no idea how this 2 got linked.

So issues are:

  • reversed right paddle (left one is ok, based on config)
  • no dimming events at all
  • somehow right paddle is linked to left paddle

Here is the log:

Left paddle on

Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=50, callback=0, payload=00 32 03 26 03 5A

  • NODE 50: Application Command Request (ALIVE:DONE)
  • NODE 50: resetResendCount initComplete=true isDead=false
  • NODE 50: Incoming command class COMMAND_CLASS_SWITCH_MULTILEVEL, endpoint 0
  • NODE 50: SECURITY not supported
  • NODE 50: Received COMMAND_CLASS_SWITCH_MULTILEVEL V1 SWITCH_MULTILEVEL_REPORT
  • NODE 50: Switch Multi Level report, value = 90
  • NODE 50: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
  • NODE 50: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SWITCH_MULTILEVEL, value=90
  • NODE 50: Updating channel state zwave:device:8fcc513b:node50:switch_dimmer to 90 [PercentType]
  • NODE 50: Commands processed 1.
  • NODE 50: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1398a8f.

Right paddle on

Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=50, callback=0, payload=00 32 03 20 01 00

  • NODE 50: Application Command Request (ALIVE:DONE)
  • NODE 50: resetResendCount initComplete=true isDead=false
  • NODE 50: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
  • NODE 50: SECURITY not supported
  • NODE 50: Received COMMAND_CLASS_BASIC V1 BASIC_SET
  • NODE 50: Basic report, value = 0
  • NODE 50: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
  • NODE 50: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_BASIC, value=0
  • NODE 50: Updating channel state zwave:device:8fcc513b:node50:basic_switch_dimmer to 0 [PercentType]
  • NODE 50: Commands processed 1.
  • NODE 50: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@983a66.

Paper UI config

30
301299×739 42.5 KB

Zwave config XML
network_dd913fe6__node_50.xml (12.7 KB)

Any ideas?

#2

I don’t have this device but according to the Usage Information in the database tapping up and down controls the load ON/OFF and pressing and holding dims devices which are associated to the TZ55D (means you need to use direct associations from your TZ55 to the device you want to dim).

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/516

Basic Operation (Local C ontrol)
The left switch on the switch allows the user to:
-The on or off the attached load.
-Include or exclude the module from the Z-Wave system.
-Control other Z-Wave enabled devices.
The right switch on the switch allows the user to:
-Control other Z-Wave enable devices
Also, when a controller prompts you to “Send Node ID” or to “Press Button on Unit”,quickly tap the switch on or off three times to satisfy those instructions.
-Tapping top of left switch turns the load attached on.
-Tapping bottom of left switch turns the load attached off.
-Pressing and holding the left switch does not effect the load attached but will allow dimming and brightening of Z-Wave dimmers if associated.

#3

Ok, just a quick update for future visitors.

Resetting the device and adding it to the network resolved the strange right paddle behavior.

As for dimming, the docs are right with some mixed-up words for left and right paddles.
Right paddle can dim devices in an associated group with but it won’t send dimming updates to lifeline. Just On and Off events.
Left paddle sends everything.

As a side note when using rules, if you set low pooling interval you will receive multiple updates as it is dimming.
I.e. you send command 90 and you will receive 30, 60 and finally 90 back.

#4

It would be great if we could add these notes, or something along these lines to the database. There is a section called something like “Usage notes” for each device - this is intended to add stuff like this to supplement the official docs and it then ends up in the openHAB documentation.

1 Like
#5

Done.
Updated and formated :slight_smile:

1 Like