Xiaomi Opple 6 button remote

[scottbaker007]

Hi, I was able to pair 1 x 6 button Opple remote and I'm very happy with it. I'm trying to pair a second and having no luck. It pairs but doesn't register any clicks and blue LED doesn't lights up like the one that's working. Anybody got any ideas? I've tried replacing the battery, same result. Is their a trick to get it to pair successfully?

When the remote is pair the first time I get the following:

ID: 0F37
Manufacturer: LUMI
Product Name:
Model Number: lumi.remote.b686opcn01
deviceTypeId: 876
manufacturer : LUMI
idAsInt : 1
inClusters : 0000,0003,0001
endpointId : 01
profileId : 0104
application : 11
outClusters : 0003,0006,0008,0300
initialized : true
model : lumi.remote.b686opcn01
stage : 4
manufacturer :
idAsInt : 2
inClusters : 0003
endpointId : 02
profileId : 0104
application :
outClusters : 0006,0003
initialized : true
model :
stage : 4
manufacturer :
idAsInt : 3
inClusters : 0012,0003
endpointId : 03
profileId : 0104
application :
outClusters : 0006
initialized : true
model :
stage : 4
manufacturer :
idAsInt : 4
inClusters : 0012,0003
endpointId : 04
profileId : 0104
application :
outClusters : 0006
initialized : true
model :
stage : 4
manufacturer :
idAsInt :
inClusters :
endpointId : 05
profileId :
application :
outClusters :
initialized : false
model :
stage : 0
manufacturer :
idAsInt : 6
inClusters :
endpointId : 06
profileId :
application :
outClusters :
initialized : false
model :
stage : 0

If I pair a second time the presence changes but the button presses are still not registered and blue LED still not lighting up:

[markus]

@scottbaker007

Is their a trick to get it to pair successfully?

Check the logs while you're pairing. They should tell you to push a button, just avoid button 1 on the device since that could turn on/off all your Zigbee lights as long as the configuration has not been sent fully yet. If you still have issues, post your pairing logs.

[scottbaker007]

Thank you for your help markus, I have tried that and no luck.

