With this missing event, the Item states are not updated in, e.g. Habpanel, and rules based on those items do not take effect. This was all working fine for OH2.
At this point, I've managed to reproduce the issue easily from a new install of either 3.0.0 or 3.0.1 with a single Leviton dimmer:
Add Thing (node 34 in the logs), create binding for switch_dimmer channel to new Item (called Office_Main in the logs).
Verify that there are ItemStateChangedEvent when operating the dimmer manually.
Restart openhab docker container.
Toggle the timmer manually from 0-100-0, there are no longer any ItemStateChangedEvent logs. It can still be controlled via z-wave.
Remove and re-add the Item either via the UI or by using a .items file and commenting out, reloading, and then uncommenting the line with the Office_Main definition.
Verify that there are ItemStateChangedEvent when operating the dimmer manually.
Have been discussing this issue for a while on the forums: Missing ItemStateChangedEvent for zwave item defined in item file after upgrade to openhab:3.0.0.
openhab:3.0.1
a0e14d8c4716
)With this missing event, the
Item
states are not updated in, e.g. Habpanel, and rules based on those items do not take effect. This was all working fine for OH2.At this point, I've managed to reproduce the issue easily from a new install of either 3.0.0 or 3.0.1 with a single Leviton dimmer:
Steps to reproduce:
Thing
(node 34 in the logs), create binding forswitch_dimmer
channel to newItem
(calledOffice_Main
in the logs).ItemStateChangedEvent
when operating the dimmer manually.ItemStateChangedEvent
logs. It can still be controlled via z-wave.Item
either via the UI or by using a.items
file and commenting out, reloading, and then uncommenting the line with theOffice_Main
definition.ItemStateChangedEvent
when operating the dimmer manually.Full log (from reboot through to working
ItemStateChangedEvent
: opnehab.log + events.log sorted by time