SmartThings Community

[RELEASE] Leviton Decora Z-Wave Plus Dimmers (DZ6HD & DZ1KD)

leviton
dth_lighting
#164

There’s no status in the app on the phone (lightbulb shows it is lit, but the switch is not on and there is no text status. It should say “On or Off” but it is blank). If I push the tile in the app, it did turn the lights on. However, if I press it again, it does not turn it off.
If I go into the app details (pressing the arrow within the tile) and change the dimmer slider, it does work and if I press the off button in there, it does seem to work. However, when I used the dimmer slider, it just sat there with the updating spinning wheel. I had to exit out of it and go back in to turn them off.

The main tile app always indicates a “lit bulb”, regardless of the state and there is no text update next to it.

(Hal) #165

Sounds like you’re using the new SmartThings app. Not that it matters much.

I’ve got two Leviton DZ15S switches and one DZ6HD dimmer.

All three of them randomly give me problems. They will suddenly show as “Disconnected” in the new ST app or will show with the wrong state (showing as “on” when actually off or vice versa).

So far they have continued to work as manual switches and usually work via Alexa commands.

I’m planning to buy the Homeseer Z-flash utility and a Z-wave stick to update the Leviton devices.

I’ve also got 6 Zooz switches and dimmers from @TheSmartestHouse installed plus 3 more waiting for me to have time. The Zooz devices have been flawless but are slated to get scene capabilities in a future update so the Z-flash utility will be needed.

Unfortunately Homeseer’s price for the utility and a stick is $70 right now

#166

Actually, any Z-Wave stick will work fine for OTA updates, and you can use the tool we talk about in the how to article for the upgrades.

If you get the Goodway stick, the cost goes down to $26 (plus shipping if your total order is under $99). Feel free to get in touch with us with any questions!

2 Likes
(Alex Stoev) #167

Guys,

This is my first post here so please be gentle. I wanted to add my 2 cents here because it would be helpful for those of you experiencing the same issues.

I had problems with Leviton switches/dimmers getting offline and then coming back on. I used to exclude them and then reinclude them to solve this but got tired of this and reached out to Leviton support. I strongly recommend you do the same otherwise you need to spend more than $100 (that is Canadian) to get the Homeseer kit which works fine but is expensive due to their crazy S/H. The kit is $50, and the S/H is also $50. 130-140 Canadian bucks is not that much compared to the type of money most of you (including me) spent already but is the principle. Shipping and handling to be more expensive than the product you are buying, really…

I bought only the dongle from a Canadian distributor (PM me if you want their name, but I think everybody buys their Z-Wave devices from them) while the s/w from Homeseer. At least there is no S/H for the s/w. Why spending the money - because I have other non-Leviton devices that I wanted to upgrade the firmware too.

Here is what you need to do if you want Leviton’s help. Call this number – 1-800-824-3005 option 8. Explain to them your situation – switches and dimmers are constantly going offline. They will ask how many. In my case I always had 1-2 at a time offline but once you fix theses, others will go offline. So overall in my case most of my switches/dimmers were acting. That was good enough for them to justify sending me a stick. The way it works is – they (Leviton support) will send you a USB stick and at the same time they will create a separate return label, so this is kind of a loaner. The moment you are done with your f/w upgrade, you are supposed to send the stick back. I don’t know why Leviton are not doing it for everyone that has the issue but that’s a totally different conversation. I know, there is S/H cost but compared to doing RMA for tons of devices this is much better for them.

Bottom line – f/w 1.20 solved my problems. Is it going to solve yours – most probably yes, but you never know. However, it will not cost you anything to get your Leviton devices upgraded to 1.20, well may be couple of hours of your time, but you will not regret it.

#168

Agreed. Bought the stick from Aartech and software from homeseer. 1.20 is so far so good.

#169

I’ve just installed the latest DTH from Jasonxh for my Leviton DZ6HD (question - how do you ‘confirm’ this is the latest - I don’t see any version info in the code itself, just the header info within github saying “Add support for firmware 1.20” and a date of Dec 16 2018. Once you install the code in your own instance, I don’t see any way to know what actual version you are running).

