ISSUE: Migrating from the Z-Wave integration to Z-Wave JS causes lock-manager to spit out Error acquiring node id from entity

[rubin110]

Describe the bug Migrating from the Z-Wave integration to Z-Wave JS causes lock-manager to spit out Error acquiring node id from entity. I included my key from Z-Wave and pasted it into the Z-Wave JS setup. The Schlage deadbolt appeared after a few minutes back into HA. I went through and restored the same entity id as what it was prior to the migration. All my other automation interacting with the lock work just fine. After migration I haven't touched any of the lock-manager prior auto generated automations.

My logs are current spammed with the error Error acquiring node id from entity lock.entry_deadbolt: 'node_id'.

Looking at the entity I don't see anything in the attributes related to node_id and am not sure if that was something exposed previously. None of the other lock entities state node_id either.

When I go to the lock-manager integration and hit the Configure button I can see the configureation is still populated with all the correct information. After clicking the Submit button without editing anything on this panel I get a User input malformed error. None of the fields look to be malformed. Please see screenshot.

Environment (please complete the following information):

• OS: Debian
• Type of device: Intel amd64 full on server
• Home Assistant version: supervisor-2021.04.3 core-2021.5.5
• Hassio/Docker/Core? Hassio
• Component version: 0.0.45

Logs

2021-05-20 13:40:50 ERROR (MainThread) [custom_components.lock-manager.sensor] Error acquiring node id from entity lock.entry_deadbolt: 'node_id'
2021-05-20 13:41:20 ERROR (MainThread) [custom_components.lock-manager.sensor] Error acquiring node id from entity lock.entry_deadbolt: 'node_id'
2021-05-20 13:41:50 ERROR (MainThread) [custom_components.lock-manager.sensor] Error acquiring node id from entity lock.entry_deadbolt: 'node_id'
2021-05-20 13:42:20 ERROR (MainThread) [custom_components.lock-manager.sensor] Error acquiring node id from entity lock.entry_deadbolt: 'node_id'
2021-05-20 13:42:50 ERROR (MainThread) [custom_components.lock-manager.sensor] Error acquiring node id from entity lock.entry_deadbolt: 'node_id'
2021-05-20 13:43:20 ERROR (MainThread) [custom_components.lock-manager.sensor] Error acquiring node id from entity lock.entry_deadbolt: 'node_id'
2021-05-20 13:43:50 ERROR (MainThread) [custom_components.lock-manager.sensor] Error acquiring node id from entity lock.entry_deadbolt: 'node_id'
2021-05-20 13:44:20 ERROR (MainThread) [custom_components.lock-manager.sensor] Error acquiring node id from entity lock.entry_deadbolt: 'node_id'

Screenshots

Additional context

[firstof9]

Select sensor.fake for the code sensor and access control sensor.

[rubin110]

Thanks for the response. I'm not sure where in the wiki sensor.fake is covered.

Those two fields seem to be disabled, or their just drop downs with no additional items in it. I can see the material design circle animation when clicking on it, but nothing else happens. No text cursor or anything like that.

[firstof9]

You need to migrate to KeyMaster

[rubin110]

Sorry I'm having a hard time following. Is lock-manager deprecated and KeyMaster is the new package to use, or is KeyMaster a fork just for Z-Wave JS?

Additionally is there any documentation on the migration path?

Thanks.

[firstof9]

lock-manager was depreciated and removed from HACS, the project was renamed KeyMaster.

There's no migration path, just remove lock-manager and install KeyMaster.

[rubin110]

Ok cool, I didn't see anything posted on the README for this project saying KeyMaster is the new thing.

Other than automations created by lock-manager, is there anything else I need to remove by hand before getting KeyMaster setup? Thanks again.

[firstof9]

There should be yaml files in your packages directory you'll want to nuke.

[rubin110]

Migrated over. Thanks.