I’m facing a serious issue with CEN+ button rules in OpenHAB. Here’s the situation:
Rules in the Same “Where” Work Fine:
If I create multiple rules triggered by CEN+ buttons from the same “where” address (e.g., 27), all of these rules work perfectly without any issues.
Problem Starts with a Different “Where”:
When I create a new rule triggered by a CEN+ button from a different “where” address (e.g., 103), the new rule works fine, but all rules from the previous “where” (27) stop working.
This issue repeats for any new “where” address: rules from the most recent “where” work fine, but all rules from previously configured “where” addresses are no longer triggered.
Manual Execution Works:
If I trigger any of the rules manually from the GUI, they all execute correctly. However, they fail to execute when triggered by the CEN+ buttons.
Additional Information:
I use OpenHAB in a Docker container.
All bindings (DMX, OpenWebNet, Denon Marantz, Spotify) work perfectly when used in HABPanel without any issues.
The problem occurs only when using CEN+ buttons as triggers.
I can send CEN+ commands on the OpenWebNet bus without any issues.
Thank you for your interest in helping me resolve this problem!
You didn’t mention which version of OH you are running. I know there were a number of problems with OpenWebNet binding in 4.3 which I think may have been fixed in 4.3.1. That might be relevant.
Is it possible that the IDs of the buttons are changing?
What ever is happening is in the binding. Maybe putting it into debug level logging will throw some light on the situation.
Thank you for your valuable insights and guidance. I am currently using OpenHAB version 4.3.0, and after carefully analyzing the situation based on your clarification, I was able to identify the root cause of the issue.
Initial Configuration
Initially, I created an object named Cen + General Scenario Control, where all 31 available buttons were configured into a single object.
Revised Configuration
Later, I decided to reorganize the setup for improved structure:
The original object (Cen + General Scenario Control) was reconfigured to use only buttons 1 to 8, instead of the previously assigned 31 buttons.
The remaining buttons were distributed across four additional objects.
Identified Problem
While the frontend (Web UI) correctly displayed the modified object with 8 buttons, the backend (binding?) appeared to retain the original configuration with 31 buttons, even after restarting OpenHAB.
This mismatch between the backend and frontend configurations caused conflicts.
I observed this discrepancy in the Rules Creation interface, where selecting the channel triggered still displayed the original 31 buttons.
Resolution
To resolve the issue, I deleted the original object entirely.
After doing so, the conflicts were resolved, and the system is now functioning as expected.
