Zooz Zen30 Dimmer Issue

Tags: #<Tag:0x00007f6180e07048> #<Tag:0x00007f6180e06c10>

EDIT: Solved, thanks to @5iver for updating the device’s support in the Z-Wave binding.

I am now 3 for 3 when it comes to Zooz, though the other two were fixed with a combo of firmware and factory resets as suggested by the helpful people at Zooz and on here. This time round I have no such luck with this formula.

The Thing is a Zooz Z-Wave Zen30 multi switch, It has a dimmer and a switch in one unit that are seperate. The upper paddle is the dimmer, and the lowe switch is just a simple On/Off Switch.

The switch part works just fine.Sends commands to OpenHab and receives them. The dimmer not so much.

I can update the dimmer form OH just fine, but there are no updates/commands from the dimmer to OH. Exactly the same behaviour I saw on the Zen27 before I factory reset it.

The events.log showed me nothing, so I worked out how to set it to debug mode for Z-Wave stuff, and I can now see the Z-Wave traffic from the switch (copy of the log below), but nothing in openhab gets updated when I press the paddle.

2020-02-09 15:33:21.951 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 0A 05 5B 03 0B 80 01 2D 
2020-02-09 15:33:21.956 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=10, callback=0, payload=00 0A 05 5B 03 0B 80 01 
2020-02-09 15:33:21.959 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=10, callback=0, payload=00 0A 05 5B 03 0B 80 01 
2020-02-09 15:33:21.961 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-02-09 15:33:21.963 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Application Command Request (ALIVE:PING)
2020-02-09 15:33:21.966 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Incoming command class COMMAND_CLASS_CENTRAL_SCENE, endpoint 0
2020-02-09 15:33:21.968 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: SECURITY not supported
2020-02-09 15:33:21.970 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Received COMMAND_CLASS_CENTRAL_SCENE V3 CENTRAL_SCENE_NOTIFICATION
2020-02-09 15:33:21.972 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 10: Received scene 1 at key 0 [Single Press]
2020-02-09 15:33:21.975 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2020-02-09 15:33:21.977 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_CENTRAL_SCENE, value=1.0
2020-02-09 15:33:21.981 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating channel state zwave:device:5426e5af:node10:scene_number to 1.0 [DecimalType]
2020-02-09 15:33:21.984 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Commands processed 1.
2020-02-09 15:33:21.986 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1fd23ec.
2020-02-09 15:33:21.988 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-02-09 15:33:21.991 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-02-09 15:33:21.993 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-02-09 15:33:21.996 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-02-09 15:33:22.945 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 0A 03 20 03 63 BB 
2020-02-09 15:33:22.950 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=10, callback=0, payload=00 0A 03 20 03 63 
2020-02-09 15:33:22.953 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=10, callback=0, payload=00 0A 03 20 03 63 
2020-02-09 15:33:22.955 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-02-09 15:33:22.958 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Application Command Request (ALIVE:PING)
2020-02-09 15:33:22.960 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
2020-02-09 15:33:22.963 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: SECURITY not supported
2020-02-09 15:33:22.965 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Received COMMAND_CLASS_BASIC V1 BASIC_REPORT
2020-02-09 15:33:22.968 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 10: Basic report, value = 99
2020-02-09 15:33:22.970 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2020-02-09 15:33:22.973 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_BASIC, value=99
2020-02-09 15:33:22.977 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating channel state zwave:device:5426e5af:node10:switch_binary to ON [OnOffType]
2020-02-09 15:33:22.980 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Commands processed 1.
2020-02-09 15:33:22.982 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1dfe6c7.
2020-02-09 15:33:22.984 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-02-09 15:33:22.986 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-02-09 15:33:22.988 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-02-09 15:33:22.991 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

I know @5iver has tested this switch fine with OH. He entered the database entry too.

Did you try factory resetting this switch?

2020-02-09 15:53:51.414 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating channel state zwave:device:5426e5af:node10:switch_binary to ON [OnOffType]

That might be the issue.

There are 4 channels for this Thing:

  • Switch zwave:device:5426e5af:node10:switch_binary
  • Dimmer: zwave:device:5426e5af:node10:switch_dimmer
  • Scene Number: zwave:device:5426e5af:node10:scene_number
  • Switch 1: zwave:device:5426e5af:node10:switch_binary1

And it would appear that when using the paddle it is trying to update the wrong channel (swich_binary instead of switch_dimmer). I’ve no idea if this is an openHab or Zooz issue though.

I did, twice.

1 Like

And helpful support from the volunteers in the forum! Your attitude appears to be more snarky than appreciative, which is not a good way to ensure continued support from said volunteers. :unamused:

When troubleshooting issues like this with the Z-Wave binding, it is helpful to check that you are using the latest version of the Thing definition, since an update may have been made that could resolve an issue you are experiencing. To do this, check the database to see when the entry for the device was last updated. Next, check the date of the binding you are using by executing…

list -s | grep zwave

… in the console. This will return something like this…

image

This example shows a binding dated Feb 9, 2020. The database shows…
image
… so I have the latest version. The update I made to this device on Jan 29, 2020 was to remove the switch_binary Channel from endpoint 0, which will hopefully resolve the issue you are reporting. Since you are showing 4 Channels, including the one I removed, you are either not using the latest binding or you have not deleted and rediscovered the Thing, which you would need to do to use the updated Thing definition. Here is a post that will help with getting the binding updated.

