Instead of switch ON, it does ON, OFF, ON

[rossko57]

@4est

I wonder why this happens:

An explanation

[SOLVED] WeMo Switch - OFF-ON-OFF-ON not OFF-ON?!

The ‘predicted’ comes from openHABs autoupdate feature. This is enabled by default, and can be disabled per individual Item. It listens for commands to that Item and has a guess/prediction about the likely outcome, then updates the Item state accordingly. This is to give a responsive UI when the actual change at the device is going to take some time, or maybe never gets reported back to OH at all. A short time later, probably in response to being sent a command, the device or an intervening…

In your case, the two channels are probably fighting in addition to the usual autoupdate dithering.

expire="10m"
That is a valid configuration by the way, but probably doesn’t do what you expect. 10 minutes after the last command or update, it will set your Item’s state to UNDEF. The binding(s) won’t do anything about sending that to the device.