ITADN

Using Protect Option Pre-Populates Entry Field With "undefined"

#1168Opendagwood08 创建于 2026-04-09
wontfixStale
D
dagwood08commented
When I enter a pin from the keypad popup as soon as I hit the first digit the field is populated with "undefined" and the key that I pressed. This worked fine previously. I'm using Version 7.0.1. - type: vertical-stack cards: - type: conditional conditions: - condition: state entity: lock.garage_side_door_deadbolt state: locked card: type: custom:button-card entity: lock.garage_side_door_deadbolt protect: pin: "8319" success_message: Unlocking door... failure_message: Wrong PIN! tap_action: action: call-service service: lock.unlock service_data: entity_id: lock.garage_side_door_deadbolt name: Unlock Side Door Garage icon: mdi:door-closed-lock styles: name: - font-size: 12px - white-space: normal - word-break: break-word - text-align: center icon: - width: 40px card: - padding: 8px - height: 75px - type: conditional Here is an example after I press 8: <img width="326" height="501" alt="Image" src="https://github.com/user-attachments/assets/5c9abcd1-d64e-4dbd-afeb-6e1f8aa0e3c5" /> I would expect the "undefined" to not be there. I've tried this on a Mac using Chrome and also on a Samsung Ultra S11 tablet using Chrome. Mac is using Tahoe 26.4 with Chrome Version 146.0.7680.178 (Official Build) (arm64).
2 条评论