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

stu.edwards · October 1, 2020, 12:57am

Hi,

I have a couple of these Xiamoi /Aqara Smart Plug/Wall Outlets. I'm unsure of the exact model number (its in Chinese) however this is the link to product and driver listed at the start of this thread works great!

I couldn't find any information online but does anyone know if these switches act as Zigbee repeaters?

Possibly a dumb question but assuming they do (and for zigbee repeaters in general) does the switch need to be ON or is just plugged in enough?

Cheers,
Stu

markus · October 1, 2020, 1:09am

They do act as repeaters.

They always act as repeaters, a device which would stop repeating because they are in off would cause some serious problems in the mesh. Just like when you have repeating bulbs which are turned off by cutting the power to them from a wall switch.

I have noticed they can possibly cause issues in a mesh, but have not pinned it down since I have just stopped using mine once I switched to smart wall outlets instead. They may very well work great for you though

I know I have unanswered posts above, I'll get to that soon...

AnubizDK · October 5, 2020, 5:40pm

Hi @markus

The 2-button Opple works great, but i'm experiencing a weird error in the log when i assign an action to double-pressing button 1.
In this case i've made a Simple Button Controller rule, that sets a shade to 17% closed:

When i press the buttons (both single and double), the button log show the events correctly (i think):

dev:1092020-10-05 19:23:34.748 infoButton 1 was pushed 2 time(s) (push event: 3)

dev:1092020-10-05 19:23:34.744 infobuttonDoubleTapped(button=1)

dev:1092020-10-05 19:23:34.742 infoButton 1 was double tapped

dev:1092020-10-05 19:23:34.736 infomsgMap: [raw:AD610100120A5500210200, dni:AD61, endpoint:01, cluster:0012, size:0A, attrId:0055, encoding:21, command:0A, value:0002, clusterInt:18, attrInt:85, valueParsed:2]

dev:1092020-10-05 19:23:30.460 infoButton 2 was pushed 2 time(s) (push event: 4)

dev:1092020-10-05 19:23:30.457 infobuttonDoubleTapped(button=2)

dev:1092020-10-05 19:23:30.454 infoButton 2 was double tapped

dev:1092020-10-05 19:23:30.448 infomsgMap: [raw:AD610200120A5500210200, dni:AD61, endpoint:02, cluster:0012, size:0A, attrId:0055, encoding:21, command:0A, value:0002, clusterInt:18, attrInt:85, valueParsed:2]

dev:1092020-10-05 19:23:26.903 infobuttonPushed(button=2)

dev:1092020-10-05 19:23:26.901 infoButton 2 was pushed 1 time(s) (push event: 2)

dev:1092020-10-05 19:23:26.896 infomsgMap: [raw:AD610200120A5500210100, dni:AD61, endpoint:02, cluster:0012, size:0A, attrId:0055, encoding:21, command:0A, value:0001, clusterInt:18, attrInt:85, valueParsed:1]

dev:1092020-10-05 19:23:19.650 infobuttonPushed(button=1)

dev:1092020-10-05 19:23:19.647 infoButton 1 was pushed 1 time(s) (push event: 1)

dev:1092020-10-05 19:23:19.642 infomsgMap: [raw:AD610100120A5500210100, dni:AD61, endpoint:01, cluster:0012, size:0A, attrId:0055, encoding:21, command:0A, value:0001, clusterInt:18, attrInt:85, valueParsed:1]

But the log for the rule log shows the following error when i double-press button 1, and nothing happens with the shade:

app:1232020-10-05 19:22:09.575 errorjava.lang.NullPointerException: Cannot get property 'cancel' on null object on line 1775 (buttonHandler)

app:1232020-10-05 19:22:09.560 infoAction: Position Shades: Rullegardin to 17 for button 1 doubleTapped

app:1232020-10-05 19:22:06.417 infoAction: Raise Shades: Rullegardin for button 1 pushed

app:1232020-10-05 19:22:04.056 infoAction: Lower Shades: Rullegardin for button 2 pushed

--- Live Log Started, waiting for events ---

It mentions "line 1775 (buttonHandler) - does this refer to your driver..?

markus · October 5, 2020, 11:53pm

I can look at this some more when I have a computer again, but no, buttonHandler is not something in my drivers. For some reason you have a missing object. Is the rule correct? I suggest opening a new thread for this so that you can have the benefit of the whole community helping, here it will not be found by everyone.

AnubizDK · October 6, 2020, 7:23am

Ok - thanks.. I'm new here, so wasn't sure where to look for the source of error..

I did another test by deleting the rule from Button Controllers, and creating the rule in RM instead - now everything works fine..

Guess i'll just leave it like that..

markus · October 7, 2020, 12:43am

I'll add that model to the next release. As you discovered, yes, it's the device itself emitting those events. Not much to do about it.

No worries, I've just been without a computer for a bit, now I'm back though

Sebastien · October 7, 2020, 12:44am

Welcome back!

mraz.camren · October 7, 2020, 1:18am

Welcome back!

andy6 · October 7, 2020, 10:26am

Hi Chris

I also got a 26LM, limited knowledge of what i'm doing, but happy to help any way i can if we can get it working.

andy6 · October 7, 2020, 1:36pm

I have a 26LM reported as

Not getting anywhere

Am-Chris · October 7, 2020, 6:09pm

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

Danny88 · October 11, 2020, 4:05pm

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?

bobbles · October 11, 2020, 4:08pm

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

RikH · October 12, 2020, 12:13pm

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

RikH · October 12, 2020, 12:15pm

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

bbholthome · October 13, 2020, 8:31pm

@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.

Equis · October 13, 2020, 9:07pm

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.

boyanski · October 15, 2020, 9:33am

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.

N4IRS · October 15, 2020, 1:52pm

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!

jesusmanuel80 · October 15, 2020, 3:39pm

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.