Aquara Smart Knob Switch H1

[Adam-Langley]

Device

• Product name: Aquara Smart Knob Switch H1 (wireless version).
• Manufacturer: LUMI
• Model identifier: lumi.remote.rkba01
• SKU: ZNXNKG02LM
• Device type : Please remove all unrelated device types.
  • Basic
  • Identify
  • Power Configuration
  • Lumi Specific
  • Multistate Input (Basic)
  • Identify

Screenshots

Basic

Identify

Power Configuration

Lumi Specific

Multistate Input (Basic)

OTAU

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[Adam-Langley]

Ping - still relevant

Actually - it makes sense to exclude "device-request" items from the "auto stale" GitHub action...

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[Adam-Langley]

Ping - still relevant

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[github-actions]

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

[theboxer]

@Adam-Langley does this switch work with deconz/phoscon? I'm about to purchase one...

[Adam-Langley]

Hi @theboxer - last I checked, no it didn’t. That was quite a while ago.
I got so frustrated with the shortcomings of Phoscon, and the fragmented UI experience in Home Assistant, I moved to z2m and it’s been a million times better in many ways. The knob works on z2m.

In fact, an unrelated thing - but huge reason to move…
In Phoscon, if a connection to a device ever failed, and the only way to get it to respond is to re/add it, you lose everything related to that device.
Z2m is HEAPS better here.
got an unresponsive device?
Hit the “add device” button in Z2m, force the device into discovery mode, and the connection is healed… no settings lost.

That alone I would have moved for.

If you’re using Phoscon standalone, or integrated with HomeAssistant - switch to HomeAssantant+Zigbee2Mqtt - you’ll never look back.

[theboxer]

@Adam-Langley I'm actually not using home assistant, but a homebridge and exposing it to the home app (apple). By z2m you mean this: https://www.zigbee2mqtt.io/?

[Adam-Langley]

Hi @theboxer - yes that's right.

Sounds like you're in a similar boat to what I was when I started.
I thought I could get away with doing the minimum outside of Apple Home - and "use the power of apple home" to set up my household.
I couldnt have been more wrong.
Apple Home is just a toy - you will hit it's limitations (and bugs) very quickly, and be hating it.

