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

🚧 Developers Broken-code
524

Hello @markus would it be possible to add support for the 26LM switch in the beta driver version at least? This would enable the button presses to be captured through the logs, so that the main driver can then be updated to include the switch's functionality. I previously attempted to manually add the 26LM as a 'known' device in the beta driver, this allowed for the button presses to be captured in the log. However, when the switch the left for long periods of time without activity (say over night). The buttons are no longer responsive.

Supporting the 26LM through the driver would be greatly appreciated. As @andy6 says, we would be happy to help any way we can :slightly_smiling_face:

1 Like
525

Hello,

I’m trying to import URL from Aqara sensor MCCGQ11LM but it shows error

“ Metadata Error:Please check if you inadvertently pasted driver code into apps code window on line 30”

Can anyone help?

526

I suppose the first question to ask is are you posting in as a new driver or are you using the new app page.

1 Like
527

Hi @markus, today the ceiling light (XDD13LM) arrived. Got no success to pair it to the HE. This was written in the comments from a buyer:

Color: MX480 Logistics: Seller's Shipping Method

This lamp doesn't work with European version of aqara software. And Chinese version doesn't support connection because of servers in china. it is slow and unreliable. 26 Jul 2020 09:14

Helpful? Yes (0) No (0)

Seller’s Reply

How does the ceiling light MX480 (adjustable temperature) carry out distributed networking? 1. Power off the ceiling lamp that has not been added to the gateway three times continuously, the lamp flashes once and the color temperature changes, indicating that the lamp has been turned on distributed networking (if there is no such effect, please try again); 2. Long press wireless The reset button on the back of the scene switch for 5 seconds, until the indicator light flashes 3 times quickly, indicating that the wireless scene switch enters the network state; 3. Keep the wireless scene switch and the ceiling light as close as possible, when the ceiling light stops changing its color temperature and flashes 3 times, it means The ceiling lamp and the wireless scene switch are successfully networked. 26 Jul 2020 09:14

So I understand how to put it in pairing mode; turn it on, switch it 3 times off an on again and it gives a flash and starts changing the color. So far so good. In pairing mode I let the hub discover new devices but it didn't find anything. In the logs it only says Zigbee discovery running and exactly 1 minute later Zigbee discovery stopped. Nothing in between. Tried to pair it stand alone to to a WXCJKG13LM button and that succeeded immediately.

For fun tried to pair it with my Hue hub but also no luck.

What can I do now?

Br, Rik

528

Not sure why a lot is bold in that text. Tried to edit it to normal but no luck.

529

@markus there is a casting exception in the model DJT11LM vibration sensor driver.
It occurs when the Set open and Set closed position buttons are pressed on the driver page.

image
image2038×210 47.7 KB

530

Can a simulated button push be added to the button's device page? I imagine it would be similar to the "set as" buttons for the other devices.

531

Hi, Markus!
First, thanks for these drivers and your work

I have a european version of the outlet, which mostly works with your driver.
The info it reports is:

  • endpointId: 01
  • application: 16
  • softwareBuild:
  • driver: v0.8.1.0830
  • inClusters: 0000,0002,0003,0004,0005,0006,FCC0
  • outClusters: 000A,0019
  • model: lumi.plug.mmeu01
  • manufacturer: LUMI

Though it sometimes reports these two messages in the logs:

[warn] Unhandled Event PLEASE REPORT TO DEV - description:read attr - raw: B11201FCC082F700413D64100103281898392FDD643F953967580242963900E00D459739890D7C40052102009A201008211601072700000000000000000921070C0B20009B1001, dni: B112, endpoint: 01, cluster: FCC0, size: 82, attrId: 00F7, encoding: 41, command: 0A, value: 3D64100103281898392FDD643F953967580242963900E00D459739890D7C40052102009A201008211601072700000000000000000921070C0B20009B1001 | msgMap:[raw:B11201FCC082F700413D64100103281898392FDD643F953967580242963900E00D459739890D7C40052102009A201008211601072700000000000000000921070C0B20009B1001, dni:B112, endpoint:01, cluster:FCC0, size:82, attrId:00F7, encoding:41, command:0A, value:64100103281898392FDD643F953967580242963900E00D459739890D7C40052102009A201008211601072700000000000000000921070C0B20009B1001, clusterInt:64704, attrInt:247]

and

`

[warn] Unhandled Event PLEASE REPORT TO DEV - description:catchall: 0000 8032 00 00 0040 00 B112 00 00 0000 00 00 0000090107BA2404BA24AEC204AEC250BD0050BDBB9B002B4AB74B04B74BE3E000E3E02D35042D35 | msgMap:[raw:catchall: 0000 8032 00 00 0040 00 B112 00 00 0000 00 00 0000090107BA2404BA24AEC204AEC250BD0050BDBB9B002B4AB74B04B74BE3E000E3E02D35042D35, profileId:0000, clusterId:8032, clusterInt:32818, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B112, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00, 09, 01, 07, BA, 24, 04, BA, 24, AE, C2, 04, AE, C2, 50, BD, 00, 50, BD, BB, 9B, 00, 2B, 4A, B7, 4B, 04, B7, 4B, E3, E0, 00, E3, E0, 2D, 35, 04, 2D, 35]]`

