Do you get these five lines at the bottom of the UI Thing page?
If not, it likely hasn’t finished configuration.
How long ago was this device added?
Is the one with the trouble farthest from the controller?
Well, I don’t know why then. Only random idea is to restart OH, then wake device and see. I’m assuming your other fibaro devices are reporting and there is an xml file for all nodes in user data/zwave.
I have these problems too (for years), sadly i found no solution.
Fibaro devices seems to have a problem with the battery status, Motion-Sensor, Door/Window-Sensor…
Some devices have a configuration where you can chose to supress the reporting of the battery level. I do not have Fibaro door sensors so I do not know if this applies here but it might be worthwile to check it.
Additional ideas:
Delete the thing (NOT excluding it from the ZWAVE network, just deleting within OH) and add it again from the Inbox. That ensures that the thing definition is updated according to the information for the device within the binding (in case there was a change since it was included).
Check that the item for the battery channel has the correct type
I can’t help unfortunately, but just want to add that I have a Z-Wave sensor that has always reported 100% (and does so every day according to its timestamp). It’s a relatively cheap Haozee device, and I’ve just assumed that this will always be the case. Lately, it’s also started to randomly report 0 for temperature, before reverting to the actual reading. So, not exactly reliable.
Personally, I think the future is Matter and Thread. We’re already starting to see some Thread devices (including door sensors), but it’s a bit annoying that the Matter standard keeps getting pushed back. Hopefully it launches in early 2022 and we can actually see it in action.