Zooz Zen34 Remote Switch unknown device

Tags: #<Tag:0x00007f433cc5cbd8> #<Tag:0x00007f433cc5ca70>

I have a Zooz Zen34 Remote Switch that is not being recognized correctly by the zwave binding. I see it was added in OH-2.5.11, but it doesn’t look like mine is being discovered correctly. I get the following warning “Device discovery could not resolve to a thingType! 027A:7000:F001::1.1”

Here is my log:

2021-01-21 10:01:03.253 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 44: Node advancer - advancing to IDENTIFY_NODE
2021-01-21 10:01:03.253 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 44: Node advancer: Initialisation starting
2021-01-21 10:01:03.495 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Controller status changed to ONLINE.
2021-01-21 10:01:03.496 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Controller is ONLINE. Starting device initialisation.
2021-01-21 10:01:03.496 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Updating node properties.
2021-01-21 10:01:03.498 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Updating node properties. MAN=634
2021-01-21 10:01:03.500 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Updating node properties. MAN=634. SET. Was 634
2021-01-21 10:01:03.500 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Properties synchronised
2021-01-21 10:01:03.502 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Update ASSOCIATION group_ZWaveAssociationGroup [index=1, name=Lifeline, profile1=0, profile2=1, associations=[node_1]]: Adding Controller (node_1)
2021-01-21 10:01:03.502 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Initialising Thing Node…
2021-01-21 10:01:03.502 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Polling initialised at 86400 seconds - start in 37238400 milliseconds.
2021-01-21 10:01:03.503 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Device initialisation complete.
2021-01-21 10:01:03.779 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: ProtocolInfo
2021-01-21 10:01:03.779 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: Listening = false
2021-01-21 10:01:03.779 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: Routing = true
2021-01-21 10:01:03.779 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: Beaming = true
2021-01-21 10:01:03.779 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: Version = 4
2021-01-21 10:01:03.779 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: FLIRS = false
2021-01-21 10:01:03.779 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: Security = false
2021-01-21 10:01:03.780 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: Max Baud = 40000
2021-01-21 10:01:03.780 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: Basic = BASIC_TYPE_ROUTING_SLAVE
2021-01-21 10:01:03.780 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: Generic = GENERIC_TYPE_WALL_CONTROLLER
2021-01-21 10:01:03.780 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 44: Specific = SPECIFIC_TYPE_NOT_USED
2021-01-21 10:01:03.780 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 44: Creating new instance of command class COMMAND_CLASS_NO_OPERATION
2021-01-21 10:01:03.780 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 44: Command class COMMAND_CLASS_NO_OPERATION, endpoint 0 created
2021-01-21 10:01:03.781 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 44: Version = 1, version set. Enabling extra functionality.
2021-01-21 10:01:03.781 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 44: Adding command class COMMAND_CLASS_NO_OPERATION to the list of supported command classes.
2021-01-21 10:01:03.781 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 44: Creating new instance of command class COMMAND_CLASS_BASIC
2021-01-21 10:01:03.781 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 44: Command class COMMAND_CLASS_BASIC, endpoint 0 created
2021-01-21 10:01:03.781 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 44: Adding command class COMMAND_CLASS_BASIC to the list of supported command classes.
2021-01-21 10:01:03.783 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 44: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@49dc42fa
2021-01-21 10:01:03.786 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 44: Node Init transaction completed with response COMPLETE
2021-01-21 10:01:03.786 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 44: Node advancer - advancing to REQUEST_NIF
2021-01-21 10:01:03.786 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 44: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2021-01-21 10:01:03.786 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 44: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@cded5a5
2021-01-21 10:01:03.787 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 44: Bump transaction 80 priority from Controller to Immediate
2021-01-21 10:01:03.787 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 44: Adding to device queue
2021-01-21 10:01:03.788 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 44: Added 80 to queue - size 31

Thanks

Hmmm. That is a different device type than listed in the database.

It is unusual for them to change but perhaps some improvement they want to track.

I updated the database & it should make ot to a snapshot version of the binding in about a week. Yo can then use the update script to manually install the binding.

Zigbee and Z-Wave manual install script - Tutorials & Examples - openHAB Community

Thanks for the quick reply!

It is also possible the device we used was a pre-production or early production device. Zooz support has been very helpful getting their devices supported in OH.

