That’s true for ESH/OH2 bindings, which don’t have the ability to dynamically adapt to the types of the items to which their channels are linked. But running an OH1 binding under OH2 should continue to work the same as in OH1, where the binding can determine which type of item it’s updating (or better, inspect what the item’s accepted data and command types are and remain unconcerned with the item type), and generate states that will be accepted by the bound item. I wish ESH/OH2 did not impose this constraint on its native bindings.
