First of all, THANK YOU to all of the folks who built and maintain KeyMaster! Awesome work!
Secondly, I’m still relatively new to HA and the learning curve is getting better after migrating after being on HomeSeer for 14 years. I have a lot to learn!
Next, I reinstalled KeyMaster for two BE469ZP locks after deleting the integration and started over. Much smoother install the second time around. Now, both locks are reporting ‘Entity not found’ on the respective dashboards (see attached)
Clicking on the entity shows ‘binary_sensor.fake’ is missing (attached)
Looking at Repairs (under Settings | System | Repairs) did not show any issues. However, after installing Watchman (thanks to Mostly Chris) shows the entity is missing from the KM common.yaml file (attached)
Watchman can sometimes be fooled by examples in documentation, or usages with templates. The name fake suggests that this is the case here. Just add it to the Watchman ignore list. The other ones too look like that have templates after them, so aren’t real id’s either. In general, if it is in a package I usually ignore it, and only check for things in my own configuration files.
I’m assuming you don’t have a sensor on the door that you’ve got Keymaster pointing at? If you had configured Keymaster with such a sensor then the generated dashboard would not have a binary_sensor.fake there but binary_sensor.your_door_sensor. This is used by Keymaster for when you use the built in auto-lock automations to know if it should actually lock the door or not as it is assumed that the lock is a deadbolt style lock and you don’t want the automation to lock if the door is still open.