Below are the logs when pairing after removing the device from Hubitat: (Note that I don't get any message to press a button)

Below are the logs when re-pairing: (Previously Joined Device) (I get the message about pressing a button and I have done that)

sys:12020-10-23 07:04:47.293 pm infoZigbee Discovery Stopped

dev:4332020-10-23 07:04:31.328 pm infoFront Door: Porch & Garage Light: Motion temperature is 17.13°C

sys:12020-10-23 07:04:12.865 pm infoZigbee Discovery Running

sys:12020-10-23 07:04:12.777 pm infoZigbee Discovery Stopped

dev:11022020-10-23 07:03:58.562 pm infomsgMap: [raw:0F5E01000012040042044C554D49, dni:0F5E, endpoint:01, cluster:0000, size:12, attrId:0004, encoding:42, command:01, value:LUMI, clusterInt:0, attrInt:4]

dev:11022020-10-23 07:03:58.480 pm infomsgMap: [raw:0F5E01000012040042044C554D49, dni:0F5E, endpoint:01, cluster:0000, size:12, attrId:0004, encoding:42, command:01, value:LUMI, clusterInt:0, attrInt:4]

dev:11022020-10-23 07:03:58.392 pm infoRecovery feature ENABLED

dev:11022020-10-23 07:03:58.360 pm infoButton settings MIGHT be set correctly for your Opple Remote! Try them by pushing a button!

dev:11022020-10-23 07:03:58.355 pm infomsgMap: [raw:catchall: 0104 FCC0 01 01 0040 00 0F5E 00 01 115F 04 01 00, profileId:0104, clusterId:FCC0, clusterInt:64704, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0F5E, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:115F, command:04, direction:01, data:[00]]

dev:11022020-10-23 07:03:58.315 pm infoButton settings MIGHT be set correctly for your Opple Remote! Try them by pushing a button!

dev:11022020-10-23 07:03:58.307 pm infomsgMap: [raw:catchall: 0104 FCC0 01 01 0040 00 0F5E 00 01 115F 04 01 00, profileId:0104, clusterId:FCC0, clusterInt:64704, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0F5E, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:115F, command:04, direction:01, data:[00]]

dev:11022020-10-23 07:03:58.271 pm infogetDriverVersion() = v0.8.1.0830

dev:11022020-10-23 07:03:58.249 pm infoRecovery feature ENABLED

dev:11022020-10-23 07:03:58.175 pm infoButton settings MIGHT be set correctly for your Opple Remote! Try them by pushing a button!

dev:11022020-10-23 07:03:58.171 pm infomsgMap: [raw:catchall: 0104 FCC0 01 01 0040 00 0F5E 00 01 115F 04 01 00, profileId:0104, clusterId:FCC0, clusterInt:64704, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0F5E, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:115F, command:04, direction:01, data:[00]]

dev:11022020-10-23 07:03:58.165 pm infogetDriverVersion() = v0.8.1.0830

dev:11022020-10-23 07:03:58.140 pm infoinitialize()

dev:11022020-10-23 07:03:58.125 pm infomsgMap: [raw:0F5E0100000A01002011, dni:0F5E, endpoint:01, cluster:0000, size:0A, attrId:0001, encoding:20, command:01, value:11, clusterInt:0, attrInt:1, valueParsed:17]

dev:11022020-10-23 07:03:58.116 pm infomsgMap: [raw:0F5E01000036050042166C756D692E72656D6F74652E623638366F70636E3031, dni:0F5E, endpoint:01, cluster:0000, size:36, attrId:0005, encoding:42, command:01, value:lumi.remote.b686opcn01, clusterInt:0, attrInt:5]

dev:11022020-10-23 07:03:57.621 pm infoNo VALID lastCheckin event available! This should be resolved by itself within 1 or 2 hours and is perfectly NORMAL as long as the same device don't get this multiple times per day...

dev:11022020-10-23 07:03:57.570 pm infoSending init command for Opple Remote...

dev:11022020-10-23 07:03:57.566 pm infomsgMap: [raw:catchall: 0000 0013 00 00 0040 00 0F5E 00 00 0000 00 00 D35E0FC775793CDF8CCF0484, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:0F5E, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[D3, 5E, 0F, C7, 75, 79, 3C, DF, 8C, CF, 04, 84]]

sys:12020-10-23 07:03:57.006 pm infoFound Previously Joined Zigbee Device Opple Button 1

sys:12020-10-23 07:03:47.275 pm infoZigbee Discovery Running

[markus]

@scottbaker007 you're not getting the expected replies. Have you tried resetting the button? I think it's done by holding the button on the back for more than 12 seconds and it should then blink 3 times rapidly. Once released you should get one blink.

[scottbaker007]

Thanks again @markus yes also just tried reseting again still no joy. Maybe this one is faulty? When holding down the reset button, the LED flashs 3x quickly every 5 seconds. No matter how long I hold it down for past 5 seconds 10, 15, 20 I get the sam behaviour when releasing it will flash 9 times, 1 second apart followed by a 10th flash which stay on a little bit longer. So it appears the resets maybe not working as it should.

The one that's working is awesome so thank you for creating the driver. I've got 2 more on order

I'm willing to trying any other suggestions, but also understand if you've run out of ideas.

[markus]

@scottbaker007

So it appears the resets maybe not working as it should.

Yes, that doesn't sound right. I just tried on one of mine. As you say, holding for 5, 10 or 15 seconds results in 3 quick flashes. Releasing after that I get one flash then a pause followed by two quick flashes. It might be worth trying to replace the battery. There's a guide here:

Xiaomi Opple 6 button remote

Received my 6 button Xiaomi Zigbee 3.0 remote. It's been an odd experience so far, from receiving my package from Canada Post on Sunday (Canada Post doesn't normally deliver on the weekend at all), to the seemingly dead on arrival device, with no instructions on how to change the battery, and it's strange pairing result. Despite all this, I will say that its physical design is very nice. The branding is very subtle, and the device feels very solid. I learned some important facts about this devi…

