Remote control Popp KFOB-C

SteMo · July 17, 2016, 7:31pm

HI,
in the past I had a threat regarding my remote control from Popp, the KFOB-C. Sorry, but I have to come back to this issue.

The last answer I got was:

I saw in this forum how to create a scene with the KFOB-C. Therefore it should be possible to include it.
Now I am exact at the point like at the beginning of this thread. The Popp KFOB-C is included, but in the
administartion interface the configuration chapter has no content. I can’ configure it.

Has someone this remote control in use and can give me a hint how to include and operate it in openhab? I have updated my z-wave binding, this can’t be the reason.

chris · July 18, 2016, 6:18am

Does the device show correctly as a KFOB in HABmin, or does it show that it is unknown? If it’s unknown, then you will have no config parameters and associations and the device needs to complete initialisation by being woken up a few times near the controller.

If it doesn’t complete initialisation after this, then get a log file and have a look at what is happening.

Chris

SteMo · July 19, 2016, 7:38pm

Hi chris,

sorry, but I don’t know what I shall looking for. I woke the device up several times but without any positive result.
The device is not shown as KFOB but as ‘ZWave.me [ID:103,Type:100]’. Within the request.log I found the Node 37. And this logfile with the node 37 line will be longer and longer, always with the same note. Probably this node tries something.

192.168.178.21 -  -  [19/Jul/2016:19:22:46 +0000] "GET /services/habmin/zwave/nodes/node37/?_dc=1468956165496 HTTP/1.1" 200 1041 
192.168.178.21 -  -  [19/Jul/2016:19:22:46 +0000] "GET /services/habmin/zwave/nodes/?_dc=1468956165498 HTTP/1.1" 200 7658 
192.168.178.21 -  -  [19/Jul/2016:19:22:51 +0000] "GET /services/habmin/zwave/nodes/node37/?_dc=1468956170497 HTTP/1.1" 200 1041 
192.168.178.21 -  -  [19/Jul/2016:19:22:51 +0000] "GET /services/habmin/zwave/nodes/?_dc=1468956170498 HTTP/1.1" 200 7658 
192.168.178.21 -  -  [19/Jul/2016:19:22:56 +0000] "GET /services/habmin/zwave/nodes/node37/?_dc=1468956175498 HTTP/1.1" 200 1041 
192.168.178.21 -  -  [19/Jul/2016:19:22:56 +0000] "GET /services/habmin/zwave/nodes/?_dc=1468956175499 HTTP/1.1" 200 7658 
192.168.178.21 -  -  [19/Jul/2016:19:23:01 +0000] "GET /services/habmin/zwave/nodes/?_dc=1468956180503 HTTP/1.1" 200 7658 
192.168.178.21 -  -  [19/Jul/2016:19:23:01 +0000] "GET /services/habmin/zwave/nodes/node37/?_dc=1468956180500 HTTP/1.1" 200 1041 
192.168.178.21 -  -  [19/Jul/2016:19:23:06 +0000] "GET /services/habmin/zwave/nodes/?_dc=1468956185501 HTTP/1.1" 200 7658 
192.168.178.21 -  -  [19/Jul/2016:19:23:06 +0000] "GET /services/habmin/zwave/nodes/node37/?_dc=1468956185500 HTTP/1.1" 200 1041 
192.168.178.21 -  -  [19/Jul/2016:19:23:11 +0000] "GET /services/habmin/zwave/nodes/node37/?_dc=1468956190503 HTTP/1.1" 200 1041 
192.168.178.21 -  -  [19/Jul/2016:19:23:11 +0000] "GET /services/habmin/zwave/nodes/?_dc=1468956190504 HTTP/1.1" 200 7658 
192.168.178.21 -  -  [19/Jul/2016:19:23:16 +0000] "GET /services/habmin/zwave/nodes/node37/?_dc=1468956195504 HTTP/1.1" 200 1041 
192.168.178.21 -  -  [19/Jul/2016:19:23:16 +0000] "GET /services/habmin/zwave/nodes/?_dc=1468956195506 HTTP/1.1" 200 7658

In the zwave.log I found this:

2016-07-19 21:25:52.227 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:25:52.281 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:25:57.306 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:25:57.308 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:02.196 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:02.199 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:07.230 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:07.232 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:12.225 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:12.228 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:17.262 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:17.265 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:22.204 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:22.207 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:27.271 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:27.273 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:32.240 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:32.242 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:37.218 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:37.221 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:42.377 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 15: No database entry: ZWave.me [ID:103,Type:100]
2016-07-19 21:26:42.380 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:288]- NODE 37: No database entry: ZWave.me [ID:103,Type:100]

Thats all I could find about this node.

SteMo · July 23, 2016, 7:15pm

