Switch type in HTTP binding not updating status

[rlkoshak (Rich Koshak)]

@Hundertvolt1

With this, I get the error that it does not know the OnOffType.

Right, I explain that in my reply too.

@Hundertvolt1

…so you can see that the command is actually executed by the switch, the script is triggered, the separate string channel sees the change from off to on, but the switch channel quickly jumps back to UNDEF.

Autoupdate will “predict” the new state of an Item based on a received command and update the Item with that prediction. Later on, when the end device (in this case the web API call) changes the binding updates the Item with the “real” state. When the device reports back new states, it’s a good idea to turn off autoupdate (metadata on the Item). This avoids that flapping.

@Hundertvolt1

I have the impression that something fundamental changed here concerning what OH expects as an input. For OH 3.x I found a lot of examples with the “ON” and “OFF” strings, which I already found unfunctional before, that’s why I came up with the OnOffType… the documentation of OH 4.x is still quite sparse at this point

Not really.

I think the combination of the onValue/offValue and the state transformation is causing problems. When you use those properties, they operate both ways. When you send the command ON it gets converted to {“name”:“TURN_ON_CMD”}. When {“name”:“TURN_ON_CMD”} is returned by the device it gets converted to ON before sending it to the Item, independent of the transform.

I do not know the order of operations either. It looks like it does the transform first and then applies the onValue/offValue and since those don’t match anything returned by the transform it fails and ignores the message.