Adding Secure, but get Clear Text messages (ZME_WALLC-S)

Hello everyone,

I’m really stuck with nothing else to try to debug this.

I had a ZME_WALLC-S that eventually failed after a year or so. Before it failed it was working ok, and was configured in a mode where a short press sent a scene number, and a long press sent another scene number, for each of the 4 buttons.

Anyway, it failed and I ordered a new one.

For the life of me, can’t add it properly to the network. I click “Add Secure” in HA, then press button 1 (upper left) for a few seconds and it starts blinking and exchanging informations. After a few seconds, it seems HA has configured it, but for some reason and I never saw that before, it is recognized as “Popp & Co 009303 Battery Wall Controller”, not as a Z-Wave.me wall controller.

Anyway, It doesn’t bother me, I just want this to work, so once it has been configured, any button I press ends up in OZW logs as :

2019-09-01 05:34:49.478 Detail, Node031,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x1f, 0x05, 0x5b, 0x03, 0x6c, 0x00, 0x01, 0xdf
2019-09-01 05:34:49.478 Detail, 
2019-09-01 05:34:49.478 Warning, Node031, Received a Clear Text Message for the CommandClass COMMAND_CLASS_CENTRAL_SCENE which is Secured
2019-09-01 05:34:49.478 Warning, Node031,    Dropping Message

I can’t figure out why.

Environment

Home Assistant 0.99.0.dev20190831 running in docker on a Raspberry Pi 3B+
Zwaze controller is a RAZBERRY V2 Z-WAVE+.
OpenZwave Version 1.4.3440 in the container

Zwave config in container :

zwave:
  usb_path: /dev/ttyAMA0
  config_path: /usr/local/lib/python3.7/site-packages/python_openzwave/ozw_config
  network_key: "0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX"

Any idea ?

Finally figured it out after days of fighting this…

I had to upgrade python-openzwave. The version I am running now (0.4.19) was able to add the wall controller secured.

After this I ran the controller again (that is running an unknown python-openzwave version — I don’t know how to check —) and the device is now operational