I woke the device up several times, but no success. Then I tried "heal node " and “reinitialize node” with the result that in the administaration interface in the column “value” also the entry “ZWave.me [ID:103,Type:100]” is escaped. Now there is nothing in this column.

Here a part of the zwave.log before I tried to wake up the device and heal it:

2016-07-23 18:03:01.478 WARN  o.o.b.z.i.p.c.ZWaveCommandClass[:239]- NODE 37: Unsupported command class ZWAVE_PLUS_INFO
2016-07-23 18:03:01.479 WARN  o.o.b.z.i.p.c.ZWaveCommandClass[:239]- NODE 37: Unsupported command class SCENE_CONTROLLER_CONF
2016-07-23 18:03:01.480 WARN  o.o.b.z.i.p.c.ZWaveCommandClass[:239]- NODE 37: Unsupported command class MULTI_INSTANCE_ASSOCIATION
2016-07-23 18:03:01.481 WARN  o.o.b.z.i.p.c.ZWaveCommandClass[:239]- NODE 37: Unsupported command class ASSOCIATION_GROUP_INFO
2016-07-23 18:03:01.482 WARN  o.o.b.z.i.p.c.ZWaveCommandClass[:239]- NODE 37: Unsupported command class POWERLEVEL
2016-07-23 18:03:01.483 WARN  o.o.b.z.i.p.c.ZWaveCommandClass[:239]- NODE 37: Unsupported command class DEVICE_RESET_LOCALLY

Afte this procedure:

2016-07-23 20:52:23.491 DEBUG o.o.b.z.i.ZWaveActiveBinding[:449]- ZwaveIncomingEvent
2016-07-23 20:52:23.493 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:1034]- NODE 37: Node advancer - FAILED_CHECK: Transaction complete (IsFailedNodeID:Request) success(true)
2016-07-23 20:52:23.494 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:202]- NODE 37: Node advancer - checking initialisation queue. Queue size 1.
2016-07-23 20:52:23.495 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:208]- NODE 37: Node advancer - message removed from queue. Queue size 0.
2016-07-23 20:52:23.496 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:267]- NODE 37: Node advancer - FAILED_CHECK: queue length(0), free to send(true)
2016-07-23 20:52:23.498 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:332]- NODE 37: Node advancer: loop - FAILED_CHECK try 1: stageAdvanced(false)
2016-07-23 20:52:23.499 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:890]- NODE 37: Node advancer - advancing to WAIT
2016-07-23 20:52:23.500 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:332]- NODE 37: Node advancer: loop - WAIT try 0: stageAdvanced(true)
2016-07-23 20:52:23.502 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:380]- NODE 37: Node advancer: WAIT - Listening=false, FrequentlyListening=false
2016-07-23 20:52:23.503 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:398]- NODE 37: Node advancer: WAIT - Still waiting!
2016-07-23 20:52:23.505 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1364]- NODE 255: Response processed after 46ms/4769ms.

and:

2016-07-23 20:52:23.170 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:993]- NODE 37: re-initialising node
2016-07-23 20:52:23.253 DEBUG o.o.b.z.i.p.ZWaveController[:506]- NODE 37: Init node thread start
2016-07-23 20:52:23.290 DEBUG o.o.b.z.i.p.i.ZWaveNodeSerializer[:138]- NODE 37: Serializing from file /var/lib/openhab/zwave/node37.xml
2016-07-23 20:52:23.292 DEBUG o.o.b.z.i.p.i.ZWaveNodeSerializer[:141]- NODE 37: Error serializing from file: file does not exist.
2016-07-23 20:52:23.293 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:267]- NODE 37: Node advancer - EMPTYNODE: queue length(0), free to send(true)
2016-07-23 20:52:23.294 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:332]- NODE 37: Node advancer: loop - EMPTYNODE try 1: stageAdvanced(false)
2016-07-23 20:52:23.295 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:337]- NODE 37: Node advancer: Initialisation starting
2016-07-23 20:52:23.296 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:890]- NODE 37: Node advancer - advancing to PROTOINFO
2016-07-23 20:52:23.297 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:332]- NODE 37: Node advancer: loop - PROTOINFO try 0: stageAdvanced(true)
2016-07-23 20:52:23.297 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:346]- NODE 37: Node advancer: PROTOINFO - send IdentifyNode

2016-07-23 20:52:23.301 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1301]- NODE 255: Sending REQUEST Message = 01 04 00 41 25 9F 
2016-07-23 20:52:23.302 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:240]- NODE 37: Node advancer - queued packet. Queue length is 1
2016-07-23 20:52:23.304 DEBUG o.o.b.z.i.p.ZWaveController[:595]- NODE 37: Init node thread finished

Init node thread finished --> but it isn’t

and then:

