@ptdalen I’ve switched over to the latest OpenZWave config files, but I still cannot get my Schlage BE469 to remove codes using the clear code method. Am I missing anything? Also the one-time feature does not work for me.
When you say latest do you mean you updated the usercode.cpp with the update posted, or do you mean you’re on 1.6? I have not done anything with 1.6 in a long while, it had too many differences and everything did not work correctly.
What is not working with the one time use? So you select enabled, a code it generated, you then turn on the lock(s) you want to use that code. Does the code work, but never clears? Does the code not work at all? Does it clear the input_text (code), turn off the switch, and set the slot back to disabled, but not clear, etc.
Did you set your codes via the lock manager or on the lock itself? I had issues with lock managers until I removed all codes on the lock itself and reset them in the lock manager.
I actually just updated the config. I’ll keep reading through this thread to see if I can find what you’re referencing. I’ll bet the issue with the scheduling has something to do with the clear issue.
I am curious what file you edited to change the node_id, I setup exactly the same lock as you using a more simplified version of the lock package you used but I found I could not send any codes successfully to the lock. Everything appeared to work but the code would not transfer. If I manually set the code in the services area the code got transferred to the lock
Did you manage to get this working?
hey @ptdalen -
Long time no talk. Gave up on the delete door code problem a while ago but recently migrated from a Rpi3 to an IntelNUC and figured I would do a little code cleanup / add some new functionality so here we are again. I’m on a Schlage BE469 Touchscreen Deadbolt and using your door code package.
I just followed this link: https://selfhostedhome.com/home-assistant-z-wave-tips-and-tricks/
I downloaded the config directory from OpenZwave, renamed it to “openzwave_config” put it inside my hassIO config directory and included it in my config file with:
zwave:
config_path: /config/openzwave_config
That’s supposed to let my zwave network use the latest OpenZwave config which supposedly gets delete door code working right? Was I supposed to do anything else besides restart HassiO?
This is (I think) the Zwave log when I try to use the delete door code functionality from the UI. Node19 is my deadbolt.
2019-11-24 09:27:24.743 Detail, Node019, Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x13, 0x02, 0x98, 0x40, 0x3a
2019-11-24 09:27:24.743 Info, Node019, Received SecurityCmd_NonceGet from node 19
2019-11-24 09:27:24.743 Info, NONCES: 0x36, 0x1f, 0x97, 0x8a, 0xfa, 0x41, 0xf5, 0x51
2019-11-24 09:27:24.743 Info, NONCES: 0x5e, 0xd1, 0x2a, 0x18, 0xda, 0xef, 0x23, 0xed
2019-11-24 09:27:24.744 Info, NONCES: 0x04, 0xde, 0xf4, 0xf4, 0xa0, 0x3d, 0x0c, 0xa2
2019-11-24 09:27:24.744 Info, NONCES: 0x47, 0x3e, 0x66, 0x80, 0x77, 0x05, 0x0d, 0xdf
2019-11-24 09:27:24.744 Info, NONCES: 0x48, 0x97, 0x09, 0xcc, 0x77, 0xb5, 0x14, 0xb7
2019-11-24 09:27:24.744 Info, NONCES: 0x08, 0x2f, 0x00, 0x1e, 0x42, 0xa9, 0xf8, 0xa4
2019-11-24 09:27:24.744 Info, NONCES: 0xa6, 0x39, 0x41, 0x1d, 0xff, 0xc2, 0x87, 0x41
2019-11-24 09:27:24.744 Info, NONCES: 0x33, 0xac, 0xb3, 0xbf, 0x55, 0xa8, 0x1f, 0xce
2019-11-24 09:27:24.744 Info, Node019, Sending (Send) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x13, 0x0a, 0x98, 0x80, 0x5e, 0xd1, 0x2a, 0x18, 0xda, 0xef, 0x23, 0xed, 0x05, 0x01, 0xbe:
2019-11-24 09:27:24.753 Detail, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-24 09:27:24.753 Detail, ZW_SEND_DATA delivered to Z-Wave stack
2019-11-24 09:27:24.772 Detail, Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x02, 0xe8
2019-11-24 09:27:24.772 Detail, ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2019-11-24 09:27:24.838 Detail, Node019, Received: 0x01, 0x28, 0x00, 0x04, 0x00, 0x13, 0x22, 0x98, 0x81, 0xd8, 0x91, 0x3d, 0xff, 0xd3, 0x92, 0xcd, 0x69, 0xab, 0x87, 0x97, 0xb7, 0x79, 0x39, 0x0c, 0xff, 0x37, 0xf4, 0x35, 0x14, 0x3a, 0x10, 0x16, 0x5e, 0xc9, 0xea, 0x40, 0x2a, 0xb3, 0xe8, 0x91, 0x62, 0x4b
2019-11-24 09:27:24.838 Info, Raw: 0x98, 0x81, 0xd8, 0x91, 0x3d, 0xff, 0xd3, 0x92, 0xcd, 0x69, 0xab, 0x87, 0x97, 0xb7, 0x79, 0x39, 0x0c, 0xff, 0x37, 0xf4, 0x35, 0x14, 0x3a, 0x10, 0x16, 0x5e, 0xc9, 0xea, 0x40, 0x2a, 0xb3, 0xe8, 0x91, 0x62, 0x4b
2019-11-24 09:27:24.839 Detail, Node019, Decrypted Packet: 0x00, 0x63, 0x03, 0x06, 0x01, 0x2a, 0x2a, 0x2a, 0x2a, 0x2a, 0x2a, 0x2a, 0x2a, 0x2a, 0x2a
2019-11-24 09:27:24.839 Detail,
2019-11-24 09:27:24.839 Info, Node019, User Code Packet is 10
2019-11-24 09:27:24.839 Detail, Node019, Refreshed Value: old value=6e82500, new value=a620cf40, type=raw
2019-11-24 09:27:24.839 Detail, Node019, Changes to this value are not verified
2019-11-24 09:27:24.839 Info, Node019, Received User Code Report from node 19 for User Code 6 (Occupied)
2019-11-24 09:27:24.839 Detail, Node019, Notification: ValueChanged
did you end up figuring out the problem?
I’m hoping this is low-hanging fruit and someone can correct me. I took the ptdalen common_lock_config.yaml, and back_door_lock.yaml, and renamed them to match the schlage lock I have.
I have one error for a template for the back_door that it complains about ([homeassistant.components.template.sensor] Could not render template Back Door, the state is unknown.) but no reference to the code, I checked the template under back_door_lock.yaml and that seems to reference the correct zwave device.
On the main page of HA, I see one big field that says Input Text, and lots of unknown for the codes. I’m guessing this is the error portion I see in the HA logs. Anyone know which field specifically creates the section that allows you to fill in the codes? Guessing I glossed over it somewhere, or I’m referencing it wrong somewhere and haven’t seen my typo.
This happens on restart. I’ve tried to get rid of the error a few times, but never got around to fully clearing the error. After a minute or two the state should change to something other than unknown. Does that happen for you?
Do you have a tab for the lovelace for the locks? Or are you seeing this all on the main page?
All this is on the main page. No extra tab that I can see.
This is the section that should be setting the lock code I assume, which is on the overview tab.
Adding as a separate reply for update.
I’ve since tried following through https://github.com/FutureTense/lock-manager and I’ve now created a ui-lovelace.yaml, and now have a separate tab for a lock. I’ve currently commented out the pdalen integrations (so the two things don’t compete), but ultimately the new tab is simply blank. No errors in the log I can trace or identify besides the web frontend easily consuming 5 gigs of ram on the browser. Will dig more into this tomorrow I suppose.
Is there anything like this for the zigbee schlage locks?
1 Like
Technically the zwave version should work for zigbee as well, as long as the functions are the same lock.set_usercode etc.
Has anyone managed to get this working with zwave js? Since switching to JS, my BE469ZP doesn’t list usercodes as one of its entities so I’m at a bit of a loss.
1 Like