The problem appears to be with zwave devices, though I’m not sure since I don’t have much in the way of other bindings besides zwave.
Ever since upgrading to 4.3.x the status/state of ‘things’ is stale or takes very long to reflect. Unless a direct action is taken. For example, if I manually turn on a switch, OpenHAB doesn’t have awareness of it being “ON”. I don’t see the event show up in the event log. Yet, I can still control the same switch just fine through OpenHAB and it’s status updates accordingly.
If I do the same to some other random zwave item, it works fine. I can come back later to the same switch that wasn’t working earlier and it will all of a sudden be fine.
Basically what I am trying to say is that there is no specific zwave ‘thing’ that’s problematic. There’s not identifiable pattern as to why sometimes it works and sometimes it doesn’t. A thermostat for example will not show the correct current temperature nor it’s operating status. As soon as I control it, the status updates.
I use rfc2217 to connect to the zwave controllers over LAN
Nothing has changed other than updating to 4.3.x (currently on 4.3.3).
Was working without any trouble in 4.2.x