I upgraded to OH 3.1 and still have the same problem. I have tried both milestone and snapshot versions, and it still shows unknown.

Did you delete & rediscover the Thing to get the latest binding settings? It should be in any version 3.0.1 and newer of the binding.

I did, but I can do it again. Do I need to exclude it from the zwave network, or just delete the thing?

You should just be able to delete the Thing. If fact I just got one of those this past weekend so I may be able to test.

Ok. I’ll try it again tomorrow. Thanks.

OK I just tested. I see this has a 700 series chip which, I thought, would be compatible with 500 Series controllers. I see this messah=ge in the logs though

2021-02-09 23:21:24.582 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 027A:7000:F001::1.1

@chris does that listed ID look correct? I do not recall seeing the double colon previously. Imay need to contact Zooz support.

The fact that it has a 700 series chip in itself is irrelevant - it makes no difference. All that matters is the external interface - not the silicon.

What do you mean by correct? It looks like it is included in the database if that’s what you mean?

The colons are just the way it is printed - it’s nothing to do with the device and Zooz support won’t have anything to do with this. All that matters is the values.

OK is this enough DEBUG log?
zen34-1.log (144.9 KB)

This is a clean install of 3.0.1 in Docker with the HUSBZB-1 controller. I just received the switch this past weekend. Node 2 is a zombie & this is node 3 after a factory reset.

Looking quickly on GitHub, it appears the new ID made it into the 2.5.x database but not the 3.x one.

EDIT: It appears that at some point the master branch was renamed to main breaking database exports.

OK I was able to get in one quick test. Since I am testing with Docker it was easy for me tio install the latest OH 3.1.0 snapshot. With that binding I actually had to exclude & include the device, but it is properly discovered now.

Usually you just need to delete & re-add the Thing but that did not work in this situation. Unfortunately, I have zombie nodes to clean up now :frowning:

It works now. Thanks for tracking it down!

1 Like

I have the latest 3.1.0 snapshot and still can’t get the ZEN34 to add correctly. It seems like inclusion never finishes, because the blue light keeps flashing on the switch, and openhab never shows a proper device name. I’ve tried excluding, factory resetting, etc, but to no avail. Any thoughts?

If inclusion never finishes it is likely some other issue. Try factory resetting the device and then including.

Failing that, contact the excellent Zooz support. You may have a defective unit and they will likely promptly replace it, sometimes with a tested one verified to work properly/

I followed this thread, upgraded to 3.1.0-SNAPSHOT using the Debian repository, and I was able to successfully add the device (Node 28 below) and it shows the proper channels (Battery and Scene), but when I press the buttons on the device there is never any event generated. I have turned on debug logging for ZWave in Karaf and still do not see anything when I change the scene back and forth.

