Yes, those are the ones to use
Can confirm. 1.12 for all Leviton Dimmers/Switches will bring your Z-Wave mesh to its knees. 1.2 is mandatory as far as I'm concerned. That said, ALL of my Leviton Z-Wave switches (Plus or not) are currently in the unused bin.
I believe that is 1.20 and not 1.2 for the Leviton FW.
1 Like
What is wrong with the Leviton? Nearly every issue I have had is not with the Leviton but the driver or the Hubs?
Awesome thanks!
1 Like
I personally had too many issues with them with over-reporting and freezing to the point where I had to power cycle them by cutting power. My logs were filled with hundreds of entries where it would report a physical press over and over again (verified by the zniffer). This would queue all other events behind it and drag my mesh down. I moved to Lutron and haven't given them a second thought.
YMMV of course.
Had them for 3 years now and never had that issue at all.
Every issue I have come across has been driver related or Hub related.
Dunno... That was my experience and I had a pretty robust Z-Wave mesh (built up because I was trying to get those switches to work better).
I've been very happy with my switch to Lutron, but it was definitely an expensive transition.
1 Like
RE: Firmware Update
I tried two methods for updating the switches, neither seemed to have any effect, the first was using the 'driver' that was apart of the above link. This failed with 'could not find matching firmware', so then I tried using the firmware updater app, I downloaded the hex file from the repo using wget. then uploaded it to my hub, then clicked through the dropdowns to choose a device to upgrade. It gave me a very slow progress bar, it said it completed but upon revisiting the device with the zwavetool driver it did not show the new version number.
So looking at the logs I do see that when i use the FirmwareUpdaterApp I get:
app:23 2021-07-27 02:46:41.381 pm debug FirmwareMdReport(manufacturerId:29, firmwareId:257, checksum:42276, firmwareUpgradable:false, numberOfTargets:0, maxFragmentSize:null, firmwareIds:[], hardwareVersion:null)
1 Like
When using the dirver the logs were
dev:132021-07-27 02:19:28.924 pm infoVersion Report - FirmwareVersion: 1.13, ProtocolVersion: 4.33, HardwareVersion: 255
dev:132021-07-27 02:19:00.033 pm debugConfiguring with commands []
dev:132021-07-27 02:19:00.023 pm debugupdated...
dev:132021-07-27 02:18:21.338 pm debugParsed SwitchMultilevelReport(value:100) to [[name:level, value:100, unit:%], [name:switch, value:on]]
dev:132021-07-27 02:18:20.277 pm debugParsed SwitchBinaryReport(value:255) to [name:switch, value:on]
dev:132021-07-27 02:15:45.269 pm infoVersionReport- applicationVersion:1.13
dev:132021-07-27 02:15:45.268 pm infoVersionReport- zWaveProtocolVersion:4.33
dev:132021-07-27 02:15:12.531 pm debuglocked by:
dev:132021-07-27 02:15:12.517 pm infoNew image was successfully stored in temporary non-volatile memory. The device will now start storing the new image in primary non-volatile memory dedicated to executable code. Then the device will restart itself.
dev:132021-07-27 01:49:55.826 pm infoOK. The device will initiate the firmware update of the target specified in the Firmware Update Meta Data Request Get Command
dev:132021-07-27 01:49:55.448 pm infoOK. The device will initiate the firmware update of the target specified in the Firmware Update Meta Data Request Get Command
dev:132021-07-27 01:49:55.442 pm infoOK. The device will initiate the firmware update of the target specified in the Firmware Update Meta Data Request Get Command
dev:132021-07-27 01:49:53.397 pm infoFirmwareUpdateMd version:2
dev:132021-07-27 01:49:36.642 pm errororg.codehaus.groovy.runtime.InvokerInvocationException: org.apache.http.client.ClientProtocolException (method firmwareStore)
dev:132021-07-27 01:49:35.581 pm infoVersionReport- applicationVersion:1.13
dev:132021-07-27 01:49:35.580 pm infoVersionReport- zWaveProtocolVersion:4.33
dev:132021-07-27 01:49:35.380 pm errororg.codehaus.groovy.runtime.InvokerInvocationException: org.apache.http.client.ClientProtocolException (method firmwareStore)
dev:132021-07-27 01:46:30.791 pm infoVersionReport- applicationVersion:1.13
dev:132021-07-27 01:46:30.789 pm infoVersionReport- zWaveProtocolVersion:4.33
dev:132021-07-27 01:46:08.057 pm debuglocked by:
dev:132021-07-27 01:46:08.037 pm warnUpdate failed to find a valid target
dev:132021-07-27 01:46:07.817 pm infocalculating crc...
dev:132021-07-27 01:46:07.716 pm infofirmware total bytes: 65536
dev:132021-07-27 01:46:07.714 pm infoSorted all the bytes. cleaning up some memory...
dev:132021-07-27 01:45:53.999 pm infoVersionReport- applicationVersion:1.13
dev:132021-07-27 01:45:53.997 pm infoVersionReport- zWaveProtocolVersion:4.33
dev:132021-07-27 01:45:53.878 pm infoFirmwareUpdateMd version:2
dev:132021-07-27 01:42:18.729 pm debuglocked by:
dev:132021-07-27 01:42:18.698 pm warnUpdate failed to find a valid target
dev:132021-07-27 01:42:18.471 pm infocalculating crc...
dev:132021-07-27 01:42:18.270 pm infofirmware total bytes: 65536
dev:132021-07-27 01:42:18.268 pm infoSorted all the bytes. cleaning up some memory...
dev:132021-07-27 01:42:00.263 pm infoVersionReport- applicationVersion:1.13
dev:132021-07-27 01:42:00.262 pm infoVersionReport- zWaveProtocolVersion:4.33
dev:132021-07-27 01:41:59.359 pm infoFirmwareUpdateMd version:2
dev:132021-07-27 01:40:54.186 pm infoVersionReport- applicationVersion:1.13
dev:132021-07-27 01:40:54.184 pm infoVersionReport- zWaveProtocolVersion:4.33`
1 Like
FirmwareID and FW Version are not the same thing.
The FW Version from the driver is correct. 1.13 is a valid FW Version but years old.
The part that worries me is:
"Update failed to find a valid target"
I have updated these with no issues.
Yeah, my concern was the quoted statement. so maybe something else is messed up on the switch.
You may want to call Leviton Tech Support.
IF that is true, they may just send you new devices.
Well things are mostly working as is, just the remotes are not causing the HE status to be updated, I guess can live with that over spending the time on the phone and reinstalling switches.
I still think it's a driver Issue personally.
Maybe the driver guy will respond with some help.
1 Like
Use the built in Device Firmware Updater app from "Add Built-in App" menu. It can be slow. The faster way is to use a secondary controller stick that you should probably have if you have a lot of Z-Wave devices. Even faster is to use the Homeseer software that will update all files from a single prompt (though it is still sequential). The Homeseer software even has the Leviton drivers included in the software.
2 Likes
Thanks for the information.
I did try to use the 'Built-in app', and that seemed to fail as well. maybe there is an issue with how I downloaded or the contents of the firmware from the aforementioned link.
Your Z-Wave mesh can have an impact on success. Try first updating a dimmer that is connected directly to the hub.
