[BTicino/OpenWebNet] Adding CEN commands: design

[massi (Massimo)]

@bastler

the “string” is what you already used in thermo for “mode”. do you
think it is possible to offer both variations as youd did in thermo?

@bastler I do not think it’s feasible to have both approaches, would make the CEN Thing too much complicated because it would mean to have at least 6 channels for each CEN button.

@Julian_Divett

Massi I don’t understand what you mean by having “no_action”. According to the Openwebnet documentation these are the types of press:

@Julian_Divett I mean that each Channel in OH has always a state, so a channel associated with a CEN button must probably have one of the 4 types of press or not_pressed state when the button is not pressed.
One then must work on OH rules or BTicino rules to associate the 4 press interactions with some rule execution/scenario.

@Julian_Divett

I’m still new to Openhab 2 but I guess we are talking about channels for each of these frames?

That is the first design option in my first message, but the more complex to handle and implement.

Regarding states:

@Julian_Divett

CEN+ just sends a frame so you need to capture that - you can’t query the state, there may be a way to store it somewhere in the bus but I’m not aware of one. That’s why you really need to use rules where you can store the state if needed.

CEN/CEN+ may not have states, but in OH2 every channel/item must have a state, always.
So in option 2 I am proposing to have a String channel for each CEN button that can have 5 possible states:

1. short_press
2. start_extended_press
3. extended_press
4. release_extended_press
5. no_press

The drowback of this soliution is that in PaperUI/SimpleUI you will never have a simple On/Off or Press button you can operate to activate the associated CEN scenario.

Can you all think about what you would like to get in your UIs and rules with CEN/CEN+ and tell me if the 5-state channel would work ?

Massi