Release 2.2.3.145 - Aeotec WallMote Quad buttons double or tripple fires

Recently upgraded from 2.2.1.116 to 2.2.3.145. I found 2.2.1.116 to be solid and had few if any issues so didn't upgrade. Since upgrading to 2.2.3.145 the Aeotec WallMote Quad with OOB driver double fires the buttons. My buttons are configured in toggle, what's on turn off, what's on turn off. (Why would you want to push the off button if the device is already off?) The double firing is causing my Zooz Double Plugs to fire twice turning on then off (or the reverse). Using buttons on the app dashboard works fine.

I'm not quite sure how to troubleshoot the situation?

dev:332020-09-14 08:11:13.161 pm infoWallMote Button 3 button 2 was pushed
dev:332020-09-14 08:11:13.159 pm debugCentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:8)
dev:332020-09-14 08:11:13.156 pm debugparse: zw device: 1E, command: 5B03, payload: 08 00 02 , isMulticast: false
dev:332020-09-14 08:11:12.352 pm infoWallMote Button 3 button 2 was pushed
dev:332020-09-14 08:11:12.347 pm debugCentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:8)
dev:332020-09-14 08:11:12.342 pm debugparse: zw device: 1E, command: 5B03, payload: 08 00 02 , isMulticast: false
dev:332020-09-14 08:11:12.023 pm infoWallMote Button 3 button 2 was pushed
dev:332020-09-14 08:11:12.020 pm debugCentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:8)
dev:332020-09-14 08:11:12.001 pm debugparse: zw device: 1E, command: 5B03, payload: 08 00 02 , isMulticast: false

When you have Debugging on, you get extra messages:

Here's my log, with Debug OFF then Debug On.

dev:838  2020-09-14 08:22:09.596 pm info  Office WallSwitch was turned on [digital]
dev:2040 2020-09-14 08:22:09.157 pm info  Aeon WallMote1 button 1 was pushed
dev:2040 2020-09-14 08:22:09.153 pm debug CentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:1, sequenceNumber:2)
dev:2040 2020-09-14 08:22:09.133 pm debug parse: zw device: 42, command: 5B03, payload: 02 00 01 , isMulticast: false
dev:838  2020-09-14 08:22:08.435 pm info  Office WallSwitch was turned off [digital]
dev:2040 2020-09-14 08:22:07.981 pm info  Aeon WallMote1 button 1 was pushed
dev:2040 2020-09-14 08:22:07.970 pm debug CentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:1, sequenceNumber:1)
dev:2040 2020-09-14 08:22:07.937 pm debug parse: zw device: 42, command: 5B03, payload: 01 00 01 , isMulticast: false
dev:2040 2020-09-14 08:22:02.370 pm warn  description logging is: true
dev:2040 2020-09-14 08:22:02.368 pm warn  debug logging is: true
dev:2040 2020-09-14 08:22:02.365 pm info  updated...
dev:840  2020-09-14 08:22:00.382 pm info  MultiSenDomeU (office3) motion is inactive
dev:838  2020-09-14 08:21:55.131 pm info  Office WallSwitch was turned on [digital]
dev:2040 2020-09-14 08:21:54.665 pm info  Aeon WallMote1 button 1 was pushed
dev:838  2020-09-14 08:21:53.695 pm info  Office WallSwitch was turned off [digital]
dev:2040 2020-09-14 08:21:53.185 pm info  Aeon WallMote1 button 1 was pushed

From the bottom, you can see the button was pressed and a light was turned off/on.

Then Debugging was turned on and each button press has 3 messages to detail out what's occurring.

Normally for Hubitat Drivers, Debugging is disabled after 30 minutes, automatically.

I experience the same behavior while pressing a Xiaomi Wireless button switch since upgrading to .145. Not always, but roughly 1 to 2 out of 10 times. Just tested it again:

dev:362020-09-15 06:47:52.491 infobuttonPushed(button=1)
dev:362020-09-15 06:47:52.490 infoButton 1 was pushed (t3)
dev:362020-09-15 06:47:52.472 infomsgMap: [raw:C3FF0100060800001001, dni:C3FF, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0, valueParsed:true]
dev:362020-09-15 06:47:52.301 infomsgMap: [raw:C3FF0100060800001000, dni:C3FF, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, valueParsed:false]
dev:362020-09-15 06:47:17.612 infobuttonPushed(button=1)
dev:362020-09-15 06:47:17.610 infoButton 1 was pushed (t3)
dev:362020-09-15 06:47:17.591 infomsgMap: [raw:C3FF0100060800001001, dni:C3FF, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0, valueParsed:true]
dev:362020-09-15 06:47:17.454 infobuttonPushed(button=1)
dev:362020-09-15 06:47:17.453 infoButton 1 was pushed (t3)
dev:362020-09-15 06:47:17.431 infomsgMap: [raw:C3FF0100060800001001, dni:C3FF, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0, valueParsed:true]
dev:362020-09-15 06:47:17.321 infobuttonPushed(button=1)
dev:362020-09-15 06:47:17.319 infoButton 1 was pushed (t3)
dev:362020-09-15 06:47:17.299 infomsgMap: [raw:C3FF0100060800001001, dni:C3FF, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0, valueParsed:true]
dev:362020-09-15 06:47:17.179 infobuttonPushed(button=1)
dev:362020-09-15 06:47:17.178 infoButton 1 was pushed (t3)
dev:362020-09-15 06:47:17.159 infomsgMap: [raw:C3FF0100060800001001, dni:C3FF, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0, valueParsed:true]
dev:362020-09-15 06:47:16.989 infomsgMap: [raw:C3FF0100060800001000, dni:C3FF, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, valueParsed:false]
dev:362020-09-15 06:43:28.012 infobuttonPushed(button=1)
dev:362020-09-15 06:43:28.008 infoButton 1 was pushed (t3)
dev:362020-09-15 06:43:27.984 infomsgMap: [raw:C3FF0100060800001001, dni:C3FF, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0, valueParsed:true]

.145 also require you manually update the Z-wave drivers unlike prior updates. Just use the setting page to do that. That is the first thing to check with .145.

I already did that... And besides that, my button is a Zigbee device...

Then it should not matter. Almost all the bug fixes and added devices are Z-Wave.

Thanks @jeff.lilliquist I have a C-5, not the C-7 which requires the radio updates.

OK, I have been busy getting a AVR driver for my Yamaha Receiver working. In typical fashion it seem impossible until you try something illogical and it works. They can now add Yamaha to their list. It actually work better then the Denon one. It seem to take about a day to figure out each new device. I have WeMo, MyQ and now the Yamaha AVR connected. For WeMo and MyQ there is an App but for the Yamaha I added it as a Virtual device and it seems to work since I am using real user defined drivers that connect to the IP address I enter to define the virtual driver. Not sure how I am going to use it but if I can get the TV on too then we might have something sweet. I tried on, off, mute, muteoff and changing volume so I suspect changing sources should work too. It has some nice preferences it saves too.

Thanks @csteele I enabled debugging and was able to get the light to action multiple times. The kitchen light started off, and then turned on and off with 1 press of the Aeotec Wallmote Quad.