2 Likes

First and foremost, I am grateful, and if my posts to not reflect this then I shall endeavour to do better on this count.

I do not appear to have this command. Do you know what package I need to install to get it? Is that part of listadmin?

I enrolled it this past weekend, and I did go into the openhab-config to make sure my openhab was completely up to date, it said it was. I had no idea that you had to update the binding independently from the rest of it, but now I know. Thanks.

It is available in the Karaf console (documentation link in previous post).

You don’t have to, but you will need to to get the new stuff.

You are very welcome!

@Lutiana, have you had a chance to try the latest binding?

1 Like

Not yet. I am going to try and get to it one of the evenings this week, but those tend to be a bit hectic with family stuff. I’ll update this post as soon as look into it and/or update the binding.

2 Likes

@5iver - Finally get back to this, you are correct I am running the old binding, I downloaded the script needed to update it and have tried to run it twice now, each time I get:

Uninstalling any managed binding(s) and installing serial transport...

Logging in as openhab
Password:
Password:
No more authentication methods available
... a 'No matching bundles' error mesage is normal, if a binding had not been previously installed.

Backing up and uninstalling any unmanaged installs of Z-Wave...

!!!!! It has taken more than two minutes to uninstall the Z-Wave binding, so exiting !!!!!

[17:45:06] openhabian@openhab:/usr/share/openhab2/addons$                                          

I am going to try and remove the binding from the PaperUI and run it again to see what happens.

Thanks,

No luck, now it’s

Uninstalling any managed binding(s) and installing serial transport...

Logging in as openhab
Password:
Password:
No more authentication methods available
... a 'No matching bundles' error mesage is normal, if a binding had not been previously installed.

Backing up and uninstalling any unmanaged installs of Z-Wave... done.

Downloading new Z-Wave jar... done.

Installing unmanaged Z-Wave binding...

!!!!! It has taken more than two minutes to install the Z-Wave binding, so exiting !!!!!

Try it again. If it does not complete, then restart OH and check the version of the binding.

I rebooted the entire system and tried it again, twice, with no luck. Still shows 2.5.1 in the addon section and no Z-wave binding is installed.

Uninstalling any managed binding(s) and installing serial transport...

Logging in as openhab
Password:
Password:
No more authentication methods available
... a 'No matching bundles' error mesage is normal, if a binding had not been previously installed.

Backing up and uninstalling any unmanaged installs of Z-Wave... done.

Downloading new Z-Wave jar... done.

Installing unmanaged Z-Wave binding...
mv: cannot stat '/usr/share/openhab2/addons/archive/staging/zwave/*.jar': No such file or directory

!!!!! It has taken more than two minutes to install the Z-Wave binding, so exiting !!!!!

You will not see it in the Paper UI. In fact the one in the Paper UI should be uninstalled.
Use the Karaf console.

openhab> list -s | grep zwave
openhab>

Allright, I deleted the “archive” folder in the addons folder and ran the script again. It timed out like before, but when I go into the Karaf console it shows up there.

openhab> list -s | grep zwave
266 │ Installed │  80 │ 2.5.2.202002150517      │ org.openhab.binding.zwave
openhab>

But it does not show up in the PaperUI, and I am not able to add Z-Wave items via the PaperUI. Am I correct in assuming that this is expected and I now need add things via the CLI and config files?

The binding is installed but not running. Try starting it from the console. and then check your logs.

What version of openHAB are you running?

It won’t but you should still be able to add your controller as a Thing and then discover other devices.

The latest version as per the openab-config utililty. 4.2.7 according to the “version” command in the console.

Not sure how to do that, “bundle:start org.openhab.binding.zwave” gives me this:

openhab> bundle:start org.openhab.binding.zwave
Error executing command: Error executing command on bundles:
        Error starting bundle 266: Could not resolve module: org.openhab.binding.zwave [266]
  Unresolved requirement: Import-Package: org.eclipse.smarthome.io.transport.serial

Not sure what that means, but if I look for the serial, this is what it finds.

package:imports | grep "serial"
org.eclipse.smarthome.io.transport.serial                 │           │            │ 266 │ org.openhab.binding.zwave

This might also be relevant:

openhab> bundle:diag
openHAB Add-ons :: Bundles :: ZWave Binding (266)
-------------------------------------------------
Status: Installed
Unsatisfied Requirements:
osgi.wiring.package; filter:="(osgi.wiring.package=org.eclipse.smarthome.io.transport.serial)"
osgi.wiring.package; filter:="(osgi.wiring.package=org.openhab.binding.zwave)"
osgi.service; filter:="(objectClass=org.eclipse.smarthome.io.transport.serial.SerialPortManager)"; effective:="active"
Declarative Services


openhab> feature:install org.eclipse.smarthome.io.transport.serial
Error executing command: No matching features for org.eclipse.smarthome.io.transport.serial/0
openhab>

Went into the PaperUI and installed the serial binding. Now the Z-Wave binding has started and shows up in the binding section of PaperUI.

Will the Z-Wave binding auto start with the system, or do I need to set something somewhere to do that?

You are entering the wrong password here and the script is not able to log into the Karaf console to remove the managed binding and install the serial transport. The default password is “habopen”.

1 Like