Everything seems to be working pretty well and I appreciate the advanced features. However, I’ve recently built a Smart Lighting routine to turn the light on / off, and it works ‘most of the time’; but I can observe numerous failures. It seems the failures correspond to the following entries in the Live Log within the API:

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:57:46 PM: **debug** Parsed BasicReport(value: 255) to null

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:57:46 PM: **debug** Bad dimming level 255

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:57:45 PM: **debug** Parsed SwitchMultilevelReport(value: 61) to [[name:level, value:61, unit:%, isStateChange:false, displayed:false, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer level is 61%], 2502]

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:57:40 PM: **debug** Parsed BasicReport(value: 255) to null

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:57:40 PM: **debug** Bad dimming level 255

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:57:39 PM: **debug** Parsed BasicReport(value: 61) to [[name:level, value:61, unit:%, isStateChange:false, displayed:false, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer level is 61%], 2502]

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:57:39 PM: **debug** Parsed Hail() to [[name:hail, value:hail, descriptionText:Switch button was pressed, displayed:false, isStateChange:false, linkText:Lights - Kitchen Dimmer], [physicalgraph.device.HubMultiAction@6ae87630](mailto:physicalgraph.device.HubMultiAction@6ae87630)]

The key elements of the log data above are ‘bad dimming level 255’
I also see:

[1013e6e4-5365-4190-b5b0-47993e730f41](https://graph-na04-useast2.api.smartthings.com/ide/logs#1013e6e4-5365-4190-b5b0-47993e730f41) 12:57:38 PM: **debug** Unhandled zwaveEvent: SwitchMultilevelSet(dimmingDuration: 255, value: 0)

(the latter may not be relevant)
A ‘good’ execution of the same button press reveals this in the live log:

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 1:00:31 PM: **debug** Parsed SwitchMultilevelReport(value: 0) to [[name:level, value:0, unit:%, isStateChange:false, displayed:false, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer level is 0%], [name:switch, value:off, isStateChange:false, displayed:false, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer switch is off]]

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 1:00:25 PM: **debug** Parsed SwitchMultilevelReport(value: 0) to [[name:level, value:0, unit:%, isStateChange:false, displayed:false, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer level is 0%], [name:switch, value:off, isStateChange:false, displayed:false, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer switch is off]]

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 1:00:25 PM: **debug** Parsed SwitchBinaryReport(value: 0) to [name:switch, value:off, isStateChange:false, displayed:false, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer switch is off]

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 1:00:25 PM: **debug** Parsed SwitchBinaryReport(value: 0) to [name:switch, value:off, isStateChange:false, displayed:false, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer switch is off]

[871a7aa9-c8fc-4e06-b844-9d7591aee0a5](https://graph-na04-useast2.api.smartthings.com/ide/logs#871a7aa9-c8fc-4e06-b844-9d7591aee0a5) 1:00:25 PM: **debug** sending data to AT

[871a7aa9-c8fc-4e06-b844-9d7591aee0a5](https://graph-na04-useast2.api.smartthings.com/ide/logs#871a7aa9-c8fc-4e06-b844-9d7591aee0a5) 1:00:25 PM: **debug** A sensor event occurred: [name:level, deviceId:ce4481cf-149a-475d-a4c6-7d7a31d4685d, isoDate:2019-05-03T20:00:25.224Z, unit:%, value:0]

[871a7aa9-c8fc-4e06-b844-9d7591aee0a5](https://graph-na04-useast2.api.smartthings.com/ide/logs#871a7aa9-c8fc-4e06-b844-9d7591aee0a5) 1:00:25 PM: **debug** sending data to AT

[871a7aa9-c8fc-4e06-b844-9d7591aee0a5](https://graph-na04-useast2.api.smartthings.com/ide/logs#871a7aa9-c8fc-4e06-b844-9d7591aee0a5) 1:00:25 PM: **debug** A sensor event occurred: [name:switch, deviceId:ce4481cf-149a-475d-a4c6-7d7a31d4685d, isoDate:2019-05-03T20:00:25.224Z, unit:null, value:off]

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 1:00:25 PM: **debug** Parsed BasicReport(value: 0) to [[name:level, value:0, unit:%, isStateChange:true, displayed:true, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer level is 0%], [name:switch, value:off, isStateChange:true, displayed:true, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer switch is off]]

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 1:00:25 PM: **debug** Parsed Hail() to [[name:hail, value:hail, descriptionText:Switch button was pressed, displayed:false, isStateChange:false, linkText:Lights - Kitchen Dimmer], [physicalgraph.device.HubMultiAction@422346a9](mailto:physicalgraph.device.HubMultiAction@422346a9)]

And here is another ‘bad’ execution of the off command:

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:56:55 PM: **debug** Parsed BasicReport(value: 255) to null

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:56:55 PM: **debug** Bad dimming level 255

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:56:53 PM: **debug** Parsed SwitchMultilevelReport(value: 61) to [[name:level, value:61, unit:%, isStateChange:false, displayed:false, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer level is 61%], 2502]

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:56:49 PM: **debug** Parsed BasicReport(value: 255) to null

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:56:49 PM: **debug** Bad dimming level 255

[1013e6e4-5365-4190-b5b0-47993e730f41](https://graph-na04-useast2.api.smartthings.com/ide/logs#1013e6e4-5365-4190-b5b0-47993e730f41) 12:56:48 PM: **debug** Unhandled zwaveEvent: SwitchMultilevelSet(dimmingDuration: 255, value: 255)

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:56:48 PM: **debug** Parsed BasicReport(value: 61) to [[name:level, value:61, unit:%, isStateChange:false, displayed:false, linkText:Lights - Kitchen Dimmer, descriptionText:Lights - Kitchen Dimmer level is 61%], 2502]

[ce4481cf-149a-475d-a4c6-7d7a31d4685d](https://graph-na04-useast2.api.smartthings.com/ide/logs#ce4481cf-149a-475d-a4c6-7d7a31d4685d) 12:56:47 PM: **debug** Parsed Hail() to [[name:hail, value:hail, descriptionText:Switch button was pressed, displayed:false, isStateChange:false, linkText:Lights - Kitchen Dimmer], [physicalgraph.device.HubMultiAction@58e69453](mailto:physicalgraph.device.HubMultiAction@58e69453)]

Several ‘bad dimming level’ messages. Note the value 61 corresponds to (I believe) the current lighting level, and the reference to ‘dimming duration’ of 255 relates to the setting to keep the dimmer level lights on indefinitely (I tried reducing this to 253 for grins, no change to the problem).
Note that I never seem to have an issue with an ‘on’ command, only the off command.

I can toggle the light maybe 20 times, and it will work 15 times but fail 5 times. I always wait a while between presses, too.

I see that my dimmer firmware version is 1.17, and that 1.20 is available. I’m going to separately pursue the updating of the firmware to see if that helps, but I wondered if this problem has any specific resolution?

#170

After a lot more testing and reviewing logs, I can pretty much confirm the root of the issue seems to be the fact the switch is not reporting its current state correctly when on. If I sit there in the ST app on my phone and hit the ‘refresh’ button within the dimmer control, I can see the status go from ‘off’ to ‘on’. Interestingly, the ‘off’ command always correctly turns off the light, and the status in the phone app always correctly shows ‘off’. But when I issue the ‘on’ command, the light comes on but the status in the phone app remains ‘off’. So my toggle app doesn’t have a hope of knowing the correct status, I guess. It DOES know the dimming level - that always goes from 0 to (eg) 48 and back to 0 as I toggle the light, but the on / off status does not change. So I guess, updating the firmware is the next step :frowning:

Still curious why the ‘bad dimmer level 255’ is showing … but maybe not a big deal.

Thanks!

#171

I bit the bullet and ordered the " **HomeSeer Z-Flash Z-Wave Firmware Update Kit" for about $44 with shipping - seems reasonable, despite the fact I object in principle to having to pay for utilities that should reasonably be expected to be part of an ecosystem like SmartThings. I’ll have it in a few days so I’ll report back if my issues are resolved with the new firmware.

1 Like
(Hal) #172

FWIW, updating has resolved issues with my Leviton switches and dimmer

#173

I received the “HomeSeer Z-Flash Z-Wave Firmware Update Kit”. Got lots of emails from HomeSeer but not the crucial one with the license codes; ultimately found in my spam/junk folder (all the unimportant emails from HomeSeer didn’t get marked as junk!). So got the program installed. Followed the instructions and was able to update the firmware on my Leviton Dimmer, and it works great now! So that’s the good news.

The bad news is … I am finding it impossible to remove the HomeSeer Z-Wave Controller; I decided to just ignore it but today I wanted to use the stick+utility again to update firmware on another device, but it is not working and I assume that’s because I’ve partially but not fully removed the device. So - I could really use some help removing the device ‘cleanly’.

It seems there’s a whole world of issues associated with removing devices from Z-Wave networks, and I’ve never had to cross that bridge until now.

The HomeSeer Z-Flash instructions here say (for ‘other’ (non-HomeSeer) systems) “Use the procedure normally required for removing Z-Wave devices to your system. When the system is in exclusion mode, switch to Z-Flash, click the Add To / Remove From Existing System button and wait for the exclusion process to finish. This should only take a moment.”
So this sounds to me like, for SmartThings:

  1. visit the newly added device ‘Z-Wave Controller’ in the SmartThings App on the phone.
  2. Click the ‘configuration’ gear, upper right corner
  3. Choose ‘Remove’.
  4. dialog is presented on phone: remove “Z-Wave Controller”. Are you sure … Please follow the manufacturer’s instructions to remove the Z-Wave device from SmartThings’ - cancel / remove options.

So - the HomeSeer instructions say to follow SmartThings instructions, the SmartThings instructions say to follow the HomeSeer instructions!

Do I choose ‘remove’ in the SmartThings app at this point, or do I switch to Z-Wave Controller and do something there? What’s the exact sequence of events, between Z-Wave utility and the phone app?

  1. If I choose ‘Remove’ as the next step in SmartThings, it says ‘Exclusion Mode ACtive’. At this point, I flip to the HomeSeer utility, and click ‘Add to / remove from Existing System’.
  2. HomeSeer utility says "Starting Add/Remove process, please wait’
  3. SmartThings app has spinning circle, and says "Having difficulty? You may Force Remove this Z-Wave device’.
  4. HomeSeer app eventually says ‘No activity in over 2 minutes - operation cancelled’.
  5. SmartThings continues to offer ‘Force Remove’. So if I try ‘Force Remove’, I see ‘attempting to forcefully remove this device’. If you force remove this device, it may be unable to reconnect your hub until it is excluded by a controller’.
  6. I chose ‘Force Remove’ but after doing so, the app simply sits there with a spinning circle ‘attempting to forcefully remove this device’.

So I’m stuck. I can’t seem to remove it, and I can’t seem to use it to update more devices. Any ideas?!

Update - reading the help associated with the app on the phone, it says "Resetting / excluding the device through the General Z-Wave Device Exclusion process will likely fix these problems … . Here are the steps to perform a General Z-Wave Device Exclusion …
(for Android)

  1. tap the menu
  2. tap the hub
  3. tap Z-Wave Utiities
  4. tap General Device Exclusion
  5. When you see message "Please follow manufacturers instructions to remove the Z-Wave device from My Smartthings’, perform the required exclusion process …

I followed the above steps, and at step 4, it says 'putting your hub into z-wave exclusion mode allows you to remove a previously included device … are you sure … ? I choose ‘Remove’. Phone says ‘Exclusion Mode Active’, with spinning circle. Then I use the HomeSeer Z-Wave utility again, and again click 'add to / remove from '. . utility says 'Starting add/remove process, please wait … ’ Then 'error .The replication Receive response object is null without reporting a normal ending - Replication Receive failed. Done with add/remove process.
Phone continues to say ‘exclusion mode active’ with the spinning circle.

(Hal) #174

All I did to remove the USB z-wave stick was

  1. Shutdown the Z-flash program
  2. Eject the device using Windows taskbar (like removing a USB drive)
  3. Delete the device from SmartThings via the IDE

I had no issues using the stick and software a couple of days later.

#175

Thanks. Is this Windows 10 or other? With a fully functional setup (app running and device plugged in and 'working), I didn’t see any manifestation of the USB device on my task bar (and I’m quite familiar with how that works/looks, and how items get ‘hidden’ and have to be revealed by the ‘up arrow’).

For “Delete the device from SmartThings via the IDE” - in my IDE, I see the device under ‘Devices’, and If I open it, I can see the option to ‘delete’ it. I can certainly try that.

After doing this, in your SmartThings phone App, do you see any manifestation of the device in ‘My Home’ / ‘Things’ ? I had (and still have) ‘Z-Wave Controller’ as a thing at the bottom of the list.

Now, I’m only trying to remove it from SmartThings because the instructions say to do so … it’s not apparent to me why you can’t just leave it there permanently, and just use it again in the future, but all the instructions suggest you need to remove it. And their instructions are to remove it using the app on the phone, not the IDE (I much prefer to use the IDE for things!).

When you wanted to use it again a few days later, did you then go through the whole ‘add a thing’ process, or did it magically just appear once you plugged it into the laptop and ran the Z-Flash utility?

Thanks again!

(Hal) #176

Windows 10, yes. You know, I’m pretty sure I saw it in the devices in the task bar. Maybe I just yanked it.

I used it in SmartThings twice (without deleting) and had to add it each time. Each time it got a new device id. That’s when I decided to just delete it when I was finished.

I had no success updating my three Leviton devices while they were part of the SmartThings network. None of them showed up in the Z-flash scan. I had to take them all out of SmartThings and used the stick as a standalone controller, adding the Levitons to it’s network. Then, of course, resetting them and adding back to SmartThings.

After deleting the “z-wave controller” via the IDE, there is no sign of it in either SmartThings app.

Not sure it matters but I didn’t buy the Homeseer stick, only their Z-flash utility. I got an S2-capable stick from @TheSmartestHouse

#177

The whole ‘exclusion mode’ behavior seems very odd to me, very ‘imprecise’. I like the idea of killing it in the IDE. My only concern is … this ‘stick’ is setting itself up as a secondary controller and I fear that not carefully ‘managing’ it might lead to issues / instability down the road. I haven’t dug into the lower level ‘network’ side of the z-wave, zigbee networks yet and I don’t want to break anything!

After posting yesterday, I gave up on ‘removing’ the device, and simply tried adding it again, and it did add; I ended up with two Z-Wave Controllers in the app. I was able to do another update (Aeon Multisensor). I then deleted one of the controllers in the IDE. I’m debating whether to delete the ‘current’ one or not; I really can’t see why I shouldn’t just leave it there in the app, and then in 2 months when I want to update another device, simply plug it into the laptop and fire up the utility. Why bother deleting it from the app only to have to re-add it later? I fear that deleting controllers may leave ‘remnants’ that come back to bite later :slight_smile:

So FWIW, I was able to update both the leviton dimmer, and an Aeon MultiSensor 6 device, without having to remove from SmartThings. Would be interesting to know why. Since I do have the z-Flash utility, that could be it. With my multisensors, I had to plug them in to get them to show up on the scan (in battery mode, they weren’t seen; I read that this may be the case).

Interestingly, these were the ONLY devices that were seen; I have Aeon Wallmote, various leak sensors, bulbs etc but none of them showed up … but they are mostly battery powered. The light bulbs are mains-powered, though … and they didn’t show up … so who knows.

(Hal) #178

I had that, too. I think I had closed the z-flash utility, when I started it again, I couldn’t figure out how to reconnect so had to add it to SmartThings a second time, resulting in two z-wave controllers.

Two of my three Leviton devices were showing as disconnected (offline in IDE). None of them showed up in the scan done by Z-flash operating as a secondary controller.

The good news is, after the annoying process of resetting the switches, adding to separate Z-flash network, updating, resetting again, and re-adding to SmartThings network, they have functioned perfectly.