how do i know if i’m using ozw or zwave? i got the script and startup stuff working by changing to the zwave.network_ready and zwave.network_stop events, but in the zwave config it’s letting me open the ozw log…
when i load the ozw log via the integration page, the first line is this:
2020-10-18 23:46:10.817 Always, OpenZwave Version 1.4.3469 Starting Up
I just did a restart of OZW and watched the OZW control panel through the whole startup process. The *****'s never showed the code. Only time I have seen a code is when setting a code,where as mentioned above, shows for 10-15 seconds and then is replaced with *****'s. A cleared code does show blank though. So at least I know that **** means something is in the slot.
That’s zwave, the old integration. The new is 1.6
This is also my experience.
is there a way to not make the UI freeze other than separating each lock code into a separate panel? i have 10 codes set up but when i have them all on the same panel, the entire UI pretty much crashes any time i try to look at that panel…if i separate them all out into individual panels, then it works (there’s a bit of a pause on load for each one, but it doesn’t crash the entire UI)…
I used this post with the help of button-card custom card and browser_mod integration for popups to create one panel page with pop-up options for each code. It seems to load significantly quicker and hasn’t ever crashed for me.
two additional questions that have come to my mind while playing with this…
what does “reset code slot” do?
when removing (disabling) a code, it actually removes that code from the lock (NOT overwrite it with a random CODE), right?
If you are running the zwave integration, you get a random code, if you’re using ozw (the new zwave hotness) the code actually deletes.
Thus the differences between old code (no longer developed on) and new code (actively developed on).
I’m not a Lovelace guru, so I’m not sure what you mean when you say panels. When you configure lock-manager and specify the settings, including the number of codes it sets up Lovelace code to create a view, which is one of the tabs that goes along the top of the screen. The view is built using two files under custom-components\lock-manager\ named lovelace.head and lovelace.code. You can modify these files to make any changes you want to the view. N.B. If you update to a new version or reinstall lock-manager these files will get overwritten, so make sure you back them up somewhere.
Open both of these files and peek inside. Note the naming convention. Anything in ALL CAPS represents one of the fields in the integration options. If you named your lock frontdoor, when you save your options, the integration will create a file below your packages folder called frontdoor_lovelace and replace every instance of LOCKNAME with frontdoor.
lovelace.head
This file is rather simple. It defines a new view to accept multiple cards, and defines the badges you want displayed across the top of the view.
lovelace.code
This is a little bit trickier. This file represents a single “slot”. If you specified you want 6 code slots, it will add this to your lovelace file 6 times. Note the TEMPLATENUM text. When creating the lovelace, this value is changed to 1,2,3,4,5,6 each time it is added to your lovelace output.
The easiest way to modify your lovelace is to make the changes to your “live” lovelace, and then compare that back to the lovelace.code file. Save the options on the integration again to regenerate the code, or from developer tools run the lock-manager.generate_package service to rebuild your lovelace code. Since it’s an entire view, I suggest deleting the current keypad view with the UI, then opening the raw configuration and pasting the code at the end.
doesn’t that make it horribly insecure on the old version? i mean you’re ending up with random codes that someone could theoretically (however unlikely) guess to unlock the door…
You could just upgrade to ozw and not worry about it 
lol, i’m open to doing that…but i literally just moved all of my stuff from vera over the past few weeks so i was hesitant to do anything else after just finally getting all of that working.
how complicated is it to upgrade?
Not that hard really, there’s a guide in the community guides to try before you buy.
Reminder, if you restart Home Assistant before switching back you’re going to have a bad time.
Make sure you switch back, or remove thezwaveconfiguration from your configuration before restarting.
does that mean if i am testing with the new version installed, if i ever want to just restart HA i need to first switch back first and then restart the container?
Means don’t try to run them both at the same time.
Note there is a migration tool under construction as well.
I surmise once the UI Control Panel is completed the migration tool will be available.
Paste the configuration options settings
sorry, not sure if this is what you were looking for?
I see my name and code retained (even after reinstall of the lock manager) however I do not see any communication with the lock in the OZW event window.
What does your input_boolean.allow_automation_execution state show?
wait, can’t i just use the lock.clear_usercode service? HA exposes this in the dev tools…
edit: nevermind, i see now there are many threads on the issues with this. i’m not at all familiar with MQTT though, so i’m having issues following the guide on this. ugh.
