@rossko57 the wave zwave works is that it has a polling function. in my experience with a previous zwave controler if a device run out of batteries or became disconnected I got an alert that it was “offline”
so I assumed that the online function of Openhab has to do with some sort of polling/pingin of the device alive status. makes sense?
Polling is an anti-pattern for zwave, consuming limited network bandwidth, and useless for sleeping battery devices. Most traffic is autonomously initiated from the device end.
If you want to put in place your own"failed device" detection, you can.
openHAB cannot guess if a given device should report once a minute or once a week, or only report changes. But you know (or can find out) what you have configured.
Typically polling is not good for battery devices, or mains devices. For battery devices you generally can’t poll them as they are asleep anyway, and in all cases, polling causes a lot of unnecessary traffic and should be kept to a minimum.
Anyway, there is a bug in the binding at the moment about marking devices offline if they don’t report in and this is what you are seeing.