ZME Dual Paddle Wall Controller 1.3 fails after upgrade of Z WAY controller

Discussions about existing Z-Wave device and their usage with Z-Way/Z-Cloud/Z-Box
Post Reply
GG72
Posts: 6
Joined: 25 Oct 2018 21:50

ZME Dual Paddle Wall Controller 1.3 fails after upgrade of Z WAY controller

Post by GG72 »

After upgrade of Z-WAY I get this in the log when pressing the buttons on the ZME dual paddle wall controller

[2022-05-26 12:48:35.027] [D] [zway] RECEIVED: ( 01 0D 00 04 00 0E 07 60 0D 00 01 20 01 FF 4D )
[2022-05-26 12:48:35.028] [D] [zway] SENT ACK
[2022-05-26 12:48:35.029] [D] [zway] SETDATA devices.14.data.lastReceived = 0 (0x00000000)
[2022-05-26 12:48:35.029] [W] [zway] Unhandled command in policy - contact Z-Wave.Me support: 20 01
[2022-05-26 12:48:35.029] [W] [zway] Got unsecure packet from device 14, but Command Class 0x20 Basic is marked as secure and not present in unsecure NIF. Ignoring packet.
[2022-05-26 12:48:35.030] [E] [zway] Error returned from (returnStatus = _zway_cc_call_handler(zway, cmd, node_id, data[3], length - 4, &data[4])): Function class not supported by the hardware (-4)

How can I get it working again?
micky1500
Posts: 298
Joined: 07 Feb 2016 16:29
Location: England

Re: ZME Dual Paddle Wall Controller 1.3 fails after upgrade of Z WAY controller

Post by micky1500 »

I get the same since 3.2.3 with a few different devices.
Forcing an Interview sometimes fixes them.
Some still work, but still give the error.

Here's my Log for investigation further.

[2022-05-26 21:46:20.294] [D] [zway] RECEIVED: ( 01 0C 00 04 00 27 03 25 03 FF C0 00 00 CA )
[2022-05-26 21:46:20.294] [D] [zway] SETDATA devices.39.data.lastReceived = 0 (0x00000000)
[2022-05-26 21:46:20.294] [D] [zway] SETDATA devices.39.instances.0.commandClasses.37.data.level = True
[2022-05-26 21:46:20.302] [core] 3,["tags"]
[2022-05-26 21:46:20.307] [D] [zway] RECEIVED: ( 01 10 00 04 00 27 07 60 0D 01 01 20 03 FF C0 00 00 BA )
[2022-05-26 21:46:20.308] [core] 3,["tags"]
[2022-05-26 21:46:20.309] [D] [zway] SETDATA devices.39.data.lastReceived = 0 (0x00000000)
[2022-05-26 21:46:20.310] [W] [zway] Unhandled command in policy - contact Z-Wave.Me support: 20 03
[2022-05-26 21:46:20.311] [W] [zway] Got unsecure packet from device 39, but Command Class 0x20 Basic is marked as secure and not present in unsecure NIF. Ignoring packet.
[2022-05-26 21:46:20.312] [E] [zway] Error returned from (returnStatus = _zway_cc_call_handler(zway, cmd, node_id, data[3], length - 4, &data[4])): Function class not supported by the hardware (-4)
[2022-05-26 21:46:20.336] [core] [BaseModule-9] Set lastLevel to on for ZWayVDev_zway_39-0-37 (was off)
[2022-05-26 21:46:21.990] [D] [zway] RECEIVED: ( 01 0C 00 04 00 27 03 25 03 00 C1 00 00 34 )
[2022-05-26 21:46:21.991] [D] [zway] SETDATA devices.39.data.lastReceived = 0 (0x00000000)
[2022-05-26 21:46:21.991] [D] [zway] SETDATA devices.39.instances.0.commandClasses.37.data.level = False
[2022-05-26 21:46:22.003] [core] 3,["tags"]
[2022-05-26 21:46:22.004] [D] [zway] RECEIVED: ( 01 10 00 04 00 27 07 60 0D 01 01 20 03 00 C1 00 00 44 )
[2022-05-26 21:46:22.005] [D] [zway] SETDATA devices.39.data.lastReceived = 0 (0x00000000)
[2022-05-26 21:46:22.006] [W] [zway] Unhandled command in policy - contact Z-Wave.Me support: 20 03
[2022-05-26 21:46:22.007] [W] [zway] Got unsecure packet from device 39, but Command Class 0x20 Basic is marked as secure and not present in unsecure NIF. Ignoring packet.
[2022-05-26 21:46:22.007] [E] [zway] Error returned from (returnStatus = _zway_cc_call_handler(zway, cmd, node_id, data[3], length - 4, &data[4])): Function class not supported by the hardware (-4)
[2022-05-26 21:46:22.008] [core] 3,["tags"]
[2022-05-26 21:46:22.034] [core] [BaseModule-9] Set lastLevel to off for ZWayVDev_zway_39-0-37 (was on)
Raspi 4 - (Buster - 32 Bit) Zwave Version 4.1.1, Raz 7 Pro, Serial API Version: 07.38
GG72
Posts: 6
Joined: 25 Oct 2018 21:50

Re: ZME Dual Paddle Wall Controller 1.3 fails after upgrade of Z WAY controller

Post by GG72 »

I have forced interview, excluded , factory reset the device (the dual paddle), and included again... Still same problem...
seattleneil
Posts: 172
Joined: 02 Mar 2020 22:41

Re: ZME Dual Paddle Wall Controller 1.3 fails after upgrade of Z WAY controller

Post by seattleneil »

Using the expert UI (http://[IP]:8083/expert), exclude the device and then include the device again with the include set to be done in "Unsecure" mode, as shown below:
unsecure inclusion.jpg
unsecure inclusion.jpg (45.12 KiB) Viewed 2653 times
You can confirm the device's security mode by looking for a yellow open padlock in the Security column here: http://[IP]:8083/expert/#/device/type
User avatar
PoltoS
Posts: 7565
Joined: 26 Jan 2011 19:36

Re: ZME Dual Paddle Wall Controller 1.3 fails after upgrade of Z WAY controller

Post by PoltoS »

This is a bug we will fix in v3.2.4. Unfortunately, new Z-Wave rules require a more strict policy and look like some unhandled case happened.
GG72
Posts: 6
Joined: 25 Oct 2018 21:50

Re: ZME Dual Paddle Wall Controller 1.3 fails after upgrade of Z WAY controller

Post by GG72 »

seattleneil wrote:
28 May 2022 03:16
Using the expert UI (http://[IP]:8083/expert), exclude the device and then include the device again with the include set to be done in "Unsecure" mode, as shown below:

unsecure inclusion.jpg

You can confirm the device's security mode by looking for a yellow open padlock in the Security column here: http://[IP]:8083/expert/#/device/type
Unfortunatly It doesnt matter if added with secure or unsecure, the same error message appear in the log and the command is discarded. I guess we have to wait for the next version as PoltoS said...
Post Reply