dev:102020-09-15 08:28:36.520 pm infoKitchen Lights power is 0W
dev:102020-09-15 08:28:36.470 pm infoKitchen Lights power is 0W
dev:102020-09-15 08:28:36.353 pm infoKitchen Lights power is 0W
dev:122020-09-15 08:28:36.305 pm infoKitchen - RIGHT Outlet power is 0W
dev:122020-09-15 08:28:36.149 pm infoKitchen - RIGHT Outlet power is 0W
dev:122020-09-15 08:28:36.054 pm infoKitchen - RIGHT Outlet power is 0W
dev:112020-09-15 08:28:35.946 pm infoKitchen LED - LEFT Outlet power is 0W
dev:102020-09-15 08:28:35.819 pm infoKitchen Lights current is 0A
dev:102020-09-15 08:28:35.729 pm infoKitchen Lights current is 0A
dev:102020-09-15 08:28:35.695 pm infoKitchen Lights current is 0A
dev:102020-09-15 08:28:34.825 pm infoKitchen Lights voltage is 0V
dev:102020-09-15 08:28:34.780 pm debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (right)
dev:102020-09-15 08:28:34.743 pm debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (right)
dev:102020-09-15 08:28:34.647 pm debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (left)
dev:102020-09-15 08:28:34.515 pm debugSwitchBinaryReport(value:0) ()
dev:102020-09-15 08:28:34.419 pm debugSwitchBinaryReport(value:0, targetValue:0, duration:0) (left)
dev:102020-09-15 08:28:34.298 pm debugSwitchBinaryReport(value:0) ()
dev:102020-09-15 08:28:34.241 pm infoKitchen Lights switch is off
dev:102020-09-15 08:28:34.232 pm debugSwitchBinaryReport(value:0) ()
dev:102020-09-15 08:28:34.162 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:33.020 pm debugoff()...
dev:332020-09-15 08:28:32.912 pm infoWallMote Button 3 button 2 was pushed
dev:332020-09-15 08:28:32.910 pm debugCentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:2)
dev:332020-09-15 08:28:32.907 pm debugparse: zw device: 1E, command: 5B03, payload: 02 00 02 , isMulticast: false
dev:102020-09-15 08:28:32.809 pm debugoff()...
dev:332020-09-15 08:28:32.701 pm infoWallMote Button 3 button 2 was pushed
dev:332020-09-15 08:28:32.699 pm debugCentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:2)
dev:332020-09-15 08:28:32.696 pm debugparse: zw device: 1E, command: 5B03, payload: 02 00 02 , isMulticast: false
dev:102020-09-15 08:28:32.666 pm debugoff()...
dev:332020-09-15 08:28:32.551 pm infoWallMote Button 3 button 2 was pushed
dev:332020-09-15 08:28:32.548 pm debugCentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:2)
dev:332020-09-15 08:28:32.545 pm debugparse: zw device: 1E, command: 5B03, payload: 02 00 02 , isMulticast: false
dev:102020-09-15 08:28:32.419 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:32.361 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:32.352 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:32.004 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:31.958 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:31.932 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:31.701 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:31.461 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:30.698 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:30.669 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:30.660 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:30.592 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:30.509 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:30.157 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:29.936 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:29.921 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:29.724 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:29.677 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:29.470 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:29.443 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:29.398 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:27.549 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:27.456 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:27.356 pm infoKitchen Lights switch is on
dev:102020-09-15 08:28:27.346 pm debugSwitchBinaryReport(value:255) ()
dev:102020-09-15 08:28:26.386 pm debugon()...
dev:332020-09-15 08:28:26.273 pm infoWallMote Button 3 button 2 was pushed
dev:332020-09-15 08:28:26.270 pm debugCentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:2)
dev:332020-09-15 08:28:26.268 pm debugparse: zw device: 1E, command: 5B03, payload: 02 00 02 , isMulticast: false
dev:102020-09-15 08:28:26.192 pm debugon()...
dev:102020-09-15 08:28:26.114 pm debugon()...
dev:332020-09-15 08:28:26.084 pm infoWallMote Button 3 button 2 was pushed
dev:332020-09-15 08:28:26.081 pm debugCentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:2)
dev:332020-09-15 08:28:26.078 pm debugparse: zw device: 1E, command: 5B03, payload: 02 00 02 , isMulticast: false
dev:102020-09-15 08:28:25.999 pm debugon()...
dev:332020-09-15 08:28:25.984 pm infoWallMote Button 3 button 2 was pushed
dev:332020-09-15 08:28:25.982 pm debugCentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:2)
dev:332020-09-15 08:28:25.979 pm debugparse: zw device: 1E, command: 5B03, payload: 02 00 02 , isMulticast: false
dev:332020-09-15 08:28:25.873 pm infoWallMote Button 3 button 2 was pushed
dev:332020-09-15 08:28:25.870 pm debugCentralSceneNotification: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:2)
dev:332020-09-15 08:28:25.867 pm debugparse: zw device: 1E, command: 5B03, payload: 02 00 02 , isMulticast: false
dev:102020-09-15 08:28:21.916 pm infoKitchen Lights power is 0W

1 Like

Well, it does matter to me. Firing an action 3 times within a second is not what it is intended to do and has unwanted consequences. Before the upgrade this never happened.

There were no changes to Zigbee in 2.2.3.xxx
The issues you're seeing likely has nothing to do with the platform update, simply rebooting a hub can cause Zigbee devices to readjust their routes, perhaps picking a worse/less reliable one to use...

If you truly believe that 145 broke this, then reverting to a prior version should explicitly resolve the issue, and switching back to 145 will re introduce it.

If that's not the observed behavior after switching versions, then the version isn't the issue.

1 Like

Download the Hubitat app