That resolved it for another user:

[Deprecated] Xiaomi / Aqara / Opple Drivers with Presence!

@markus Yesterday I spend several hours trying to get the 6 button Opple (WXCJKG13LM) to work. There are three of them. I'm sure I'm doing something wrong but what. The first one took MANY times, say 10 - 12, to pair and it paired correct in the end. It is working like it should. The second one paired as a "device" only. After repeating the pairing proces after deleting the device it suddenly paired and looked the same as the first one that paired correct. It only doesn't react on the buttons. S…

[scottbaker007]

I'll try this tomorrow and let you know how it goes. Thanks, Scott

[scottbaker007]

It's working Thank you so much @markus after reading the the link you provide this is what I did:

1. Removed the battery and left it out over night
2. Replaced the battery the following day 1m of my Hubitat,
3. Within 1m of my Hubitat pair by holding the reset button for 5 seconds while watching the logs and pressing a button when suggested in the logs.

If others have a similar issue I would suggest trying to pair within 1m of their Hubitat first as removing the battery is a bit of stuffing around and may not be necessary. But if that doesn't work then go down removing the battery path.

Note: I was going to restart my hub before I tried to pair but forgot and it worked anyway.

[jeff12]

[quote="[Release] Xiaomi / Aqara / Opple Drivers with Presence!, post:542, topic:41537"]
@markus
[/quote]

I have read every thread I could find on this one. No matter I try including removing the battery and a full reset of the device (button for 12 seconds) I can only get this to be recognized as a water sensor.

@markus Do you see anything in the logs that could help steer me in the right direction?

dev:6182021-01-09 04:12:18.610 am infomsgMap: [raw:catchall: 0000 0013 00 00 0040 00 D55C 00 00 0000 00 00 D75CD508CC7D3CDF8CCF0484, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:D55C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[D7, 5C, D5, 08, CC, 7D, 3C, DF, 8C, CF, 04, 84]]

dev:6182021-01-09 04:11:48.754 am warnUnhandled Event PLEASE REPORT TO DEV - description:catchall: 0104 0008 01 FF 0040 00 D55C 01 00 0000 03 00 0000 | msgMap:[raw:catchall: 0104 0008 01 FF 0040 00 D55C 01 00 0000 03 00 0000, profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:01, destinationEndpoint:FF, options:0040, messageType:00, dni:D55C, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:03, direction:00, data:[00, 00]]

dev:6182021-01-09 04:11:48.750 am infomsgMap: [raw:catchall: 0104 0008 01 FF 0040 00 D55C 01 00 0000 03 00 0000, profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:01, destinationEndpoint:FF, options:0040, messageType:00, dni:D55C, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:03, direction:00, data:[00, 00]]

dev:6182021-01-09 04:11:48.520 am warnUnhandled Event PLEASE REPORT TO DEV - description:catchall: 0104 0008 01 FF 0040 00 D55C 01 00 0000 01 00 000F0000 | msgMap:[raw:catchall: 0104 0008 01 FF 0040 00 D55C 01 00 0000 01 00 000F0000, profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:01, destinationEndpoint:FF, options:0040, messageType:00, dni:D55C, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[00, 0F, 00, 00]]

dev:6182021-01-09 04:11:48.515 am infomsgMap: [raw:catchall: 0104 0008 01 FF 0040 00 D55C 01 00 0000 01 00 000F0000, profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:01, destinationEndpoint:FF, options:0040, messageType:00, dni:D55C, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[00, 0F, 00, 00]]

dev:6182021-01-09 04:11:45.694 am warnUnhandled Event PLEASE REPORT TO DEV - description:catchall: 0104 0008 01 FF 0040 00 D55C 01 00 0000 02 00 005507000000 | msgMap:[raw:catchall: 0104 0008 01 FF 0040 00 D55C 01 00 0000 02 00 005507000000, profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:01, destinationEndpoint:FF, options:0040, messageType:00, dni:D55C, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:00, data:[00, 55, 07, 00, 00, 00]]

