No Factory ID trying to add new Zwave device Popp KeyFob

Using OH 2.5.10-1, I have issues connecting a new Z-wave device, the Popp KeyFob-C. The manufacturerId and the device ID cannot be found, and the XML file is not generated. As a consequence, I get an empy Zwave thing which cannot do anything in Openhab. However, the correct Zwave messages are visible on the OH log, using Zwave debug mode.
What is going wrong here ?

Context: Rasperry PI 3b, Aeotec Zwave USB stick, OH 2.5.10-1.
Device: Popp Keyfob with 4 buttons, 009204, it is in the OH database since OH 2.3.0

The openhab.log extract:

NODE 20: Node found
NODE 20: Init node thread start
NODE 20: Serializing from file /var/lib/openhab2/zwave/network_dd73867f__node_20.xml
NODE 20: Error serializing from file: file does not exist.
NODE 20: Starting initialisation from EMPTYNODE
NODE 20: Init node thread finished
NODE 20: Node advancer - advancing to IDENTIFY_NODE
NODE 20: Node advancer: Initialisation starting
NODE 20: ProtocolInfo
NODE 20: Listening = false
NODE 20: Routing   = false
NODE 20: Beaming   = true
NODE 20: Version   = 4
NODE 20: FLIRS     = false
NODE 20: Security  = false
NODE 20: Max Baud  = 40000
NODE 20: Basic    = BASIC_TYPE_CONTROLLER
NODE 20: Generic  = GENERIC_TYPE_GENERIC_CONTROLLER
NODE 20: Specific = SPECIFIC_TYPE_REMOTE_CONTROL_SIMPLE
NODE 20: Creating new instance of command class COMMAND_CLASS_NO_OPERATION
NODE 20: Command class COMMAND_CLASS_NO_OPERATION, endpoint 0 created
NODE 20: Version = 1, version set. Enabling extra functionality.
NODE 20: Adding command class COMMAND_CLASS_NO_OPERATION to the list of supported command classes.
NODE 20: Creating new instance of command class COMMAND_CLASS_BASIC
NODE 20: Command class COMMAND_CLASS_BASIC, endpoint 0 created
NODE 20: Adding command class COMMAND_CLASS_BASIC to the list of supported command classes.
NODE 20: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@10381ce
NODE 20: Node Init transaction completed with response COMPLETE
NODE 20: Node advancer - advancing to REQUEST_NIF
NODE 20: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@117ca
NODE 20: Bump transaction 61961 priority from Controller to Immediate
NODE 20: Adding to device queue
NODE 20: Added 61961 to queue - size 1
NODE 20: Device discovery completed
NODE 20: Device discovery could not resolve to a thingType! Manufacturer data not known.
NODE 20: MANUFACTURER not set
NODE 20: Controller status changed to ONLINE.
NODE 20: Controller is ONLINE. Starting device initialisation.
NODE 20: Updating node properties.
NODE 20: Updating node properties. MAN=2147483647

However, Zwave commands from this device are visible in the log, so at the Z-wave layer, commands are visible:

NODE 20: Received scene 4 at key 0 [Single Press]

Any idea’s ?

That is your problem. Battery operated devices usually need to be woken up many timed for them to respond to the NIF request & device discovery to complete.

1 Like

OK, thanks, I’ll try that!