BUG[Fix Pending] 2.2.4.153 "Zooz double switch" driver bug while double tapping button 2, debug parse and config update

  1. I have two of these devices (Zooz zen30) that the dimmer rocker button 2 is incorrectly mapped.
    If I single or double press dimmer button 2 it will be registered as double pressing fan button.

  2. Additionally, driver is parsing zwave commands but debug login is disabled.

  3. When commiting the setting save there is always a message saying that there was a one change pending.
    dev:24342020-11-27 05:06:13.488 pm warnThere are 1 pending changes, please click the Save button again.

Double tap the dimmer button 2:

ev:24352020-11-27 04:46:44.680 pm infoMaster Room Fan - Button 2 doubleTapped

dev:24372020-11-27 05:02:01.549 pm infoStudio Fan - Button 2 doubleTapped

dev:24372020-11-27 05:01:59.367 pm infoStudio Fan - Button 2 pushed

  • deviceId: 40968
  • deviceType: 40960
  • manufacturer: 634
  • inClusters: 0x5E,0x26,0x25,0x85,0x8E,0x59,0x55,0x86,0x72,0x5A,0x73,0x70,0x5B,0x60,0x9F,0x6C,0x7A
  • zwNodeInfo: D3 9C 00 04 11 01 5E 26 25 85 5C 8E 59 55 86 72 5A 73 70 5B 60 9F 6C 7A 68 23
  • firmwareVersion: 1.5

State Variables

  • resyncAll : false
  • configVal1 : 0
  • configVal2 : 0
  • configVal23 : 0
  • configVal3 : 1
  • configVal4 : 1
  • configVal5 : 2
  • configVal6 : 0
  • configVal7 : 1
  • configVal8 : 0
  • configVal9 : 0
  • lastSequenceNumber : 27
  • configVal11 : 0
  • configVal10 : 0
  • pendingSwitch0 : false
  • pendingSwitch1 : false
  • configured : true
  • configVal15 : 99
  • configVal14 : 2
  • configVal13 : 3
  • configVal12 : 0
  • configVal19 : 1
  • configVal18 : 2
  • configVal17 : 1
  • refreshConfig : false
  • pendingCustomBrightness :
  • configVal21 : 4
  • configVal20 : 1

@bcopeland

What version of HE software are you running? A very similar problem (relay reporting actuated when dimmer pressed) was reported in this thread:

The combination of new firmware v 1.07 from Zooz and a driver patch released by @bcopeland in 2.2.4.147 fixed the issues we'd encountered.

I should note that the fixes allowed proper operation when included with S2 security. It looks like you're included with no security, and I'm not sure how Bryan's driver fix will perform in that scenario.

I have 1.07 and 2.2.4.148 and am still having issues (though I'm also not on s2 security because i'm on a c5 hub) so I suspect the issues are not fully fixed in that case @eppower.

Tagging @agnes.zooz from Zooz-Land. :slight_smile:

1 Like

Latest and greatest, ver 2.2.4.148 Hardware Version Rev C-7.
And no S2 security, both paired with no security.

Can you please request the 1.07 firmware from our support and update your switch to see if that helps the issue?

Will do Agnes, thanks

@agnes.zooz Upgraded to ver 1.07

Here is the observed behavior:
-If included as S2 - unauth, clusters would be incomplete.

vs unsecured

-After 1.07, there is not notifications at the the log even thou its enabled with description notifications, on/off, button press would not be registered on the log.

-There is a pending change that neves goes away.

-Always debug verbose is observed regardless of the setting.

So now firmware broke basic binary reporting and button press and drivers is not consistent with its settings.
Did a 15sec lower paddle and 15 upper paddle factory restore with same behavior.

dev:28242020-11-30 11:02:51.491 am warnThere are 1 pending changes, please click the Save button again.

dev:28242020-11-30 11:02:47.380 am debugzw device: 46, command: 7006, payload: 01 01 00 , isMulticast: false

dev:28242020-11-30 11:02:46.317 am debugzw device: 46, command: 7006, payload: 12 01 01 , isMulticast: false

dev:28242020-11-30 11:02:45.356 am debugzw device: 46, command: 7006, payload: 0C 01 02 , isMulticast: false

dev:28242020-11-30 11:02:44.338 am debugzw device: 46, command: 7006, payload: 06 01 00 , isMulticast: false

dev:28242020-11-30 11:02:43.324 am debugzw device: 46, command: 7006, payload: 05 01 00 , isMulticast: false

dev:28242020-11-30 11:02:42.325 am debugzw device: 46, command: 7006, payload: 04 01 01 , isMulticast: false

dev:28242020-11-30 11:02:41.278 am debugzw device: 46, command: 7006, payload: 03 01 01 , isMulticast: false

dev:28242020-11-30 11:02:40.387 am warndescription logging is: true

dev:28242020-11-30 11:02:40.383 am warndebug logging is: false

dev:28242020-11-30 11:02:40.378 am infoupdated...

dev:28242020-11-30 11:00:48.305 am warnThere are 1 pending changes, please click the Save button again.

dev:28242020-11-30 11:00:44.209 am debugzw device: 46, command: 7006, payload: 01 01 00 , isMulticast: false

dev:28242020-11-30 11:00:43.350 am warndescription logging is: true

dev:28242020-11-30 11:00:43.346 am warndebug logging is: false

Confirming its a bug. Downgraded back to 1.05, on C7 would show swapped button presses as before.
Excluded and made factory default.
This time added it to my C5 hub, absolutely no problem at all, reporting of binary switch and button presses are 100% logged and aligned with respective buttons.
dev:27222020-11-30 12:40:33.979 pm infoStudio Light: switch is off
dev:27222020-11-30 12:40:33.952 pm debugBasicReport(value:0, targetValue:0, duration:0)
dev:27222020-11-30 12:40:33.946 pm debugzw device: 02, command: 2003, payload: 00 , isMulticast: false
dev:27232020-11-30 12:40:32.961 pm infoZooz Double Switch-Relay - Button 2 pushed
dev:27222020-11-30 12:40:32.955 pm debugCentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:4)
dev:27222020-11-30 12:40:32.951 pm debugzw device: 02, command: 5B03, payload: 04 80 02 , isMulticast: false
dev:27232020-11-30 12:40:20.977 pm infoZooz Double Switch-Relay - Button 1 doubleTapped
dev:27222020-11-30 12:40:20.968 pm debugCentralSceneNotification(keyAttributes:3, sceneNumber:3, sequenceNumber:3)
dev:27222020-11-30 12:40:20.962 pm debugzw device: 02, command: 5B03, payload: 03 83 03 , isMulticast: false
dev:27222020-11-30 12:40:14.519 pm infoStudio Light: switch is on
dev:27222020-11-30 12:40:14.515 pm infoStudio Light: level is 99
dev:27222020-11-30 12:40:14.512 pm debugBasicReport(value:99, targetValue:0, duration:0)
dev:27222020-11-30 12:40:14.507 pm debugzw device: 02, command: 2003, payload: 63 , isMulticast: false
dev:27232020-11-30 12:40:13.537 pm infoZooz Double Switch-Relay - Button 1 doubleTapped
dev:27222020-11-30 12:40:13.531 pm debugCentralSceneNotification(keyAttributes:3, sceneNumber:1, sequenceNumber:2)
dev:27222020-11-30 12:40:13.524 pm debugzw device: 02, command: 5B03, payload: 02 83 01 , isMulticast: false
dev:27232020-11-30 12:39:57.058 pm infoZooz Double Switch-Relay - Button 2 doubleTapped
dev:27222020-11-30 12:39:57.052 pm debugCentralSceneNotification(keyAttributes:3, sceneNumber:2, sequenceNumber:1)
dev:27222020-11-30 12:39:57.038 pm debugzw device: 02, command: 5B03, payload: 01 83 02 , isMulticast: false
@bcopeland

