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
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
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.
I’m now on 4.3.7 and still experiencing this problem. I also recently added a Zooz Zwave “Remote Switch” (ZEN34) to my things. It’s successfully included, but pressing the buttons usually don’t generate any events, neither does anything show in the logs:
root@openhab-server:~ # fgrep "zwave:device:5191b78b16:node42" /var/log/openhab/*.log
/var/log/openhab/events.log:2026-01-15 15:37:50.824 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from UNINITIALIZED (HANDLER_MISSING_ERROR): Handler factory not found to UNINITIALIZED (NOT_YET_READY)
/var/log/openhab/events.log:2026-01-15 15:37:55.046 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from UNINITIALIZED (NOT_YET_READY) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
/var/log/openhab/events.log:2026-01-15 15:37:55.291 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
/var/log/openhab/events.log:2026-01-15 15:37:55.292 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
/var/log/openhab/events.log:2026-01-15 15:38:08.898 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
/var/log/openhab/events.log:2026-01-15 15:38:17.905 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE to UNINITIALIZED
/var/log/openhab/events.log:2026-01-15 15:38:17.913 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
/var/log/openhab/events.log:2026-01-15 15:38:57.388 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from UNINITIALIZED (NOT_YET_READY) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
/var/log/openhab/events.log:2026-01-15 15:38:57.630 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
/var/log/openhab/events.log:2026-01-15 15:38:57.631 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
/var/log/openhab/events.log:2026-01-15 15:39:15.501 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
/var/log/openhab/events.log:2026-01-15 15:39:21.768 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE to ONLINE: Node initialising: REQUEST_NIF
/var/log/openhab/events.log:2026-01-15 15:57:19.342 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: REQUEST_NIF to ONLINE: Node initialising: SECURITY_REPORT
/var/log/openhab/events.log:2026-01-15 15:57:19.343 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: SECURITY_REPORT to ONLINE: Node initialising: MANUFACTURER
/var/log/openhab/events.log:2026-01-15 15:57:19.667 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: MANUFACTURER to ONLINE: Node initialising: APP_VERSION
/var/log/openhab/events.log:2026-01-15 15:57:20.005 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: APP_VERSION to ONLINE: Node initialising: DISCOVERY_COMPLETE
/var/log/openhab/events.log:2026-01-15 15:57:20.005 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: DISCOVERY_COMPLETE to ONLINE: Node initialising: VERSION
/var/log/openhab/events.log:2026-01-15 15:57:24.927 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: VERSION to ONLINE: Node initialising: ENDPOINTS
/var/log/openhab/events.log:2026-01-15 15:57:24.930 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: ENDPOINTS to ONLINE: Node initialising: UPDATE_DATABASE
/var/log/openhab/events.log:2026-01-15 15:57:24.930 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: UPDATE_DATABASE to ONLINE: Node initialising: STATIC_VALUES
/var/log/openhab/events.log:2026-01-15 15:58:27.783 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: STATIC_VALUES to ONLINE: Node initialising: ASSOCIATIONS
/var/log/openhab/events.log:2026-01-15 15:58:28.767 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: ASSOCIATIONS to ONLINE: Node initialising: SET_WAKEUP
/var/log/openhab/events.log:2026-01-15 15:58:29.344 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: SET_WAKEUP to ONLINE: Node initialising: SET_ASSOCIATION
/var/log/openhab/events.log:2026-01-15 15:58:29.955 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: SET_ASSOCIATION to ONLINE: Node initialising: SET_LIFELINE
/var/log/openhab/events.log:2026-01-15 15:58:29.956 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: SET_LIFELINE to ONLINE: Node initialising: GET_CONFIGURATION
/var/log/openhab/events.log:2026-01-15 15:58:31.957 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:5191b78b16:node42' changed from ONLINE: Node initialising: GET_CONFIGURATION to ONLINE
I figure this is related to the overall issue that OpenHAB is ignore or dropping incoming events from Zwave devices.
I did manage to capture a TCP dump on the device with the Zwave controller that OpenHAB connect to using rfc2217. The capture was done while I pushed the on and off buttons on the switch: https://download.morante.net/unibia/other/tdpdump.pcap
I can’t make sense of what the actual data is but I can confirm that the even.log file on the OpenHAB server doesn’t show any zwave events for the time period captured.
Generally, this is related ZW network congestion. Setting the ZW binding to debug should help diagnostics. The event log and the OH log info level have no useful diagnostic information for ZW. Outside of OH, if you have a Zniffer, that will show actual ZW radio traffic.
What do I need for a Zwave sniffer? A very long time ago I played around with a Zigbee radio in sniffer mode and hooked it up via serial to my Windows machine and did see ‘stuff’. Is it basically the same thing?
In this case the device is sending a non-sensical message and I don’t see why. Using the Zwave log viewer it is sending all the supported command classes, not a simple basic command.
There is not a lot of documentation in the ZW db about the parameters, but the alternate exclusion parameter (19) looks odd. Maybe when you change the switch locally, it is trying to exclude itself. I’d switch that option and try again. Also may want to review all the parameters in your manual.
I can try to exclude and re-include it and see if it helps, but it’s not just that one item.
It’s multiple items (switches, locks, thermostat) with varying models/vendors.
ZW4009 / GE39354 Smart Toggle Switch
GE 46202 GE Enbrighten Z-Wave Plus Smart Switch.
Honeywell T5 Pro thermostat that doesn’t always update operating state or it’s temperature.
Kwikset Home Connect 620
Kwikset Covert Smart Lock 914C
The only pattern are the items are at one specific location (2 total, separated geographically), but not all the items in that location are having the problem. There’s another location that’s working just fine. (I use an Aeotec Z-Stick Gen5 at each location).
FYI, this did at one point in history work fine. Unfortunately I don’t remember exactly when this all stopped working or what version of OpenHAB I was using at the time.
UPDATE: I just noticed that my Honeywell T5 Pro thermostat somehow ended up reporting as attached to both Z-Wave controllers which is impossible. How did that happen?
I wasn’t suggesting that. Just check the parameter 19 because of the type of message in your log was wrong.
As to the others, I can’t say without seeing the logs with problems. How separate are the locations? Maybe there is interference. The node6 shouldn’t be able to do that
I checked the setting on a light switch that is properly updating and it’s the same. I could try swapping the setting to see what it does, but supposedly, that’s the default setting according to some very limited documentation on the subject.
Oh.. I tried capturing debug events for the thermostat, but generated nothing.
But here’s the log from a different light switch zwave:device:5191b78b16:node20 with a similar problem:
