Turn off encryption in the driver.
Only the lock code events are encrypted
How do I turn of encryption in the driver? I could only find a "Enable lockCode encryption" setting in the Device page, but I think that's something else, as that already defaulted to "Off".
Yup off by default. There is nothing else encrypted
Ah, maybe encryption is not the problem then. How do I read a message in the logs like:
dev:52018-10-29 12:03:45.720 warn CommandResponse skipped clusterId:0001, descMap:[raw:catchall: C25D 0001 C4 C4 0040 00 D3EB 00 00 0000 0A 00 0700420A79616C656C6F636B76320400420534322E3035050020FF0600210100000020040100212C01020021B004030020010B00210A000C0020160F002300030000, profileId:C25D, clusterId:0001, clusterInt:1, sourceEndpoint:C4, destinationEndpoint:C4, options:0040, messageType:00, dni:D3EB, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0A, direction:00, data:[07, 00, 42, 0A, 79, 61, 6C, 65, 6C, 6F, 63, 6B, 76, 32, 04, 00, 42, 05, 34, 32, 2E, 30, 35, 05, 00, 20, FF, 06, 00, 21, 01, 00, 00, 00, 20, 04, 01, 00, 21, 2C, 01, 02, 00, 21, B0, 04, 03, 00, 20, 01, 0B, 00, 21, 0A, 00, 0C, 00, 20, 16, 0F, 00, 23, 00, 03, 00, 00]]
I was assuming that the hex data in that message was encrypted, as it doesnt convert to any meaningful text.
Yeah, what you see is the actual hex data from the device. Normally you need to dig into the zigbee spec to decode these, starting with the cluster ID, then the attribute and command, then the payload.
However this particular payload is using a manufacturer specific profile (C25D), not the usual HA (0104) profile, so whatever that payload is (and its huge BTW), only the manufacturer knows.
Given this data is not part of the the zigbee HA profile spec, you can probably safely ignore it.
In the data section of the driver details, what's listed for the manufacturer?
This message is from the YRD256, the one for which I sent you the fingerprint data. So
model:YRD256-TSDB
endpoints.01.manufacturer:Yale:8002:0600
1 Like
Right, you have to excuse me if i forget where i'm at in some of these threads. Not much you can or need to do with that payload since we have no isea what it is.
No problem, thanks for all your help.
I was trying to work out what the message meant because it is continually showing up in the logs, every couple of minutes. So I was concerned if something is wrong, and also if such frequent messaging will deplete the batteries.
Well, it's not going to help, but without more knowledge not much can be done about it.
Thanks Mike. I've contacted Yale support to see if they can give me some more info.
1 Like
I got the codes working i needed to wait for the codes to populate it took a while. All working now 
1 Like
Any updates on this? I'm super impatient to order a bunch of keypad door locks whose codes I can manage through Hubitat =).
Any updates on what specifically?
you can already use locks and handle the codes (add, change, trigger).
Working great with my Yale 210 -zwave lock
Cool! I'm looking at the Yale YRD216, and it says it can do up to 250 codes with a "network module." Does the Hubitat enable this number of codes? Is it possible to make even more unique codes than the manufacturer's spec?
Does the Hubitat support schedules for when codes work or not? Such a helpful community!
Yes
No
Limited scheduling (enable and disable on date time) will be available in the initial release of Lock Code Manager, which will be included in the next platform release.
Weekly periodic scheduling will likely not make the initial release.
1 Like
The codes are stored in the lock. It only has space for 25 codes without a network module. You can completely program and run the lock without ever hooking it up to any hub . The network module just gives you 250 codes, remote control to program, lock, unlock and reporting.
1 Like
I read that if a code is typed in incorrectly 5 times, that the lock disables until a master code is typed in. Is there any way to disable this functionality? Can you set every code to be a master code? Is that a security risk?
Master code is master. No point in duplicating it. There is a mention of 5 wrong code lockout as factory default, implying that there is a way to override it, but there is nothing in the manual. Yale support might be able to help with that.
I'm the owner of the master code and also have my own separate code along with the rest of the family, each having their own. This is good, because they were each told to use a code they would never forget, and they all did a great job with that. If they're locked out, I can use the master code, or even tell them it over the phone if I'm not home.
But as I mentioned in another thread earlier, that's what the August lock on the back door is for 
1 Like