As a side note, I've seen somewhere in Zigbee2MQTT that some of these plugs have the feature of keeping their state after power loss, which isn't on by default, but would be nice to have as a setting.

532

I bought a few of the leak detectors ( SJCGQ11LM) from Amazon Aqara Water Leak Sensor I installed the driver before I attempted to pair.

I had no problem pairing other then knowing how hard to press on the plastic top to activate the switch. Device paired first time. No problems getting data. Thanks!

1 Like
533

Aqara temperature sensor doesnt report temperature changes. This driver is not working for me, i had to install the other aqara driver from the other thread.

534

Will there be support for reading pressure from the above devices? The data is there, using @veeceeo driver, it works

535

Pressure readings are reported using @markus' driver. Can I suggest re-pairing your sensor close to the Hubitat (no need to first remove it)?

Untitled
Untitled925×335 38.4 KB

2 Likes
536

You are so right. Repairing did the trick. Tnx a lot

1 Like
537

From what I'm reading about this one it should pair and should even work with a standard zigbee bulb driver. You might have to pair it closer to the hub and do make sure you get that colour temperature change mentioned in the pairing instructions.

1 Like
538

Ok, I'll give it some more tries. Thanks man!

539

Ok, I tried everything but no result. Restarted hub, light as close as 30cm from hub which is the closest. The logs say Zigbee Discovery running and after a minute Zigbee Discovery stopped. Logs show nothing in between. Tried to put light in pairing mode before hub in discovery and during discovery mode. Nothing. Tried everything about 10 times. Closed hub down, waited 20 minutes and powered it again without result.

Quiet frustrating, any suggestions?

540

I don't have any of these products from Opple, not even sure they are sold here in China. Do you have any of the scene controllers from Opple? Could be worth seeing if you get that part working. Do you have the full manual? Even if it's in Chinese that would be useful. If you have a Zigbee sniffer that could be worth taking a look at to see what is being sent from the light.

541

Yes, they pair immediately.

Not anymore, Chinese only so threw it away I'm afraid.

I don't have one but willing to invest and experiment with it. Do you have any suggestions for one easy to use for a layman like me?

542

@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. Same for the third one, paired but not responding on buttons though they are present. Here is the data section for the working one:

  • endpointId: 01
  • application: 11
  • driver: v0.8.1.0830
  • model: lumi.remote.b686opcn01
  • physicalButtons: 6
  • manufacturer: LUMI

Here is number 2:

  • endpointId: 01
  • application: 11
  • driver: v0.8.1.0830
  • model: lumi.remote.b686opcn01
  • physicalButtons: 6
  • manufacturer: LUMI

And 3:

  • endpointId: 01
  • application: 11
  • driver: v0.8.1.0830
  • model: lumi.remote.b686opcn01
  • physicalButtons: 6
  • manufacturer: LUMI

All exact the same as you see. Here is the current state of the working one:

Current States

  • battery : 100
  • batteryLastReplaced : 2020-10-20 16:38:16
  • doubleTapped : 4
  • driver : v0.8.1.0830
  • held : 5
  • lastCheckin : 2020-10-21 09:00:24
  • lastHoldEpoch : 0
  • notPresentCounter : 0
  • numberOfButtons : 30
  • presence : present
  • pushed : 4
  • restoredCounter : 0
  • released : 5

And number 2:

Current States

  • batteryLastReplaced : 2020-10-21 07:39:52
  • doubleTapped : 0
  • driver : v0.8.1.0830
  • held : 0
  • lastCheckin : 2020-10-21 08:45:17
  • lastHoldEpoch : 0
  • notPresentCounter : 0
  • numberOfButtons : 30
  • presence : present
  • pushed : 0
  • restoredCounter : 1

And 3:

Current States

  • battery : 100
  • batteryLastReplaced : 2020-10-20 16:12:09
  • doubleTapped : 0
  • driver : v0.8.1.0830
  • held : 0
  • lastCheckin : 2020-10-21 08:44:14
  • lastHoldEpoch : 0
  • notPresentCounter : 0
  • numberOfButtons : 30
  • presence : present
  • pushed : 0
  • released : 1
  • restoredCounter : 0

What is going wrong here?? I also have a 4 button Opple which works like a charm but that one didn't pair easy either.

Edit: guess what, I opened the button like @SmartHomePrimer described here and removed the battery. Waited like 5 minutes and tried to pair the bare motherboard and it did. Immediately. Have to say I switched off the hub for half an hour as well before this attempt. Furthermore I held it next (like 10cm or 4") to the hub this time.

Edit 2: the last one now paired immediately as well without opening it. So my guess would be the shutdown of the hub for half an hour did the trick. Pity I didn't think about doing this step by step to make a more reproducible result. Keep learning...

Problem solved!

2 Likes
543

Hello,

I am so new into HE. I did successfully installed related drivers provided in this thread but i don't really have idea on to how to start the automation. Even i didn't see on/off switch for my WXKG03LM switch.

If somebody would very kind guide me how to start , i would really really appreciate...

Thank you.