ok it works
Considerations:
I performed the test 6 times.
The first 3 nothing, the 4 found me only one CEN +, 5 and 6 the second does not recognize it.
Hi Michele,
I suggest you do the following:
It’s important to do that during the Scan process:
You should have now a new Thing in PaperUI with 1 channel: button2.
It works for me (in my simulator) and it works for others here (Julian_Divett, see above), so the CEN/CEN+ discovery by activation should work for you as well.
If it does not work all you have to do is set debug level to DEBUG (see README how), repeat the discovery process, send me the openhab.log file via PM.
Bye
M
Hello Massi,
Thanks for a very good job.
The CEN and CEN+ button works and the rules works.
Example:
rule “Volet_Knx_1_Down”
when
Item VoletKnx1D received update “PRESSED”
then
sendCommand(Volet_Knx1, DOWN)
end
rule “Volet_Knx_1_Up”
when
Item VoletKnx1U received update “PRESSED”
then
sendCommand(Volet_Knx1, UP)
end
rule “volet_Knx_1_Stop”
when
Item VoletKnx1D received update “PRESSED_EXT”
or
Item VoletKnx1U received update “PRESSED_EXT”
then
sendCommand(Volet_Knx1, STOP)
end
rule “Volet_Gen_Down”
when
Item VoletKnx2D received update “PRESSED”
then
sendCommand(gRollladen, DOWN)
end
rule “Volet_Gen_Up”
when
Item VoletKnx2U received update “PRESSED”
then
sendCommand(gRollladen, UP)
end
rule “volet_Gen_Stop”
when
Item VoletKnx2U received update “PRESSED_EXT”
or
Item VoletKnx2D received update “PRESSED_EXT”
then
sendCommand(gRollladen, STOP)
end
Very good
Best Regards
Arnaud
@tagada
I suggest you make this change, see link
item changed [from <state>] [to <state>]
other way:
rule "Da CEN 10-02"
when
Item iLR_scenario changed
then
switch(iLR_scenario.state ) {
case "PRESSED": {
}
case "RELEASE": {
}
case "PRESSED_EXT": {
sendCommand(Luce_sala, ON)
}
case "RELEASED_EXT": {
sendCommand(Luce_sala, OFF)
}
}
end
The new version beta9-1 has been released, it should close all the requirements and issues with CEN/CEN+.
Note that there are some changes from the previous beta9 version in the support for CEN/CEN+:
CEN/CEN+ things are now separated:
bus_cen_scenario_controlbus_cenplus_scenario_controlchannels are now named button_X where X is the button number on the Scenario Control device
for discovered things, button channels appear in PaperUI after the first time the corresponding button is activated from the physical device. Refresh the PaperUI/Control page if needed
when creating CEN/CEN+ things using manual/file configuration, use the new buttons config parameter to define a comma-separated list of buttons numbers [0-31] configured for the scenario device, example: buttons=1,2,4
sending commands: PRESSED, RELEASED, etc. will simulate a virtual short/long pressure of the corresponding CEN/CEN+ button, enabling the activation of MH202 scenarios on the BUS from OpenHab
| Channel Type ID (channel ID) | Item Type | Description | Read/Write |
|---|---|---|---|
scenarioButton (button_X) |
String | Events or virtual pressure for CEN/CEN+ scenario buttons: PRESSED, RELEASED, PRESSED_EXT, RELEASED_EXT
|
R/W |
bus_cenplus_scenario_control LR_CENplus_scenario "Living Room CEN+" [ where="212", buttons="1,5,18" ]
String iLR_scenario_btn1 "Scenario Button 1" <network> { channel="openwebnet:bus_cenplus_scenario_control:mybridge:LR_CENplus_scenario:button_1" }
// long pressure on CEN+ button will switch off dimmer
rule "CEN+ dimmer off"
when
Item iLR_scenario_btn1 received update "RELEASED_EXT"
then
sendCommand(iLR_dimmer, OFF)
end
bye,
Massi
Thank you so much
hi massimo,
sorry i can´t get this work, i see the cen/cen+ functionality now first time but if i think right i´m afraid this may be not what i was waiting for.
what i don´t have is a 4-button cenario-control device
i use an mh200n and i wrote a lot of cenarios there.
actually i start this scenarios either with normal physical switches that are coded to send cen/cen+ commands or i even can start them on my mobile with the domotica app.
a cen command consists an “ambient” (0-10), a “pointlight” (0-15) and a button nr (0-99)
a cen+ command consists an “cen-plu” (0-2047), and a button nr (0-31)
for example to switch several lights on i start cen a=2, pl=1, btn=5 and i have to integrate installation niveau (#4#01). best would be a kind of “pushbutton”
can anybody help?
thanks, stefan
Hello,
I report this example of Massimo
.things
Thing bus_cenplus_scenario_control LR_scenario "Scenario " @ "Scena" [ where="21", buttons="1,2,4,5" ]
.items
String iLR_scenario_btn1 "Scenario Button 1" <network> { channel="openwebnet:bus_cenplus_scenario_control:mybridge:LR_scenario:button_1" }
.sitemap
Switch item=iLR_scenario_btn1 label="Scenario (btn1)[]" mappings=[PRESSED="Scenario-1 (PRESSED)", PRESSED_EXT="Scenario-2 (PRESSED_EXT)", RELEASED_EXT="Scenario-2 (RELEASED_EXT)"]
clicking on the buttons as in the animation are sent on the BUS of the virtual command CEN / CEN + equivalent to short pressure (PRESSED) or long press / release (PRESSED_EXT / RELEASED_EXT) of the scenario buttons.
@gozilla01 is correct, the binding beta9-1 now supports sending virtual pressure events on the BUS, replicating what happens when you press CEN/+ physical buttons.
You can do that by sending commands to button channels (for example using OH2 rules), or if you want to use sitemaps and oh2 apps you can define buttons like in the example above.
Activating CEN from PaperUI is more complicated because PaperUI does not support simple pushbuttons (at least not in a simple way).
The only thing you have to pay attention from example above you should change the Thing definition to CEN (and not CEN+).
Try to define it , if it does not work copy here your thing/item/sitemap conf and we will give a look.
Bye
M
thank you both, so obviously i did something wrong because it can´t get it work.
i´ll go on and report when sucessfull 
hi massimo,
now i tried to switch a light on (cen 21, btn 9) and off (cen 21, btn 10). two things that i realized:
if i send command with domotica-app i receive this
2018-12-28 16:35:23.012 [INFO ] [org.openwebnet.OpenGatewayBus$a ] - MON RECEIVED <<<<<<<<<<< *15*09*21#4#01##
2018-12-28 16:35:28.256 [INFO ] [org.openwebnet.OpenGatewayBus$a ] - MON RECEIVED <<<<<<<<<<< *15*10*21#4#01##
if i send command with openhab i receive this:
2018-12-28 16:38:59.771 [INFO ] [g.openwebnet.bus.MyHomeJavaConnector] - COM SENDING ============>>>>>>>>>>>> *15*9*21#4#01##
2018-12-28 16:38:59.843 [INFO ] [g.openwebnet.bus.MyHomeJavaConnector] - COM SENDING ============>>>>>>>>>>>> *15*9*21#4#01##
2018-12-28 16:39:00.368 [DEBUG] [et.handler.OpenWebNetScenarioHandler] - ==OWN:ScenarioHandler== # 21#4#01 sending CEN virtual release...
2018-12-28 16:39:00.372 [INFO ] [g.openwebnet.bus.MyHomeJavaConnector] - COM SENDING ============>>>>>>>>>>>> *15*9#1*21#4#01##
2018-12-28 16:39:05.766 [INFO ] [g.openwebnet.bus.MyHomeJavaConnector] - COM SENDING ============>>>>>>>>>>>> *15*10*21#4#01##
2018-12-28 16:39:05.875 [INFO ] [org.openwebnet.OpenGatewayBus$a ] - MON RECEIVED <<<<<<<<<<< *15*10*21#4#01##
2018-12-28 16:39:06.355 [DEBUG] [et.handler.OpenWebNetScenarioHandler] - ==OWN:ScenarioHandler== # 21#4#01 sending CEN virtual release...
2018-12-28 16:39:06.359 [INFO ] [g.openwebnet.bus.MyHomeJavaConnector] - COM SENDING ============>>>>>>>>>>>> *15*10#1*21#4#01##
2018-12-28 16:39:06.442 [INFO ] [org.openwebnet.OpenGatewayBus$a ] - MON RECEIVED <<<<<<<<<<< *15*10#1*21#4#01##
2018-12-28 16:39:06.654 [DEBUG] [et.handler.OpenWebNetScenarioHandler] - ==OWN:ScenarioHandler== # 21#4#01 updating state to 'RELEASED'...
switching light off that works with both, domotica and openhab. but switching on does only work in domotica, so i suppose it might be the missing “0” at openhab at the button number?
problem with disappearing things:
here is my things (i added the installation-niveau “#4#01” there):
Thing bus_cen_scenario_control AAA_CENNNNN "AAA CEN Light-test" [ where="21#4#01", buttons="9,10" ]
my items:
String iLR_scenario_btn1 "Scenario 1" <network> { channel="openwebnet:bus_cen_scenario_control:MH200N:AAA_CENNNNN:button_9" }
String iLR_scenario_btn2 "Scenario 1" <network> { channel="openwebnet:bus_cen_scenario_control:MH200N:AAA_CENNNNN:button_10" }
as you see the name “AAA_CENNNNN” thats because very often if i change something in my things-file, the entry disappears in paperui/things. i have to give a new name then thing is back again. its enough to add a single letter and the thing is back.
do i something wrong?
best, stefan
How did you configure the .sitemap file?
hi michele,
my sitemaps looks simply:
Switch item=iLR_scenario_btn1 label="Scenario (btn1)" mappings=[PRESSED="Scenario-1 (PRESSED)"]
Switch item=iLR_scenario_btn2 label="Scenario (btn1)" mappings=[PRESSED="Scenario-1 (PRESSED)"]
bye, stefan
CORRECT : it’s a bug. Feel free to file a new issue: it will be corrected in the next release/patch.
Do you have another thing (light?) with the same WHERE address 21#4#01 as the CEN?
Does the log show some error when it happens that the CEN thing disappears ?
Bye
M
thanks michele for opening the issue for me 
massimo, perhaps i did something wrong, i cannot find out why thing disappeared, this does not happen again - everything ok
best, stefan
hello all,
i successfully added contacts now an just want to post a little example for everyone that is interested in:
this is the (manually managed) things-file:
Bridge openwebnet:bus_gateway:myGateway [ host="xx.xx.xx.xx", passwd="?????" ] {
Thing bus_dry_contact_ir LR_contact "LR_contact" @ "contacts" [ where="352" ]
...(further entries)
}
(here i added contact nr 52, don´t forget to prefix a “3” - so it will become “352”)
this is the items-file:
Switch iLR_contact "my contact" { channel="openwebnet:bus_dry_contact_ir:myGateway:LR_contact:sensor" }
this is the sitemap-file (state will only be displayed if contact state = ON):
Text item=iLR_contact label="my contact" labelcolor=["red"] icon="error" visibility=[iLR_contact=="ON"]
and this is an additionally rule file that sends an email when state changes to ON (of course mail has to be configured in folder “services”):
rule "iLR_contact"
when
Item iLR_contact changed to ON
then
sendMail("info@my-emai-address.com","email subject info", "email text")
logInfo("email an info@my-emai-address.com", "text to log")
end
happy new year!
Stefan,
thanks for example.
You reminded me to open a new Topic
I copied your example inside
In the new topic we publish only examples that work perfectly.
good idea michele, thanks
the second idea could be massimo wants to add it to his readme.
This morning I did other tests.
I configured two physical keys
It works well both from physical buttons and from OH
Thing bus_cen_scenario_control AAA_Cena "CEN Licht-test" @ "Cen/CenPlus" [ where="26", buttons="9,10" ]
String iLR_scenario_btn1 "light on" <network> { channel="openwebnet:bus_cen_scenario_control:mybridge:AAA_Cena:button_9" }
String iLR_scenario_btn2 "light off" <network> { channel="openwebnet:bus_cen_scenario_control:mybridge:AAA_Cena:button_10"}
Switch item=iLR_scenario_btn1 label="light on (btn9)" mappings=[PRESSED="Scenario (PRESSED)"]
Switch item=iLR_scenario_btn2 label="light off (btn10)" mappings=[PRESSED="Scenario (PRESSED)"]
rule "sktest"
when
Item iLR_scenario_btn1 changed or
Item iLR_scenario_btn2 changed
then
logInfo("light btn1 test", "success!" )
switch(iLR_scenario_btn1.state ) {
case "PRESSED": {
Luce_sala.sendCommand(ON)
}
}
switch(iLR_scenario_btn2.state ) {
case "PRESSED": {
Luce_sala.sendCommand(OFF)
}
}
end