Module PoppKeypad doesn't work

[piet66]

Hi,
tried to make my Popp keypad run. But I can't manage it:

1. The module requires the input of the chosen keypad, but the enum menu remains empty. Reason I think: there's no device 'devices_sensorBinary:tamper' created. Exchanged in module.json "namespaces:devices_sensorBinary:tamper:deviceId" by "namespaces:devices_battery:deviceId" to be able to select the battery device of my keypad.

2. After storage of the config message 'Something went wrong'.
Log-messages:
[2019-08-27 14:31:27.962] [core] Notification: error (core): Cannot instantiate module: PoppKeypad: TypeError: Cannot read property 'data' of undefined
[2019-08-27 14:31:27.971] [core] TypeError: Cannot read property 'data' of undefined
at ZWave.dataBind (automation/modules/ZWave/index.js83)
at AutomationController._dataBind (automation/modules/ZWave/index.js:208:9)
at AutomationController.EventEmitter.emit (automation/lib/eventemitter2.js:322:33)
at automation/userModules/PoppKeypad/index.js:71:37
at PoppKeypad.zwayReg (automation/userModules/PoppKeypad/index.js:78:19)
at PoppKeypad.init (automation/userModules/PoppKeypad/index.js:122:18)
at AutomationController.instantiateModule (automation/classes/AutomationController.js:498:13)
at AutomationController.createInstance (automation/classes/AutomationController.js:936:17)
at ZAutomationAPIWebRequest._.extend.createInstance (automation/ZAutomationAPIProvider.js31)
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:263:35)

What can I do to get the keypad work?

[piet66]

Seems that the device has no command class 5B=91=Central Scene and that's the reason why the module fails.

I have repeated inclusion and interview several times. What does this mean: is the device defective or does the module not support this device (Popp Keypad 700045 EU)?

[PoltoS]

Can you press buttons on the deviec so it sends you something via Central Scene?

May be another version of the device is in your hands. Other than we have seen

[piet66]

I don't know how often I have excluded and included again this device. Always it was the same: interview was completed, but only 9 command classes are displayed in interview results (always the same ones). According to the device documentation 18 command classes are supported.

Now after one more inclusion suddenly it shows 17 command classes including Alarm and Central Scene. Only command class Door Lock is missing. It's very mysterious.

Do you know whether this missing command class is disposable? Is anybody running the Popp Keypad with or without the Door Lock command class?

(Application version 1.8, SDK version 4.54)

[PoltoS]

Ha! Make sure to have Security interview done. Without Security it will not operate. In fact it will like a dummy

[piet66]

I tested with secure and with unsecure inclusion. Both with same problem.

Indeed it may have anything to do with Security command class.
The NIF now includes 9 command classes. They are identically with the 9 classes from my previous trials, minus Basic plus Security. Security was missing in the wrong interview results.

I'm wondering why ZWay told, that interview was completed for 100%. And I'm wondering why NIF only contains 9 classes whereas the interview results now contain 17.

current classes

Bildschirmfoto vom 2019-08-28 19-26-52.png (40.82 KiB) Viewed 1420 times

[PoltoS]

Is it working now when security is in?

[piet66]

It's working fine now.

But the effects after the previous interviews were very irritating. Maybe you can change something here?

The interview results should show all classes even if Security interview was failed. And it shouldn't tell 'Interview completed 100%' if it isn't true.

[PoltoS]

The device is hiding them if Security failed, so we don't even see then via Z-Wave

[piet66]

But ZWay gets all supported classes already before Security interview starts:

Code: Select all

[2019-08-27 15:03:00.516] [I] [zway] Job 0x4a (Add/re-include node to network): Adding controller: #76
[2019-08-27 15:03:00.526] [I] [zway] Job 0x62 (Check if node is failed): Node 76 is operating
[2019-08-27 15:03:09.494] [I] [zway] Node 76:0 supports CC Basic
[2019-08-27 15:03:09.494] [I] [zway] Node 76:0 supports CC SensorBinary
[2019-08-27 15:03:09.494] [I] [zway] Node 76:0 supports CC AssociationGroupInformation
[2019-08-27 15:03:09.494] [I] [zway] Node 76:0 supports CC DeviceResetLocally
[2019-08-27 15:03:09.494] [I] [zway] Node 76:0 supports CC CentralScene
[2019-08-27 15:03:09.494] [I] [zway] Node 76:0 supports CC ZWavePlusInfo
[2019-08-27 15:03:09.495] [I] [zway] Node 76:0 supports CC UserCode
[2019-08-27 15:03:09.496] [I] [zway] Node 76:0 supports CC Configuration
[2019-08-27 15:03:09.496] [I] [zway] Node 76:0 supports CC Alarm
[2019-08-27 15:03:09.496] [I] [zway] Node 76:0 supports CC ManufacturerSpecific
[2019-08-27 15:03:09.496] [I] [zway] Node 76:0 supports CC PowerLevel
[2019-08-27 15:03:09.496] [I] [zway] Node 76:0 supports CC FirmwareUpdate
[2019-08-27 15:03:09.496] [I] [zway] Node 76:0 supports CC Battery
[2019-08-27 15:03:09.497] [I] [zway] Node 76:0 supports CC Wakeup
[2019-08-27 15:03:09.497] [I] [zway] Node 76:0 supports CC Association
[2019-08-27 15:03:09.497] [I] [zway] Node 76:0 supports CC Version
[2019-08-27 15:03:09.497] [I] [zway] Node 76:0 supports CC Security
[2019-08-27 15:03:09.497] [I] [zway] Node 76 controls CC Basic
[2019-08-27 15:03:09.498] [I] [zway] Node 76 controls CC DoorLock
[2019-08-27 15:03:09.498] [I] [zway] Node 76:0 CC Security Interview started