I was on the last 2024.9 version and as soon as I upgraded it to 2024.10.2, my zwave battery operated devices became unavailable (and their state unknown).
This is true at least for all my Fibaro Window Sensors.
After restoring the 2024.9.x backup, it all works fine again, so that’s why I’m relating the upgrade with the issue.
Any clues why this might be happening?
FYI, I’ve been using the ZWave JS UI addon to manage my zwave devices.
I have similar problems, but not the same.
i was on 2024.7 and migrate to the latest version about 2 weeks ago.
after that, several sensors went offline (like yours), I woke them up and re-interviewed them and they went back to work.
however, they are very sluggish, and sometimes they dont update at all!
i think something on the Zwave JS is missing the messages coming to the controller, as when i pass in front of the PIR it resumes the work.
so my impression is that the controller is busy doing something else, miss the message (or in your case the moment the device report) and shows as offline/unavailable.
would be keen to know if there is something to improve or fix it.
the previous version were working fine!
For me all of my Fibaro Smart Implants went nuts… switches on devioces are working fine, analog inputs are also OK, but all alarm/binary sensors are gone. On 6 devices at the same trime. I tried to reinterview, heal, power cycle devices and even Z-Wave stick, restart HA but nothing helped. More over, I even restored to some 2 month old backup (2024.8.x, with older version of Z-Wave JS UI) but also this did not helped, something went really wrong. I’m afraid I’ll need to remove these nodes and add them again… hope this will work.
Did anyone take their chances with 2010.10.3? Is this problem solved?
I upgraded my HA to 2024.10.4 just to find that this problem is still there.
What’s happening here? Will the use of battery based zwave devices be compromised with the installation of newer versions of HA?
“Batteryless?” Are you having problems with battery devices, or mains-powered devices? Is it all devices or some? All entities or some?
All devices are working fine for me on 2024.10.
Perhaps you can post your device diagnostic file for an affected device and specify which entity IDs are not working. Otherwise, there’s not much to go on.
Sorry, I meant battery based devices 
. In my case it’s a bunch of Fibaro door/window sensors.
I’ll edit my comment to fix it.
But anyway, basically all my battery based devices no longer get any meaningful state after upgrading HA version (they get an “unknown” state)
I’m not really sure what could cause an “unknown” state for Z-Wave entities. Maybe some kind of error. “unavailable” would be more explainable.
I’d suggest posting the device diagnostic, then look in the Home Assistant logs for errors. Finally, you can turn on integration debug logs, activate the device, and see what happens.
Well, nevermind, my bad in the end.
I have all my battery powered zwave devices related to door / windows mapped into “proxy sensors” based on templates so that I can refer to the state “open” or “closed” everywhere instead of “on” and “off”.
For some reason, with the 2014.10.x updates, the binary sensor was renamed (it used to be device_name_access_control_window_door_is_open, but now it is just device_name_window_door_is_open without the “access_control” part), thus my sensor template was assigning the “unknown” value all the time.
It is solved now
Sounds like you were using sensor not binary_sensor for the same notification type. The latter have always existed. The former were removed (not renamed) in 2024.10 because they are redundant. Unfortunately this breaking change was not announced.
These binary sensors are already “open” and “close” everywhere except for automations. There’s no need for a “proxy” sensor.