Christoph Weitkamp

@andrewfg Thank you very much for the analysis. I incorporated your suggestions from https://github.com/openhab/openhab-addons/pull/11842#issuecomment-1001633159.

@lolodomo Thanks for your review. I incorporated your suggested changes and pushed a new version.

I'd prefer to see it in milestone 3.3.M1. But in advance we have to merge https://github.com/openhab/openhab-core/pull/2695 too. Maybe @openhab/core-maintainers can take care of that soon.

Both `default` and `defaultValue` are allowed. See https://github.com/openhab/openhab-core/pull/2383 and https://github.com/openhab/openhab-core/pull/2376#discussion_r637870924 for more information. We maybe can check why Swagger definition uses `defaultValue` as example and try to change that.

Yes, that is okay for me. But I would like to agree on a temporarily solution like suggested in #1878. We should maybe hide binding actions having an additional parameters...

I agree. By default - as a temporarily solution in OHC - or by adding the visibility annotation in every add-on. I tend to the first solution because it will...

I tried to find out the behavior in other UIs by looking it's the code of the `ItemUIRegistry`. It looks like the transformation is priorized over state options over there....

This is an UI related issue in OHC. Imo the correct place for a proper implementation has to be done in the `SseItemStatesEventBuilder`.

May I ask you to amend one of those stack traces? We maybe can identify a good place to handle those exceptions and map it to a user-friendly result.

Thanks for looking into this. From my POV we at least need to tweak the REST API to make use of this feature or add a special method for retrieving...