I use the same Zooz stick as @Bruce_Osborne, and it’s been very reliable.
I have a BE469 lock as well, and for changing user codes, I’m guessing you’re referring to this post by @5iver:
Once you’ve got your locks set up, each of them will show up in PaperUI, and you’ll be able to change/add/remove codes in the thing configurations. The next time a lock wakes up, it will pick up the changes from openHAB. That’s all you need, unless you want to build in more advanced functions like enabling/disabling guest codes via rules (I haven’t done that).
As noted in the linked post, you have to have the codes in sequential slots; so you can’t have code 1 and code 4, it has to be codes 1 and 2 (and 3 and 4…etc.). Also, you won’t be able to see the existing codes in openHAB, they’ll just display as “2A 2A 2A 2A 2A 2A 2A 2A 2A 2A”. There’s no syntax for entering codes, though. Just type the numbers without spaces (“123456”).
There’s one more thing you should know: older BE469 locks don’t have a channel to report a simple “locked/unlocked” state (I recall reading somewhere that newer locks have the channel, but don’t quote me on that). If you don’t have the channel, you’ll need to set up a rule that interprets the “alarm raw” channel so you know the status of your locks. I managed to do that with help from this post:
I wouldn’t get too concerned about this right now; it’s just something to be aware of when you’re ready to tackle it.