2016-07-23 20:52:23.347 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:56]- NODE 37: ProtocolInfo
2016-07-23 20:52:23.348 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:72]- NODE 37: Listening = false
2016-07-23 20:52:23.349 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:73]- NODE 37: Routing = false
2016-07-23 20:52:23.349 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:74]- NODE 37: Beaming = true
2016-07-23 20:52:23.350 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:75]- NODE 37: Version = 4
2016-07-23 20:52:23.351 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:76]- NODE 37: FLIRS = false
2016-07-23 20:52:23.351 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:77]- NODE 37: Security = false
2016-07-23 20:52:23.352 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:78]- NODE 37: Max Baud = 40000
2016-07-23 20:52:23.353 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:94]- NODE 37: Basic = Controller
2016-07-23 20:52:23.353 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:102]- NODE 37: Generic = Remote Controller
2016-07-23 20:52:23.354 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:110]- NODE 37: Specific = Simple Remote Controller
2016-07-23 20:52:23.355 DEBUG o.o.b.z.i.p.c.ZWaveCommandClass[:243]- NODE 37: Creating new instance of command class NO_OPERATION
2016-07-23 20:52:23.356 DEBUG o.o.b.z.i.protocol.ZWaveNode[:613]- NODE 37: Adding command class NO_OPERATION to the list of supported command classes.
2016-07-23 20:52:23.357 DEBUG o.o.b.z.i.p.c.ZWaveCommandClass[:243]- NODE 37: Creating new instance of command class BASIC
2016-07-23 20:52:23.358 DEBUG o.o.b.z.i.protocol.ZWaveNode[:613]- NODE 37: Adding command class BASIC to the list of supported command classes.
2016-07-23 20:52:23.359 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:66]- Sent message Message: class = IdentifyNode (0x41), type = Request (0x00), payload = 25 
2016-07-23 20:52:23.360 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:67]- Recv message Message: class = IdentifyNode (0x41), type = Response (0x01), payload = 13 96 01 01 01 06 
2016-07-23 20:52:23.361 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:68]- Checking transaction complete: class=IdentifyNode, expected=IdentifyNode, cancelled=false
2016-07-23 20:52:23.362 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:74]-          transaction complete!
2016-07-23 20:52:23.363 DEBUG o.o.b.z.i.p.ZWaveController[:648]- Notifying event listeners: ZWaveTransactionCompletedEvent
2016-07-23 20:52:23.363 DEBUG o.o.b.z.i.ZWaveActiveBinding[:449]- ZwaveIncomingEvent
2016-07-23 20:52:23.364 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:1034]- NODE 37: Node advancer - PROTOINFO: Transaction complete (IdentifyNode:Request) success(true)
2016-07-23 20:52:23.365 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:202]- NODE 37: Node advancer - checking initialisation queue. Queue size 1.
2016-07-23 20:52:23.366 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:208]- NODE 37: Node advancer - message removed from queue. Queue size 0.
2016-07-23 20:52:23.367 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:267]- NODE 37: Node advancer - PROTOINFO: queue length(0), free to send(true)
2016-07-23 20:52:23.370 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:332]- NODE 37: Node advancer: loop - PROTOINFO try 1: stageAdvanced(false)
2016-07-23 20:52:23.371 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:890]- NODE 37: Node advancer - advancing to NEIGHBORS
2016-07-23 20:52:23.372 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:332]- NODE 37: Node advancer: loop - NEIGHBORS try 0: stageAdvanced(true)
2016-07-23 20:52:23.373 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:356]- NODE 37: Node advancer: NEIGHBORS - send RoutingInfo
2016-07-23 20:52:23.373 DEBUG o.o.b.z.i.p.s.GetRoutingInfoMessageClass[:30]- NODE 37: Request routing info
2016-07-23 20:52:23.374 DEBUG o.o.b.z.i.p.SerialMessage[:113]- NODE 255: Creating empty message of class = GetRoutingInfo (0x80), type = Request (0x00)
2016-07-23 20:52:23.375 DEBUG o.o.b.z.i.p.ZWaveController[:632]- Enqueueing message. Queue length = 1
2016-07-23 20:52:23.376 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:240]- NODE 37: Node advancer - queued packet. Queue length is 1

I do not understand the logfile. What can I do to get this device in operation?

chris · July 24, 2016, 9:06am

There’s nothing wrong with the log file at all. Everything you have presented is normal.

You will need to wake up the device - probably a few times. To do this you will need to press a button on the device - please read the manual on how to do this. When you do this, the device must be reasonably close to the controllers so that the controller can configure the device.

SteMo · July 26, 2016, 7:29pm

OK, I woke up the device like described in the manual. By the way, I did the same some month ago with the zwave.me software and there I could include this device.

