EvaLogik Smart Plug Dimmer ZW39 Stops powering lamp after device config update

🛎️ Get Help Devices
1

EvaLogik Smart Plug Dimmer ZW39 Stops powering lamp after device config update using Hubitat's built-in EVA LOGIK Smart Plug Dimmer driver

Hubitat hubVersion : 2.3.2.141

EvaLogik Smart Plug Dimmer ZW39 v.1.0d Date Code : 0421 FW : 2.02

Highlights:
I have had this problem with 2 different dimmers however a third is working as expected with the same driver/settings.

Steps to duplicate:

  1. Hubitat Zwave Include
  2. Plug-in ZW39 Dimmer and it will begin flashing fast.
  3. Hubitat recognizes the device and asks if we want to Include with security - I always choose No.
  4. Hubitat brings-in the device with the built-in "EvaLogik Smart Plug Dimmer" driver and I name it and provide a room.
  5. I wait about 30 minutes for the Zwave network to build neighbors for the device before testing.
  6. Initial testing looks good; the device responds and can be dimmed.
  7. Since this driver provides some of the additional features mentioned in the EvaLogik manual I make the following changes:
    Pulled from Hubitat device logs:
    Hold Dimming Duration(#11) from null to 4
    Push Dimming Duration(#10) from null to 0
    Maximum Brightness(#9) from null to 99
    Minimum Brightness(#8) from null to 1
    Dimming Duration(#7) from null to 5
    LED Indicator(#1) from 0 to 1
  8. I hit Config to update the device.
    Pulled from Hubitat device logs:
    debugHold Dimming Duration(#11) = 4
    debugPush Dimming Duration(#10) = 0
    debugMaximum Brightness(#9) = 99
    debugMinimum Brightness(#8) = 1
    debugDimming Duration(#7) = 5
    debugPower Recovery(#6) = 2
    debugAuto On Interval(#4) = 0
    debugAuto Off Interval(#2) = 0
    debugAuto Off Interval(#2) = 0
    debugLED Indicator(#1) = 1
  9. Now the Device indicates its working both by the LED and Hubitat Zwave responses, but No power is sent to the light.
  10. Things I've tried:
    Obviously tried pressing the physical button and changing the Hubitat device's levels with no joy.
    I tried switching to a Generic Zwave Dimmer driver.
    I tried Using the Hubitat User: "Basic Zwave Tool" driver to reset the advanced features to Default via the EvaLogik manual.
    I tried Excluding the Device - Resetting it to Factory and Including it back in with no joy.
    Now I have 2 of these that don't work and 1 new in a box that I don't dare try.
    Any advice is welcome.
2

Did you try running the full parameter scan in the basic zwave tool to see if any other odd parameters got set? I think if you run it without a parameter it just checks 1-250 or something ridiculous, I would edit the code first to make it stop somewhere around 20-30 when you know nothing is higher than that. Might be possible a factory reset is not resetting the parameters, even though it should.

There is also a zwave command you could send it telling it to reset to factory defaults, I can dig that up if you want to try it.

3

Thanks for the quick reply.
I see 255 in the "getParameterReport" section so I'll change that to 20 for the future.
I noticed that the HE debug log showed a change from null to a decimal value. Makes me wonder if that broke it for some reason.
I'll give one of these another go around - manual reset and then read the parameters 0-20

4

My findings and current workaround -

Parameters when no power to lamp but hub indicates On and Off at level 99.
This happened after sending config to device using Hubitat's built-in EVA LOGIK Smart Plug Dimmer driver.

dev:3532022-08-24 04:05:23.202 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 04:05:22.172 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 04:05:21.634 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 04:05:20.699 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 04:05:20.167 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 04:05:19.654 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 04:05:19.127 pm infoConfigurationReport- parameterNumber:11, size:1, value:4
dev:3532022-08-24 04:05:18.637 pm infoConfigurationReport- parameterNumber:10, size:1, value:0
dev:3532022-08-24 04:05:18.146 pm infoConfigurationReport- parameterNumber:9, size:1, value:99
dev:3532022-08-24 04:05:17.621 pm infoConfigurationReport- parameterNumber:8, size:1, value:1
dev:3532022-08-24 04:05:17.119 pm infoConfigurationReport- parameterNumber:7, size:1, value:5
dev:3532022-08-24 04:05:16.618 pm infoConfigurationReport- parameterNumber:6, size:1, value:2
dev:3532022-08-24 04:05:16.117 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 04:05:15.617 pm infoConfigurationReport- parameterNumber:4, size:4, value:0
dev:3532022-08-24 04:05:15.114 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 04:05:14.751 pm infoConfigurationReport- parameterNumber:2, size:4, value:0
dev:3532022-08-24 04:05:14.110 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 04:05:13.609 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 04:05:13.561 pm traceconfigurationGet command(s) sent...

Below are the parameters after manual brightness settings min-max via device button (see Current Workaround)

dev:3532022-08-24 03:58:17.538 pm infoConfigurationReport- parameterNumber:11, size:1, value:4
dev:3532022-08-24 03:58:17.064 pm infoConfigurationReport- parameterNumber:10, size:1, value:0
dev:3532022-08-24 03:58:16.535 pm infoConfigurationReport- parameterNumber:9, size:1, value:99
dev:3532022-08-24 03:58:16.034 pm infoConfigurationReport- parameterNumber:8, size:1, value:41
dev:3532022-08-24 03:58:15.569 pm infoConfigurationReport- parameterNumber:7, size:1, value:5
dev:3532022-08-24 03:58:15.159 pm infoConfigurationReport- parameterNumber:6, size:1, value:2
dev:3532022-08-24 03:58:14.528 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 03:58:14.027 pm infoConfigurationReport- parameterNumber:4, size:4, value:0
dev:3532022-08-24 03:58:13.524 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 03:58:13.048 pm infoConfigurationReport- parameterNumber:2, size:4, value:0
dev:3532022-08-24 03:58:12.689 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 03:58:12.078 pm infoConfigurationReport- parameterNumber:1, size:1, value:1
dev:3532022-08-24 03:58:11.973 pm traceconfigurationGet command(s) sent...

Current Workaround -
Change Driver to Generic Zwave Smart Dimmer (to prevent the built-in EVA LOGIK Smart Plug Dimmer driver from issuing a config).
Follow the Device Manual to manually set the Min and Max brightness - This begins to send power to the lamp where previously there was none.

  1. Set Min with 5 quick clicks of the button (indicator flashes slowly), the lamp will adjust to the min brightness automatically, press and hold button for your Min setting and when found
  2. 5 more quick clicks to set Max lamp will automatically raise to Max, Set as you wish, then
  3. 5 more quick clicks to acknowledge and lamp will run Min - Max then Max - Min and indicator stops flashing
    At this point it works as a generic dimmer.
5

Sounds like the driver is in need of an update if it setting bad parameters. I have the non-dimmer version which uses a different driver and that one works fine.

@support / @bcopeland ??

2 Likes