Bump @agnes.zooz @bptworld . Should I initiate a proper support case for this then. Cheers,

@agnes.zooz Updated to 2.2.4.153 today, no change still.

Did you also exclude and re-include the switch after the platform update?

Did factory restore with both firmware's. On each firmware upgrade device has to be exclude a and re-included. C7 doesnt work, c5 works as stated.

@agnes.zooz

After Firmware update from 1.05 to 1.07:
2020-12-03 08:05:10.486 am debugFirmwareMdReport(manufacturerId:634, firmwareId:40968, checksum:43807, firmwareUpgradable:false, numberOfTargets:0, maxFragmentSize:40, firmwareIds:[], hardwareVersion:null)
deviceId: 40968
deviceType: 40960
manufacturer: 634
inClusters: 0x5E,0x26,0x25,0x85,0x8E,0x59,0x55,0x86,0x72,0x5A,0x73,0x70,0x5B,0x60,0x9F,0x6C,0x7A
zwNodeInfo: 9C 00 04 11 01 5E 26 25 85 5C 8E 59 55 86 72 5A 73 70 5B 60 9F 6C 7A 68 23
firmwareVersion: 1.07

Switch became unresponsive to physical button push on any of the three buttons.
No button presses were observed on the log or debug, bringing me to the conclusion that manual button were disabled.
Air gapped the switch for 30sec, after reset still no physical control, as such was impossible to issue a factory default.
Configured zooz double switch and I could change things like led color and turn on the fan relay, dimmer would not power light.
Made sure I was selecting manual and zwave controls on the drivers, pushed configuration, but there was always 1 pending change.
Loaded basic Zwave tool driver to query as was still responsive to zwave commands even thou the light would not turn on the bulb, but then the leds on the paddle could be seen polling up and down accordingly to the dimmer level set.

Queried parameter 19 and 20:
dev:28982020-12-03 09:04:51.867 am infoConfigurationReport- parameterNumber:20, size:1, value:1
dev:28982020-12-03 09:04:51.816 am traceconfigurationGet command(s) sent...
dev:28982020-12-03 09:03:48.081 am infoConfigurationReport- parameterNumber:19, size:1, value:1
dev:28982020-12-03 09:03:47.947 am traceconfigurationGet command(s) sent...

Varied Parameter 19 and 20 to value 0,1,2 for good meassure, still no manual control on neither button:
dev:28982020-12-03 09:09:14.424 am infoConfigurationReport- parameterNumber:19, size:1, value:1
dev:28982020-12-03 09:09:14.374 am traceconfigurationGet command(s) sent...
dev:28982020-12-03 09:09:05.276 am infoConfigurationReport- parameterNumber:19, size:1, value:1

For testing purposes I varied parameter 3 and 4 to value 3, this changed the led to red, all light blinked momentarily and led turned red, meaning its receiving.
dev:28982020-12-03 09:13:41.329 am infoConfigurationReport- parameterNumber:4, size:1, value:3

get command class debugFirmwareMdReport):

dev:28982020-12-03 08:54:52.855 am infoCommandClassReport- class:0x7A, version:4
dev:28982020-12-03 08:54:52.357 am infoCommandClassReport- class:0x6C, version:1
dev:28982020-12-03 08:54:51.844 am infoCommandClassReport- class:0x9F, version:1
dev:28982020-12-03 08:54:51.303 am infoCommandClassReport- class:0x60, version:4
dev:28982020-12-03 08:54:50.801 am infoCommandClassReport- class:0x5B, version:3
dev:28982020-12-03 08:54:50.298 am infoCommandClassReport- class:0x70, version:1
dev:28982020-12-03 08:54:49.821 am infoCommandClassReport- class:0x73, version:1
dev:28982020-12-03 08:54:49.313 am infoCommandClassReport- class:0x5A, version:1
dev:28982020-12-03 08:54:48.818 am infoCommandClassReport- class:0x72, version:2
dev:28982020-12-03 08:54:48.307 am infoCommandClassReport- class:0x86, version:3
dev:28982020-12-03 08:54:47.791 am infoCommandClassReport- class:0x55, version:2
dev:28982020-12-03 08:54:47.283 am infoCommandClassReport- class:0x59, version:1
dev:28982020-12-03 08:54:46.782 am infoCommandClassReport- class:0x8E, version:3
dev:28982020-12-03 08:54:46.285 am infoCommandClassReport- class:0x85, version:2
dev:28982020-12-03 08:54:45.759 am infoCommandClassReport- class:0x25, version:1
dev:28982020-12-03 08:54:45.221 am infoCommandClassReport- class:0x26, version:4
dev:28982020-12-03 08:54:44.750 am infoCommandClassReport- class:0x5E, version:2