I really don’t know what I can do now, I woke up the device, reinitialized it, healed it, all without any success.

Please, I include here my logfile from all these unsuccessful tries. Can someone find the reason why I can’t include the remote? The device has the node 37.

zwave.pdf (975.7 KB)

chris · July 26, 2016, 7:31pm

Please provide the log as a text file - I can’t process a PDF - sorry.

SteMo · July 27, 2016, 3:33pm

ok, but it’s a long one. Therefore I attched the pdf. Unfortunately I can’t attach a textfile here and have convertet it into xml. You cab change the .xml against the .log

zwave.xml (793.5 KB)

chris · July 27, 2016, 3:53pm

Thanks - that’s fine. 800k is tiny compared to many logs I have the “pleasure” to look at

chris · July 27, 2016, 3:58pm

Can you please remind me of what’s not working and also confirm it’s node 37 I need to look at?

Assuming it is node 37, then from the log it looks ok from a first look anyway. I can see the initialisation of the node, and that’s all looking ok. The device isn’t in the database, but otherwise it initialises and I guess it’s written a node37.xml file?

Can you attach the node37.xml file if there is one please?

SteMo · July 27, 2016, 5:12pm

It’s the node 37. I see it in HABmin, but without any content. All the chapters like Configuration parameters, Association Groups, etc. are empty.

Here the node37.xml:

<node>
  <deviceClass>
    <basicDeviceClass>CONTROLLER</basicDeviceClass>
    <genericDeviceClass>REMOTE_CONTROLLER</genericDeviceClass>
    <specificDeviceClass>SIMPLE_REMOTE_CONTROLLER</specificDeviceClass>
  </deviceClass>
  <homeId>0xf419aebf</homeId>
  <nodeId>37</nodeId>
  <version>4</version>
  <manufacturer>0x115</manufacturer>
  <deviceId>0x103</deviceId>
  <deviceType>0x100</deviceType>
  <listening>false</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>false</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <nodeInformationFrame/>
  <supportedCommandClasses>
    <entry>
      <commandClass>MULTI_CMD</commandClass>
      <multiCommandCommandClass>
        <version>1</version>
        <instances>1</instances>
      </multiCommandCommandClass>
    </entry>
    <entry>
      <commandClass>NO_OPERATION</commandClass>
      <noOperationCommandClass>
        <version>1</version>
        <instances>1</instances>
      </noOperationCommandClass>
    </entry>
    <entry>
      <commandClass>BATTERY</commandClass>
      <batteryCommandClass>
        <version>1</version>
        <instances>1</instances>
        <batteryLevel>96</batteryLevel>
        <batteryLow>false</batteryLow>
        <isGetSupported>true</isGetSupported>
      </batteryCommandClass>
    </entry>
    <entry>
      <commandClass>CENTRAL_SCENE</commandClass>
      <centralSceneCommandClass>

chris · July 27, 2016, 5:26pm

That simply means that it’s not in the database. So I think it’s working fine and you should be able to use it even though the database isn’t included.

chris · July 27, 2016, 5:28pm

Unfortunately only half the file is provided. If you can provide the full file I’ll add this into the database, but someone will need to add any configuration entries - it would be great if you could do this? .

SteMo · July 27, 2016, 6:18pm

Maybe only a misunderstanding, but what do you mean with “only the half” That’s the whole xml file.Or do you mean the missing entries?
I can include something but you should explain how to do it respectively what I shall include. Sorry, I’ve never done this before.

chris · July 27, 2016, 6:24pm

No - it only seems to be half the file - well, I say half - I mean it’s not complete. It’s is not a correctly finished XML file as the different elements are not closed (eg there is no </node> on the end of the file). If this is the full file, exactly as you see if on the drive, then something is very wrong somewhere, but I’ve never seen the binding write a corrupt file like this. My guess is a cut and paste problem?

SteMo · July 27, 2016, 8:32pm

You are right. Sorry. I tried it with Putty but it seems that this was nor the right way.
Here the complete file:

node37.xml (4.5 KB)

chris · July 27, 2016, 8:54pm

Great - thanks.

I’ve added this to the database here. We will need to find the PDF for the manual and upload that, and then add the configuration parameters and association groups. This will need to be typed in by hand…

As I said above though, if you’re using this in OH1, you should be abel to use the device now even without configuration etc (unless of course you need to change the default configuration).

SteMo · July 28, 2016, 7:54am

Here the manual.
I will check whether the device runs without configuration.

Manual_KFOB_POPP-C_En.pdf (968.0 KB)

SteMo · July 30, 2016, 3:03pm

Hey Chris, how to proceed. Do you need anything from my side?

chris · July 30, 2016, 3:05pm

No - it should be all done. Just update to the latest binding and hopefully it will be discovered ok.