Battery powered Z-wave devices stuck in "Initializing (Cache)" state when restarting HA

finity, I don’t understand how a binary sensor can reflect the correct state if one of the possible states is “unknown” (such as we would get when HA reboots and the z-wave device is still sleeping).

Mine doesn’t lose the state when I reboot HA even during the startup phases. My binary_sensor always shows the last state and never unknown.

I don’t think that the device being in the “sleeping” state will interfere with the device correctly reporting the binary sensor status. I think that only affects the periodic reporting of ancillary attributes (battery status, etc).

It shouldn’t need to wake up to report a state change in one of its monitored conditions (motion, tilt, lux etc). I have a couple of door sensors that periodically show as sleeping but they still send status updates to HA even in that state. Just as they do even while in “initializing(cacheload)” state.

Hello everybody,
I have same issue with one thermostatic valve from Danfoss. I tried to unmount and placed it closer to UZB stick (Z-wave usb connected in Raspberry). And suddenly it started work. There can be issues that some devices may not support routing. See more info: https://www.vesternet.com/pages/understanding-z-wave-networks-nodes-devices.