Why would you want to disable those?
what does āreset code slotā do?
Deletes the PIN from the lock, and wipes the slot ācleanā. Basically the āpersonā name and whatever advanced settings you made.
1 Like
next random question: what happens if you try to enable a blank code?
It will fail with a message in HA log stating the code must be at least 4 length.
cool. last question (i think, lol this is so awesome once you get it working but i have a million thoughts that keep popping into my head)ā¦
how do i increase the number of slots? i changed from 10 to 12 and i can see the new yaml files in packages, but i still only have 10 entities in the integration. iāve tried reloading the integration and restarting hass, but neither one has added the two extra entitiesā¦
it does look like the extra two automations are there for each automation, but not the entities.
edit: for that matter, the 10 entities the integration shows donāt match up anyway (i started with slot 3 and my 10 entities go from _1 to _10). also, theyāre all āunavailableā
The code slot sensors are still new and may have a few quirks. You should normally start with slot 1 not slot 3, unless you have an ID brand lock.
i started with 3 because i was worried i might have left a code or two on the lock before i migrated it from vera to HA. i wasnāt sure if starting with 1 would break anything.
am i safe to go back now and change it to start at 1?
Yes itās fine
ok, cool.
am i safe to just ignore the missing slot sensors for now? what do they do (or i guess what are they supposed to do)?
I suggest factory resetting the lock. Though if you do, remember this turns on the 30 minute auto lock feature.
ok. iāll give that a shot later tonight. once i do that, should i uninstall/reinstall the integration and start over?
also, iām still not clear on what the codeslot entities doā¦
If itās like my case, where there is nothing shown but ********** then it just continuously tries to program the lock non-stop. I didnāt let it run for long, but I canāt image that wonāt drain the battery pretty quickly.
Schlage BE469, seems like the most common lock on here.
Thereās BE469 and BE469ZP (Zwave Plus), I think the ZP model shows the codes causing the automation not to continuously run, and the non-ZP model shows just ********** for the new OZW.
nope thereās no need to do this.
they display the code thatās currently programmed into your lock for that slot
Iāll get this fixed, work has me tied up right now, but disabling the automation should prevent it from spamming your lock for now.
1 Like
this is absolutely perfect, thank you! working much better and doesnāt crash my UIā¦
Donāt worry, we will fix that soon. Iām waiting for some code before I make my updates.
1 Like
v.0.0.31 is out. Just a few updates to make sure your codes are always updated in the lock. I suggest you rebuild your lovelace. Just delete your current lock view and paste the new lovelace (after you generate it by opening options and pressing submit) at the end of the raw configuration. There are a few debug sensors to show you the code in the lock and the synchronization status.
1 Like
Version 0.0.31
Changes
- Add
zwavesupport for code slots (needs testing) - Increased the refresh interval from 10 seconds to 5 seconds
Bug Fixes
- Ignore "*"s in code slots
Maintenance
- Removed unused import