Open jbell968 opened 2 years ago
Hi @jbell968, could you try to add lock and call:
service: virtual.set_available
data:
entity_id: __name_of_entity__
value: true
Hello,
I have the same problem. The lock is unavailabe at startup. Calling virtual.set_available service as described above works and the lock becomes available. But if I set the config option "initial_availability: true", my config doesn't pass the check config test with the following error: "Invalid config for [lock.virtual]: [initial_availability] is an invalid option for [lock.virtual]. Check: lock.virtual->initial_availability"
Ok, I will check if some breaking change was done to lock.
Fix proposed, my bad. Hi @twrecked, could you check PR, please.
The issue seems to be fixed. The lock is available after restart and adding the option "initial_availability: true" doesn't generate any config errors. Thanks.
I just upgraded Homme Assistant and the virtual lock now shows as unavailable. I tried commenting out the lock in configuration.yaml, restarting, manually deleting the entity, and re-adding to no avail. System info below:
System Health