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

Hi I bought a "Aqara Smart Wall Switch H1 EU (With Neutral, Single Rocker) (WS-EUK03)" as it fitted a specific need. I tried a few drivers and the Aqara specific ones didn't work - was throwing exceptions off (below) when I tried to use the "Zigbee - Aqara Wall Switch v1.0.1.1208b" driver.

But the good news is that it seems to work OK with the generic driver "Zigbee - Generic Switch (with Presence) v1.0.1.1123b". I get two child devices (I have the single switch model) but that's OK I just ignore the second child. All I really want is the switch state on/off and that works fine.

Awesome work Markus thanks!

Exception with Aqara specific driver: "Unknown model (lumi.switch.n1aeu1) - PLEASE REPORT THIS LOG TO THE DEV - description:read attr - raw: 323D0100002E050042126C756D692E7377697463682E6E3161657531, dni: 323D, endpoint: 01, cluster: 0000, size: 2E, attrId: 0005, encoding: 42, command: 01, value: 126C756D692E7377697463682E6E3161657531 | parseMap:[raw:323D0100002E050042126C756D692E7377697463682E6E3161657531, dni:323D, endpoint:01, cluster:0000, size:2E, attrId:0005, encoding:42, command:01, value:lumi.switch.n1aeu1, clusterInt:0, attrInt:5]"

Hi,

I have come back to looking at these drivers again, as I have switched to the new C8 Hub and I noticed some regular log warning, from one of my 2 gang no neutral aqara wall switches.

In fact I had this warning before, but only now I am getting around dealing with it.

So I am using this driver:
Zigbee - Aqara Wall Switch
/**

I have replied to your message, because I did indeed make some modifications to Markus' original drivers, in order to make it work with some wall switch models, that were not supported. I don't know much about driver programming, but this kind of modification is quite straight forward. Only a few lines have to be copied, with the new model number like "lumi.switch.l2aeu1", like in this case. In some cases the button numbering is a bit weird and it takes some trial and error to figure this out. But nothing major has to be modified in the code to make it work.

I could send my current driver code, so you could update your GitHub collection. I can see you have created new versions 2.0x. I wonder if you figure out the changes I made easily or if I need to guide you. It seems you added some US models, so you probably know where to look.

Could be great if you could include my modifications in your code, so I can use the "official" driver again and get updates in the future.....:slight_smile:

...anyhow, concerning that warning, it says this:
Unhandled Event PLEASE REPORT TO DEV - description:catchall: 0000 0005 00 00 0040 00 845D 00 00 0000 00 00 EB0000 | msgMap:[raw:catchall: 0000 0005 00 00 0040 00 845D 00 00 0000 00 00 EB0000, profileId:0000, clusterId:0005, clusterInt:5, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:845D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[EB, 00, 00]]

I seems most of the data just says "00"
The first 2 digits in the [] only count upwards by +1 every 10 seconds. The message is generated every 10 seconds.
If I press a button or reinitalize, the message stops for about a minute before it starts sending again.
The switches that are currently on have a red LED blinking. It also stops, when the message stops.

This is the only device doing this. However, the other ones I have are not no neutral models, display either a "not present" status (even if they work) or are using the aqara plug/outlet driver (which should not work but is...). So comparison is difficult... This might in fact be the only exact same model with the same driver I have...

Firmware: 115F-0C18-00000E0B

I tried to understand the driver code to figure out what could be going on but it is not obvious for me how the message is created. I can tell I get into some default case at some point, but I am not sure why none of the other cases in the code are applicable..

Hi, I could probably make it work. I have, amongst others, added the lumi.switch.n2aeu1 model to the driver. If kkossev is willing to add my modifications to his version of the driver, I can make sure I add your model before I send him my code. However, I don't have that specific model, so you might want to help us out by testing it.

1 question though: you say you use driver version Zigbee - Aqara Wall Switch v1.0.1.1208b, where did you find this? It's not in the collection linked by kkossev in the message above...

Hi @andre-berlin ,

Yes, please send me in a DM your mods, I can compare and merge the additions to the forked driver in GitHub.