I have a question from development and user point of view and I would like to understand it a little bit more. As I don’t find it necessary to go over github yet and there are no code changes I think it will be easier to go over here. Please correct me if my though process is wrong.
Ultimately we have two kinds of channels in openHAB - a trigger and state one. Main difference is how they work and what they can do. The trigger channels works on event basis and its state can not be read directly from backing device (let say a sunrise, it just happens). State channels retain its own situation and they allow to get back to device and refresh state based on the physical system. We could dive a little bit more into philosophical aspects of this fine separation when devices come into the play, however this separation is there and makes a lot of sense.
Since 2.4 release we have support for profiles which can affect how the trigger and state channel works. Thanks to that framework has additional layer between things and items where it can retain state in case of events and also affect the way how state is processed.
Now, based on review I did there is whole set of trigger profiles which can be used to control the sate (
RawButtonToggleSwitchProfile) of linked item but we have no such thing for state profiles. This forces use of rules for something which is quite basic and available out of the box for simpler (stateless) channels.
While the difference between trigger and state profile from conceptual point of view is clear and quite big I see a big shortage of “toggle” profile (for
OnOffType) for state channels. Same applies to rollershutter (
Shouldn’t we have it?