search

FutureTense / keymaster

Home Assistant integration for managing Z-Wave enabled locks
MIT License
219 stars 43 forks source link

ERROR: Z-Wave integration not found #239

Closed mrmch closed 2 years ago

mrmch commented 2 years ago

Environment

Logs Seeing this error persistently in my core logs ERROR (MainThread) [custom_components.keymaster.binary_sensor] Z-Wave integration not found

I'm using quite a few Z-Wave devices that are working just fine, and I don't seem to be having any issues directly with Keymaster, but this error message persists.

edit - the issue template didn't populate the first time, my bad. I went through creating a new issue to get the template.

firstof9 commented 2 years ago

We have a template for a reason.

firstof9 commented 2 years ago

Does the error persist? I only get it once in a while when startup of HA is being slow.

mrmch commented 2 years ago

It does persist, looks like it's happening multiple times per minute (a sample from my logs):

2021-10-29 14:00:59 ERROR (MainThread) [custom_components.keymaster.binary_sensor] Z-Wave integration not found
2021-10-29 14:03:59 ERROR (MainThread) [custom_components.keymaster.binary_sensor] Z-Wave integration not found
2021-10-29 14:03:59 ERROR (MainThread) [custom_components.keymaster.binary_sensor] Z-Wave integration not found
2021-10-29 14:03:59 ERROR (MainThread) [custom_components.keymaster.binary_sensor] Z-Wave integration not found
2021-10-29 14:06:59 ERROR (MainThread) [custom_components.keymaster.binary_sensor] Z-Wave integration not found
2021-10-29 14:06:59 ERROR (MainThread) [custom_components.keymaster.binary_sensor] Z-Wave integration not found
2021-10-29 14:06:59 ERROR (MainThread) [custom_components.keymaster.binary_sensor] Z-Wave integration not found
firstof9 commented 2 years ago

What does your binary_sensor.<doorname>_network sensor say on or off?

mrmch commented 2 years ago

It's reading unavailable, with these state attributes (from the dev tools):

restored: true
supported_features: 0
device_class: connectivity
friendly_name: 'frontdoor: Network'

The lock & entities are responsive to commands / from the dashboard...

firstof9 commented 2 years ago

Unavailable status means the network isn't detected. Are you using the zwavejs integration or using mqtt with discovery?

mrmch commented 2 years ago

Thanks for following up, I am using mqtt with discovery.

firstof9 commented 2 years ago

That method isn't supported.

mrmch commented 2 years ago

Well that would explain it. I must have missed that when I migrated to zwave js. I'll close the ticket.