Get Assosiation Report:
dev:28982020-12-03 08:56:14.137 am infoAssociationReport- groupingIdentifier:1, maxNodesSupported:1, nodes:[]
dev:28982020-12-03 08:56:13.620 am infoAssociationReport- groupingIdentifier:4, maxNodesSupported:5, nodes:[]
dev:28982020-12-03 08:56:13.128 am infoAssociationReport- groupingIdentifier:3, maxNodesSupported:5, nodes:[]
dev:28982020-12-03 08:56:12.583 am infoAssociationReport- groupingIdentifier:2, maxNodesSupported:5, nodes:[]
dev:28982020-12-03 08:56:12.090 am infoAssociationReport- groupingIdentifier:1, maxNodesSupported:1, nodes:[]

Currently falling back to 1.05, will keep you posted.

Downgrade 1.07 to 1.05:
dev:28982020-12-03 09:49:03.952 am debugignore: FirmwareUpdateMdStatusReport(status:255)

Performed exclusion, this time buttons were responsive, did a factory default w 15 sec down up paddle.

Inclusion, non S2:
sys:12020-12-03 09:58:14.411 am warnZ-Wave device id: 78 failed S2 bootstrapping - KEX_FAIL_KEX_KEY: Key failure indicating that no match exists between requested/granted keys in the network. - the device needs to be excluded then included again to use securely.
sys:12020-12-03 09:58:08.843 am warnS0 security was selected for an S2 capable device, it will include using nonoptimal security.

Driver was not installed automaticly, so I had to force discover on the zwave page:
dev:29032020-12-03 10:00:05.448 am warnThere are 14 pending changes, please click the Save button again.
dev:29032020-12-03 10:00:01.369 am debugCustom Brightness(#23) = 0
dev:29032020-12-03 10:00:01.327 am debugzw device: 4E, command: 7006, payload: 17 01 00 , isMulticast: false
dev:29032020-12-03 10:00:00.999 am warnThere are 15 pending changes, please click the Save button again.
dev:29032020-12-03 09:59:56.970 am debugDimmer LED Indicator Mode(#1) = 0
dev:29032020-12-03 09:59:56.930 am debugDimming Speed when Dimmer Paddle is Held(#21) = 4
dev:29032020-12-03 09:59:56.917 am debugzw device: 4E, command: 7006, payload: 01 01 00 , isMulticast: false
dev:29032020-12-03 09:59:56.873 am debugzw device: 4E, command: 7006, payload: 15 01 04 , isMulticast: false
dev:29032020-12-03 09:59:56.818 am debugRelay Load Control(#20) = 1
dev:29032020-12-03 09:59:56.795 am debugDimmer Load Control(#19) = 1
dev:29032020-12-03 09:59:56.763 am debugDimmer Brightness Control(#18) = 0
dev:29032020-12-03 09:59:56.728 am debugzw device: 4E, command: 7006, payload: 14 01 01 , isMulticast: false
dev:29032020-12-03 09:59:56.704 am debugDimmer Double Tap Function(#17) = 0
dev:29032020-12-03 09:59:56.696 am debugzw device: 4E, command: 7006, payload: 13 01 01 , isMulticast: false
dev:29032020-12-03 09:59:56.673 am debugDimmer Maximum Brightness(#15) = 99
dev:29032020-12-03 09:59:56.665 am debugzw device: 4E, command: 7006, payload: 12 01 00 , isMulticast: false
dev:29032020-12-03 09:59:56.645 am debugDimmer Physical Ramp Rate(#13) = 1
dev:29032020-12-03 09:59:56.636 am debugzw device: 4E, command: 7006, payload: 11 01 00 , isMulticast: false
dev:29032020-12-03 09:59:56.612 am debugDimmer Minimum Brightness(#14) = 1
dev:29032020-12-03 09:59:56.597 am debugzw device: 4E, command: 7006, payload: 0F 01 63 , isMulticast: false
dev:29032020-12-03 09:59:56.575 am debugOn/Off Status Recovery After Power Failure(#12) = 3
dev:29032020-12-03 09:59:56.536 am debugzw device: 4E, command: 7006, payload: 0D 01 01 , isMulticast: false
dev:29032020-12-03 09:59:56.523 am debugzw device: 4E, command: 7006, payload: 0E 01 01 , isMulticast: false
dev:29032020-12-03 09:59:56.512 am debugzw device: 4E, command: 7006, payload: 0C 01 03 , isMulticast: false
dev:29032020-12-03 09:59:55.961 am debugRelay Auto Turn-On Timer(#11) = 0
dev:29032020-12-03 09:59:55.906 am debugzw device: 4E, command: 7006, payload: 0B 04 00 00 00 00 , isMulticast: false
dev:29032020-12-03 09:59:55.459 am warnThere are 18 pending changes, please click the Save button again.
dev:29032020-12-03 09:59:51.444 am debug0-MultiChannelAssociationReport(groupingIdentifier:1, maxNodesSupported:1, reportsToFollow:0, nodeId:[], multiChannelNodeIds:[[nodeId:1, bitAddress:0, endPointId:0]])
dev:29032020-12-03 09:59:51.433 am debugRelay Auto Turn-Off Timer(#10) = 0
dev:29032020-12-03 09:59:51.422 am debugzw device: 4E, command: 8E03, payload: 01 01 00 00 01 00 , isMulticast: false
dev:29032020-12-03 09:59:51.402 am debugDimmer Auto Turn-On Timer(#9) = 0
dev:29032020-12-03 09:59:51.353 am debugzw device: 4E, command: 7006, payload: 0A 04 00 00 00 00 , isMulticast: false
dev:29032020-12-03 09:59:51.329 am debugzw device: 4E, command: 7006, payload: 09 04 00 00 00 00 , isMulticast: false
dev:29032020-12-03 09:59:51.154 am debugDimmer Auto Turn-Off Timer(#8) = 0
dev:29032020-12-03 09:59:51.123 am debugScene Control LED Indicator(#7) = 1
dev:29032020-12-03 09:59:51.077 am debugRelay LED Indicator Brightness(#6) = 1
dev:29032020-12-03 09:59:51.056 am debugzw device: 4E, command: 7006, payload: 08 04 00 00 00 00 , isMulticast: false
dev:29032020-12-03 09:59:51.033 am debugDimmer LED Indicator Brightness(#5) = 1
dev:29032020-12-03 09:59:51.019 am debugzw device: 4E, command: 7006, payload: 07 01 01 , isMulticast: false
dev:29032020-12-03 09:59:50.989 am debugRelay LED Indicator Color(#4) = 0
dev:29032020-12-03 09:59:50.986 am debugzw device: 4E, command: 7006, payload: 06 01 01 , isMulticast: false
dev:29032020-12-03 09:59:50.964 am debugDimmer LED Indicator Color(#3) = 0
dev:29032020-12-03 09:59:50.930 am debugzw device: 4E, command: 7006, payload: 05 01 01 , isMulticast: false
dev:29032020-12-03 09:59:50.914 am debugzw device: 4E, command: 7006, payload: 04 01 00 , isMulticast: false
dev:29032020-12-03 09:59:50.903 am debugzw device: 4E, command: 7006, payload: 03 01 00 , isMulticast: false
dev:29032020-12-03 09:59:50.717 am debugDimmer LED Indicator Mode(#1) = 0
dev:29032020-12-03 09:59:50.705 am debugRelay LED Indicator Mode(#2) = 0
dev:29032020-12-03 09:59:50.647 am debugzw device: 4E, command: 7006, payload: 01 01 00 , isMulticast: false
dev:29032020-12-03 09:59:50.644 am debugzw device: 4E, command: 7006, payload: 02 01 00 , isMulticast: false
dev:29032020-12-03 09:59:50.625 am debugBasicReport(value:0, targetValue:0, duration:0) (Endpoint 1)
dev:29032020-12-03 09:59:50.622 am debugAssociation Report - Group: 1, Nodes: []
dev:29032020-12-03 09:59:50.611 am debugzw device: 4E, command: 8503, payload: 01 01 00 , isMulticast: false
dev:29032020-12-03 09:59:50.604 am debugFirmware: 1.05
dev:29032020-12-03 09:59:50.601 am debugzw device: 4E, command: 8612, payload: 03 05 03 01 05 02 00 , isMulticast: false
dev:29032020-12-03 09:59:50.598 am debugzw device: 4E, command: 600D, payload: 01 00 20 03 00 00 00 , isMulticast: false
dev:29032020-12-03 09:59:49.809 am debugFirmware: 1.05
dev:29032020-12-03 09:59:49.807 am debugzw device: 4E, command: 8612, payload: 03 05 03 01 05 02 00 , isMulticast: false
dev:29032020-12-03 09:59:49.575 am warnThere are 22 pending changes, please click the Save button again.
dev:29032020-12-03 09:59:45.368 am warnconfigure...
dev:29032020-12-03 09:59:45.328 am debugcomponentRefresh(Zooz Double Switch-Relay)...
dev:29032020-12-03 09:59:45.273 am debugCreating Child Relay
dev:29032020-12-03 09:59:45.252 am warninstalled...

Driver status:
deviceId: 40968
deviceType: 40960
manufacturer: 634
inClusters: 0x5E,0x26,0x25,0x85,0x8E,0x59,0x55,0x86,0x72,0x5A,0x73,0x70,0x5B,0x60,0x9F,0x6C,0x7A
zwNodeInfo: D3 9C 00 04 11 01 5E 26 25 85 5C 8E 59 55 86 72 5A 73 70 5B 60 9F 6C 7A 68 23
firmwareVersion: 1.05

Tested double button down on dimmer:
dev:29042020-12-03 10:04:26.756 am infoZooz Double Switch-Relay - Button 2 doubleTapped
dev:29032020-12-03 10:04:26.749 am debugCentralSceneNotification(keyAttributes:3, sceneNumber:2, sequenceNumber:0)
dev:29032020-12-03 10:04:26.730 am debugzw device: 4E, command: 5B03, payload: 00 83 02 , isMulticast: false

Double button on up dimmer:
dev:29032020-12-03 10:06:38.482 am infoZooz Double Switch: switch is on
dev:29032020-12-03 10:06:38.478 am infoZooz Double Switch: level is 99
dev:29032020-12-03 10:06:38.474 am debugBasicReport(value:99, targetValue:0, duration:0)
dev:29032020-12-03 10:06:38.468 am debugzw device: 4E, command: 2003, payload: 63 , isMulticast: false
dev:29042020-12-03 10:06:37.481 am infoZooz Double Switch-Relay - Button 1 doubleTapped
dev:29032020-12-03 10:06:37.475 am debugCentralSceneNotification(keyAttributes:3, sceneNumber:1, sequenceNumber:4)
dev:29032020-12-03 10:06:37.470 am debugzw device: 4E, command: 5B03, payload: 04 83 01 , isMulticast: false

Single down and up:
dev:29032020-12-03 10:07:05.994 am infoZooz Double Switch: switch is on
dev:29032020-12-03 10:07:05.990 am infoZooz Double Switch: level is 99
dev:29032020-12-03 10:07:05.986 am debugBasicReport(value:99, targetValue:0, duration:0)
dev:29032020-12-03 10:07:05.980 am debugzw device: 4E, command: 2003, payload: 63 , isMulticast: false
dev:29042020-12-03 10:07:04.995 am infoZooz Double Switch-Relay - Button 1 pushed
dev:29032020-12-03 10:07:04.987 am debugCentralSceneNotification(keyAttributes:0, sceneNumber:1, sequenceNumber:6)
dev:29032020-12-03 10:07:04.980 am debugzw device: 4E, command: 5B03, payload: 06 80 01 , isMulticast: false
dev:29032020-12-03 10:07:02.967 am infoZooz Double Switch: switch is off
dev:29032020-12-03 10:07:02.961 am debugBasicReport(value:0, targetValue:0, duration:0)
dev:29032020-12-03 10:07:02.956 am debugzw device: 4E, command: 2003, payload: 00 , isMulticast: false
dev:29042020-12-03 10:07:02.070 am infoZooz Double Switch-Relay - Button 2 pushed
dev:29032020-12-03 10:07:02.065 am debugCentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:5)
dev:29032020-12-03 10:07:02.061 am debugzw device: 4E, command: 5B03, payload: 05 80 02 , isMulticast: false

Single relay button:
dev:29032020-12-03 10:09:06.772 am debugSwitchBinaryReport(value:255) (Endpoint 1)
dev:29032020-12-03 10:09:06.767 am debugzw device: 4E, command: 600D, payload: 01 00 25 03 FF , isMulticast: false
dev:29032020-12-03 10:09:05.786 am debugCentralSceneNotification(keyAttributes:0, sceneNumber:3, sequenceNumber:11)
dev:29032020-12-03 10:09:05.781 am debugzw device: 4E, command: 5B03, payload: 0B 80 03 , isMulticast: false
dev:29042020-12-03 10:09:06.787 am infoZooz Double Switch-Relay: switch is on
dev:29042020-12-03 10:09:05.794 am infoZooz Double Switch-Relay - Button 1 pushed

Double relay button:
dev:29032020-12-03 10:10:34.379 am debugCentralSceneNotification(keyAttributes:3, sceneNumber:3, sequenceNumber:12)
dev:29032020-12-03 10:10:34.375 am debugzw device: 4E, command: 5B03, payload: 0C 83 03 , isMulticast: false
dev:29042020-12-03 10:10:34.386 am infoZooz Double Switch-Relay - Button 1 doubleTapped

Again a double button 2 on dimmer:
dev:29032020-12-03 10:11:12.867 am debugCentralSceneNotification(keyAttributes:3, sceneNumber:2, sequenceNumber:14)
dev:29032020-12-03 10:11:12.859 am debugzw device: 4E, command: 5B03, payload: 0E 83 02 , isMulticast: false
dev:29042020-12-03 10:11:12.879 am infoZooz Double Switch-Relay - Button 2 doubleTapped

@agnes.zooz Unfortunately seems like I bricked my switch last time it was flashed to 1.07.
There is no response from the buttons nor can make it pair or exclude. Air gapped it, opened the junction box and disconnected its power. And now I dont even have a manual means to even turn the light or relay. All lights are led are lit normally but no control in any way or form.
Tried to flash it using the new application with hubitat "Device Firmware Updater" and driver by @bcopeland to no avail.

Now, I dont even get the zwave basic tool to reply.
I am a sitting duck...

Can’t even get it to factory reset?

No single button works, tried it all. Airgapped while leaving pressed any button took me nowhere, there is no reaction. Tried all combination I can think off. Its dead.

image

2 Likes

I even had to install a mechanical switch like a mortal peasant, hahaha.
Man, what a frustration, going from a simple button bug to this... :sleepy: :pensive:

2 Likes