[Edge] Driver for Aqara Switches and Remotes

@veonua Sure. Let me know what is needed from my end. Happy to help in testing this feature.

I’m sorry for upping, but has anyone encountered this? Everything else smartthings works fine and my switches work fine if added through the Aqara app, but via this driver, they have been rendered basically unusable.

I love how it works and it has saved me for the last several months (because I really need the H1 switches’ decoupled mode) but it’s absolutely not working now.

Any help would be greatly appreciated :slight_smile:

OK, understood.
Is possible tell me what file (github) driver, have this fields?
I could try to edit.
Thanks

tell me the full model name , better from the fingerprints

Although the driver has not been updated for a while, ST keeps updating their platform. This may result in some components becoming outdated. However, I haven’t come across many reports of broken integrations. Have you read a post on this forum about how to ensure a reliable Aqara/Xiaomi network?

Hey! Have read some of the threads, but quite likely I have missed something.
I am readding everything in ST today from scratch to see if something just went south at some point.

Hello,
Attached the details

Thanks

Manufacturer: LUMI
Model: lumi.switch.n2aeu1

should be supported with @veonua driver and @Mariano_Colmenarejo driver.

Yes It is, I was talking asking if consumption could work as well. Because here with 230v Europe, the consumption reported is wrong. One led bulb with 10w cannot report 90w in the app.
Thank you.

Send some logs from CLI to @veonua who developed the driver. I’m sure he can eerily fixed the power consumption displayed.

Just an update on my “constantly disconnecting issues” - they are only with my wired switches, my wireless switches are working fine consistently.

Moved one of the problematic switches to the Aqara App, has had no problems since.

The ones through Smartthings trigger their “Pressed” state fine, then after a couple of seconds go into blinking red-blue, then after a minute or so connect again fine. Eventually, after hours they completely disconnect and turn off.

You may have a newer firmware. The LED indication is on the device and I can’t find red-blue blinking in the manual. Aqara might disable non-supported hubs.

Firmware is 0.0.0_1411

Then it’s a red light flishes slowly? But just the blue light is on under? I don’t know, it does sound weird. I’ll upload a video of the blinking.

These are the switches that i have:

D1 Wall Switch (No Neutral, Triple Rocker)
lumi.switch.l3acn3

D1 Wall Switch (No Neutral, Double Rocker)
lumi.switch.b2lacn02

D1 Wall Switch (With Neutral, Double Rocker)
lumi.switch.b2nacn02

D1 Wall Switch (With Neutral, Triple Rocker)
lumi.switch.n3acn3

updated in v25

The new profile is applied to the newly added devices, I don’t have any 3-button devices, so there might be side effects.

@veonua thanks for merging the new fingerprint for the Mini Switch T1. I’m now able to select the driver in SmartThings, and pick actions for button presses. But when I press the button, the actions never trigger.

Do I need to update other files in order to detect these?
Maybe xiaomi-switch/src/configurations.lua ?

I recommend installing the SmartThings CLI and checking device mappings. Some devices may not send events to third-party hubs.

I have been running the switches for about a week. Seems ok for all of them including the triple rocker switch.

3 Likes

@veonua just a quick update, I noticed a few rare occasion on the triple rocker where the child switch is still supplying electricity to the lights even though on both app and physical button shows that the switch is off.
The affected switch is turned on and off by automation and rarely physically.

The sluggish routine performance is unrelated to the device profile( how the features are displayed and grouped in the ST app and how they exposed to 3rd party api) .

My primary worry is that certain settings or features might be lost post-update.