Lock Code Manager

This.

Basic Zwave tool is just a driver that's a tool that can be used to get/set z-wave parameters on any z-wave device, so you'll change back to the original driver after getting the firmware version. Don't forget to hit "Configure" after changing back to the original.

2 Likes

image
This what I got on my lock

I called Alfred, they were clueless....they said they would look into it and email me back ;-(

I changed the driver....saved it. There is not a 'configure' button in the Alfred device page in HE.

Send email to Support@alfredinc.com

There's a bug in the tool for secure commands, until I fix it can you replace the existing VersionReport method with this one and click get version report again?

def zwaveEvent(hubitat.zwave.commands.versionv1.VersionReport cmd) {
log.debug cmd
log.info "VersionReport- zWaveLibraryType:${zwLibType.find{ it.key == cmd.zWaveLibraryType }.value}"
log.info "VersionReport- zWaveProtocolVersion:${cmd.zWaveProtocolVersion}.${cmd.zWaveProtocolSubVersion}"
log.info "VersionReport- applicationVersion:${cmd.applicationVersion}.${cmd.applicationSubVersion}"
}

???

There should be one in the upper left corner.

[dev:390](http://172.32.31.53/logs#dev390)2020-04-22 02:26:53.409 pm [info](http://172.32.31.53/device/edit/390)VersionReport- applicationVersion:null.null

[dev:390](http://172.32.31.53/logs#dev390)2020-04-22 02:26:53.406 pm [info](http://172.32.31.53/device/edit/390)VersionReport- zWaveProtocolVersion:5.3

[dev:390](http://172.32.31.53/logs#dev390)2020-04-22 02:26:53.403 pm [info](http://172.32.31.53/device/edit/390)VersionReport- zWaveLibraryType:Enhanced Slave

@jonasd1
I need you to do this as well:

Mike - I'm new to the this HE game, please walk me through what you need me to do here. I"m not quite getting it. Is there code in the basic tool driver you posted above that i need to change and add these lines? Sorry for being unclear on this and I appreciate your help.

its OK, I was able to get the version information I needed.

old firmware: zWaveProtocolVersion:5.3
new firmware: zWaveProtocolVersion:6.7

adding/changing and deleting lock codes will only work with the 6.7 and later firmware.
Also peculiar to the db2 only, the initial code read from the device isn't able to read the actual pin codes from the lock, so they will display as code ????
lockCodes : {"1":{"name":"code #1","code":"????"}}

each code will need to be deleted then re-added using the driver prior to use with Hubitat

The DB1 lock correctly sends any existing lock codes when included.

I thought by now that the older firmware modules would have worked through the supply chain by now.
I'll look at updating the driver to detect the older versions and notify the user...

2 Likes

I think this one was purchased from Amazon? Which means it's very likely old stock.

They have a OTA firmware available. Should work with @bcopeland updater?

1 Like

Ok thanks. Interestingly enough, when i changed the driver back to Alfred, 3 users came through. I have no users installed. So sounds like I need to wait on LCM until you finish your work. The lock still works fine so I am happy for that.

I just ran mine and the one I received last week is 5.3. So you're saying that we won't have to reach out to alfred for a swap? I'll check the one I got today when I'm not working this evening.

1 Like

I don't think @mike.maxwell has any current plans to change the Alfred lock driver (he plans to change the basic z-wave tool driver).

The version information you pulled using the current version of the basic z-wave tool driver indicates you have the older z-wave module. You will either have to contact Alfred for a newer z-wave module, or @jeubanks suggests, you may be able to use @bcopeland's firmware update driver to update the firmware on your existing Alfred z-wave module.

1 Like

The lock codes will not work until you have the correct firmware, yes it will read the slots being used, but delete and add won't work.

There isn't any work that I need to do, you will need to contact Alfred and replace the zwave module.
When you receive the new module you will need to exclude the lock from Hubitat, replace the module, then include the lock again...

2 Likes

Possibly, but I have no way of knowing this.

1 Like

OK, they acted like they didn't know what I was talking about when I just called. She said she'd email me back. So if I am understanding correctly I need 6.7?

The updated driver was written for 6.7, I don't know if there were other versions between 5.3 and 6.7, nor do I know it there was anything after 6.7, its likely anything after and including 6.7 would be fine.

2 Likes

let's do it!

1 Like