4.3.x Stale things, state is not updating

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

Is there a way to force OpenHAB to request a state update from z-wave things?

If you send a myitem.sendCommand("REFRESH") all the Thing items should get updated.

As to the manual operation of a switch, it could be with the device configuration or you may need to update the UI page. There is a refresh button on the items UI page

Seems like that didn’t work or I’m not doing it right?

For example:

openhab> FrontPorch.sendCommand("REFRESH")
FrontPorch.sendCommand(REFRESH)

The OpenHab log doesn’t show any action and the UI didn’t update even after doing a refresh.

Maybe it’s time to look into using MQTT + Zwave? Or maybe that’s more trouble than it’s worth. I’m not sure what to do at this point other than try downgrading to an earlier version of OpenHAB.