Yale Assure deadlock not always refreshing ZWave values

Configuration Z-Wave
1

I have a Yale Assure ZWave-enabled deadbolt on a garage door. Most of the time it works really well - I use the Keymaster add-on to auto-lock it and configure PINs, etc., and it’s usually great.
Sometimes though it does not refresh its values back to ZWave, which results in a situation where the lock is open but ZWave thinks it is locked. Not ideal.
If I force a refresh of the device it updates its status, and Keymaster’s lock timeout starts if it is unlcoked. At the moment I have a “every 5 minutes refresh ZWave values for garage door lock” automation - but that is obviously a workaround not a fix.
Anyone having anything similar, or have any ideas?
I am using latest HA, fully updated, with ZWaveJS2MQTT control panel.

One other thing to note, not sure if it’s related. On the ZWaveJS2MQTT Network graph, the garage door lock shows as grey (unconnected). However it is live, active on the ZWave network and controllable. I have tried healing (both individual device and whole network) and that grey status never changes.

2

Interestingly to the second point about greyed out on the map, and again not sure if it’s related to the primary issue:

In debug view in the Control Panel, the device has:

  "neighbors": [
    5,
    6,
    8,
    9,
    11,
    12,
    16,
    21,
    22,
    25,
    26,
    27,
    31,
    35,
    37,
    38,
    43,
    51,
    62
  ],

…which would seem to indicate that it is on the network but he map does not show it as such.

3

No-one have any ideas?
My “check every 5 mins” is working OK - and does not appear to be affecting battery life. Anyone else have any other ideas or suggestions?

It’s no longer showing on the network map as not connected either, which is good news.

alias: 'Security: Refresh Garage Rear Door ZWave'
description: ''
trigger:
  - platform: time_pattern
    minutes: /5
condition: []
action:
  - service: zwave_js.refresh_value
    data:
      entity_id: lock.garage_rear_door_lock
      refresh_all_values: true
mode: single
4

Have you tried healing the network? Mine did this for a week or two after I switched to Home Assistant w/ Zwave2MQTT, but after healing it’s been rock solid.

5

Yes, tried healing, did not make it refresh values any better. I’ve left it with a 5min cycle of zwave_js.refresh_value and that seems to be keeping it current without impacting battery life.