Unexpected Sitemap Behaviour: Switch resets itself and gets updated a few seconds later (hue Binding, Video included)

Hi,

i am just tried to setup openhab in an Docker environment on my newly bought unraid server.

Everything is working fine, however i am experience this strange behaviour with Hue connected Items:

  • Platform information:
    • Hardware: x86/16GB Ram/20 GB
    • OS: unraid Server with Linux 4.19.56-Unraid x86_64 Kernel
    • Java Runtime Environment: I think this is included in the Docker Container
    • openHAB version: openhab/openhab:2.5.0.M1-amd64-debian; openhab/openhab:2.4.0-amd64-debian both from https://hub.docker.com/r/openhab/openhab/
  • Issue of the topic: see above
  • Please post configurations (if applicable):
    • Items configuration related to the issue
Switch Wohnzimmer_Leseleuchte "Leseleuchte" { channel="hue:0220:00178827902c:Zigbee_Wohnzimmer_Leseleuchte:brightness" }
  • Sitemap configuration related to the issue
sitemap test label="Test" {
	Frame {
		Switch item=Wohnzimmer_Leseleuchte
	}
}
  • Services configuration related to the issue
Bridge hue:bridge:00178827902c "Bridge: Philips Hue" [ ipAddress="philips-hue", userName="VViZCo1BH3-bAyB4jRHJQvG-39BIJsfR0kWrRtYB" ] {
	0220 Zigbee_Wohnzimmer_Leseleuchte "Zigbee: Wohnzimmer Leseleuchte" @ "Wohnzimmer"                         [ lightId="49" ]
}
  • If logs where generated please post these here using code fences:
2019-10-12 20:37:46.749 [ome.event.ItemCommandEvent] - Item 'Wohnzimmer_Leseleuchte' received command OFF
2019-10-12 20:37:46.750 [nt.ItemStatePredictedEvent] - Wohnzimmer_Leseleuchte predicted to become ON
2019-10-12 20:37:49.094 [vent.ItemStateChangedEvent] - Wohnzimmer_Leseleuchte changed from ON to OFF
2019-10-12 20:40:44.545 [ome.event.ItemCommandEvent] - Item 'Wohnzimmer_Leseleuchte' received command ON
2019-10-12 20:40:44.546 [nt.ItemStatePredictedEvent] - Wohnzimmer_Leseleuchte predicted to become OFF
2019-10-12 20:40:56.570 [vent.ItemStateChangedEvent] - Wohnzimmer_Leseleuchte changed from OFF to ON
2019-10-12 20:41:22.961 [ome.event.ItemCommandEvent] - Item 'Wohnzimmer_Leseleuchte' received command OFF
2019-10-12 20:41:22.961 [nt.ItemStatePredictedEvent] - Wohnzimmer_Leseleuchte predicted to become ON
2019-10-12 20:41:26.670 [vent.ItemStateChangedEvent] - Wohnzimmer_Leseleuchte changed from ON to OFF
2019-10-12 20:41:30.146 [ome.event.ItemCommandEvent] - Item 'Wohnzimmer_Leseleuchte' received command ON
2019-10-12 20:41:30.147 [nt.ItemStatePredictedEvent] - Wohnzimmer_Leseleuchte predicted to become OFF
2019-10-12 20:41:36.698 [vent.ItemStateChangedEvent] - Wohnzimmer_Leseleuchte changed from OFF to ON

Hopefully this is just some dumb mistake i made. I searched for something similar, however i couldn’t find anything at all.

Thanks in advance

Cheers

Andreas

That’s the odd part; autoupdate is messing up the prediction.

Similar story

Hi rossko57,

thanks for the reply! That’s odd if somebody else would got that behaviour i would expect that there will be a lot more fuzz about. This is something i can’t explain to my family and friends.

I just tried to fixed the issue with autoupdate=“false”

Switch Wohnzimmer_Leseleuchte "Leseleuchte" { channel="hue:0220:00178827902c:Zigbee_Wohnzimmer_Leseleuchte:brightness", autoupdate="false" }
   

This fixes the unexpected behaviour. So thanks for you reply, however in my opinion this should either be fixed by the binding or from the autoupdate function. Should i open an issue on github?

Thank you

Especially if you recreate the problem, yes.
I think this is most likely something about hue binding (which can override what autoupdate normally does)

I wouldn’t rule out something odd with your config; I don’t use hue, is it usual to link a brightness type channel to a Switch type Item?

I just openend an issue on github for this: