[Bug Report]: Enbrighten/GE/Honeywell/UltraPro - ZW4008/39348/46201, ZW4009/39354/46202 - 5.54 (Double/Triple tap also turns regular "On/Off")

[badmuz]

What brand is the bug report for?

Enbrighten-GE

ZW Number

ZW4008

Product Number

46201

FW Version

5.54

Bug Report Details

Hi there.

On new 5.54 software "Double tap" function also triggers the regular "On" function.

How To Reproduce

Set up automation with "Double Tap" action. Push up paddle twice, switch will run programmed action and trigger regular "On" action.

[jascoproducts]

Thanks for the report. A beta firmware to correct this is issue in development.

[cmamatey]

I have also observed this same behavior when upgrading to FW v5.54 on the following:

• GE Enbrighten 46202 / ZW4009
• UltraPro 39348 / ZW4008

Note that the issue applies to all multi-taps, not just double-tap up.
Double and triple taps UP will both turn the load on and trigger the expected scene.
Double and triple taps DOWN will both turn the load off and trigger the expected scene.

I was able to reinstall FW v5.53 on both devices and restore the correct functionality.

[jascoproducts]

@cmamatey Thanks for the feedback. We will look into these devices as well.

[jascoproducts]

We have working beta firmware that includes features from 5.54 while retaining the behavior of 5.53. Still polishing a few things out; should be ready sometime next week. Will keep you all posted.

[jascoproducts]

@badmuz Just posted beta firmware for this device that should fix your issue while retaining the full functionality of v5.54.

Leaving this topic open until versions are released for models 46202 and 39348 as mentioned by @cmamatey

[tuday2]

I observed same behavior and installed beta firmware and it is now behaving like it did before (double taps on/off do not trigger device on/off). Thank you!!

[icemarkom]

Likewise. Several of my switches were affected by this bug (new Home Assistant upgrade feature rolled out today). Luckily, I found this great repo and this issue, and v0.54 seems to indeed resolve the problem for me.

[jascoproducts]

@tuday2 @icemarkom Awesome, really happy to hear it worked for you all!

Just rolled out another update today adding beta releases of this same firmware for similar devices:

• Honeywell ZW4008 / 39348
• UltraPro ZW4008 / 39348
• Honeywell ZW4009 / 39354
• UltraPro ZW4009 / 39354
• Enbrighten ZW4009 / 46202

Need to double check a few things on my end to make sure we've covered our entire lineup of similar products. For now this issue will remain open.

[badmuz]

@jascoproducts ,
Thank you so much for a quick fix. I can confirm 0.54 has fixed the issues.

[icemarkom]

Will you be releasing a non-beta of this? Those of us with a recently-added Home Assistant upgrade system are still seeing upgrade available, but that would be to a broken version.

[icemarkom]

Any updates?

[ghost]

I am looking for updates as well.

[mrrobotnic]

Same here running FW 5.54 on a GE/Enbrighten 46201 / ZW4008 and have observed this behavior as well and curious to see when the finalized version of the firmware will be released. Thanks for the progress on this so far!!

[nickbits1024]

I was about to make a bug for [Enbrighten ZW4009 / 46202] when I found this already was made. This also applies to double/triple tap DOWNS. So if the light was on and you execute a double/triple tap down, it also shuts off the light.

[jascoproducts]

We are working on a way to introduce 0.54 as a recognized current version that will no longer prompt you to upgrade. We have no plans to release a 5.55 (a certified 0.54) as we will not be bringing in any more new inventory of the affected devices and thus will not be undergoing certification.

If HA prompts an "upgrade" to 5.54, please ignore it indefinitely as we work on the pull request.

[jascoproducts]

To expand on this a bit, we are in the process of replacing the affected devices with our 700 and 800 series product line which is why we will not be replenishing and therefore certifying existing devices.

We originally introduced v5.54 without the delay as the vast majority of device owners were complaining about the delay required for Central Scene control (aka the multi tap) to function correctly, even after tuning the delay as tight as possible.

