Aeotec wall switch ZWA038 capability missing

🧰 Built-In Apps and Drivers Built-in Drivers
1

I just installed an Aeotec ZWA038. So far, I like it. However, there seems to be something missing in the built in driver. If I understand the documentation for the switch correctly, a double tap up or down should generate an event for the hub to react to. It seems these are intended to trigger scenes. However, I don't see anything in the driver that allows me to capture and react to those double taps.

Use case:
Right now I have it setup as a simple 3-way switch to control my lights in my room. But come Christmas, I plug in an Aeotec ZWA023 plug on the Christmas tree. I'd love to be able to double tap this switch and turn the tree on and off independent of the light that the switch is attached to. I thought that if the HE could capture the double tap on the switch (like it seems it should be able to), I could use that to trigger a rule.

Questions:

  1. Am I misunderstanding this capability? Looking on the Aeotec web site, it seems that there are some local control functions built into the switch if you have a capable device to program it. Is this double tap only available in that way?

  2. Is there a better driver to use out there than the canned Aeotec driver for the ZWA038? Is there one that does capture these events so that I can react to them?

2

Try my universal dimmer driver. I think that switch should support the features needed to scan and present all the settings. I could not tell from a quick search what z-wave chip they are using in it currently. There is possibly a setting you need to change to enabled the "scene" (button) presses.

Also if you don't mind, post the entire "Data" section from the bottom from the device page. I think one of the values there will let me figure out what chip/protocol it is using.

3

One way to tell: enable debug logging and do a double tap. Do you see any skipped/ignored Z-Wave data coming into the driver? Quite likely, this would be something like a CentralSceneNotification (from multi-taps), though some, likely mostly older, devices may do this differently. If so, this parsing could be added to the driver.

If so, also confirm what driver you are using.

4

Indeed there are skipped messages!!!

skip:CentralSceneNotification(keyAttributes:3, sceneNumber:2, sequenceNumber:7, slowRefresh:true)
skip:CentralSceneNotification(keyAttributes:3, sceneNumber:1, sequenceNumber:6, slowRefresh:true)

The driver is the "Aeotec Illimino Wall Switch" that is one of the built in Aeotec drivers.

Getting that capability to captures these would be really good.

5

Thanks! That looks standard and would be straightforward to add to the built-in driver (drivers? I assume the Switch and Dimmer hardware would be the same here...) in 2.4.0. The only thing you might want to confirm is which is a double tap up and which is a double tap down, since that is one thing manufacturers differ on.

6

There are both double tap and press/hold features. Here is what I've captured for output:

Double tap up:

parse:zw device: 17, command: 5B03, payload: 12 83 01 , isMulticast: false
skip:CentralSceneNotification(keyAttributes:3, sceneNumber:1, sequenceNumber:18, slowRefresh:true)

Double tap down:

parse:zw device: 17, command: 5B03, payload: 13 83 02 , isMulticast: false
skip:CentralSceneNotification(keyAttributes:3, sceneNumber:2, sequenceNumber:19, slowRefresh:true)

Tap/hold up:

parse:zw device: 17, command: 5B03, payload: 14 82 01 , isMulticast: false
skip:CentralSceneNotification(keyAttributes:2, sceneNumber:1, sequenceNumber:20, slowRefresh:true)
parse:zw device: 17, command: 5B03, payload: 15 81 01 , isMulticast: false
skip:CentralSceneNotification(keyAttributes:1, sceneNumber:1, sequenceNumber:21, slowRefresh:true)

Tap/hold down:

parse:zw device: 17, command: 5B03, payload: 16 82 02 , isMulticast: falseskip:CentralSceneNotification(keyAttributes:2, sceneNumber:2, sequenceNumber:22, slowRefresh:true)
parse:zw device: 17, command: 5B03, payload: 17 81 02 , isMulticast: false
skip:CentralSceneNotification(keyAttributes:1, sceneNumber:2, sequenceNumber:23, slowRefresh:true)

Note that I reversed the time order here from the logs, so the first event is on top, not on the on the bottom.

I'm certainly no z-wave expert, but I read this to mean up is scene 1, and down is scene 2. Key attribute 3 is a double tap, attribute 2 is a press/hold and attribute 1 is a release.

Note that a single tap (up/down) reports keyAttributes:0 on a centralscenenotification.

Up:

skip:CentralSceneNotification(keyAttributes:0, sceneNumber:1, sequenceNumber:24, slowRefresh:true)

Down:

skip:CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:25, slowRefresh:true)

7

Thanks for the like to your driver. I will have to play with that option too:

Here is the data section:

  • deviceId: 38
  • deviceType: 259
  • firmwareVersion: 1.4
  • hardwareVersion: 1
  • inClusters: 0x5E,0x25,0x70,0x5B,0x85,0x8E,0x59,0x55,0x86,0x72,0x5A,0x87,0x2B,0x2C,0x73,0x9F,0x6C,0x7A
  • manufacturer: 881
  • protocolVersion: 7.13
  • serialNumber: ##############
  • zwNodeInfo: D3 9C 00 04 10 00 5E 25 70 5B 85 5C 8E 59 55 86 72 5A 87 2B 2C 73 9F 6C 7A 68 23
8

Ok that should be a 700 series chip based on the protocol version. It should support the needed command classes for my driver to scan for all the settings. My driver also supports multi-taps. I think it will work 100% with that driver. Even if cannot detect all the settings, I think the button events should still work.

9

Thanks! That all looks pretty standard. These changes should be in 2.4.0. (That being said, a custom driver should certainly work, too, if you prefer! But this seems like a useful addition regardless.)

1 Like
10

I just installed your switch driver. It does work!!!!

I will register this as the solution given that today, it is the only way I've found to make this work. However, I still like the idea of the built-in Aeotec driver getting this functionality and hope that it does get in there.

That said, your driver is behaving a little strange. It registers 6 buttons, which would make sense: single tap up and down; double tap up and down; press and hole up and down. That would be 6. However, the "pushed" property will only register 1, 2, 4, and 5. The three-way switch I have attached to it registers as button 3. No idea what 6 would be. Maybe that is how it should work, but it does seem a little strange to me.

11

hold and release will register on the primary buttons, 1 and 2. The way most switches report I have it set where 1 should be up and 2 is down. Then after that 3 and 4 are 2x tap (and also sends a doubletapped events), then 5 and 6 should be 3x taps.

If the switch does not report things in the way I expected it then yes it might be strange results. Once you know what button event is for what though you can program it all the same.