09:17:01.196 [INFO ] [ig.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:3b823768:node28' to inbox.
09:17:01.197 [INFO ] [openhab.event.InboxAddedEvent        ] - Discovery Result with UID 'zwave:device:3b823768:node28' has been added.
09:17:11.959 [INFO ] [openhab.event.InboxRemovedEvent      ] - Discovery Result with UID 'zwave:device:3b823768:node28' has been removed.
09:17:11.965 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:3b823768:node28' changed from UNINITIALIZED to INITIALIZING
09:17:11.971 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:3b823768:node28.
09:17:11.974 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Controller status changed to ONLINE.
09:17:11.975 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Controller is ONLINE. Starting device initialisation.
09:17:11.976 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:3b823768:node28' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
09:17:11.981 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:3b823768:node28' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
09:17:11.988 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Updating node properties.
09:17:11.991 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Updating node properties. MAN=634
09:17:11.993 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Updating node properties. MAN=634. SET. Was 634
09:17:11.994 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Properties synchronised
09:17:11.997 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration synchronised
09:17:12.000 [DEBUG] [ave.internal.protocol.ZWaveController] - Event listener added.
09:17:12.002 [INFO ] [openhab.event.ConfigStatusInfoEvent  ] - ConfigStatusInfo [configStatusMessages=[]]
09:17:12.002 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Initialising Thing Node...
09:17:12.004 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Initialising cmd channel zwave:device:3b823768:node28:scene_number for DecimalType
09:17:12.006 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Initialising state channel zwave:device:3b823768:node28:scene_number for DecimalType
09:17:12.007 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Initialising cmd channel zwave:device:3b823768:node28:battery-level for PercentType
09:17:12.008 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Initialising state channel zwave:device:3b823768:node28:battery-level for PercentType
09:17:12.009 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Polling initialised at 1800 seconds - start in 909000 milliseconds.
09:17:12.010 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Device initialisation complete.

I unboxed and paired a second device and added it to my OpenHAB successfully and still have the same issue of no events. Regardless of which button I press or which combination of “clicks”, I see no events in the debug logs.

Perhaps another interesting bit of information is that from the “Thing” config I tried to set the bottom button LED color to Green and in the logs it looks like the configuration was applied, but the switch behavior has not changed. Pressing the bottom button still shows a white light.

09:23:50.091 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration update received
09:23:50.093 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration update ignored config_1_1 to 1 (BigDecimal)
09:23:50.095 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration update ignored config_2_1 to 1 (BigDecimal)
09:23:50.096 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration update ignored wakeup_node to 1 (BigDecimal)
09:23:50.098 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration update ignored wakeup_interval to 43200 (BigDecimal)
09:23:50.099 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration update set config_3_1 to 2 (BigDecimal)
09:23:50.101 [DEBUG] [dclass.ZWaveConfigurationCommandClass] - NODE 28: Creating new message for application command CONFIGURATION_SET
09:23:50.102 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 28: SECURITY not supported
09:23:50.104 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 28: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured
09:23:50.105 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Bump transaction 135 priority from Config to Immediate
09:23:50.107 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Adding to device queue
09:23:50.108 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Transaction already in queue - removed original
09:23:50.109 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Added 135 to queue - size 6
09:23:50.111 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
09:23:50.112 [DEBUG] [dclass.ZWaveConfigurationCommandClass] - NODE 28: Creating new message for application command CONFIGURATIONCMD_GET
09:23:50.114 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 28: SECURITY not supported
09:23:50.115 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 28: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured
09:23:50.117 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Bump transaction 136 priority from Config to Immediate
09:23:50.118 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Adding to device queue
09:23:50.119 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Transaction already in queue - removed original
09:23:50.121 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Added 136 to queue - size 6
09:23:50.122 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
09:23:50.124 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration update set group_1 to [] (String)
09:23:50.126 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Association 1 consolidated to []
09:23:50.127 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Current members before update ZWaveAssociationGroup [index=1, name=null, profile1=null, profile2=null, associations=[]]
09:23:50.128 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Members after config update ZWaveAssociationGroup [index=1, name=null, profile1=null, profile2=null, associations=[]]
09:23:50.130 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Controller is master - forcing associations
09:23:50.134 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Group is controller - forcing association
09:23:50.136 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Members after controller update ZWaveAssociationGroup [index=1, name=null, profile1=null, profile2=null, associations=[node_1_1]]
09:23:50.137 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Adding node_1_1 to association group 1
09:23:50.139 [DEBUG] [andclass.ZWaveAssociationCommandClass] - NODE 28: Creating new message for application command ASSOCIATIONCMD_SET, group=1, node=1
09:23:50.140 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 28: SECURITY not supported
09:23:50.142 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 28: Command Class COMMAND_CLASS_ASSOCIATION is NOT required to be secured
09:23:50.143 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Bump transaction 137 priority from Config to Immediate
09:23:50.145 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Adding to device queue
09:23:50.146 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Transaction already in queue - removed original
09:23:50.147 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Added 137 to queue - size 6
09:23:50.149 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
09:23:50.150 [DEBUG] [andclass.ZWaveAssociationCommandClass] - NODE 28: Creating new message for application command ASSOCIATIONCMD_GET group 1
09:23:50.152 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 28: SECURITY not supported
09:23:50.153 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 28: Command Class COMMAND_CLASS_ASSOCIATION is NOT required to be secured
09:23:50.155 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Bump transaction 138 priority from Config to Immediate
09:23:50.156 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Adding to device queue
09:23:50.158 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Transaction already in queue - removed original
09:23:50.159 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 28: Added 138 to queue - size 6
09:23:50.161 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
09:23:50.162 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration update ignored group_3 to [] (EmptyList)
09:23:50.164 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration update ignored node_id to 28 (BigDecimal)
09:23:50.165 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 28: Configuration update ignored group_2 to [] (EmptyList)
09:23:50.170 [INFO ] [openhab.event.ConfigStatusInfoEvent  ] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_3_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]