dev:6182021-01-09 04:11:45.689 am infomsgMap: [raw:catchall: 0104 0008 01 FF 0040 00 D55C 01 00 0000 02 00 005507000000, profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:01, destinationEndpoint:FF, options:0040, messageType:00, dni:D55C, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:00, data:[00, 55, 07, 00, 00, 00]]

dev:6182021-01-09 04:10:53.243 am infomsgMap: [raw:catchall: 0000 0013 00 00 0040 00 D55C 00 00 0000 00 00 D35CD508CC7D3CDF8CCF0484, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:D55C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[D3, 5C, D5, 08, CC, 7D, 3C, DF, 8C, CF, 04, 84]]

dev:6182021-01-09 04:10:38.165 am infomsgMap: [raw:catchall: 0000 0013 00 00 0040 00 16A5 00 00 0000 00 00 D3A51608CC7D3CDF8CCF0484, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:16A5, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[D3, A5, 16, 08, CC, 7D, 3C, DF, 8C, CF, 04, 84]]

dev:6182021-01-09 04:10:06.015 am infomsgMap: [raw:482E01000012040042044C554D49, dni:482E, endpoint:01, cluster:0000, size:12, attrId:0004, encoding:42, command:01, value:LUMI, clusterInt:0, attrInt:4]

dev:6182021-01-09 04:10:05.646 am infoNo VALID lastCheckin event available! This should be resolved by itself within 1 or 2 hours and is perfectly NORMAL as long as the same device don't get this multiple times per day...

dev:6182021-01-09 04:10:05.630 am warnUnhandled Event PLEASE REPORT TO DEV - description:catchall: 0000 8005 00 00 0040 00 482E 00 00 0000 00 00 FD002E480101 | msgMap:[raw:catchall: 0000 8005 00 00 0040 00 482E 00 00 0000 00 00 FD002E480101, profileId:0000, clusterId:8005, clusterInt:32773, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:482E, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[FD, 00, 2E, 48, 01, 01]]

dev:6182021-01-09 04:10:05.621 am infomsgMap: [raw:catchall: 0000 8005 00 00 0040 00 482E 00 00 0000 00 00 FD002E480101, profileId:0000, clusterId:8005, clusterInt:32773, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:482E, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[FD, 00, 2E, 48, 01, 01]]

dev:6182021-01-09 04:10:04.768 am infoNo VALID lastCheckin event available! This should be resolved by itself within 1 or 2 hours and is perfectly NORMAL as long as the same device don't get this multiple times per day...

dev:6182021-01-09 04:10:04.742 am infoRecovery feature ENABLED

dev:6182021-01-09 04:10:04.673 am infogetDriverVersion() = v1.0.1.1123

dev:6182021-01-09 04:10:04.667 am infoinstalled()

[SmartHomePrimer]

It might pair as one device, but you simply change it to the correct device in the driver settings page. I'm not familiar with the driver, since I still use mine directly joined to a Xiaomi Aqara Hub that I sync back to HE via HomeKit/Homebridge, but there should be a configure button.

After changing driver type to the community driver, click Save and then click Configure. This sends driver specific data to the device. If the driver does not have a configure button, set the correct driver, click save and then without removing the. device from Hubitat, pair it again.
This will force the device to be discovered again with the correct driver in place.

However, I recall there were special instructions to watch the logs when pairing (I don't recall the details of that, but they're in this thread). As I remember, it was necessary to follow the pairing procedure directly so the device doesn't trigger every single Zigbee device on your network with a single button push.

[jeff12]

EUREKA! it just started working and I have no idea why other than ask for help. Thanks for the reply @SmartHomePrimer @markus never mind sir thank you anyway

[Rxich]

It's all magic, or that's how it seems most times. I had the hardest time pairing my first one. It works great, and the capabilities are incredible.
Have fun.