For those that prefer the functionality of Central Scene via multi-tap control, 0.54 will be your version.

[mrrobotnic]

@jascoproducts Out of curiosity, since 0.54 is the best of 5.53 and 5.54 for those of us who want double tap enabled, what are the differences between 5.53 and 5.54? I see the changelog mentions three items, but I am not well versed enough to know what they mean in practice. Thanks!

Changes introduced in 5.54

1. Add Parameter 84
2. Valid Value 0 – No specific behavior necessary Valid Value 1 – Reset Switch to Factory Defaults
3. Valid Value 1 – Reset Switch to Factory Defaults

[mrrobotnic]

Just updated to v0.54 and it works great and brought back the double tap without also turning the light connected to the switch on and off at the same time.

For anyone looking to update in Home Assistant running Z-Wave JS UI you can download the firmware from the link provided by @jascoproducts (quoted below), select the desired device to update, select "Advanced," under "Firmware update" click "Begin" and then select the .otz file that you downloaded, click OK, and it will start the update. When it is done, you will see a notification in Home Assistant that there is an update to a newer version of the firmware, but you can skip the update to hide that notification.

@badmuz Just posted beta firmware for this device that should fix your issue while retaining the full functionality of v5.54.

[jascoproducts]

@jascoproducts Out of curiosity, since 0.54 is the best of 5.53 and 5.54 for those of us who want double tap enabled, what are the differences between 5.53 and 5.54? I see the changelog mentions three items, but I am not well versed enough to know what they mean in practice. Thanks!

Changes introduced in 5.54

1. Add Parameter 84
2. Valid Value 0 – No specific behavior necessary Valid Value 1 – Reset Switch to Factory Defaults
3. Valid Value 1 – Reset Switch to Factory Defaults

@mrrobotnic 5.54 The 3 items you are referencing are really just the same piece of information. We introduced Parameter 84 that will cause a remote reset to factory default settings. Z-Wave does not natively support remotely telling an end device to leave the network and reset itself to factory defaults. This parameter will specifically do this. The default value is always 0. If you were to set it to 1, it would instantly reset itself, leave the network, and reset the parameter value to 0 so you can add it back the network or to another network.

[jascoproducts]

Closing this thread: Beta releases have been uploaded for the 6 affected In-Wall products on all brands released (see below)

@tuday2 @icemarkom Awesome, really happy to hear it worked for you all!

Just rolled out another update today adding beta releases of this same firmware for similar devices:

• Honeywell ZW4008 / 39348
• UltraPro ZW4008 / 39348
• Honeywell ZW4009 / 39354
• UltraPro ZW4009 / 39354
• Enbrighten ZW4009 / 46202

Need to double check a few things on my end to make sure we've covered our entire lineup of similar products. For now this issue will remain open.

[whoisdecoy]

first of all, thank you! if someone else stumbles upon this and gets this error when trying to update using zwavejs in home assistant, change the firmware extension from .zip to .bin.

Z-Wave error 1506: Could not detect firmware format zw4008

edit: also getting this error Firmware update (part 1 / 1) failed with status Error_InsufficientMemory

what is the correct firmware_target for this manual update?

[jascoproducts]

@whoisdecoy Could you perform a Manufacturer_Specific_Get for us on the device in question and attach the data it returns? Here's an example:

[whoisdecoy]

Thank you for the response. I apologize, but I’m not sure how to do that. Could you elaborate?

[jascoproducts]

@whoisdecoy No worries, thanks for helping us out by contributing.

Rats, I am not sure how or if there is even a way to perform Manufacturer_Specific functions with Home Assistant on the front end.

Try updating with a firmware file for the opposite model number within the ZW4008 device category. e.g. 46201 --> 39348, 39348 --> 46201. Report back your results with that.

Also, if you don't mind, could you describe to us more in detail about your solution for changing the file extensions of the firmware archive .zip to .bin? What were you doing, and what exactly did it fix?