What I do now, is load everything (except Apple HSV devices... that's not a great story yet) into HA, then "expose" just the devices you want to Apple.
That way Apple stays clean, and all your more complex and powerful configurations stay inside of HA.

It's best to just treat Apple Home as a simple dashboard for you really commonly used things, lights, door locks, security cameras (if you have HSV) etc.

When you first look into it, you'll think - "this is a lot of different components, for what I used to do with 1, or 2... too much hassle?"
I urge you to give it a try, and you'll see, once you've installed it, you're done. It works like a dream. HomeAssistant ("HA") releases updates (applied automatically if you like), almost every few days - so, they're so incredibly active, it's awesome.
Just follow the instructions. You'll be installing

1. Home Assistant (the environment)
2. Zigbee2Mqttt (the add on which talks to your zigbee hardware, and then passes the zigbee messages to/from the next component...)
3. An MQTT broker - probably just the built-in one called "Mosquitto". MQTT is a messaging system - think of it like a highway system, it connects things which publish messages, to things which want to listen to messages... It's how your zigbee events will eventually find their way into HomeAssistant

Looking at the list above... where's the Phoscon components?? Yep - they're gone. No need for them. Zigbee2Mqtt is compatible with the dresden devices.

Can I ask, what is your installation platform?
For example, I'm doing everything above with a Pi4 + RaspBee II.
But you could equally be running on a workstation+Conbee or such...

[theboxer]

@Adam-Langley I have Rpi4 + Conbee2. I'm just configuring the docker container and going to try it :) Thank you for the hint! btw. I'm on deCONZ's discord if you wanna chat more about the setup.

[Mimiix]

Hi @theboxer - yes that's right.

When you first look into it, you'll think - "this is a lot of different components, for what I used to do with 1, or 2... too much hassle?" I urge you to give it a try, and you'll see, once you've installed it, you're done. It works like a dream. HomeAssistant ("HA") releases updates (applied automatically if you like), almost every few days - so, they're so incredibly active, it's awesome. Just follow the instructions. You'll be installing

1. Home Assistant (the environment)
2. Zigbee2Mqttt (the add on which talks to your zigbee hardware, and then passes the zigbee messages to/from the next component...)
3. An MQTT broker - probably just the built-in one called "Mosquitto". MQTT is a messaging system - think of it like a highway system, it connects things which publish messages, to things which want to listen to messages... It's how your zigbee events will eventually find their way into HomeAssistant

Looking at the list above... where's the Phoscon components?? Yep - they're gone. No need for them. Zigbee2Mqtt is compatible with the dresden devices.

Can I ask, what is your installation platform? For example, I'm doing everything above with a Pi4 + RaspBee II. But you could equally be running on a workstation+Conbee or such...

Hey guys, I'm all for helping each other, but we are going a bit off topic now. May i suggest you reach out to each other through discord or forums?

[Adam-Langley]

Hey @Mimiix - sure thing no prob - was just about to do that just didnt want to jump the gun.
@theboxer sure thing - I'll look for you now.

[Smanar]

In fact, an unrelated thing - but huge reason to move… In Phoscon, if a connection to a device ever failed, and the only way to get it to respond is to re/add it, you lose everything related to that device. Z2m is HEAPS better here. got an unresponsive device? Hit the “add device” button in Z2m, force the device into discovery mode, and the connection is healed… no settings lost.

It's same in phoscon, you just need to DON'T delete the device, and make the same procedure, all will be invisible.

[saxn-paule]

I bought two of those devices but I'm not able to pair them via Phoscon. What has to be done to make it work?

[xADDRx]

HI,
any Solution here? Have the Same Problem

[xADDRx]

Has anyone got it working yet?

[sadpixel]

I also have this device and would love for it to work with DeCONZ. Happy to provide any information that may be needed, though it looks like the OP already added the required screenshots...

[sadpixel]

Dear @Mimiix, can we please get this re-opened? I'll try to put together a test DDF based on the one for the standard Aqara H1-series wireless switch (lumi.remote.b28ac1 aka WRS-R02), but I'll probably need some help with the Multistage Input cluster (0012)...

[Mimiix]

Happy to re open. @Smanar would this be possible with DDF ?

[Smanar]

Honnestly IDK, this device need lot of work.

• It seem it need a special request on inclusion.
• The Lumi specific cluster give a payload with angle/vitesse/speed, like for all rotating switch, not easy to convert in X00Y event. Need to use special field.

The problem will be not the 0x0012 cluster, on this one you will just have some value according to action.

Can make try, make a basic DDF, without buttonmap part. use the device and look at return on logs to make the buttonmap file.

And I m not sure the "special request" can be automatic :

        {
          "name": "config/devicemode",
          "refresh.interval": 3000,
          "parse": {
            "at": "0x0009",
            "cl": "0xfcc0",
            "ep": 1,
            "eval": "if (Attr.val == 1) { Item.val = 'compatibility' } else if (Attr.val == 2) { Item.val = 'zigbee' } else { Item.val = 'unknown' }",
            "fn": "zcl:attr",
            "mf": "0x115f"
          },
          "read": {
            "at": "0x0009",
            "cl": "0xfcc0",
            "ep": 1,
            "fn": "zcl:attr",
            "mf": "0x115f"
          },
          "write": {
            "at": "0x0009",
            "cl": "0xfcc0",
            "dt": "0x20",
            "ep": 1,
            "eval": "if (Item.val == 'compatibility') { 1 } else if (Item.val == 'zigbee') { 2 }",
            "fn": "zcl:attr",
            "mf": "0x115f",
            "state.timeout": 2
          },
          "values": [
            ["\"compatibility\"", "Default mode for Xiaomi devices"],
            ["\"zigbee\"", "Closer to zigbee standard"] 
          ],
          "default": "compatibility"
        },

On my side, this kind of code have never worked automaticaly, but it seem it work for other devices.

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[github-actions]

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.