[SOLVED] Strange item updates after update from 2.4 to 2.5M5

Bridge mqtt:broker:main "Main MQTT broker" @ "MQTT" [ host="localhost", secure=false, username="...", password="...", retainMessages=true ]
{
    Thing topic Zigbee2mqtt_hue_dimmer1 "Zigbee2mqtt.io Philips HUE Dimmer 01" @ "Zigbee" {
        Channels:
            Type number : duration [ stateTopic="zigbee2mqtt/hue_dimmer1",  transformationPattern="JSONPATH:$.duration" ]
            Type number : counter [ stateTopic="zigbee2mqtt/hue_dimmer1",  transformationPattern="JSONPATH:$.counter" ]
            Type number : battery [ stateTopic="zigbee2mqtt/hue_dimmer1", transformationPattern="JSONPATH:$.battery"]
            Type dimmer : dimmer [ stateTopic="zigbee2mqtt/hue_dimmer1", min=0, max=100, step=1, transformationPattern="JS:huewhite2openhab.js" ]
            Type number : linkquality [ stateTopic="zigbee2mqtt/hue_dimmer1",  transformationPattern="JSONPATH:$.linkquality" ]
            Type string : action [ stateTopic="zigbee2mqtt/hue_dimmer1",  transformationPattern="JSONPATH:$.action"]
    }

}

String Hue_Dimmer1_Action { channel="mqtt:topic:main:Zigbee2mqtt_hue_dimmer1:action", autoupdate="false"}

Dimmer Hue_Dimmer1_Brightness <dimmablelight> { channel="mqtt:topic:main:Zigbee2mqtt_hue_dimmer1:dimmer"}

rule "GF_Office_TableLight update"
when
    Item Hue_Dimmer1_Action received update
then
    logInfo("command", "+")
end

This working well in 2.4 but after update to 2.5 rule fires several times, in most cases 6 times )

Log:
2019-11-20 16:14:38.268 [vent.ItemStateChangedEvent] - Hue_Dimmer1_Action changed from off-press to up-press

==> /var/log/openhab2/openhab.log <==

2019-11-20 16:14:38.274 [INFO ] [lipse.smarthome.model.script.command] - +

2019-11-20 16:14:38.276 [INFO ] [lipse.smarthome.model.script.command] - +

2019-11-20 16:14:38.279 [INFO ] [lipse.smarthome.model.script.command] - +

==> /var/log/openhab2/events.log <==

2019-11-20 16:14:38.280 [vent.ItemStateChangedEvent] - Hue_Dimmer1_Brightness changed from 22 to 41

==> /var/log/openhab2/openhab.log <==

2019-11-20 16:14:38.277 [INFO ] [lipse.smarthome.model.script.command] - +

2019-11-20 16:14:38.293 [INFO ] [lipse.smarthome.model.script.command] - +

2019-11-20 16:14:38.298 [INFO ] [lipse.smarthome.model.script.command] - +

I’m sure that only one mqtt payload happend (checks several times). Openhab and server restarted several times. Openhab updated via openhabian-config tool. Hoq I can fix this?

I would start with cleaning the cache and rebooting more than once.

sudo systemctl stop openhab2

sudo openhab-cli clean-cache

sudo reboot

Then check if the problem continues and if reboot again. If this does not work set the binding to DEBUG via the console.

no luck

Make sure you do not have duplicate items and simple mode is turned of in PaperUI.

This checked before post.

:+1: Just making sure…it’s the small things that can get overlooked.:grin:

Have you setting the binding to DEBUG and see if you get any additional info that may help? While in the console verify your items are not duplicated.

event:display show me this
2019-11-20 16:47:46 - smarthome
2019-11-20 16:47:46 - openhab/update/Hue_Dimmer1_Action
2019-11-20 16:47:46 - openhab/update/Hue_Dimmer1_Brightness
2019-11-20 16:47:46 - org/osgi/service/log/LogEntry/LOG_INFO
2019-11-20 16:47:46 - openhab/update/Hue_Dimmer1_Brightness
2019-11-20 16:47:46 - openhab/update/Hue_Dimmer1_Brightness
2019-11-20 16:47:46 - openhab/update/Hue_Dimmer1_Brightness
2019-11-20 16:47:46 - openhab/update/Hue_Dimmer1_Action
2019-11-20 16:47:46 - org/osgi/service/log/LogEntry/LOG_INFO
2019-11-20 16:47:46 - openhab/update/Hue_Dimmer1_Brightness
2019-11-20 16:47:46 - org/osgi/service/log/LogEntry/LOG_INFO

looks strange )

I tries to set log level

log:set DEBUG org.openhab.binding.mqtt
log:get org.openhab.binding.mqtt                                                                                                                                                                         
DEBUG

but no debug messages in log:tail just INFO

Roll back to M4 and see if that helps as M5 was just released in the past day or two. If that does solve the issue then I would open an issue on github.

Yep M4 looks like working well

1 Like

From the command line run apt-cache showpkg openhab2 you should see a list of all the versions you have. If you do not see a complete list then use sudo apt-get update then showpkg again. Select the one you want and use sudo apt-get install openhab2=2.1.0-1 (2.1.0-1 is just example so replace with the version you want).

I’m not the fastest with typing.:laughing:

Like I mentioned M5 was just released so there are bugs to be fixed. You should be fine on M4 but I would file an issue on github so they are aware of this issue.

Please mark the topic solve by clicking the square box that provided the solution.
Thanks