Add sensor entities for each code slot, which are automatically populated with the text from their corresponding input_text helper.
In this way, the User Name and Code can stay visible in the text helpers, but the sensor can be cleared or populated based on code status options for that particular users. e.g. When support for schedules is added, then the sensor is updated based on the schedule, while the code stays visible in the text helper. The code in the actual lock is then updated to reflect the status of the sensor rather than the status of the text helper.
*This is how Keymaster manages it's codes and is a more robust design.
*This is also how the Keymaster codes with Alarmo blueprint works, by querying codes in corresponding sensors, as they are only present if the code should be otherwise available.
Add sensor entities for each code slot, which are automatically populated with the text from their corresponding input_text helper.
In this way, the User Name and Code can stay visible in the text helpers, but the sensor can be cleared or populated based on code status options for that particular users. e.g. When support for schedules is added, then the sensor is updated based on the schedule, while the code stays visible in the text helper. The code in the actual lock is then updated to reflect the status of the sensor rather than the status of the text helper.
*This is how Keymaster manages it's codes and is a more robust design.
*This is also how the Keymaster codes with Alarmo blueprint works, by querying codes in corresponding sensors, as they are only present if the code should be otherwise available.