The sensor is created by the integration, not in the yaml files.
firstof9,
Thank you I will, I will remove the integration and try again.
I just remove everything and redeployed the integration and same issue.
You are using zwave or ozw?
Please enable debugging and report what the log shows on github, we’ll need it for tracking.
Thanks.
It’s in the current update. You need to redo the lovelace to see it. Delete your current lock view and paste in the new lovelace you generated.
LM will “send” the PIN to the lock (or delete it) when the PIN is inside the “schedule window”. If you click enable, and haven’t messed with any of the advanced settings then the PIN should have a window of “always on” and LM will immediately try to send the PIN. Disable the PIN and LM will try to remove it. If you use the advanced settings and limit the PIN to 9am-5pm, then the PIN becomes “active” inside that window of time and LM will ensure the PIN is added during that window. Interesting enough, if you manually wipe all codes from the lock LM will detect PINS that should be in the lock, but aren’t and will attempt to add them.
This is somewhat of a major change we made, because I was always concerned about a PIN that was supposed to be added but failed for some reason. So now LM will always notice a missing PIN, or a PIN that shouldn’t exist and will automatically fix it.
Did you re-submit the integration options again?
Yep, no change there. Do you think the difference in entity name (vs the example in the instructions) for user_code entity might make a difference?
Also, I don’t see that change you mentioned wrt to the PIN synchronized with lock values, I still see this after updating the integration, deleting the old lovelace code, going to the file and re-copying it into my dashboard raw editor:
Did I miss something?
What version of HA is installed?
See this post, and follow the steps to enable debugging for the sensor then post what gets spit out into the log please.
I actually tried following that before, but I don’t see a “logger.set_level” at all in my list. The closest I have is “logbook.log”. Is that the same thing?
No, it should be in your list.
Maybe your advanced mode is off in your profile:
That was my first thought too, but it’s on.
just a wild guess but maybe you removed logger?
try dropping this in your configuration.yaml:
logger:
default: warning
Yeah, I don’t think I removed it - I don’t recall it ever being there. I went ahead and added it back into my configuration.yaml and I see it in my list now.
What version of lock-manager have you installed?
It says v0.0.34 in the info screen.